Replies

The way Microsoft is behaving/communicating on this feels like something bad is going on.
I reached out to our TAM today and all he could tell was that he does not have more information either from the engineers and that there will be a PIR over the next 5 business days.

So how can you already know you will need 5 business days to do a PIR? Someone obviously fixed the issue ‘magically’ so in order to fix it, you usually need to know what change(s) broke it. It almost looks like Microsoft is sitting on a huge 0-day vulnerability they tried to patch yesterday server-side and broke a ton of recent Current Channel builds by doing that, had to roll back the change and are now buying themselves a few days time to patch it after all before being able to share further details that would publicly expose the vulnerability.

But that’s my gut feeling 🙂

1 user thanked author for this post.

woody

Well apparently Microsoft’s communication to Enterprise customers was wrong, and they didn’t care to send a follow-up communication to let us know, they just posted a message in the Windows Message Center:

Update: Starting September 24, 2019, mitigation for this vulnerability is included as part of the 9C optional update, via Windows Update (WU) and Microsoft Update Catalog, for all supported versions of Windows 10, with the exception of Windows 10, version 1903 and Windows 10, version 1507 (LTSB). For devices running Windows 10, version 1903, mitigation for this vulnerability will be included as part of the 9D optional update via WU, WSUS and the Microsoft Update Catalog (targeted for September 26, 2019.) To apply this update, go to Settings > Windows Update > Check for Updates. (Note Because this update requires a reboot, we are making it optional to give customers and administrators a choice to install/deploy the update now.)

For customers running Windows 8.1/ Windows Server 2012 R2 or below, the 9C update is also available on Windows Server Update Services (WSUS). For other supported versions, IT admins using WSUS can import this update into WSUS/SCCM manually. See instructions on the <u>WSUS and the Catalog Site</u>.

So basically only the Win10 1903 one will be in WSUS as part of the D release, on 9/26. The ones for all other Win10 versions will need to be imported manually.

1 user thanked author for this post.

mobartz