[SOLVED] How to answer a thread closed from discussion?

[CrashTester]

I came to Toms looking for an answer, unlike the past I did not find an answer to my problem which was why bios could see my hard drive and windows couldn't. The thread is here.

https://forums.tomshardware.com/thr...-not-in-device-manager.1524311/#post-11134623

I figured it out quickly but could not add to the thread because closed. I found a UEFI setting which disabled SATA power management and allowed my hard drive to get power when booted. Anyone have any ideas how that could be added so the next person might get an additional solution?

 

[DSzymborski]

I came to Toms looking for an answer, unlike the past I did not find an answer to my problem which was why bios could see my hard drive and windows couldn't. The thread is here.

https://forums.tomshardware.com/thr...-not-in-device-manager.1524311/#post-11134623

I figured it out quickly but could not add to the thread because closed. I found a UEFI setting which disabled SATA power management and allowed my hard drive to get power when booted. Anyone have any ideas how that could be added so the next person might get an additional solution?

It's designed this way intentionally. We do not have threads for the purpose of long-term catch-all conversations for vaguely similar problems. People have specific threads for their specific problem and specific hardware. When it was being noticed that the thread was being randomly necroed, it was closed. It will stay closed.