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?
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?