Discovered Major Bug!!!

Richard Shank · 06 Dec 2015

DOS stands for Disk Operating system.

At it's heart Windows OS main goal is to maintain Disks and the files on it.
Keep them secure and keep track of them.

Well, I was doing some maintenance today and I turned off my computer, swapped out my backup drive which is the same size and make as the one being backed up. A 4 TB Seagate.

All went well then when I put the original drive back in Windows 10 did not recognize it.
Turned it off again and turned it back on then it said it was the backup drive with all parameters.
Partition size, Drive letter and what not.

Before I went crazy and tried a recovery I right clicked it offline then back online and it was finally recognized.
This is BS at the highest level. I have never encountered this behavior with all the Windows version below 10.

I reported a ways back that Win 10 lost 2 4TB partitions and turned them raw just by changing the drive letter and it took a whole week and some serious software to recover just 99% of it.

Microsoft has serious issues on their hands and someone needs to let them know pronto.

I can't see any organization adopting 10 if it looses partitions out of the blue and being 10 was blatantly forced on users through the autoupdate disguised as a mandatory, MS has seriously cooked their own balls.

alphanumeric · 06 Dec 2015

Windows 10 does not have DOS in it. Windows hasn't had DOS since Windows 95. There is a command prompt but its not DOS.

Ztruker · 06 Dec 2015

I have seen reports of similar problems but never a fix.

All I can think of is the drive was removed before power completely shut of thus corrupting the drive then when it was put back it had problems. Seems unlikely but that is all I can come up with.

I've done a lot of drive swapping at the shop and never ran into this problem so it's not prevelant.
BIOS problem? See if a BIOS update is available.
Weak CMOS battery (CR2032) causing BIOS configuration setup data to be messed up? Replace battery.

Nothing explains your offline/online fix though.

nigelmercier · 06 Dec 2015

Almost certainly a problem in the BIOS, rather than Windows. Did you rescan when swapping?

alphanumeric · 06 Dec 2015

I'm leaning towards it being a BIOS issue to.

Richard Shank · 07 Dec 2015

alphanumeric said:

Windows 10 does not have DOS in it. Windows hasn't had DOS since Windows 95. There is a command prompt but its not DOS.

No one said it does.
Your forgetting Windows 98, Me, NT, bob....
Maybe I should re quote in technical terms.

Windows ITSELF is to maintain the hard drive and not lose your stuff just by turning it on.
That also happened when Windows decides to do a disk check.

Richard Shank · 07 Dec 2015

Ztruker said:

I have seen reports of similar problems but never a fix.

All I can think of is the drive was removed before power completely shut of thus corrupting the drive then when it was put back it had problems. Seems unlikely but that is all I can come up with.

I've done a lot of drive swapping at the shop and never ran into this problem so it's not prevelant.
BIOS problem? See if a BIOS update is available.
Weak CMOS battery (CR2032) causing BIOS configuration setup data to be messed up? Replace battery.

Nothing explains your offline/online fix though.

This has only happened with Windows 10 which could be Windows 10 drivers for my system.
All other systems that used to be on there worked fine.
Believe me I've still got a future proof system with 8 cores and 16 gigs of memory.

alphanumeric · 07 Dec 2015

Richard Shank said:

No one said it does.
Your forgetting Windows 98, Me, NT, bob....
Maybe I should re quote in technical terms.

Windows ITSELF is to maintain the hard drive and not lose your stuff just by turning it on.
That also happened when Windows decides to do a disk check.

Why quote DOS in your first statement then? What does it have to do with your issue and Windows 10?
Windows NT does not have DOS.

Richard Shank · 11 Dec 2015

alphanumeric said:

Why quote DOS in your first statement then? What does it have to do with your issue and Windows 10?
Windows NT does not have DOS.

With the rhetorical questions your neither solving anything or passing along the promise of getting it fixed.

I know this man who is a contractor. He doesn't get a whole lot of business because instead of doing what he's getting paid for he tends to ask "Why do you want to do that" more than doing the actual work. Because I FKNG said so and paying your damn salary that's why.

You will never get anywhere or solve anything if you just want to cause attention to something that has nothing to do with the issue.

Have fun with that.

alphanumeric · 11 Dec 2015

Richard Shank said:

With the rhetorical questions your neither solving anything or passing along the promise of getting it fixed.

I know this man who is a contractor. He doesn't get a whole lot of business because instead of doing what he's getting paid for he tends to ask "Why do you want to do that" more than doing the actual work. Because I FKNG said so and paying your damn salary that's why.

You will never get anywhere or solve anything if you just want to cause attention to something that has nothing to do with the issue.

Have fun with that.

You should take your own advice then, and limit your original question to relevant info. All you did was confuse things with your reference to DOS.

Did you actually shut down the PC? It wasn't by chance in hibernate or sleep mode. If Windows Fast Startup was enabled it may have messed things up for you. The PC goes into a hybrid sleep mode instead of a full shutdown.