When Windows 10 first appeared, Microsoft said that it’d be the last ever version of Windows. Of course this didn’t mean that it’d remain the same forever, it just meant that Windows 10 would be constantly updated. The latest version of Windows 10 is far removed from the first version and some of the major upgrades might as well have been called Windows 11, Windows 12, and so on. Continuing to call them Windows 10 was just a marketing decision. Microsoft has said that it regards Windows 10 as a service rather than a product. However, this new approach has introduced what many people regard as a big problem – obligatory updates.
Years ago, people seemed generally happy with Windows 7. When Windows 8 appeared, a lot of people took one look at it and said ‘no thanks’. They carried on using Windows 7 and were happy as long as Microsoft continued to provide security and other updates. However, Windows 10 has proved to be a source of trouble by bringing out what are effectively new systems and forcing them on users. In November 2017 Microsoft released the Windows 10 Fall Creators Edition, and many users are angry that this update is virtually being forced on them. Having such a major change foisted on you could be annoying even if it worked properly, but the main problem with this particular new version is that the upgrade keeps failing and retrying in an endless cycle. Doing any useful work becomes virtually impossible, and Microsoft hasn’t seen fit to provide a big, obvious button that says ‘I don’t want this!’
The Windows 10 Upgrade Assistant is a very tenacious program. If you uninstall it, you might think that your problems are over. However, shortly after removing this pesky program the darn thing will reinstall itself whether you like it or not, and the rolling nightmare of huge downloads followed by lengthy upgrade attempts that ultimately fail will start all over again. The odd thing is that the upgrade should work. At the start of the process, the program checks out your computer to make sure that it has enough resources to run the new version of Windows 10. However, the installation of the new version often fails and the system never says exactly why. You could of course conduct an investigation, and start trawling through log files and event logs to look for clues as to what’s gone wrong, but Microsoft has never been very good at producing clear error messages, and you’d probably end up wasting an awful lot of time. Anyway, users should never be forced to do this kind of thing.
After encountering this problem in the field, I’ve now worked out what has to be done to get rid of the Windows 10 Update Assistant so it won’t come back again just a few hours later. A future update from Microsoft could always start the problem off again, but at least for the time being it enables affected computers to be used once more to do useful work. If you’ve been affected by this infuriating problem, please get in touch and I’ll be glad to sort out the problem for you.