In Windows-speak, an upgrade repair install refers to upgrading a Windows installation to the version that’s already running. This sounds like a waste of time, at first blush. But, consider that this replaces all OS files and device drivers, and rebuilds the registry from scratch. It also leaves user-installed applications in place along with all data files, settings, preferences and so forth. Thus it provides a squeaky-clean new version of the OS. This can be incredibly handy when trying to fix mysterious or difficult Windows problems. In the wake of a problem-plagued release for Insider Preview 17074.1000, MS let go of a new version yesterday. With tongue in cheek, I assert that this build 17074.1002 introduces involuntary upgrade repair install techniques. That’s because it starts completely over with a new version of Win10.
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
Installing this update took nearly 3 hours — and left a Windows.old behind!
WAG*: Why I Think 17074.1002 Introduces Involuntary Upgrade Repair Install
[Note; WAG = wild-a**ed-guess.] Users reported many problems with the initial release, 17074.1000. I think MS just wanted a complete do-over. The original announcement blog post, now kicks off like this:
UPDATE 1/18: Today we have released Windows 10 Insider Preview Build 17074.1002 to Windows Insiders in the Fast ring. This build is the same as the version of Build 17074 released last week with 2 additional fixes. We have fixed the issue causing AMD PCs to become unbootable – which means we have removed the block for AMD PCs we put in place last week. And we also fixed the issue causing certain devices to hang on the boot screen after upgrading if virtualization is enabled in the BIOS.
Outside the two items specifically mentioned — namely unbootable AMD PCs and post-install boot hangs when virtualization is enabled in BIOS/UEFI — others report inaccessible boot devices, issues with network access and activation problems, and more. There’s an emerging consensus that 17074.1000 is one trouble-wracked Insider Preview release, in fact.
My theory is that Microsoft recognized these (and perhaps even other) difficulties. They decided Insiders should start over with a fresh new Windows 10 Insider Preview version. They pushed 17074.1002 out. That’s my story, and I’ll stick to it until something more sensible comes along! I also wish they’d warned us more explicitly that what looks like a small update from 17074.1000 to 17074.1002 is really another full-blown major version upgrade. Sigh.
[Note Added 1/19 4 PM: A note from Woody Leonhard…]
Here’s a great quote on the recent patchpocalypse at Microsoft, straight from Woody at ComputerWorld
With (hundreds of?) thousands of PCs bricked by bad patches this month and (hundreds of?) millions of Windows customers bewildered by the avalanche of patches — we’ve seen bucketloads of patches on Jan. 3, 4, 8, 9, 11, 12, 17 and now Jan. 18 — you have to wonder when it will all straighten out. Best I can tell you is to turn off Automatic Update, and wait for some semblance of sanity to return.