It’s official: Microsoft is pushing Win10 1809 on non-seeker machines

Topic

New Reply

In the no good deed goes unpunished department… I’ve now seen several reports that Microsoft has started pushing Win10 1809 on normal Win10 PCs, eve
[See the full post at: It’s official: Microsoft is pushing Win10 1809 on non-seeker machines]

9 users thanked author for this post.

Great Lake Bunyip, Laptop Boy, lurks about, abbodi86, PhotM, CADesertRat, geekdom, lanceboil

Reply | Quote

Replies

I’m waiting for them to come up with a way to force it on us 7’s during an up date.

Reply | Quote

Hah! I actually am wondering if something that nefarious might actually be coming — both in terms of secretly installing telemetry even in Group B Security Only updates, and in forced upgrades when Win7 reaches its EOL.

3 users thanked author for this post.

Great Lake Bunyip, Steve, woody

Reply | Quote

Just yesterday I got a new KB 4023057 which needed a reboot so I would imagine 1809 will be coming down the chute as you report. I turned off feature updates in gpedit though and for some reason it stopped ALL updates except for KB 4023057. I have to manually check for Win Defender updates and I manually installed the SSU for 1803.

Don't take yourself so seriously, no one else does 🙂
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

Reply | Quote

I made few tests with UUP dump API, and i cannot see that happens

“Feature update to Windows 10, version 1809 (17763.195)” is only shown if IsSeeker=1 attribute is set (i.e. “Check for updates” button)

7 users thanked author for this post.

geekdom, Great Lake Bunyip, Microfix, PhotM, PKCano, ch100, woody

Reply | Quote

Any chance there’s another way to update, without leaving notice in the UUP dump?

Admittedly, there are lots of people who’ve been updated – through various means, over many years – without remembering that they initiated contact….

1 user thanked author for this post.

PhotM

Reply | Quote

Yes, feature updates applicability rules always had glitches and accidental upgrades

or maybe the update/upgrade facilitators initiated the Seeker status (e.g. the famous KB4023057)

but so far, in the matter of seeker, 17763 is not yet pushed for non-seekers

1 user thanked author for this post.

woody

Reply | Quote

It seems a new version of KB4023814 is pushed to pre-1809 version of Windows 10
https://support.microsoft.com/en-us/help/4023814/some-versions-of-windows-10-display-a-notification-to-install-the-late

this would bypass WU settings and get 1809 without seek
not sure if it always show prompt or not

4 users thanked author for this post.

Great Lake Bunyip, woody, ch100, PKCano

Reply | Quote

Windows 10 Home x64 1709 – it tried to update me to 1809 yesterday even with metered connection set (which I do have). It does not care about what you set. I have all the settings recommended on here from various posts. Play cat and mouse with Windows Show/Hide. It will find a way to sneak onto your machine through sedlauncher.exe. I was able to stop it by turning off my WiFi and I was able to uninstall an old kb4023057 that was installed in august (when I purchased my computer). So far it hasn’t started up again.

1 user thanked author for this post.

Great Lake Bunyip

Reply | Quote

I was using:
https://greatis.com/blog/stopupdates10
to stop Win10 from updating.
Now, thanks to posts here I use:
https://www.oo-software.com/en/shutup10

It (shutup10) has capabilities past just blocking Win10 updates. It has an à la carte menu “with suggestions” to choose from.
ymmv

Reply | Quote

You could try turning off updates in services.msc and downloading / installing CUs and SSUs manually to avoid feature updates.

Turning Windows Update off in services.msc doesn’t work with Windows 10 because MS will ‘magically’ change it from Disabled to Manual and start downloading updates after a certain period of time.

You need something like Windows Update Blocker (which I use after someone here recommended it) to stop MS from changing the Windows Update Service from Disabled to Manual. Best part is it also works with Windows 10 Home.

1 user thanked author for this post.

Great Lake Bunyip

Reply | Quote

And I’m sat here using Windows 7, laughing as I update exactly when, or if I want to.

🙂

I really don’t know how you guys let MS tell you what to do with your own possessions in your own house. It would rage me beyond belief.

1 user thanked author for this post.

Elly

Reply | Quote

@BobT ‘rage’ does not go to describe the experience. I have a Win 10 with updates broken on my daily driver, so I experience your bliss, but my others are always up to some no good on regular occasions.

The question is ‘are you prepared for the future?’ At some stage this insidious infection will have to be caught. I held off for years, but would advise a dual boot or a VM of Win 10 so you at least know your enemy and the inevitable future; one day you will update hardware or need a program to run, and it just won’t. Already happened to my much loved Win 9 (8.1).

Reply | Quote

Woody, thanks for keeping us updated.  However, I do notice a problem with the picture of Christmas.  The Santa Claus looks like the devil and is apparently making the little boy cry.

Hope everyone has a good holiday and time to enjoy family and friends!

Charles

Reply | Quote

Its not coal in your stocking, its just 1809 on your PC. I think I’ll take the coal myself.

1 user thanked author for this post.

lurks about

Reply | Quote

lol, coal in the stocking would be an improvement.

Reply | Quote

Sighhhh~If it forces the PC to update to 1809 when they see it as ready, it better be when I am at home and around 3:30pm or 4pm because I ain’t doing it before bed and/or when I come home to see a sign in screen.

Also thank goodness my parents upgraded to 200mbps for spectrum speed. D*** Microsoft and Windows…..Their Xmas grinches and scrooges.

NB: Please respect the Lounge Rules on language

Reply | Quote

Is this the “home vs. pro” issue? My home laptop running 1803 pro shows no updates available. I did not check for updates, but simply opened windows update.

Red Ruffnsore

Reply | Quote