Big problems with Win7 Preview of Monthly Rollup KB4041686

Topic

New Reply

I just saw a heads-up from @abbodi86 about the Monthly Rollup Preview for Win7 that was released yesterday. It’s KB 4041686, the 2017-10 Preview of Mo
[See the full post at: Big problems with Win7 Preview of Monthly Rollup KB4041686]

3 users thanked author for this post.

walker, JDeC, abbodi86

Reply | Quote

Replies

I confirmed and reported issue via https://support.microsoft.com/en-us/help/4041686.

3 users thanked author for this post.

walker, woody, Noel Carboni

Reply | Quote

Not related: Issue “Addressed issue where USBHUB.SYS randomly causes memory corruption that results in random system crashes that are extremely difficult to diagnose” also appears in the Windows 7 October 2017 monthly rollup, but that apparently is an error because file USBHUB.SYS isn’t present in the file list for the Windows 7 October 2017 monthly rollup, but it is present in the file list for the Windows 7 October 2017 preview monthly rollup.

1 user thanked author for this post.

walker

Reply | Quote

Thanks for the heads-up, Woody.

I agree with your advice. If an update is unchecked, optional, and/or a preview, then leave well alone – unless you’re running an isolated test system and know what you’re doing.

I’ve already hidden several optional updates this month, including a couple of previews (being the monthly roll-up preview  and a .Net Framework preview), an unchecked .Net Framework update and an Nvidia display driver update.

1 user thanked author for this post.

JDeC

Reply | Quote

‘Is anybody at Microsoft listening?’

I’d rather they were reading as it all seems to fall on deaf ears.

Windows - commercial by definition and now function...

1 user thanked author for this post.

Cybertooth

Reply | Quote

Thanks for the heads up, Woody.

Since waiting for MS-DEFCON 3 or higher for the regular updates often means seeing the preview and thinking, “gee, should I take a chance”, this reaffirms that the chance is better left taken after the NEXT MS-DEFCON cycle.

On at least one occasion (a week ago for sure) I still saw the last month’s “preview” update listed during the next patch Tuesday testing. I can’t recall whether that’s typical, but it seemed weird.

P.S., I have only done minimal testing (there are only so many hours in the day) on my Win 7 test system after installing the regular October patch Tuesday patches group A style, but I didn’t encounter any issues so far based on the way I run that OS.

-Noel

1 user thanked author for this post.

walker

Reply | Quote

Just got this tweet from @koitsu2009:

Interesting. I’ve seen that usbhub.sys SFC scan failure before, too (August updates, I think?). Like usual, guess I’ll wait this patch out.

Reply | Quote

Can we involve patchmanagement list? 😀

since “Michael Niehaus” sometimes participate in

 

Regards.

2 users thanked author for this post.

walker, Noel Carboni

Reply | Quote

Lemme see what I can do…

2 users thanked author for this post.

walker, abbodi86

Reply | Quote

I got a question from someone that I don’t know how to answer…

If a Win 7 system has already been updated with KB4041686, can that update just be uninstalled to relieve the hash mismatch with usbhub.sys.mui? From what I gather they did not do an SFC /SCANNOW, but rather saw the messages that KB4041686 should be avoided. Apparently nothing was actually changed but SFC /VERIFYONLY no longer shows “All OK”.

-Noel

Reply | Quote

Yes

running SFC /SCANNOW will not actually change anything
in the same session, it will replace new version of usbhub.sys.mui with old version
then it will replace old version with the new version from KB4041686

2 users thanked author for this post.

walker, Noel Carboni

Reply | Quote

Thanks, abbodi86.

The USBHUB.SYS issue (memory corruption) that KB4041686 claims to resolve seems serious but if the system wasn’t having ongoing problems before the update then this fix can probably wait until next month, and maybe Microsoft will make it right.

One would imagine someone at Microsoft should have checked SFC /VERIFYONLY after putting together the update package and testing it on at least one system… Hm, maybe none of them has a Windows 7 system that still passes the tests. 😀

I see that there are already two “Microsoft is working on a resolution…” notes listed in the KB4041686 article but not for this issue, specifically. At this point I don’t know how to ensure someone at Microsoft even knows about the problem. My old inside networking contacts are long gone.

-Noel

Reply | Quote