Updating failed even after wow repair

10-Nov-2017 06:37

The company was completely stubborn about the idiotic start screen with Windows 8, forcing me and others to revert to products like Classic Shell so we could get an efficient experience. But now Microsoft—or factions within the company—want to slowly revert back to Windows 8, and the Anniversary Update was step one.Of course, this is only a suspicion, but the way the company defended the huge page of massive square icons and idiotic full-screen apps obviously reflected a corporate opinion.But Microsoft has barely dodged a bullet with this cavalier upgrade process.I do not see the corporate culture shifting enough to change the methodologies employed for these upgrades. So here is what we can expect, something that could easily happen in the next few years: Instead of a simple reboot issue, a patch goes out that fries the machine dead.That is probably why my recent Windows 10 update worked fine on one but did not "take" properly on my wife's machine, which went into endlessly rebooting.It finally stopped after a while, but now she is afraid to turn off the machine.

We are getting a glimpse into the future if Microsoft persists with forced upgrades; the company needs to rethink its strategy immediately.

Next, press Enter and the Windows Services dialog will appear.

Now scroll down until you see the Windows Update service, right-click on it and choose Stop.

Exactly why this change did not occur on a third machine I do not know.

If Microsoft is going to constantly toy with the UI, then I am fearful.

We are getting a glimpse into the future if Microsoft persists with forced upgrades; the company needs to rethink its strategy immediately.Next, press Enter and the Windows Services dialog will appear.Now scroll down until you see the Windows Update service, right-click on it and choose Stop.Exactly why this change did not occur on a third machine I do not know.If Microsoft is going to constantly toy with the UI, then I am fearful.This article lists the known issues for Visual Studio 2015 Update 3.