Could somebody tell me: Is the latest Win10 1809 cumulative update, KB 4495667, forced or optional?

Topic

New Reply

There’s a kind of unwritten rule that the first cumulative update each month gets pushed onto Win10 machines, and the second is an “optional” update –
[See the full post at: Could somebody tell me: Is the latest Win10 1809 cumulative update, KB 4495667, forced or optional?]

2 users thanked author for this post.

PhotM

Reply | Quote

Replies

It was pushed down my throat the moment I powered up my PC earlier today.

So: forced, methinks.

Fantastic timing nevertheless, especially as this weekend in the UK is longer (Early May Bank Holiday on Monday).

Ming boggles (again).

1 user thanked author for this post.

woody

Reply | Quote

See my answer here. (not to duplicate things)

1 user thanked author for this post.

woody

Reply | Quote

Woody – I check for updates on my 1809 laptop everyday.
I actually have not received this second cumulative update since the 1st Patch Tuesday in April.
This leads me to believe that if that laptop is being updated regularly, it will not receive this second patch.
Microsoft’s KB indicates as much.

Reply | Quote

Yeah, it’s forced. I could hide it before automaticaly install itself. Thank goodness for metered connection.

I miss Windows XP...

Reply | Quote

Looks like it’s all over the place.

Any idea if it’s forced-on-Home but not on Pro? (I think Susan’s using Pro, though.)

My Pro machine still doesn’t show the patch with wushowhide.

Reply | Quote

I just checked with wumt , wumgr and wushowhide. No sign of KB 4495667.
Windows 10 1809 Pro 17763.437

Reply | Quote

My home copy of 10 got it a few hours back, nothing negative happening so far.

Reply | Quote

Pushed to a 1809 Home laptop on 4th May at 6pm in UK.

And as a side observation it was only moving to 17763.475 that threw the Firefox certification error where add-ons were auto disabled by Mozilla. In my case UBlockOrigin, Umatrix, CookieAutoDelete and Decentraleyes all gone … were working happily prior to the CU. That is a Mozilla problem entirely though.

.https://www.bleepingcomputer.com/news/software/firefox-addons-being-disabled-due-to-an-expired-certificate/

Apologies – only just noticed Patch Lady’s topic re Firefox certificates.

Reply | Quote

I’ve been doing some more research into this whole Japanese era issue, maybe some of you will be interested…..

Heisei: 平成
Reiwa: 令和

The name of the new era, “Reiwa” was announced on April 1, with the name coming into effect on May 1.  This means that everybody had one month to get everything prepared.  (This can’t have been enjoyable for people in many rural areas of Japan, where most government and legal work is still done on paper.)

Japanese era information is stored in the registry — see the screenshot.

One would think that it’d just be a matter of adding a value to the Registry, and you’re done.  Oh, if only.  The last era change was in 1989, which predates every operating system and programming framework in use today.  This means that support for introducing a new Japanese era is not at all well-tested.

For example — In .NET Framework 4, Japanese era information comes from Windows…. but in .NET Framework 3.5, the Japanese eras are hard-coded into the framework.  This means that Microsoft had to change code written 15+ years ago to follow what’s in the Registry.

Microsoft also had to update OLE, so that VB6, VBScript, VBA, and other things built with 1990s-era technology will display the new date correctly.

There are also likely to be a lot of applications out there that will still display the era wrong, because they’re using a date library bundled with their app.  This is more likely with cross-platform applications that don’t use OS-provided date/time parsers.

…..

But what I find interesting about all this is that, by default, Windows’ Japanese regional settings doesn’t even display the Japanese era by default!  They use regular dates like the rest of us: 2019/05/04, or 2019年5月4日.  You have to choose to show the Japanese era by digging deep into the Regional settings.

So it seems to me that Microsoft is rushing these changes out out of respect to the country, not because it’s going to be showing the wrong date to everyone, or it will calculate something incorrectly in a financial or business context.

…..

I also looked into where macOS is with Japanese era.  Support for Reiwa is coming in the next update to Mojave, 10.14.5.  It’ll probably be out in the next 2 weeks.  No word on whether High Sierra will get these changes, too.

 

 

1 user thanked author for this post.

woody

Reply | Quote

