New
#40
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. :)
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.
Last edited by Slartybart; 19 Aug 2016 at 17:39.
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.