Win10 2004 suddenly removed access to multiple external hard drives. In desperate need of help [ cannot find a solution :( ]

Hi,

I just encountered your ChkDsk issue after a Shutdown with Fast Startup turned off..

Everything worked good several times prior.. I was unable to access anything after booting and turning it on.. After a restart and an automatic ChkDsk I was able to access the files normally, but there was a hidden "Found.00" folder that had appeared..

The only thing I can recall doing differently is that on this last occasion I manually powered off the USB 3.0 drive after shutting down the computer.. I am looking into this some more after deleting the contents and reformatting.. This is a new drive with less than 100 hours use that has worked perfectly until now..

It is almost acting like turning off Fast Startup is not deactivating all of the Fast Startup functions..

And then I wasn't alone. I hope your drive is ok and doesn't run into anymore issues! Especially what I've been going through. You shouldn't have to deal with this nonsense. No one should!

Hi,

I was using a spare HDD, so any data loss is not an issue..

I have been unable to repeat the malfunction though.. The only thing I can think that is different is that I deleted the partition and reformatted using the build having problems.. (2004)..

I don't doubt that Windows 10 is behind the problem in some fashion.. At least the new 2004 build anyway..

It is not ChkDsk though for sure.. Something else is happening that is triggering ChkDsk to run..

You are correct that a good number of people are reporting ChkDsk running for no reason.. Again, I do not believe that ChkDsk is the cause of the problem.. It is responding to something happening to the drive caused by something else.. Most people are not even aware of Fast Startup and the issues it can cause..

It is probably by far the biggest cause of most reports of the ChkDsk running.. Simply removing power from your motherboard in any fashion with Fast Startup enabled will likely cause ChkDsk to run on the next boot, and possibly cause irreparable corruption to the drive(s)..

Hey Gentlemen,

So i've been using these past few weeks to work on the recovery files, shifting content around and making new backups. I even backed up the recovery files to be safe, which after what just happened, was the right thing to do. It will, however, require an entire restart of going through all the files again thanks to a repeat performance of Windows 10...

After working on the drive for weeks on Windows 7, I needed to connect it to my Win10 PC again to get some other files transferred over and out. I left my PC running overnight to handle the long transfers. Everything was fine this morning. I ejected and shutdown all my drives and then the PC. a few hours later I turned on my Win10 PC and after logging in, I turned on my external and behold, windows asking me to format one drive and then telling me the other drive is no longer accessible. Thus repeating the same issue I had under 2004 now happens in version 1909.

I can say after all that work on that drive, I am once again **** pissed off at the redundant work I need to do again. The only saving grace is that I don't have to run recoveries again. Just have to waste my time going through recovery files again, renaming and recreating backups.

All I did was turn it on and Windows did something either before I shut down earlier overnight, or the moment the drives were turned on. It's a shame because somehow, a couple weeks ago, windows update went corrupt and disappeared, which I was excited about and no longer have to use sledgehammer. I tried getting it back anyway so I could at least update defender, but of course, nothing worked and I'll assume the only option that will work is an entire reset again. Which now knowing that this issue isn't related to version 2004, or 1909, it's just a general windows 10 issue that will most likely never get resolved.

Just wanted to get this info out feeling it's kinda significant to windows users, rather than the programmers at MS.

And to provide more details - the drives seemed to have been wiped clean by windows and there is nothing on the drives. Even tells me "the Volume does not contain a recognized file system. It was NTFS who knows what it is now. But it doesn't matter since they are both empty and need to be reformatted and never used on windows 10 again.

Hi,

I don't have a clue as to what would be causing that on such a repeated basis..

I thought maybe turning off Fast Startup was for some reason not actually turning off all of it's features..

If this is also happening on 1909, that is even more strange..

After the one time I was able to duplicate your problem, I have not been able to do it again..

I switch my external drives between Win 7 Pro and 10 Pro on a frequent basis and have never encountered something like that.. Very rarely I will need to allow ChkDsk to run, but no issues are found and everything works..

Not only do I do this with USB drives, but SATA as well.. I have run SATA power and data cables to an area outside the computer on a shelf for this purpose..

There may be a problem with Windows 10, but I am thinking there is some kind of an unknown contributing factor as well.. Otherwise I would be having a lot more of these issues, and there would be a lot more of this showing up on the Forums..

I suppose it could even be hardware\driver related in some fashion... I know all the guessing is of little help, but maybe something to think about..

Hi,

I don't have a clue as to what would be causing that on such a repeated basis..

I thought maybe turning off Fast Startup was for some reason not actually turning off all of it's features..

If this is also happening on 1909, that is even more strange..

After the one time I was able to duplicate your problem, I have not been able to do it again..

I switch my external drives between Win 7 Pro and 10 Pro on a frequent basis and have never encountered something like that.. Very rarely I will need to allow ChkDsk to run, but no issues are found and everything works..

Not only do I do this with USB drives, but SATA as well.. I have run SATA power and data cables to an area outside the computer on a shelf for this purpose..

There may be a problem with Windows 10, but I am thinking there is some kind of an unknown contributing factor as well.. Otherwise I would be having a lot more of these issues, and there would be a lot more of this showing up on the Forums..

I suppose it could even be hardware\driver related in some fashion... I know all the guessing is of little help, but maybe something to think about..

It's expected with Win10. Turns out the Drives were changed from NTFS to RAW. Ran a fix I found online through cmd and thankfully both drives are back to NTFS and the data is showing it's there. Was able to fuss with the permissions on one drive and regain access and everything seems to be fine with it. The other drive just finished getting repaired back to NTFS and now I'm going to fuss with the permissions and hope there is no damage.

I decided I'm going to let Windows keep breaking down until I have no other choice but to wipe it clean again. Any recommendations on which version of Windows10 I should reinstall? I'm not a fan of these "features" they keep releasing and I don't need them. I just want to edit my video, play my games and VR, use Plex and, what seems to be impossible, backup and manage data on external drives.