Here comes updates for November. Remember at this time I urge you to defer, not install UNLESS you have a test bed/good backup plan and you are one of
[See the full post at: November patches here we come]
Susan Bradley Patch Lady/Prudent patcher
![]() |
Patch reliability is unclear. Unless you have an immediate, pressing need to install a specific patch, don't do it. |
SIGN IN | Not a member? | REGISTER | PLUS MEMBERSHIP |
Home » Forums » Newsletter and Homepage topics » November patches here we come
Here comes updates for November. Remember at this time I urge you to defer, not install UNLESS you have a test bed/good backup plan and you are one of
[See the full post at: November patches here we come]
Susan Bradley Patch Lady/Prudent patcher
AKB 2000003 has been updated for Group B Win7 (ESU) and Win8.1 on Nov 9, 2021.
There is a Security-only Update for those with Win7 ESU subscriptions.
There was no Nov. IE11 CU for Win7.
November Rollup KB5007236 Download 32-bit or 64-bit for those with Win7 ESU subscriptions.
You must have at least the August 2020 Servicing Stack KB4570673 previously installed to receive these updates).
There is a October 2021 Servicing Stack KB5006749 – Download 32-bit or 64-bit for those with Win7 ESU subscriptions.
There is a revised Licensing Preparation Package KB4575903 dated 7/29/2020 for Win7 ESU subscriptions, if you need it.
There are .NET updates listed for Win7. See #2400690.
There are also security updates for MS Office 2013 and 2016
More info available over on November 2021 updates for Microsoft Office Excel security update and others..
Just updated PC2 in my signature, no problems so far. However, Microsoft also decided to “helpfully” install PC Health Check even though this particular system doesn’t qualify for Windows 11, it doesn’t even have any form of TPM whatsoever. It “popped up” while I was updating and I noticed it had been added to the Start Menu after I finished installing the updates.
“BleepingComputer reports that some users are noticing the app will reinstall itself even after manually removal. In response, Microsoft said it’s investigating the problem, which it called unexpected behavior”.
Yes, of course it is. I’m sure its the same as all of the “unexpected behaviour” that occurred when they were pushing Windows 10 hard about 5 years ago.
PC Health Check was easy enough to uninstall (for now, at least) and it hasn’t tried to reinstall itself so far. Possibly because I always have Windows Update blocked with a third party tool when I’m not doing the monthly updates plus I also have a truckload of MS IP addresses blocked with the Hosts file (which I also need to unblock when doing the monthly updates).
I’ll update PC1 sometime in the next few days and I’m expecting the same installation of PC Health Check even though that PC also doesn’t qualify for Windows 11.
Actually, I need to start paying more attention on Patch Tuesdays. That PC Health Check is a separate update – KB5005463 (4.39 MB).
I went back and restored a Macrium Reflect image that I made before I ran Windows Update yesterday then ran Windows Update again and this time I’ve hidden KB5005463 (thank goodness for Update Manager for Windows – WuMgr, especially with Windows 10 Home).
The reason I’ve gone to all this trouble is because after I uninstalled KB5005463 yesterday I noticed there were about a dozen registry entries left behind according to CCleaner and I don’t want any little ‘surprises’ suddenly popping up even after I removed them.
UNLESS you have a test bed/good backup plan and you are one of the regulars that love to test for the rest of us to let us know how the patching looks.
KB5007186 Cumulative Update for Windows 10 Version 21H1 for x64-based Systems along with the Malicious Software Removal Tool. No hiccups.
Windows 10 Pro 21H1 (OS Build 19043.1348)
Microsoft pushed 3 updates to my Windows 11 installation on unsupported hardware.
(KB5007215) Cumulative Update for Windows 11 for x64-based Systems
(KB5008295) Update for Windows 11 for x64-based Systems
(KB5005537) Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 11 for x64 (KB5005537)
No hiccups.
OS build 22000.318
I still had 62 days update pause, but I hit [Resume Updates] of my Win 10 H64 21H1 anyway.
It worked fine, though slow as usual. Microsoft fed me KB890830, KB 5007885 and KB5007186. My computer accepted it without groaning or grumbling. Routine, you know?
So now I have OS build 19043.1348, though still 21H1.
Now I’m confused. What’s keeping 21H2? Or is 21H2 = Windows 11?
BTW. I applied the pause period tweak. Now every day the update pause period is reduced by 1 day. But the pause ending day is advanced 1 day. By tweaking the pause period every day or so, you can keep it at 9 weeks. IOW, you can defer windows update as long as you want. Though NOT indefinitely, as that compromises security.
Not sure what is keeping Windows 10 21H2 from releasing.
Perhaps it’s not baked properly yet, Microsoft in the middle and crusty outside?
Hasn’t stopped them before..so it can’t possibly be that excuse.
After installing this update, Windows print clients might encounter the following errors when connecting to a remote printer shared on a Windows print server:
0x000006e4 (RPC_S_CANNOT_SUPPORT)
0x0000007c (ERROR_INVALID_LEVEL)
0x00000709 (ERROR_INVALID_PRINTER_NAME)
Note The printer connection issues described in this issue are specific to print servers and are not commonly observed in devices designed for home use. Printing environments affected by this issue are more commonly found in enterprises and organizations.Devices with Windows installations created from custom offline media or custom ISO image might have Microsoft Edge Legacy removed by this update, but not automatically replaced by the new Microsoft Edge. This issue is only encountered when custom offline media or ISO images are created by slipstreaming this update into the image without having first installed the standalone servicing stack update (SSU) released March 29, 2021 or later.
Bleepingcomputer.com mentions November updates suggested to trigger server authentication issues.
All systems here (1909 enterprise license) got a weird undocumented KB5007114 pushed, in all cases failed to install. The regular cumulative update went fine. Weird. Looks like this specific update either doesn’t belong on 1909 or there is something not ok with it, whatever it’s supposed to do.
Possibly detection is faulty.
Susan Bradley Patch Lady/Prudent patcher
November update to system below broke network share printer, just like the October update. This was update to 20H2 NOT 21H1
Windows 10 Home version 20H1
Update KB5007186 to version 20H2 Build 19042.1348
This changes win32spl.dll to version 10.0.19041.1320 (Was version .1288 in the October update)
This breaks the share printer with a similar error message as before.
Replaced the win32spl.dll with the 10.0.19041.1237 version.
Shared printing over the home network was instantly restored.
Since others may need a copy of the 10.0.19041.1237 win32spl.dll file, I uploaded a copy to the following link.
https://www.mediafire.com/file/6344ky1cqg77vs7/win32spl.dll/file
HTH, Dana:>>
HTH, Dana:))
Hi Susan:
I have a Win 10 Pro v21H1 OS, and received two updates for the November 2021 Patch Tuesday (updates paused until 12-Nov-2021). So far everything looks fine.
This is a home computer so I can’t provide any feedback about the status of networked LAN printers. I did not receive KB5006365 (2021-11 Cumulative Update for .NET Framework 3.5 and 4.8 for Win 10 v2004 to v21H1) but I gather that’s expected since I have “Select When Preview Builds and Feature Updates Are Received” enabled in GPEdit (“Semi-Annual Channel” / defer for 1 day), and this month’s .NET Framework update does not include a security update. See donnegar’s June 2021 .NET Update Confusion for a discussion on this topic.
———–
Dell Inspiron 5584 * 64-bit Win 10 Pro v21H1 build 19043.1348 * Firefox v94.0.1 * Microsoft Defender v.4.18.2110.6-1.1.18700.4 * Malwarebytes Premium v4.4.10.144-1.0.1499
I am Win10/Pro 21H1
I have finally gotten around to installing the November Patch Tuesday CU (KB5007186)
It installed successfully on both of my laptops (a 6th generation and an 8th generation), but afterwards on both I had to repair corrupted files with the PowerShell command sfc /scannow. This happened with the October patch also (KB5006670).
Donations from Plus members keep this site going. You can identify the people who support AskWoody by the Plus badge on their avatars.
AskWoody Plus members not only get access to all of the contents of this site -- including Susan Bradley's frequently updated Patch Watch listing -- they also receive weekly AskWoody Plus Newsletters (formerly Windows Secrets Newsletter) and AskWoody Plus Alerts, emails when there are important breaking developments.
Welcome to our unique respite from the madness.
It's easy to post questions about Windows 11, Windows 10, Win8.1, Win7, Surface, Office, or browse through our Forums. Post anonymously or register for greater privileges. Keep it civil, please: Decorous Lounge rules strictly enforced. Questions? Contact Customer Support.
Want to Advertise in the free newsletter? How about a gift subscription in honor of a birthday? Send an email to sb@askwoody.com to ask how.
Mastodon profile for DefConPatch
Mastodon profile for AskWoody
Home • About • FAQ • Posts & Privacy • Forums • My Account
Register • Free Newsletter • Plus Membership • Gift Certificates • MS-DEFCON Alerts
Copyright ©2004-2025 by AskWoody Tech LLC. All Rights Reserved.
Notifications