Event Id | 1033 |
Source | Microsoft-Windows-SpoolerSpoolss |
Description | The print spooler cannot start because the PrinterBusEnumerator could not start. Error code %1. This can occur because of system instability or a lack of system resources. |
Event Information | According to Microsoft : Cause : This event is logged when the print spooler cannot start because the PrinterBusEnumerator could not start. Resolution : Check resource availability Windows printing could not allocate sufficient resources for an operation or was processing an upgrade. No immediate action is required. If problems persist, determine whether the computer is low on system resources such as CPU resources, disk I/O performance, or memory, and consider restarting the server after notifying users. To do this, use the procedures in the following sections to generate a System Diagnostics Report, which presents system information collected for 60 seconds, or to use Resource Monitor to monitor system resources in real time. To perform these procedures, you must be a member of the local Administrators group on the print server, or you must have been delegated the appropriate authority. Generate a System Diagnostics Report To collect system information for 60 seconds and generate a System Diagnostics Report:
To start Resource Monitor:
Perform the following tasks to verify that you resolved the problem:
|
Reference Links | Event ID 1033 from Source Microsoft-Windows-SpoolerSpoolss |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.