Welcome to Microsoft Q&A!
Thank you for getting back to me and quickly update.
Based on the additional information you provided, there is an important distinction here:
- The Print Spooler starts but stops again.
- Reinstalling the printer drivers does not resolve the issue.
- Microsoft Print to PDF is also affected, so the problem is not limited to a particular physical printer or its driver.
- Printing starts working again after the November update is removed.
Because Microsoft Print to PDF and multiple applications are affected at the same time, this no longer appears to be an Excel, Word, Adobe, or single-printer configuration issue. The Print Spooler itself is the common Windows component involved in these printing operations. When this service fails, printers can become unavailable and printing can stop working.
The results you have already provided narrow the issue considerably.
The Print Spooler contains Windows components and can also load optional vendor-supplied components. Therefore, when the service starts and then terminates unexpectedly, determining the exact cause requires identifying what caused the spooler process to fail. This is a recommendation checking the relevant event logs when the Print Spooler cannot remain running and collecting diagnostic information when further investigation by Microsoft Support is required.
At this point, I would not recommend repeatedly reinstalling the printer drivers or repairing Office or Adobe applications. You have already tested the relevant documented troubleshooting, and the fact that Microsoft Print to PDF is also unavailable while the Print Spooler is failing indicates that repeating application-level troubleshooting is unlikely to provide additional useful information.
Since you have already demonstrated that removing the affected November update allows the Print Spooler and printing to work again, the rollback can be used as a temporary workaround while the underlying issue is investigated.
However, please treat this only as a temporary mitigation. Removing a Windows security update also removes the fixes contained in that update, so I would not consider remaining on the unpatched state to be a permanent resolution.
One final validation that will help the investigation
If possible, reproduce the problem on one affected device with the update installed and then open:
Event Viewer → Windows Logs → Application
And
Event Viewer → Windows Logs → System
Check the events generated at the exact time the Print Spooler stops, and record:
- Event ID
- Faulting application, particularly if it shows spoolsv.exe
- Faulting module or DLL
- Exception/error code
- Time of the failure
It is a recommendation examining event logs when the service fails to start correctly.
Moreover, I also want to be transparent about why I am directing you to Microsoft Support rather than continuing to give you additional troubleshooting steps.
This is not because I do not want to continue investigating the issue. Based on the information you provided and the troubleshooting already completed, I have reached the limit of what I can reliably investigate through a public Microsoft Q&A thread without simply asking you to repeat steps you have already performed.
The remaining question is no longer simply “how do I restart or reinstall the printer?” It is “what is causing the Print Spooler process to terminate on this particular Windows installation after the update is installed?”
Answering that reliably requires analysis of system diagnostic data, event information, and potentially diagnostic traces from the affected computer. Microsoft documentation recommends collecting diagnostic information for Microsoft Support when this level of Print Spooler investigation is required.
Microsoft Q&A is a public forum, so it is not an appropriate place to upload potentially sensitive diagnostic packages or system data. I do not want to speculate about an undocumented Windows root cause without the diagnostic evidence required to support that conclusion.
Therefore, for an organization-managed device, I recommend opening a Microsoft Support request so that the support engineer can securely collect and analyze the required diagnostic data.
I appreciate the time you have already spent testing and confirming these details. Your rollback test in particular is useful because it establishes a clear relationship between the installed Windows state and the printing failure, even though the available information is not sufficient for me to responsibly identify the exact underlying component through the forum.
References:
Fix print spooler service not running errors in Windows | Microsoft Support
Printing issues caused by Print Spooler service not running - Windows Server | Microsoft Learn
Fix printer connection and printing problems in Windows | Microsoft Support
If you find it useful, please click Accept Answer.
Thank you for choosing Microsoft Q&A.