Stop sevices Printer Spooler after update KB5132043

Question

Stop sevices Printer Spooler after update KB5132043

Kien Nguyen Trung 0

After installing KB5132043, printers show 'Not connected' and cannot print. Uninstalling KB5132043 resolves the issue.

0 comments

2 answers

Your answer

Answer 1

Hi Kien,

Since the Print Spooler service stops after installing KB5132043 and printing works again after uninstalling it, we recommend investigating a possible printer driver or service compatibility issue. However, Microsoft currently lists no known issues with this update.

Please try the following:

Open services.msc and check the Print Spooler service status.
If stopped, try starting it and note any error message.
Check Event Viewer → Applications and Services Logs → Microsoft → Windows → PrintService for related errors.
Update the printer drivers using the manufacturer's latest supported versions.

Documentations for reference.

Hope this helps!

Ronald

Answer 2

KB5132043 is a Windows 11 Hotpatch with no currently documented printing issue, so after the already-tested uninstall, temporarily pause its redeployment and reset the Print Spooler before testing the update again on one device. Microsoft lists KB5132043 for Windows 11 versions 24H2, 25H2, and 26H2 and currently reports no known issues with it.^1^

1. Reset the Print Spooler

Run PowerShell as administrator:

Stop-Service Spooler -Force
Remove-Item "$env:WINDIR\System32\spool\PRINTERS\*" `
    -Force -ErrorAction SilentlyContinue
Set-Service Spooler -StartupType Automatic
Start-Service Spooler
Get-Service Spooler

Deleting the spool files discards pending print jobs, but does not remove installed printers. Microsoft documents stopping the service, clearing %WINDIR%\System32\spool\PRINTERS, and restarting it with startup type set to Automatic.^2^

The final command should show:

Status: Running
Name: Spooler

Then open Settings → Bluetooth & devices → Printers & scanners, select the printer, and print a test page.

2. If the Spooler stops again

Do not repeatedly restart it without identifying the component causing the termination.

Open Event Viewer.
Check:
- Windows Logs → System
- Windows Logs → Application
Find events at the exact time spoolsv.exe stopped.
Record:
- Event ID
- Faulting application and module
- Driver DLL or print monitor named in the event
- Printer model and connection type
Check whether Group Policy is disabling the service:
```
   gpresult /h "%TEMP%\gpresult.html"
```
Open the report and examine computer policies affecting printing or system services.

Microsoft identifies Group Policy, outdated drivers, antivirus interference, system instability, and vendor-supplied spooler components as relevant checks when the service will not remain running.^3^

If an event names a printer-driver DLL, remove that printer and its old or duplicate driver under Device Manager → Print queues/Printers, then install the current package from the printer manufacturer. Windows guidance specifically recommends removing conflicting or obsolete drivers when the spooler crashes.^4^

3. Control deployment while testing

Because removing KB5132043 restores printing, keep it off production devices temporarily while reproducing the problem on a pilot device. On an unmanaged test device, use Settings → Windows Update → Pause updates → Pick a date. This is temporary; Windows will resume update installation when the pause ends.^5^

Compare these states on the pilot:

Before KB5132043: confirm the Spooler remains running and printing works.
After KB5132043: capture the Spooler status and corresponding Event Viewer errors.
If the failure consistently returns only after installation, retain the before/after event details and affected printer-driver versions.

Report the reproducible behavior through Feedback Hub by pressing Windows+F, and attach screenshots or a recording plus the event details. Feedback Hub is the supported channel for reporting unexpected Windows behavior; immediate guided assistance should go through Microsoft Support.^6^

References