Microsoft has released the optional KB5007253 Preview cumulative update for Windows 10 2004, Windows 10 20H2, Windows 10 21H1, and Windows 10 21H2.
Microsoft claims this update fixes network printing issues causing 0x000006e4, 0x0000007c, or 0x00000709 error codes to be displayed.
The KB5007253 cumulative update preview is part of Microsoft's September 2021 monthly "C" update, allowing admins to test fixes coming as part of the December 2021 Patch Tuesday.
However, unlike Patch Tuesday updates, the "C" preview updates are optional and do not include any security updates.
Windows users can install this update by going into Settings, clicking on Windows Update, and manually performing a 'Check for Updates.'
As this is an optional update, you will be asked whether you wish to install it by clicking on the 'Download and install' link, as shown in the image below.
Windows 10 users can also manually download and install the KB5007253 preview update from the Microsoft Update Catalog.
Microsoft claims to fix networking printing errors
After Microsoft modified the Windows printing experience to deal with PrintNightmare vulnerabilities, users began experiencing errors when attempting to print to network printers.
Print jobs would fail when attempting to print to a network printer, and Windows would display a 0x000006e4, 0x0000007c, or 0x00000709 error, as shown below.
Source: Microsoft Forums
Last month, Microsoft began privately sharing printing fixes using ADMX installers that manually added Known Issue Rollback (KIR) fixes to the Windows Registry.
These installers fixed the Windows 0x0000007c printing errors but did not help with the other error codes people were receiving. However, Microsoft told Windows admin in private support chats that the fixes would formally be released as part of the December 2021 Patch Tuesday updates.
These fixes are now being released as part of this week's Windows 10 KB5007253 update and allegedly fix the 0x000006e4, 0x0000007c, or 0x00000709 printing errors.
BleepingComputer has not tested this update to see if it resolves this error. If you install the update, please share whether it resolved your network printing problems.
What's new in Windows 10 KB5007253
After installing this update, Windows 10 2004 will be updated to build 19041.1387, Windows 10 20H2 will be updated to build 19042.1387, Windows 10 21H1 will be updated to build 19043.1387, and Windows 10 21H2 will be updated to build 19044.1387
The Windows 10 KB5007253 cumulative update preview includes thirty-three improvements or fixes, with eleven highlighted fixes below:
-
Updates an issue that that causes some variable fonts to display incorrectly.
-
Updates an issue that might cause the 32-bit version of Microsoft Excel to stop working on certain devices when you export to PDF.
-
Updates an issue that displays letters or characters at the wrong angle when you use the Meiryo UI font and other vertical fonts. These fonts are frequently used in Japan, China, or other countries in Asia.
-
Updates an issue that causes Internet Explorer to stop working when using the Input Method Editor (IME) to insert elements.
-
Updates an issue that causes the Settings page to unexpectedly close after you uninstall a font.
-
Updates an issue that affects your ability to rename a file using folder view in File Explorer when you use the new Japanese IME.
-
Updates an issue that turns off screen capture and recording functionalities on the Windows Game Bar after a service failure.
-
Updates an issue that prevents the applications that you use often from appearing on the Start menu as they should.
-
Updates an issue that causes Internet Explorer to stop working.
-
Addresses a known issue that causes error codes 0x000006e4, 0x0000007c, or 0x00000709 when connecting to a remote printer that is shared on a Windows print server.
-
Addresses a known issue that might prevent apps, such as Kaspersky apps, from opening after you attempt to repair or update the apps using the Microsoft Installer (MSI).
You can find a complete list of fixes in the KB5007253 support bulletin.
Comments
manzooramin - 2 years ago
after updating the issue still persists, request to all to share your experience
oregonjohn - 2 years ago
Got connected to shared printer over vpn finally with this on the print server, but the name doesn't show correctly, instead the name shows as the printer model and I can't change it.
dwg2 - 2 years ago
This latest KB5007253, is a partial fix. Sort of....
Using ANY of the previous updates from Patch Tuesday (Sept, Oct, Nov), typically broke Network printing, and a simple roll back was all that was needed to restore network printing, except KB5007186 (Nov), which took quite a bit to resolve/remove to restore Network printing, at least in my case. I'm not commenting on that experience as the troubles I experienced may have been self induced. It is just important to note that KB5007186 broke network printing and not to install it.
With this latest update, KB5007253, installing this on a Windows 10 Pro computer, and adding a Network printer located on a machine that does NOT have KB5007253 works perfectly. It is also worth noting that adding a Network printer located on a Windows 7 Pro 64 bit machine was also tested successfully.
However, updating the Windows 10 Pro 64 bit computer that is sharing it's printer, with the latest KB5007253 update, indeed repeats the same "Cannot Connect..." error that we have seen in all the other updates, when attempting to add this shared printer to another Windows 10 Pro 64 bit computer on the network that also has this update installed. The specific error is 0x0000011b.
Reverting and / or Uninstalling the KB5007253 on the Windows 10 Pro machine sharing it's printer, set the OS 21H1 level to 19043.1288 and DID NOT restore printing. In addition, viewing the installed updates, it now lists, KB5006670 as being installed, which was not the case prior to installing KB5007253. To make matter worse, KB5006670 is NOT Removable now.
To Restore network printing in my case, was fixed by stopping the Print Spooler, taking ownership of win32spl.dll, which is required to replace the file, then copying older file versions of "spoolsv.exe" and "win32spl.dll" from another machine, to the System32 folder. Then restarting the Print spooler after the files have been copied. I can't say this works in all cases. Seems that there are variations in what gets installed, and removed, to which I'm unaware specifically what is occurring. The file versions I used successfully were 1165 though I have read that slightly newer files also work.
This is what I've experienced at this point. The fact that it failed here, is reason enough for me to choose to not install, and or block this update. It is also reason to not test any further, as it has already failed at this basic level.
Way to go Microsoft.
henryga - 2 years ago
hello all: I am Honored that my Screen print that I posted on the Microsoft support forums was used here, but one thing that this article. does not represent was this screen print was taken from a windows 2019 server NOT a window 10 workstation. I am having this problem when try to map that DYMO printer that is connected to a windows 10 machine from a windows 2019 server.
While I know Bleeping Computer is all about workstations, does anyone have any idea how to attempt to fix this problem? When I try to Map the DYMO printer from the server it does not work (By the way ther DYMO printer works fine on my windows 10 machine). Since DYMO does not have Windows server drivers I cannot install it directly.
Any help or pointers to someone that can help me would be really helpful!!
Thanks
Gary
mightyz4rg - 2 years ago
I was excited to see something finally fixing our printer issues but sadly I had no success installing this update on a few test machines - still the same error when trying to add a printer.