Windows Updates Thread - August 2019 - Patch Yo Shizzle

more weird patch fuckery this morning.

2018-02 Dynamic Update for Windows 10 Version Next for x64 etc etc KB4078128.

wtf is version next?

go to the kb article and am greeted with this...

https://support.microsoft.com/en-au...patibility-update-for-upgrading-to-windows-10

 

well we're all beta testers now anyway so meh why not eh?

 

Outsource patch management they say....

Pretty sure in the last year this is the 3rd "test" patch I've seen go live from Microsoft.....
Control -a, right click deploy all, ok, ok, ok

What could possibly go wrong

 

more test patches released over the weekend.

 

is kb4056892 failing hard for everyone else, or are we just 'special'? I'm seeing a 40% failure rate on 500 win10 machines (best was 38 failed installation attempts in the one machine), only fix short of reimaging is to uninistall and install the 600MB .msu

 

Another Month, another Bunch

https://support.microsoft.com/en-us/help/4093492/credssp-updates-for-cve-2018-0886-march-13-2018

Keep in mind the CredSSP fix needs some Group Policy loving before its actually enabled.

 

Get patching to your exchange boxen:

https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2018-0940

This bug allows fake style OWA login pages to be presented due to bad scrubbing of links from within OWA.

 

I think I read something about them pushing that update from January that required a reg key to be set by your AV.

 

anyone having any issues with:

kb4088776 error 0x80092004

which is apparently a bad signed cert?

Hmm now seeing it on 2 boxes, same issue....

 

Yeah, theres a couple...
If your AV doesn't set (or you don't set, via some other method).

Key="HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat"
Value Name="cadca5fe-87d3-4b96-b7fb-a231484277cc"
Type="REG_DWORD”
Data="0x00000000”

Then you won't be offered updates.

Once you are being offered updates
https://support.microsoft.com/en-us/help/4090007/intel-microcode-updates has the microcode updates and contains links to the registry settings you need to set to enable them, once the update has been applied.

 

No no you misunderstand, I thought I read they'd stopped checking for that.

Might be wrong but could have sworn I read it on twitter this morning.

 

COrrect, this months update patches say it isn't needed as the AV vendors have got their shit together.

 

It's still needed for Win7

https://support.microsoft.com/en-us/help/4088875/windows-7-update-kb4088875

And I think its still needed for one of the Spectre fixes.

 

Updats binning VMXNet3 and Win7/2008r2 boxen.

Thanks ms.

The combination seems to be VMXNet3 adapter's and KB4088875 and KB4088878. There is also reports that people are seeing this on some POS desktops.
Guests will get a 169 IP address (unless you have dhcp). The fix is reportedly.
-Windows Run -cmd In the same CMD window run-

set devmgr_show_nonpresent_devices=1

Then

start devmgmt.msc

In Device Manager

View > Show Hidden Devices

Then go under networking and delete the grayed out NICs and everything will come back.

 

WhatYearIsThis.jpgs...

Also, KB4011730 breaks Word 2016...

#JustMicrosoftQA

https://social.technet.microsoft.co...-b650-33c8231ae1ca/kb4011730-breaks-word-2016

 

seems to be related to add-ins somehow. so glad i spent the time to block the add-ins function of word.

 

Anybody else have RDP broken last night after last nights updates?

I removed them all (not time to test which was the one that broke it) , rebooted the server , and all good again.

 

noooooooooooooooo?

sku?

 

The CredSSP update will break it, depending on what clients you're using to connect.

 

We're just using the regular Windows 7 and Windows 10 RDP clients.