Lost "connection" to local drive E:\

johannilzn

Prominent
Dec 12, 2017
3
0
510
So i recently rolled back my windows 10 to a previously working version after a terrible experience with the creators edition 1709. All the problems i had with 1709 got fixed but i lost "connection" to my local hard drive E:\.

I can't find the disk in file explorer, or in disk management. But its visible in BIOS and after running a disk test with Western Digitals Data LifeGuard Diagnostics the disk was working properly without errors, wtf?

I will include some pictures:

2mhfllh.jpg

nmfg3a.jpg

2q355e0.jpg

22yec1.jpg


The disk is connected with a SATA6G cable to my ASUS MAXIMUS VII HERO motherboard, i've tried changing the port but i'm suspecting that it's not where the problem is.


I'm currently running with the windows 1703 update that i rolled back to. Anyone has any experience with this? Feels like i've tried everything, but surely i must have missed something.

/Johan
 
Solution
I honestly don't know why the 1709 update should be causing the problem you're experiencing re not detecting a secondary drive. I'm not a gamer but I've spoken with a number of my gamer friends who have the 1709 update installed and not one has experienced a problem along the lines you have.

I assume you've done a Google search on "problems with the Windows 10 Fall Creators update 1709" to see if anything can be learned from that source. Probably would also be advisable to check with ASUS tech support and hope you can obtain some definitive info from that source. (They were quite responsive in the "old days" but these days it's more of a crapshoot.)
1. Presumably there's data on the 3 TB secondary HDD, right? If so, it would be a wise precautionary move to install the drive as a USB device and see if it's detected in the system that way. If so, it would be good idea to backup the data on that drive with whatever backup strategy you employ.

2. And you've changed the SATA data cable as well, right?, in addition to using one or more other SATA ports on the motherboard.

3. Might be a good idea to reinstall the Intel RST driver. If you do, ensure you install the ASUS version for this MB, not the version on the Intel website.

4. Want to give the 1709 update another shot? We've installed that update on about 7 or 8 systems without any glitches. But if you do, FIRST clone the existing build so that you can easily fall back should the reinstall again fail. (BTW, we're assuming before you installed the update the system functioned fine, without any problems.)

5. And you might want to contact ASUS tech support to see if they can shed any light on the problem you experienced.
 

johannilzn

Prominent
Dec 12, 2017
3
0
510


Hey, thanks for you answer!

I have not replaced the sata cable for the drive, i don't have a spare at the moment but i don't think that the drive would be visible in BIOS and pass the test if the cable was defect. Was the 1709 versions you installed for commercial use? Because the only bad thing i found about it was that it lowered my FPS in games drastically. I will try to reinstall the RST driver.

 

johannilzn

Prominent
Dec 12, 2017
3
0
510
The only way i got the disk working was by installing windows 1709 update again, but now i'm back to my FPS problem. This is ridiculous.

EDIT: So i rolled back to 1703 again just to see if the disk problem would appear again, and yes. 1703 cant find my disk but solves the FPS problem, 1709 can find my disk but i get the FPS problem...
 
I honestly don't know why the 1709 update should be causing the problem you're experiencing re not detecting a secondary drive. I'm not a gamer but I've spoken with a number of my gamer friends who have the 1709 update installed and not one has experienced a problem along the lines you have.

I assume you've done a Google search on "problems with the Windows 10 Fall Creators update 1709" to see if anything can be learned from that source. Probably would also be advisable to check with ASUS tech support and hope you can obtain some definitive info from that source. (They were quite responsive in the "old days" but these days it's more of a crapshoot.)
 
Solution