Bork Tuesday, Any Problems Yet?

Woody Leonhard - 6 Nov 2017

"Microsoft yanks buggy Windows patches KB 4052233, 4052234, 4052235"
https://www.computerworld.com/artic...ndows-patches-kb-4052233-4052234-4052235.html

 

http://windowsreport.com/kb4052233-kb4052234-issues/

 

Good advice from article:

 

October 10, 2017,

Today, I installed October 10th KB4043766 for .NET Framework, as I found no reports of any issues with KB4043766.
Also today, I hid today's latest version of KB2952664.

 

Today i hid 2664 again like i did many times before.

 

Updated both Win 7 computers Tuesday with all updates. No problems so far.

 

https://www.sevenforums.com/perform...ts-corrupted-files-again-after-kb4041686.html ........ https://www.askwoody.com/2017/big-problems-with-win7-preview-of-monthly-rollup-kb4041686/

 

https://www.sevenforums.com/perform...ts-corrupted-files-again-after-kb4041686.html

 

I have installed the 2017-10 Security Only Quality Update for Windows 7 for x64-based Systems (KB4041678 ), on two systems, instead of the Monthly Quality Rollup (KB4041681).
I said yes to all of the Office and Outlook Security Updates, as well as the Malicious Software Removal Tool.
I created a Macrium Reflect backup prior to installation. All appears well at this point.

 

https://www.computerworld.com/artic...rarily-turn-off-windows-automatic-update.html "This month, we already know that KB 4041686, the 2017-10 Win7 Preview of a Monthly Rollup, has a retrograde bug in it that clobbers SFC scans. It’s not at all clear if Microsoft is going to fix that bug before the Preview becomes the for-real Monthly Rollup. AskWoody poster abbodi86 has detected a retrograde bug in KB 4041686, the 2017-10 Win7 Preview of a Monthly Rollup. If you install it, an SFC (System File Check) scan will report and fix an error in \system32\drivers\en-US\usbhub.sys.mui – even though there is no error. This is precisely the problem @abbodi86 reported to Microsoft after installing the old KB 3125574, which is the “convenience rollup” I call “Win7 SP 2.” The bug was fixed in KB 3181988, but it’s back again. If you install KB 4041686, you’ll trigger a bogus SFC error, even if you have KB 3125574 installed."

 

Win10 x64 1709 updated (quite quickly) without issue.

Edit: Except the machine I had hid 1709 on is downloading it again now.

 

Two Windows 7 x64 machines updated with no problem.
I installed KB4048957 Rollup and MSRT.
KB4048957 Rollup did not cause any System File Checker issues, like the Preview did. It looks like Microsoft fixed that issue before releasing KB4048957 Rollup.
I did not install 'recommended' update KB4049016 for .NET Framework, that one can wait a few weeks.

 

Thanks for the SFC info. I take it that you ran a SFC after the 957 update and it ran with no issue from the rollup.

 

https://www.ghacks.net/2017/11/14/microsoft-security-updates-november-2017-release/

 

On an old fart machine w/its original and perfect Fall CU install, zip,zip, zip to winver 16299.64. On a five month old powerhouse: total failure at the install phase--0x8e5e0408. Anyone, particularly from the Start Menu is Broken crew, experiencing the same? Gonna try it again, if not, I'll try updating from the catalog. This is insane, four Windows installs (reset, repair, two cleans) and it's not happening. Wow.

Edit: OK, tried again, it went this time, I feel like a brat who got a lollipop and is all better now. This Fall CU and its updates--not easy for some, wish I'd kept Windows.old like you did, Krusty, but like you know this developed well after the fact, so it seemed OK to ditch it, esp w/a tiny C drive.

 

No problem on either my 1709 cleanly installed machine or my upgraded machine.

It looks like the 1703 machine that I had hidden 1709 on didn't upgrade, thankfully.

 

Update in my Windows 10 1709 went well as always (build 16299.64).



Bo

 

That is correct.

 

Update to Win 10 64 (bit) 1709 build 16299.64 was successful on two machines, albeit a few retries were needed.

 

Except I didn't keep Windows.Old. I used Macrium Reflect to restore my machines.

 

But of course! I think I might have a defective drive somewhere, all these problems. I tried imaging twice w/Macrium and both were riddled with errors. You reminded me to start up with this again. I'll give it another try, it's worth it.

 

Just for record, today's updates (KB4048951, KB4048955, KB890830) installed fine and no issue observed aftermath.