Windows Updates (Again...)

Mick

Well-Known Member
Reaction score
811
Location
Cambridge, UK
I know this subject has been discussed many times here, but...I have a Win 10 Home PC on my bench right now that has been knackered three times in the past few weeks by an attempted install/update to the 'Feature Update version 1709'. (It's currently on 1703) Three times, I've restored it or reset it to get things back to a working edition, but of course, the update just resurfaces after a few days and has another go. It's passing the compatibility test (in theory) but in practice we just keep winding up with a machine that either won't get past the log-in stage or runs like a lame donkey when it does so. Got to be a way of killing this thing off, surely. I've tried DISM, SFC, Windows AIO, ChkDsk, SDI etc and I'm on the verge of just disabling the update service as a last resort, but don't really want to do that if there's another, better way. I've already tried the reghack which tells Windows to treat the Ethernet connection as 'metered' but that doesn't seem to be doing anything (or the user is clicking on 'I accept' buttons without realising what they're doing, which is a strong possibility).

This whole machine is scheduled to be replaced in approx six months or so, so I don't want to spend a whole heap of time and money on it - and neither does the customer - but it needs to work until then. All I want to do is disable this particular update, for good.

Any suggestions?
 
Thanks. I may give that a try, but I was really after just zapping this one particular update. This tool looks like it just disables the update service, which I can do anyway. I'd prefer not to do that because I don't want to miss other, perfectly good, updates.
 
Ensure you have the latest Win 10 from the media creation tool and run the install from within Windows.
It will update the system to the latest release without affecting data or apps.

I've done this successfully on machines where the Win 10 updates keep crapping out.
If this method fails, updates aren't fixable that I have found, reload time.
 
The latest media creation tool is now build 1709 so I don't think that is going to help out if he is wanting to stay on 1703.
 
Thanks all. The updates don't crap out as such - they report completing successfully. It's just the end result that's a mess. Thanks to @trevm999 - I'll give that a whirl.
 
If you want the 'official' method from Microsoft you can find it here. While the article title says it's 'temporary' that just means until you unblock the update with the same tool.


I've had to use this tool quite a lot lately as both September's and October's update rollouts caused issues for a bunch of client systems. Needless to say, MS is pretty far down on my totem pole right now.
 
I do a modified limited tune-up on the balky machine and then do the update to 1709 from my flash drive ISO. I have found that if there are existing problems on the platform that the over-the-top reinstall doesn't always work correctly. By doing the things that would normally be done to tune up and clear problems will usually allow the update to finally work successfully. Here are some of the things I will do (not necessarily in order!):

1. Check for correct date/time. (Windows updates is sensitive to time issues!)
2. Set Power profile to Max Performance and ensure Sleep is turned off.
3. powercfg -h off from command prompt to disable Hibernation.
4. chkdsk c: /R (prepare for many hours to boot up! use /F for a quicker reboot)
5. Ensure system backup and/or file history are complete and current.
6. Turn off system restore and delete all restore points.
7. Uninstall all junk or questionable Apps.
8. Ensure any existing hardware issues are cleared in Device Manager.
9. Disk Cleanup wizard and delete everything!
10. Malwarebytes scan and delete everything!
11. Ccleaner but don't mess with the registry!
12. PatchMyPC and make sure apps are up to date.

After the machine is successfully updated make sure to reconfigure the power and system restore profiles for consumer use.
 
Thanks again, all. Some very useful stuff here. I think this particular machine may have a hardware compatibility problem. It's an 'own-brand', put together by a local firm that's since closed down. I don't want to pull it apart to check every last component - neither would the customer pay me to do so - and since he's replacing it in a while anyway, I'm tempted to just add this to the great pile of unsolved Microsoft mysteries...
 
Back
Top