Upon receipt of Level 4 from Woody yesterday, I attempted to install 4495667 onto two separate computers, but the System Mechanic installed on both would not let the install happen on either as it suspected 4495667 was malware.  Maybe more truth than poetry with that?

1 user thanked author for this post.

woody

Reply | Quote

I got the Win10 1809 cumulative update, KB 4495667 on both of my Win10 Pro as well as on my Win10 Home yesterday Friday 5/3/19.
— When a cumulative update is due, I create a system image back beforehand.
— Usually I do that just before the 2nd Tue (Update Tuesday) of the month.
— This time, however, the cumulative update is in Microsoft’s “out-of-band” release
https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-10-update-servicing-cadence/ba-p/222376
“An out-of-band release is any update that does not follow the standard release schedule. These are reserved for situations where devices must be updated immediately either to fix security vulnerabilities or to solve a quality issues impacting many devices.”

HP EliteBook 8540w laptop Windows 10 Pro (x64)

1 user thanked author for this post.

woody

Reply | Quote

I checked UUP dump API
KB4495667 (17763.475) is indeed pushed for all, without seeking
“Cumulative Update for Windows 10 Version 1809 (17763.475)”

however, “Feature update to Windows 10, version 1809 (17763.475)” is only available for seekers on 1803 and below

2 users thanked author for this post.

woody, PKCano

Reply | Quote

So KB 4495667 – the May 3 “second second” cumulative update – is being pushed on all Win10 1809 machines?

But the KB article says it’s for seekers.

And the upgrade from 1803 to 1809 is now being pushed on 1803 seeker machines?

Crazy.

Any idea why some machines are getting it pushed and others aren’t? I still can’t see 4495667 in wushowhide.

Reply | Quote

Yes, i verified multiple times with and without seeker attribute

yes, that too
isn’t been available for 1803 seekers since they annouce it broadly-ready?
but i just wanted to point that KB4495667 is also available with feature update (i.e. it will be applied during upgrade)

Reply | Quote

Regarding wushowhide

CU are handled by the new UUP since version 1709
traditional wushowhide and WUMT cannot process (or sometimes request) UUP data correctly

Reply | Quote

Strange. I’m still not seeing it on my Win10 Pro Build 17763.437 – not even checking for updates (may 5). See my settings here.

1 user thanked author for this post.

abbodi86

Reply | Quote

My tests were on Pro with default settings, nothing set or changed

Reply | Quote

Win10 pro 1809 –  KB 4495667 not seen in wushowhide

1 user thanked author for this post.

woody

Reply | Quote

Win10 pro -checked for updates 30apr but nothing installed, no other signs of forced…..

feature update 2/20

Reply | Quote

Looked in the management thing we have, saw 4495667 in the push queue for “my” system ONLY out of several 1809s, let it through… logged in after installing and had a BSOD.

Oh well. Not letting that through for others, then – at least not right away.

(Did start normally on a second try though, now up with reported version 10.0.17763.475. I wonder if I should bother looking into what’s in the dump… at least got a proper bugcheck event logged from the BSOD, for once.)

The other thing though, tried “being a seeker” on a 1803 box just now, didn’t get a feature update on that one.

Go figure…

Reply | Quote

This update was forced on my laptop yesterday awaiting restart which I have delayed.  I did not click “check for updates”…I am NOT a seeker…it automatically downloaded and awaiting install.   Microsoft is pushing this to users.  I’m a Win 10 Home Edition user with limited ability to stop these automatic updates.

Reply | Quote

Forced on both my machines.

I did not seek them, but they arrived anyway.

MS up to their tricks again, it seems………….

Reply | Quote

I’m on Pro and try to update every day.

Have not received these patches, even going out for “Check for Updates”

Reply | Quote

Same here, Seeking but not Finding…

I have the telemetry service disabled, may this be the reason?

The Captcha is a nonstarter…!

Reply | Quote

On my 1809 Home tablet, wushowhide revealed KB4495667 in the que – so it is getting pushed at least to some machines. I quickly hid it for now until next months Defcon OK by AskWoody – or until it’s been demonstrated as benign. 🙂

Win10 Pro x64 22H2, Win10 Home 22H2, Linux Mint + a cat with 'tortitude'.

