Windows 10: Windows 10 Anniversary Update Might Hide Partitions After Install

+1,, It's really hard to say how many really do encounter this issue and the article claiming that "many" are having it makes me wonder where they get the information from. But the way I look at it Softpedia is good for sensational articles that generate more hits than they have fact,, the things that matter. IMO.

 

The issue for me is that people don't choose or control when to get the upgrades to the next build of Windows 10.

Unlike the Get Windows X app, which allowed some control, for Windows 10 Home users this upgrade will just happen one day when mostly they aren't expecting it. I don't think there's a warning or message that now would be a really good time to make a backup, for instance.

If Microsoft are going to upgrade people's machines with no control or warning, then it needs to be 100% reliable (or at least 99.999%). If they offered it as an upgrade which people could choose and prepare for, then the reliability bar could be lower, but they don't.

The fact that it seems to have happened to quite a few people (including a Forum regular) suggests the update isn't reliable enough.

 

finally I fix it, at least it work for me

here's when partition become RAW. I usualy run chkdsk /b






and now it work!







what I do is

1. backup my hdd with WinPE tools... (contain macrium reflect)
2. delete and re creating partition under win 10 1607 (latest update)

Here's Important part

3. Disable driver signing via advanced restart
4. Update Standard sata controller (to AMD Sata Controller)

Hope it help. I'm no longer having disappear HDD issue, everytime I run chkdsk /B

 

I've posted what happened to me in a couple of threads here. That will likely show up as three or so hits in a Google search. If I post the same message on 7 and 8 forums, more hits. Like you say hard to tell for sure how many got hit?

 

But generally speaking we don't have people post that things just work so know how bad this issue really is would be very hard to determine.

 

Bit like Doctors, really. They must think everyone is sick!

But, must say, dropping a terabyte drive with an update is pretty bad, even if it happens to one person. Especially, as David says, you don't really know when the update will happen.

Would really be good to know what caused it. Also glad none (so far) of the people I support have rung saying where has my drive gone*cry

 

The bad fact is that this thing happens. And this is a good reason to skip this update.
To me the only good solution os that microsoft withdraw the anniversary update and prepare a new iso.

It is crazy for me if they want me to install the defective update+fix

I want a good non bugged iso.
Otherwise they lose a customer.
and my next computer will be apple.

 

I've deferred updates on my 2 Windows 10 Pro PCs until this important bug is fixed. I'm amazed this problem wasn't found during the extensive Insider testing programme.

 

Yes, totally agree. I was just showing how it could get exaggerated to look worse than it really is. It still sucks if your one of the few though. I had everything backed up so I just lost some time copying my files back etc.

 

So far I have reading in this forum, there are reports from almost 1 year ago about the problem of accessing Drives. Just now it seems that is affecting more people.

 

I doubt they will pull the ISO, they will just patch it and update the image.

There is no such thing as a bug free operating system, Windows or MAC. There will always be glitches and unexpected's .
They can't possibly test every piece of hardware on the planet and all the combinations there of.
I grant you, this is a bad one to slip through though.

 

+1.. well put. Given an OS has over 50 Million lines of code it's impossible to make it bug free. I suspect we'll get a CU some time soon to address this issue.

 

That is True. And it is also True that it becomes more difficult to track Bugs. What we see is that Windows is growing and growing in Code.
Let´s hope we get a fix soon for this.

 

I bet there will be a fix for this issue in a week or so.

 

Well I don't post much in this thread, but I just Upgraded a friends computer this weekend for him. This computer was on Windows 10 version 1511 and was pretty messed up. It had lots of problems. This was a new upgrade from his Windows 7 Home. I put it back to his Windows 7 Home, repaired and cleaned up his Win 7, then used my Windows 10, 1607 ISO to Upgrade his Win 7 Home back to Windows 10, the 1607 version. Then cleaned it up a little more, then upgraded his computer to the latest build. 14393.51 This computer is now running just fine, has no problems, no partition problems, its a older Dell computer from 2011. I have upgraded my 3 computers all to our latest release of Windows 10 . 2 of these computers are over 10 years old. They have NO Problems. I did not do ANY clean install on these computers. Just the Upgrade using an ISO and I did not use MCT either.

Bottom line, not everyone had problems with the AU process. I've done 4 computers and all are running just Fine. *Smile