Newsletter Archives
-
Is Windows pushing you to upgrade to version 1903? Don’t be bullied.
I’m getting a lot of questions from people with Win10 version 1803 who wonder if they’re doomed to upgrade to Win10 1903 in the next few weeks. Microsoft’s “Download and install now” notification certainly makes it sound that way, but you have more control over the matter than you may think.
Detailed explanation of the pros, the cons, the howtos and the wherefores, in Computerworld Woody on Windows.
-
Microsoft on forced Win10 1803 upgrades: “We are aware of these reports and actively investigating this issue”
At least, that’s what Bogdan Popa says Microsoft told him. Reporting on Softpedia, Polpa says:
Details aren’t yet available, but the company said it’s looking into this to determine what exactly happened. No specifics were provided though.
“We are aware of these reports and actively investigating this issue,” a Microsoft spokesperson told us.
‘Course Microsoft hasn’t exactly been beating down my door, but that’s to be expected. Just as well. I couldn’t tell them anything more than what I’ve already reported.
Anybody out there have additional insight into this, the first “ooops” forced upgrade to 1803? We’re still behind the Win10 1709 “ooops” upgrade count, which stands at three.
-
Microsoft admits that it forced Win10 1703 machines to upgrade to Win10 1709, even with updates blocked
Third time they’ve pulled this “Gawrsh” garbage in the past four months.
Computworld Woody on Windows.
-
So how DO you block the upgrade to Win10 1709
More than a few people have asked, what with Win10 1703’s new-found ability to upgrade to 1709 all by itself — no Windows Update required — what does it take to make sure Microsoft doesn’t change its mind again and pushes you onto whatever version it likes?
@abbodi86 has an interesting observation:
Windows Update in Windows 10 is a lost cause without intervention
some steps are obligatory to keep the current version:
– set connection to metered
– set Automatic Update policy to disabled or notification
– disable UpdateOrchestrator and WindowsUpdate schedule tasks
– use wushowhide.diagcab or WUMT to check for updates and hide the upgrader-updateswhich seems to be a whole lot of work just to stay with what you have.
Comments?
-
Report: Win10 users being pushed onto 1709 even if they have Feature Updates deferred
UPDATE: See Computerworld Woody on Windows.
Hey @woodyleonhard , it seems Microsoft is now forcing Windows 10 1607 and 1703 users to upgrade to 1709, even if Feature Updates have been deferred. This notification just popped to my laptop, which is running 1703.
Couldn't stop it upgrading.
More info:https://t.co/9hgphP7QI9 pic.twitter.com/IYBouieDl0— Juzu Operatzija (@juzuo) March 8, 2018
-
Win10 machines with “Defer feature updates” now getting pushed Creators Update
There’s a reason why your Win10 1607 PC with “Defer feature updates” is getting pushed onto 1703 — and you aren’t going to like it. Fortunately, there’s a partial solution.
Tip: If you’re running Win10 Anniversary Update, version 1607, and don’t want to get pushed onto 1703, go into Windows Update and see if “Feature update to Windows 10, version 1703” is waiting download. If so, use wushowhide or a metered connection to block it. If it’s already downloaded and awaiting a reboot, DON’T reboot just yet.
Computerworld Woody on Windows
UPDATE: I can confirm that this method worked on my production PC. Per @netdef:
If the updater shows 1703 still pending a reboot, and you have successfully used wushowhide.diagcab to block it, go to C:\Windows\SoftwareDistribution\Download and delete ALL subfolders and files in there (but don’t delete the Download folder itself.)
Now at the Start menu, you should have roughly double the count of shutdown options listed. Half are normal, the other half say something like Update and Restart or Update and Shut down.
Restart the workstation without the Update option.
Now when you recheck updates, the Feature update to 1703 should abort, and no longer be listed as pending.
Brilliant!
UPDATE: There’s a reason why you were caught flat-footed. You were probably waiting for the usual “4 months to CBB” delay. That interval is shrinking precipitously…