Reply | Quote

Windows 10 Pro, 1809.

Neither the second CU nor the “second second” CU was offered by MS Update, even when seeking.

I manually downloaded both CUs from the MS Update Catalog and installed them manually.

There is also a SSU (Servicing Stack Update). That one did automatically apply as soon as it was released.

All appears well. Fortunately I have waited this time (unusually long for me) before running AV scans and system image backup. There’s nothing more frustrating than doing a long piece of work, then finding out I have to do it all over again.

Well, maybe a Blue Screen would be more frustrating, but those never happen to my NUC.

-- rc primak

Reply | Quote

Belarc Advisor marks my Windows 10 Pro 1809 (17763.437) as up-to-date with updates.

Reply | Quote

https://docs.microsoft.com/en-us/windows/release-information/status-windows-10-1809-and-windows-server-2019#355msgdesc

“Latest cumulative update (KB 4495667) installs automatically

Due to a servicing side issue some users were offered KB4495667 (optional update) automatically and rebooted devices. This issue has been mitigated.”

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

For those complaining about forced updates (Microsoft told ya years ago when Windows 10 was released), just disable automatic updates and decide yourself when to update, or not.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU]
“AUOptions”=dword:00000002
“NoAutoUpdate”=dword:00000000
“NoAutoRebootWithLoggedOnUsers”=dword:00000001

Reply | Quote

anonymous wrote:

For those complaining about forced updates (Microsoft told ya years ago when Windows 10 was released), just disable automatic updates and decide yourself when to update, or not.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU]
“AUOptions”=dword:00000002
“NoAutoUpdate”=dword:00000000
“NoAutoRebootWithLoggedOnUsers”=dword:00000001

I checked my registry and that information as presented isn’t in there: I don’t think that applies anymore. EDIT: I should say I don’t think it applies to Windows 10.
This article includes that information but it’s dated Aug 17, 2006
https://blogs.msmvps.com/athif/2005/09/14/manually-configure-wua/

HP EliteBook 8540w laptop Windows 10 Pro (x64)

Reply | Quote

“NoAutoUpdate” should have a DWORD value of 1 (aka. 00000001) to disable automatic updates.

at least I have THAT reg value on my Win10 LTSC 2019 (v1809) machine. I do not have the other reg values like “AUOptions” and “NoAutoRebootWithLoggedOnUsers” which are not present.

1 user thanked author for this post.

cmptrgy

Reply | Quote

EP wrote:

“NoAutoUpdate” should have a DWORD value of 1 (aka. 00000001) to disable automatic updates.

at least I have THAT reg value on my Win10 LTSC 2019 (v1809) machine. I do not have the other reg values like “AUOptions” and “NoAutoRebootWithLoggedOnUsers” which are not present.

I have Windows 10 Pro Version 1809 OS build: 17763.503

My registry searches
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU
— Didn’t find it and just reported “Finished searching the registry”.

NoAutoUpdate
— Didn’t find it and just reported “Finished searching the registry”.

AUOptions
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PolicyManager\default\Update\AllowAutoUpdate\ GPBlockingRegValueName\ AUOptions
— There aren’t any DWord values to work with.

That’s ok, my computer doesn’t have what I was looking for but I can live with that since that is the normal case.

Windows 10 release information
https://docs.microsoft.com/en-us/windows/release-information/
Reports OS build: 17763.503. Availability date: 2019-05-14.
Servicing option: Semi-Annual Channel _ Semi-Annual Channel (Targeted) _ LTSC. KB article: KB 4494441.
— That doesn’t tell me if my servicing option is Semi-Annual Channel or Semi-Annual Channel (Targeted)
— Is there a way I can determine which servicing option my computer is using?

Further down in https://docs.microsoft.com/en-us/windows/release-information/ it appears to me LTSC applies to
Enterprise and IoT Enterprise LTSB/LTSC editions
— That’s ok, at least I know LTSC doesn’t apply to me.

In my prior post I mentioned “I should say I don’t think it applies to Windows 10.”
— My apologies for that as I shouldn’t have assumed that to be a possibility just because it wasn’t on my computer, please know I appreciate the information you have provided.

HP EliteBook 8540w laptop Windows 10 Pro (x64)

Reply | Quote