I’ve been having a problem installing the “Feature update to Windows 10, version 1709” and after ‘Googling’ the problem, found many others are also experiencing similar problems. Try as I might, the update fails every time, both during MS auto updates and manual updates. No actual error code is reported in the Update History – just “Failed to install on (date)”. So, I contacted the ‘Microsoft Answer Desk’ via a chat session. The agent requested direct access to my laptop – which I granted – and I was eventually informed that my laptop was incompatible with this particular update!
I find this incredible since I was virtually forced to accept Windows 10 OS from my original Windows 7 OS, during the time when it was being installed automatically, whether I wanted it or not… Surely, if my laptop was compatible at the time of the OS ‘update’, then future Windows 10 updates should be compatible. The only solution offered was to ‘Hide’ the update so that I was not constantly being plagued by pop-up windows informing me that the update need to be installed… Not really a solution, I’m sure you will agree.
Have you heard of this problem??
I want to be clear: I do not have a solution for this problem.
While the majority of Windows 10 users have upgraded to 1709 (the “Fall Creators Update”) without problems, there are definitely a number of people sharing your pain.
I’ll share a few straws I might grasp at, were I in your shoes. I’ll also share my expectations of this update, and exactly how they’re not being met.
Spoiler: My expectation is that it should just work.
Become a Patron of Ask Leo! and go ad-free!
Straw #1: Microsoft’s “Fix Windows Update issues”
Microsoft has provided a general-purpose troubleshooter at this page: Fix Windows Update issues.
That page will ask a question or two and have you download a troubleshooting tool which, when run, will examine various characteristics of your system and the services that need to work to provide Windows Update.
Once completed, particularly if problems are reported and supposedly fixed, it’s time to give Windows Update a try again.
While assumptions of this sort are dangerous, I’d assume that your technical support person did this with no luck.
Straw #2: Reset Windows Update components
This falls into the category of getting a bigger hammer.
I’ve outlined the steps in the article How Do I Fix Windows Update?
Essentially, it’s a lengthy list of commands you enter into the Windows Command prompt to disable Windows Update, remove any cached data it’s recorded about the state of your system, and then re-enable Windows Update and all its components.
Because it’s a lengthy list of somewhat geeky commands, I strongly recommended you take an image backup immediately prior to embarking on the process.
This is something I can easily see a support technician not attempting, so it might be something that hasn’t been tried on your machine.
Straw #3: Back up, reinstall Windows, then update
This is perhaps the most painful method, but it’s what I would do if the steps above don’t resolve anything.
First, create a complete image backup of your machine. This is to preserve all data and whatever else might be important, because we’re about to erase everything.
Reinstall Windows 10 from scratch. If offered, do not choose to “Keep my files”. We want this to be as clean a reset as possible, and that really does mean starting over from scratch. That’s why we took a backup first.
After the install is complete, run Windows Update and take all available updates. Run Windows Update again, and take all available updates again. Keep repeating this cycle until either of two things happens:
- You successfully installed 1709, and continue repeating the cycle until there are no more updates to install.
- You run into a problem — presumably the same problem that started us down this path.
If you’re successful, congratulations! Now you get to reinstall all your applications from scratch and restore your data from the backup you took (or from other more convenient copies).
If this process failed, however, I’m out of options… at least when it comes to Windows 10.
Last resort: hide or switch
Since the technician mentioned hiding the update, that’s an option if you can do it. It’s disappointing, but it is what it is.
Your other options include reverting to Windows 7 or jumping ship entirely and moving to Linux.
Or just living with the problem. My concern is that I don’t know what other updates — possibly important security updates — you may miss while you’re in this “blocked by 1709” state.
What I would do depends on my expectations for the machine on which this was happening and my own comfort with the alternatives. Linux is no small leap, but it’s one with which I am already comfortable, as I have two machines running it in my basement. I’m also comfortable enough to know that it’s insufficient for my day-to-day work1. Windows 7 would be a better alternative in that case.
Your mileage, as they say, will almost certainly vary.
I was under the impression that the Windows 10 “lifetime guarantee” meant that it would continue to work — updates and all — for the life of the machine on which it was installed. That’s how I recall it being positioned as “the last version of Windows.”
On one hand, it would have made sense.
On the other hand, at some point it was bound to break. Maintaining absolute compatibility with existing hardware would never allow Windows 10 to take advantage of new hardware capabilities we’ve not even heard of yet.
Even then, though, I would expect there to be a clear notice about new requirements, and a much more seamless experience for those machines not meeting the requirements.
It should just work. Unfortunately, for some, it just doesn’t.