DonatShell
Server IP : 180.180.241.3  /  Your IP : 216.73.216.252
Web Server : Microsoft-IIS/7.5
System : Windows NT NETWORK-NHRC 6.1 build 7601 (Windows Server 2008 R2 Standard Edition Service Pack 1) i586
User : IUSR ( 0)
PHP Version : 5.3.28
Disable Function : NONE
MySQL : ON  |  cURL : ON  |  WGET : OFF  |  Perl : OFF  |  Python : OFF  |  Sudo : OFF  |  Pkexec : OFF
Directory :  /Windows/System32/en-US/

Upload File :
current_dir [ Writeable ] document_root [ Writeable ]

 

Command :

[ HOME SHELL ]     

Current File : /Windows/System32/en-US/ntprint.dll.mui
MZ@	!L!This program cannot be run in DOS mode.

$uEEELlDLl
DRichEPELJY!	 @
.rsrc@@0H	?@AC0DHL`RxXY				 	0	@	P	`	p			pD& "$D#V#T((\MUIWyThi3P8AU*ތWd'JMUIen-USAdd Printer WizardSelect the manufacturer and model of your printer. If your printer came with an installation disk, click Have Disk. If your printer is not listed, consult your printer documentation for a compatible printer.PrintersInstalling Port Monitor@The files installed are not valid for the selected architecture.Add Printer DriverUPlease provide a printer INF that contains the port monitor installation information._An error occurred installing port monitor '%s'. Please contact the manufacturer for assistance. Please provide a printer driver.AThere is no printer driver for the requested environment at '%s'.No printer drivers found%Install print drivers (x86 processor))Install print drivers (Itanium processor)%Install print drivers (x64 processor)Driver Installation WarningDriver Installation ErrorWindows can't install the %s kernel-mode print driver. To obtain a driver that is compatible with the version of Windows you are running, contact the manufacturer.Windows can't install the %s print driver. To obtain a driver that is compatible with the version of Windows you are running, contact the manufacturer.Internet PrintingActive Server Pages!Selected printer driver not found_The specified location does not contain the driver %s for the requested processor architecture.%Install Components From Windows media5Please provide path to Windows media (x86 processor).9Please provide path to Windows media (Itanium processor).5Please provide path to Windows media (x64 processor).pThe provided inbox printer INF does not contain the required driver components. Please provide a different path.OPlease provide the path to the original media containing the printer driver %s.CPlease provide a printer INF that contains the core printer driver.9Please provide the path containing the printer driver %s.PAUnsigned driver warningkWindows could not determine the publisher of this driver package. Are you sure that you want to install %s?IEEE 1394 and SCSI printersPAWindows needs to download and install a software driver from the %1 computer to print to %2.  Proceed only if you trust the %3 computer and the network.Windows needs to download and install a software driver from the %1 computer to print to %2.  Proceed only if you trust the %3 computer and the network.  For more information about installing drivers, see Help and Support.Windows needs to download and install a software driver from the %1 computer to print to %2.  Proceed only if you trust the %3 computer and the network, and then restart the print job.Printers&Cancel&Install driver&Don t show this againDo you trust this printer?(0113300
004008PPp	p4ppD	p'p	)p6p(dcehknorsvwz}h #`$&'p(3,C45EIJKRPXVb,edd@{gu~LНX\ĸ "P%BJWef($Local Spooler

(Remote Spooler

Printer

0Document Print Job

0Spooler Connection

$Print Driver

$Printer Setup

$Spooler Trace

4Classic Spooler Event

,Active Directory

Router

@Client Side Rendering (CSR)

4Print Filter Pipeline

$Print Spooler

4Print Driver Sandbox

$XPS Print API

<XPS Print API performance

$Response Time

WDI Diag

Info

Start

Stop

<Spooler Operation Started

@Spooler Operation Succeeded

<Spooler Operation Failed

(Spooler Warning

$Spooler Trace

HUnexpected process termination

4XPS Print API failure

Critical

Error

Warning

 Information

Verbose

DInitializing a print provider

<Opening a printer handle

<Closing a printer handle

,Adding a printer

0Deleting a printer

@Adding a printer connection

DDeleting a printer connection

8Adding a printer driver

<Deleting a printer driver

DStarting a document print job

@Ending a document print job

DStarting a new document page

8Ending a document page

<Seeking in the spool file

DSetting printer configuration

DParsing a printer driver inf

@Installing a printer driver

LCopying a printer driver package

4Enumerating printers

<Tracing a spooler message

,Pausing a printer

0Resuming a printer

HPurging jobs from printer queue

0Printing a document

0Deleting a document

0Adding a print form

4Deleting a print form

,Sharing a printer

0Unsharing a printer

HInitializing the print spooler

dPublishing a printer in the Active Directory

dRemoving a printer from the Active Directory

,Pruning a printer

$Initializing

HInitializing a print processor

lVerifying or regenerating a print driver package

LRouting print spooler command(s)

4Client-side rendering

hExecuting print filters in the spooler pipeline

4Print job diagnostics

`Process termination due to critical failure

4Deleting a directory

@Executing a file operation

HEnabling spooler RPC endpoints

|Client Side Rendering reverting to Server Side Rendering

DChanging the default printer

dIsolating printer drivers and other plug-ins

DExecuting XPS Print API calls

PXPS Print API performance tracking

`General print spooler performance tracking

8Print driver operation

HMicrosoft-Windows-PrintService

Admin

 Operational

Debug

XThe print spooler encountered a fatal error while executing a critical operation (%1, error %2) and must immediately terminate. Try to manually restart the print spooler service (from Control Panel | Administrative Tools | Services or from an elevated command prompt running: net start spooler).

Printer %3 successfully added. See the event user data for context information.

Failed to add printer %3, error code %2. See the event user data for context information.

Deleting printer %3 succeeded. See the event user data for context information.

Deleting printer %3 failed, error code %2. See the event user data for context information.

Starting document job %3 for printer %4 succeeded. See the event user data for context information.

Starting document job %3 for printer %4 failed, error code %2. See the event user data for context information.

Ending document job %3 for printer %4 succeeded. See the event user data for context information.

Ending document job %3 for printer %4 failed, error code %2. See the event user data for context information.

Adding printer driver %3 succeeded. See the event user data for context information.

Adding printer driver %3 failed, error code %2. See the event user data for context information.

Opening printer %3 succeeded. See the event user data for context information.

Opening printer %3 failed, error code %2. See the event user data for context information.

Starting page job %3 at printer %4 succeeded. See the event user data for context information.

Starting page failed at printer %3, error code %2. See the event user data for context information.

Ending page job %3 at printer %4 succeeded. See the event user data for context information.

Ending page job %3 at printer %4 failed, error code %2. See the event user data for context information.

Setting printer %3 failed, error code %2. See the event user data for context information.

Adding CSR printer connection %3 succeeded. See the event user data for context information.

Adding CSR printer connection %3 failed, error code %2. See the event user data for context information.

Deleting CSR printer connection %3 succeeded. See the event user data for context information.

Deleting CSR printer connection %3 failed, error code %2. See the event user data for context information.

Opening CSR printer %3 failed, error code %2. See the event user data for context information.

Closing CSR printer %3 succeeded. See the event user data for context information.

Closing CSR printer %3 failed, error code %2. See the event user data for context information.

Parsing inf (%4) for printer driver %5 succeeded (processor architecture %7). See the event user data for context information.

8Parsing inf (%4) for printer driver %5 failed (processor architecture %7), error code %8, HRESULT %9. See the event user data for context information.

Installing printer driver %5 succeeded. See the event user data for context information.

Installing printer driver %5 failed, error code %10, HRESULT %11. See the event user data for context information.

A printer setup operation succeeded during the installation process. See the event user data for context information.

$A printer setup operation failed during the installation process, error code %5, HRESULT %6. See the event user data for context information.

Copying printer driver package %5 succeeded. See the event user data for context information.

Copying printer driver package %5 failed, error code %8, HRESULT %9. See the event user data for context information.

Retrieving CSR cache information for printer %3 succeeded. See the event user data for context information.

Retrieving CSR cache information for printer %3 failed, error code %2. See the event user data for context information.

%1

A remote print driver package operation %1 failed with error code %2, server name %3. This was most likely caused by an unexpected error in the protocol communication between the client and the print server.

pPrinter %1 was created. No user action is required.

Printer %1 was deleted, and users will no longer be able to print to this printer. No user action is required.

xPrinter %1 will be deleted. No user action is required.

pPrinter %1 was paused. No user action is required.

pPrinter %1 was resumed. No user action is required.

The jobs in the print queue for printer %1 were deleted. No user action is required.

Settings for printer %1 were changed. No user action is required.

Document %1, %2 owned by %3 on %4 was printed on %5 through port %6.  Size in bytes: %7. Pages printed: %8. No user action is required.

8Document %1, %2 owned by %3 was paused on %4. This document will not print until the document owner resumes the print job. No user action is required.

Document %1, %2 owned by %3 was resumed on %4. No user action is required.

Document %1, %2 owned by %3 was deleted on %4. No user action is required.

(An administrator moved document %1, %2 owned by %3 to position %4 on %5. This changes when the document will print. No user action is required.

hForm %1 was added. No user action is required.

lForm %1 was removed. No user action is required.

Document %1, %2 owned by %3 timed out while printing on %4. The spooler waited for %5 milliseconds and no data was received.

The print spooler failed to share printer %2 with shared resource name %3. Error %1. The printer cannot be used by others on the network.

Printer driver %1 for %2 %3 was added or updated. Files:- %4. No user action is required.

Printer driver %1 was deleted. No user action is required.

DFailed to upgrade printer settings for printer %1 driver %2. Error: %3. The device settings for the printer are set to those configured by the manufacturer.

Printer %1 failed to initialize because a suitable %2 driver could not be found. The new printer settings that you specified have not taken effect. Install or reinstall the printer driver. You might need to contact the vendor for an updated driver.

@Printer %1 failed to initialize because none of its ports (%2) could be found. This can occur if the ports were deleted or the port information is invalid.

File(s) %1 associated with printer %2 were added or updated. No user action is required.

 While attempting to publish the printer to the Active Directory directory service, Windows failed to publish property %1 at %2.  Error: %3

pWhile attempting to publish the printer to the Active Directory directory service, the print spooler could not create or update the print queue because Windows failed to bind to container: %1.  Error: %2. The printer is not published in Active Directory and cannot be located by searching Active Directory.

$While attempting to remove the printer from the Active Directory directory service, Windows failed to delete print queue %1 at %2.  Error: %3

4While attempting to publish the printer to the Active Directory directory service, the print spooler could not create or update the print queue under container %1.  Error: %2. The printer is not published in Active Directory and cannot be located by searching Active Directory.

|While attempting to publish the printer to the Active Directory directory service, the print spooler could not create print queue %1 under container %2 because Mandatory properties could not be set.  Error: %3. The printer is not published in Active Directory and cannot be located by searching Active Directory.

While attempting to publish the printer to the Active Directory directory service, the print spooler could not find the appropriate print queue container because the primary domain query failed. Error: %1. This can occur if Domain Name System (DNS) cannot resolve the domain controller IP address, or if the domain controller or directory service is not functioning correctly. The printer is not published in Active Directory and cannot be located by searching Active Directory.

While attempting to publish the printer to the Active Directory directory service, the print spooler could not find the appropriate print queue container because the Domain Name System (DNS) domain name could not be retrieved. Error: %1. This can occur if DNS cannot resolve the domain controller IP address, or if the domain controller or directory service is not functioning correctly. The printer is not published in Active Directory and cannot be located by searching Active Directory.

<While attempting to publish the printer to the Active Directory directory service, the print spooler could not find the appropriate print queue container on domain %1.  Error: %2. The printer is not published in Active Directory and cannot be located by searching Active Directory.

`The printer was successfully published to the Active Directory directory service. The print queue %1 was successfully created in container %2. No user action is required.

,While attempting to publish the printer to the Active Directory directory service, the print spooler failed to create or update print queue %1 in container %2.  Error: %3. The printer is not published in Active Directory and cannot be located by searching Active Directory.

The printer was successfully removed from the Active Directory directory service. Print queue %1 was successfully deleted from container %2. The printer can no longer be located by searching Active Directory. No user action is required.

PWhile attempting to remove the printer from the Active Directory directory service, the print spooler failed to delete print queue %1 from container %2.  Error: %3

Print queue %1 was successfully updated in the Active Directory directory service container %2. No user action is required.

tThe print queue could not be found on domain %1.  It may have been deleted from the Active Directory directory service. Windows will attempt to republish the print queue.  Error: %2

lPrinter %1 was successfully removed from the Active Directory directory service. The printer can no longer be located by searching Active Directory. No user action is required.

The print spooler removed print queue %1 from the Active Directory directory service because it does not have a Universal Naming Convention (UNC) name or server name listed. No user action is required.

The print spooler was unable to connect to print queue %1 based on the information published in the Active Directory. Error %2. No user action is required. If this print queue continues to be unreachable it may be removed from Active Directory.

The print spooler removed print queue %1 from the Active Directory directory service. No user action is required.

PThe print spooler removed print queue %1 from the Active Directory directory service because it is a duplicate of another print queue. No user action is required.

The print spooler removed print queue %1 from the Active Directory directory service. No user action is required.

Print queue %1 could not be deleted (pruned) from the Active Directory directory service.  Error: %2. The spooler will periodically try to remove the entry until it is successful. Continued failures may indicate an Active Directory problem, a basic network problem, or a communication problem between the domain controller and the print server.

This version of %1 is incompatible with this version of Windows. Please obtain and install a new version of the driver from the manufacturer (if available), or choose an alternate driver that works with this print device.

@The print spooler failed to create a symbolic link between HKEY_LOCAL_MACHINE\\System\\CurrentControlSet\\Control\\Print\\Printers and HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Windows NT\\CurrentVersion\\Print\\Printers. Error %1. This only affects older applications, but is probably a sign that the system itself is in a poor condition or that the print spooler does not have the proper registry permissions.

4Document %1 failed to print and was deleted because of corruption in the spooled file. The associated driver is: %2. Try printing the document again.

tThe attempt for %1 to use a Windows NT 4.0 (kernel mode) driver failed because this version of Windows does not support Windows NT 4.0 printer drivers. Please obtain and install a new version of the driver from the manufacturer (if available), or choose an alternate driver that works with this print device.

HThe priority of document %1, %2 owned by %3 was changed to %4 on %5. Windows prints the document with the highest priority number before other print jobs with lower priority numbers. Documents that are currently printing are unaffected by changes in priority. No user action is required.

The document failed to print because the user did not have the necessary privileges.

%1 initialization failed at %2. Error: %3. This can occur because of system instability or a lack of system resources.

Failed to install or update driver %1 on cluster spooler resource %2. Win32 error: %3. The printer driver is different from the driver in use on other computers (nodes) in the cluster. This can occur because of a transient failure in replication between nodes, or if the nodes are running Windows 2000 (which does not automatically replicate drivers).

The attempt to install printer %1 into an offline operating system image failed with Win32 error code %2. This can occur if the printer driver requires user input or displays a user interface (UI) during installation.

XUpdating the color profile failed for printer %1 with Win32 error code %2. The colors printed may not be correctly matched to the colors in the document being printed.

Printer %1 failed to initialize its ports. Win32 error: %2. This error usually occurs because of a problem with the port monitor. Try recreating the port using a standard TCP/IP printer port, if possible. This problem does not affect other printers.

The print spooler could not initialize because resolving the local machine name to IP addresses failed with error code %1. This may be a transient error. Try to manually restart the print spooler service (from Control Panel | Administrative Tools | Services or from an elevated command prompt running: net start spooler).

The print spooler %1 failed to start. To determine the cause of this error, examine the preceding events in the Event Log.

Windows could not load print processor %1 because EnumDatatypes did not return any data. Module: %2. Please obtain and install a new version of the driver from the manufacturer (if available), or choose an alternate driver that works with this print device.

Windows could not load print processor %1 because EnumDatatypes failed. Error code %2. Module: %3. Please obtain and install a new version of the driver from the manufacturer (if available), or choose an alternate driver that works with this print device.

The print server security descriptor for %1 is invalid. The default print server security descriptor will be used.

Windows could not initialize printer %1 because the print processor %2 could not be found. Please obtain and install a new version of the driver from the manufacturer (if available), or choose an alternate driver that works with this print device.

The print spooler failed to verify printer driver package %1 for environment %2. Win32 system error code %3. This can occur after an operating system upgrade or because of data loss on the hard drive. The print spooler will try to regenerate the driver information from the driver store, which is where drivers are saved before they are installed. No user action is required.

The print spooler failed to verify printer driver package for environment %1. Win32 system error code %2. This can occur because of insufficient memory or other system failures. No user action is required.

The print spooler failed to regenerate the printer driver information for driver %1 for environment %2. Win32 system error code %3. This can occur after an operating system upgrade or because of data loss on the hard drive.

The print spooler failed to unshare printer %2 which is shared as %3. Error %1.

The document %1, owned by %2, failed to print on printer %3. Try to print the document again, or restart the print spooler. %nData type: %4. Size of the spool file in bytes: %5. Number of bytes printed: %6. Total number of pages in the document: %7. Number of pages printed: %8. Client computer: %9. Win32 error code returned by the print processor: %10. %11

The spooler has detected that a component has an unusually large number of open Graphical Device Interface (GDI) objects. As a result, some enhanced metafile (EMF) print jobs might not print until the spooler is restarted.

The print spooler failed to get the computer name. Error %2. This can occur due to system instability or a lack of system resources.

(The system failed to initialize the local print provider: Error %2. This can occur because of system instability or a lack of system resources.

Failed to initialize the router work crew: Error %2. This can occur because of system instability or a lack of system resources.

<Failed to create Phase2Init event in WaitForSpoolerInitialization: Error %2. This can occur because of system instability or a lack of system resources.

The system failed to initialize the name cache: Error %2. This can occur because of system instability or a lack of system resources.

Failed to initialize the router cache: Error %2. This can occur because of system instability or a lack of system resources.

`The print spooler cannot start because the PrinterBusEnumerator could not start. Error code %2. This can occur because of system instability or a lack of system resources.

InitializeProvider cannot allocate memory for %1. This can occur because of system instability or a lack of system resources.

The print spooler failed to load print provider %1. This can occur because of system instability or a lack of system resources.

InitializePrintProvider failed for provider %1. This can occur because of system instability or a lack of system resources.

Group Policy was unable to add per computer connection %1. Error code %2. This can occur if the name of the printer connection is incorrect, or if the print spooler cannot contact the print server.

Group Policy was unable to delete per computer connection %1. Error %2. This can occur if the name of the printer connection is incorrect, or if the print spooler cannot contact the print server.

Group Policy was unable to delete per computer printer connection %1. Error %2. The printer connection is still available to users on this computer. This can occur if the name of the printer connection is incorrect, if there is a Group Policy problem, or if the print spooler cannot contact the print server. Group Policy will periodically retry deleting the printer connection.

Group Policy was unable to deploy per computer printer connection %1. Error %2. The printer connection is not available to users on this computer. This can occur if the name of the printer connection is incorrect, if there is a Group Policy problem, or if the print spooler cannot contact the print server. Group Policy will periodically retry adding the printer connection.

Group Policy was unable to update per computer printer connection %1. Error code %2. This can occur if the name of the printer connection is incorrect, if there is a Group Policy problem, or if the print spooler cannot contact the print server. Group Policy will periodically retry updating the printer connection.

Group Policy was unable to delete the per user printer connection %1. Error code %2. The printer connection is still available to users on this computer. This can occur if the name of the printer connection is incorrect, if there is a Group Policy problem, or if the print spooler cannot contact the print server. Group Policy will periodically retry deleting the printer connection.

TGroup Policy was unable to deploy per user printer connection %1. Error code %2. The printer connection is not available to the users on this computer to which the Group Policy object applies. This can occur if the name of the printer connection is incorrect, if there is a Group Policy problem, or if the print spooler cannot contact the print server. Group Policy will periodically retry adding the printer connection.

xGroup Policy was unable to update per user printer connection %1. Error code %2. This can occur if the name of the printer connection is incorrect, if there is a Group Policy problem, or if the print spooler cannot contact the print server. Group Policy will periodically retry updating the printer connection.

The print spooler failed to import the printer driver that was downloaded from %1 into the driver store for driver %2. Error code= %3. This can occur if there is a problem with the driver or the digital signature of the driver.

The print spooler failed to download and import the printer driver from %1 into the driver store for driver %2. Error code= %3.

The print spooler failed to reopen an existing printer connection because it could not read the configuration information from the registry key %1\%2. This can occur if the key name or values are malformed or missing.

lThe print spooler failed to reopen an existing printer connection because it could not read the configuration information from the registry key %1. The print spooler could not open the registry key. This can occur if the registry key is corrupt or missing, or if the registry recently became unavailable.

(The print spooler encountered an unknown driver type while saving %1 cache information. This can occur because of a protocol or network error.

tThe print filter pipeline host cannot initialize with the Component Object Model (COM) system. Error %1. This can occur because of system instability or a lack of system resources.

LThe print filter pipeline host is shutting down due to the following error: Error %1. This can occur because of system instability or a lack of system resources.

The print filter pipeline host is shutting down due to an error in signaling the Component Object Model (COM) proxy in the spooler. Error %1. This can occur because of system instability or a lack of system resources.

The print filter pipeline host is shutting down because the query interface for ISignal in the Component Object Model (COM) proxy in the spooler failed. Error %1. This can occur because of system instability or a lack of system resources.

,Spooling job %1.

,Printing job %1.

,Deleting job %1.

,Rendering job %1.

(Pausing job %1.

,Resuming job %1.

The print spooler failed to load a plug-in module %1, error code %2. See the event user data for context information.

The print spooler failed to recursively delete the directory %1, error code %2. See the event user data for context information.

$The print spooler failed to delete the directory %1 and the contained files, error code %2. See the event user data for context information.

The print spooler failed to move the file %1 to %2, error code %4. See the event user data for context information.

The print spooler failed to delete the file %1, error code %4. See the event user data for context information.

The print spooler failed to copy the file %1 to %2, error code %4. See the event user data for context information.

The print spooler failed to install the print processor %1 %2 %3, error code %4.

,The print spooler service failed to register the RPC server protocol sequence %1, error code %3. See the event user data for context information.

The print spooler service detected an invalid RPC protocol sequence %1, expecting %2, error code %3.

The RPC end-point policy for the print spooler service is disabled. See the event user data for context information.

The print spooler RPC server failed to start, error code %1. See the event user data for context information.

Client Side Rendering is currently disabled by policy (%1).

TClient side rendering to %1 failed, error code %4. The print spooler service will retry server side rendering. See the event user data for more context information.

dThe print spooler Client Side Rendering is attempting to render the job %1 on the server (Server Side Rendering), status %3. See the event user data for context information.

@Unknown print processor (%1) or invalid data type (%4), error %7, Client Side Rendering is disabled. See the event user data for more context information.

The default printer was changed to %3. See the event user data for context information.

0A fatal error occurred while printing job %1, id %2 on the print queue %3. The print filter pipeline process was terminated. Error information: %4.

\Client side rendering to %1 failed, error code %4. The print spooler service will not retry server side rendering. See the event user data for more context information.

Force Client Side Rendering policy was successfully set on printer %1, path %2, port %3.

\The specified print queue %1 is invalid.

`The print job %1 failed with error code %2.

DXPS API call %1 (%2) started.

XXPS API call %1 (%2) ended, status %3.

PXPS API dependency %1 (%2) started.

dXPS API dependency %1 (%2) ended, status %3.

\Print spooler operation %1 (%2) started.

lPrint spooler operation %1 (%2) ended, status %3.

The print job %1 was sent through the print processor %2 on printer %3, driver %4, in the isolation mode %5 (0 - loaded in the spooler, 1 - loaded in shared sandbox, 2 - loaded in isolated sandbox). Win32 error code returned by the print processor: %6.

The print spooler service recorded %1 successful and %2 failed RPC requests for all active print driver sandbox hosts.

dThe print spooler selected the isolation mode %1 (0 - loaded in the spooler, 1 - loaded in shared sandbox, 2 - loaded in isolated sandbox) for printer %2, printer driver %3.

Attempted to load module %1 for printer %2, printer driver %3. Win32 error code %4.

Cached printer %1 has been scavenged and deleted. This printer's age (%2 seconds) has surpassed the expiry age of %3 seconds.

$Cached printer %1 has been scheduled for deletion due to a logon scavenging operation. This printer is no longer referenced in the registry.

lPrinter %1 was shared by the print spooler as %2.

Printer %1 shared as %2 was unshared by the print spooler.

XThe print spooler called the function %2 in print driver module %1. This call initialized the Component Object Model (COM) system without properly un-initializing it.

Point and Print not allowed by policy for queue %1. Cannot make a Point and Print connection to this queue. Error %2.

XDriver %1 could not be installed for printer connection %3. The print system selected the replacement driver %2 for the printer connection. No user action is required.

Print Client Side Rendering synchronization for print job cache completed with code %1 for printer %2.

Print Client Side Rendering synchronization for printer information cache completed with code %1 for printer %2.

OpenPrinter cache entry added for printer %1 with access code %2.

0In VALIDATINGDRVINFO, Adding printer driver %3 failed, error code %2. See the event user data for context information. Driver has no valid catalog

0The print spooler failed to download package for driver %1. Error code= %2. Blocking driver as there could be a possibility of potential tampering.

4VS_VERSION_INFOQ]Q]?StringFileInfo040904B0LCompanyNameMicrosoft CorporationLFileDescriptionSpooler Setup DLLr)FileVersion6.1.7601.23889 (win7sp1_ldr.170810-1615)8InternalNameNTPRINT.DLL.LegalCopyright Microsoft Corporation. All rights reserved.HOriginalFilenamePRINTUI.DLL.MUIj%ProductNameMicrosoft Windows Operating SystemBProductVersion6.1.7601.23889DVarFileInfo$Translation	PADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPAD

Anon7 - 2022
AnonSec Team