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

Once the fix is found, and verified to work. I would expect it to be rolled into the current ISO and new images put up on the MCT. That way no body else gets caught out by it.

 

I was wondering as to that very point as I only do upgrade installs at this point and thankfully didn't see this problem at all....two machines at home--desktops.

 

It's kind of awe inspiring to realize that Windows has been so large for many years now that there is no single person in the company who understands the whole code base well enough to troubleshoot it successfully 100% of the time, and in addition the hardware & driver variables globally are far too huge for any company to be able to test "every configuration" before a product ships--doing everything that "consumers do" with the software (for the simple reason the customers do things with their software and hardware that doesn't occur to anyone employed in the company!) That's where the value of massive beta testing comes in--like the Insider's Program.

 

It was doing an upgrade that nuked my drive. A clean install after that was fine. My system is about as stock as it gets. No third party menu programs, Window defender, no RAID. Fairly old hardware too. Luck of the draw I guess?

 

I agree with Alphanumeric re people posting problems only.
I updated/upgraded (I'm not sure which) and had no problems whatsoever.

I have a fair mix of SSD's and internal HDD's using Intel and marvel sata ports. My external HDDs were not mounted when I performed the upgrade so no problems there. I have moved my users folder to another drive using the method fully described in the tutorial by Kari on this forum and this also was unaffected by the upgrade. I did take backups prior to upgrading just in case!
The only minor issue was on the system SSD where the upgrade created another hidden recovery partition (WinRE I think) This is only 450 MB or so and is discussed elsewhere on this forum.
I wonder if it was the processes which create this new partition which somehow caused the problem? No evidence to support this statement merely an observation.
I hope the issue is resolved fully and the circumstances which cause this serious error are documented in due course. I just pleased that I was one of the lucky ones and had no issues.

 

There are two reported issues:

• Drive letter not assigned
  Easy fix - Disk Managment > right click partition > change paths and drive letter > add drive letter
  
  
• Raw / Unallocated drive
  This is really bad for people who experience it. Windows prompts for a format
  - DO NOT format the drive
  
  MS is aware of the issue
  
  Two possible solutions (not tested by me)
  
  • Uninstall IDE ATA Controller(s)
    Cold start your machine
    
    The controller(s) should reinstall
    Run Windows Update just in case
    
    
  • Recover partitons with Minitool or EaseUS
    Per rwhite1 in post# 65
    Miniool Partition Wizard - Partition Recovery did no resolve the issue
  I'm wondering if uninstalling IME would also fix it.
  Don't have an Intel box at the moment or a fragged drive so can't test that theory.

 

Not really true. Windows, and most software, is tested in sections. Most testing is one via test scripts. As for the File System issue, this is actually really critical and should have been caught as a show stopper. I worked on the Dos 6.0 DoubleSpace internal beta team. I remember when it was shipped even though we felt it wasn't ready. Folks in marketing felt that the percentage of data loss was low, like 5%. Unfortunately, at that time the install base was 100 million, so we had a very bad problem. Today Windows 10 is over three times that install base and growing. Certain sections of the OS can and should be tested thoroughly. Also, you have teams of developers that work on sections of code. Thus the file system team is not the same of the UI team. Today it's even easier via object oriented programming to manage these projects. These teams either did not do their jobs properly, their code release team dropped the ball, or marketing really hosed things up. Regardless, the core purpose of a computer, and the OS, is to handle data reliably. Otherwise the computer isn't worth anything. Whatever the root cause is, they also need to make sure from an internal process position they fixed the gaps.

 

I didn't get affected but this is pretty lousy from MS. Although it seems to be the trend, poor QA testing. Apple have dropped some pretty shocking bugs in OSX and iOS too. These juggernauts are in too much of a hurry to push out update after update for some kind of bragging rights. I'm sure they know the software isn't always up to scratch. Personally I prefer consolidation and maturing OS but they are trying to pack too much 'new' and 'change'. Old bugs don't all get addressed, new bugs arise, rinse and repeat. It's a shame and it's tough to swallow - I know people enjoy the new builds etc etc but a lot of us don't fancy playing Russian roulette with our expensive machines. Hopefully though MS will see they dropped the ball badly here and as others have alluded will have this sorted/fixed quickly as its serious to probably catch their attention

 

I have 2 desktop and 1 laptop with AMD chipset. I use the Windows 10 Standard SATA driver ver 10.0.14393.0 that came with 1607 upgrade and have no problems with my SSD or HDD. Just curious what SATA drivers are being used on the failing systems.

Jim *Cool

 

The PC I had it happen on, is as follows:

MotherBoard - Asus M4N68T-M V2 µATX Motherboard
Chipset - NVIDIA nForce 630a / GeForce 7025
Processor - AMD Phenom II X4 980 Black Edition Deneb 3.7GHz
Ram - 8GB 4GB X 2 Kingston PC10600 DDR3 1333MHz Memory
Hard Drive - Crucial MX100 256 GB SSD and 1 TB WD Blue SATA

All stock Windows supplied drivers.

 

What SATA driver are you using?

Jim *Cool

 

The stock Windows supplied driver. The ASUS supplied drivers for that motherboard are way out of date. The only driver I update manually is the video driver. The rest I just let Windows handle. Right now I'm still on the stock video driver. I haven't installed any games yet so I haven't bothered to update it.

 

The act of uninstalling / reinstall the SATA drivers might be what clears up the issue as opposed to the driver or driver version.

As funny as it sounds, I wish this issue happened on one of my machines.

Bill

 

I've only ever had two issues with updates:

(1): some would not install via windows update, had to download and 'inplaceupgrade' using downloaded files;

(2) Windows Defender itself updates consistently, but windows update often will not update defender's definitions.

Also< I image my entire drive all partitions off of the machine periodically.

 

I've had the Windows 10 Anniversary Update for 1 week now. This big/useless update caused my screen size to shrink. I had 2 inches around the four sides of my 23" Samsung monitor that were completely empty and unusable. Had to do some deep Googling to find that the only way to "stretch" the screen to make it fill the monitor again, was to manipulate some registry entries. (The regular screen resizing controls on the monitor, or through Windows 10, just couldn't make the screen stretch/expand far enough.)

On another note, all the gripes about the EDGE browser are still there. Can't go back several pages at a time; very few print sizing options; can't do a right-click on a photo or image to print it. Also, Edge no longer gives the option to "Open" a downloaded file without saving/naming it first.

I'm sure glad that Windows-10 was free...or I'd be royally pissed at how simple-minded Microsoft has become.