Troubleshooting Driver Isolation

Administrators can troubleshoot driver isolation issues using the event logs. By default, Admin logging for the PrintService is enabled in Windows 7 and Windows Server 2008 R2, and you should monitor the Application and System Event Logs for events coming from the print spooler.

To see additional events related to driver isolation activities, you can enable Operational logging as follows:

1. Open Event Viewer and expand the following:
   Application and Services\Logs\Microsoft\Windows\PrintService.
2. Right-click Operational and select Enable Log.

After you enable Operational logging, look for Informational Events with an Event ID of 842 and with a Source that is PrintService. This event indicates the Isolation mode that was used to print a particular print job and provides information such as the following.

The print job <x> was sent through the print processor <print processor name> on printer
<printer name>, driver <print driver name>, in the isolation mode <x> (0 - loaded in the
spooler, 1 - loaded in shared sandbox, 2 - loaded in isolated sandbox). Win32 error code
returned by the print processor: 0x0.