Windows 8
- The Windows 7 client security group cannot be removed because it has not been configured for this entry point. Specify the ...
- The Windows 9x version of the CreateFileMapping API requires a SEC_COMMIT flag, while the Windows XP version does not. This ...
- The Windows All-User Install Agent cannot determine if user SID %1 is a valid user account. The Windows All-User Install ...
- The Windows All-User Install Agent could not delete the registered packages after the profile was deleted for user SID %1. ...
- The Windows All-User Install Agent could not register the package named %1 for the user account %2\%3. The error code is ...
- The Windows All-User Install Agent could not register the package named %1 for the user account %2\%3. The status is %4. ...
- The Windows All-User Install Agent could not remove %1 packages during the profile deletion of the user profile %2. The error ...
- The Windows All-User Install Agent could not retrieve user information from session %1. The package will not be updated. ...
- The Windows All-User Install Agent could not schedule a package registration for session %1 and the user account %2\%3. The ...
- The Windows All-User Install Agent could not schedule a package registration for the user acccount %1\%2 due to a security ...
- The Windows All-User Install Agent could not to retrieve a list of packages for the user account %1\%2. The error code is ...
- The Windows All-User Install Agent could not update the registration status for the package named %3 for the user account ...
- The Windows All-User Install Agent detected an attempt to delete a temporary or mandatory profile for user SID %1. Package ...
- The Windows All-User Install Agent detected an invalid user SID %1. All packages associated with this user SID will be unregistered. ...
- The Windows All-User Install Agent detected that the user account %1\%2 has been assigned a temporary or mandatory profile. ...
- The Windows All-User Install Agent is no longer waiting to register a package for user account %1\%2. The error code is %3. ...
- The Windows All-User Install Agent recovery request for the user account %1\%2 failed with the following error code: %3. ...
- The Windows All-User Install Agent starts package registration for user account %1\%2 because of new or updated application, ...
- The Windows All-User Install Agent starts package registration for user account %1\%2 because of recovery action, detail ...
- The Windows All-User Install Agent starts package registration for user account %1\%2 because of user has been assigned a ...
- The Windows All-User Install Agent successfully registered the package named %1 for the user account %2\%3. The registration ...
- The Windows Assessment Services results share could not be accessed. Results from previously run jobs might not be available ...
- The Windows Assessment Services shares are not configured. Please initialize the server again to correct the configuration. ...
- The Windows Biometric Credential Manager failed to remove a credential because the Windows Fingerprint Credential Provider ...
- The Windows Biometric Credential Manager failed to remove a credential for %2 (%1) due to the caller having insufficient ...
- The Windows Biometric Credential Manager failed to retrieve the credential state because the Windows Fingerprint Credential ...
- The Windows Biometric Credential Manager failed to retrieve the credential state for %2 (%1) due to the caller having insufficient ...
- The Windows Biometric Credential Manager failed to retrieve the state of a credential.%r%rThe operation failed with error: ...
- The Windows Biometric Credential Manager failed to store a credential because the Windows Fingerprint Credential Provider ...
- The Windows Biometric Credential Manager failed to store a credential for %2 (%1) due to the caller having insufficient privileges.%r%rThe ...
- The Windows Biometric Credential Manager failed to switch to the specified user because the Windows Fingerprint Credential ...
- The Windows Biometric Credential Manager failed to switch to the specified user.%r%rThe operation failed with error: %1. ...
- The Windows Biometric Credential Manager failed to switch to user %2 (%1) because they are already the interactive user. ...
- The Windows Biometric Credential Manager failed to switch to user %2 (%1) due to the caller having insufficient privileges.%r%rThe ...
- The Windows Biometric Service cannot complete a request because biometric operations are disabled by current system policy. ...
- The Windows Biometric Service cannot complete a request because Terminal Server client sessions are not allowed to access ...
- The Windows Biometric Service completed a privileged vendor-specific operation for sensor: %1.%r%rThe command was directed ...
- The Windows Biometric Service completed a vendor-specific operation for sensor: %1.%r%rThe command was directed to the biometric ...
- The Windows Biometric Service could not complete an identification operation using sensor: %1.%r%rThe operation failed with ...
- The Windows Biometric Service detected a missing or invalid biometric database configuration for sensor: %1.%r%rThe operation ...
- The Windows Biometric Service encountered an error while opening the database associated with sensor: %1.%r%rThe operation ...
- The Windows Biometric Service encountered an error while processing and updating an enrollment request using sensor: %1.%r%rThe ...
- The Windows Biometric Service failed to begin a capture operation using sensor: %1.%r%rThe operation failed with error: %8 ...
- The Windows Biometric Service failed to complete a capture operation using sensor: %1.%r%rThe operation failed with error: ...
- The Windows Biometric Service failed to complete a privileged vendor-specific operation for sensor: %1.%r%rThe command was ...
- The Windows Biometric Service failed to complete a vendor-specific operation for sensor: %1.%r%rThe command was directed ...
- The Windows Biometric Service failed to configure a Biometric Unit for sensor: %1.%r%rThe operation failed with error: %8%r%rSee ...
- The Windows Biometric Service failed to delete a database record for %9 (%8) on sensor: %1.%r%rThe operation failed with ...
- The Windows Biometric Service failed to initialize an adapter binary: %1.%r%rThe module's "%8" initialization routine failed ...
- The Windows Biometric Service failed to load an adapter binary: %1.%r%rThe module was not properly signed or its "Force Integrity" ...
- The Windows Biometric Service failed to set the mode of sensor: %1.%r%rThe operation failed with error: %8%r%rSee the "Details" ...
- The Windows biometric service gives client applications the ability to capture, compare, manipulate, and store biometric ...
- The Windows Biometric Service successfully created a Biometric Unit for sensor: %1%r%rThe sensor's mode is "%6," and its ...
- The Windows component "%1" could not be configured. The component installer returned an error: %2 "%3" (Command line: "%4") ...
- The Windows default exit module publishes certificates when they are issued. To publish a certificate, the publication location ...
- The Windows Deployment service was unable to create the service control point. The service will run with default settings ...
- The Windows Deployment Services Configuration Wizard detected Microsoft DHCP service running on the server. Please select ...
- The Windows Deployment Services Image Capture Wizard found an encrypted file. Because this file will not be readable to others, ...
- The Windows Deployment Services image server refreshed Image Cache successfully. The Windows Deployment Services server will ...
- The Windows Deployment Services multicast server successfully read its configuration settings. The Windows Deployment Services ...
- The Windows Deployment Services related data on the server appears corrupt. Please repair the Windows Deployment Services ...
- The Windows Deployment Services server failed to update the boot programs. Windows Deployment Services will not function ...
- The Windows Deployment Services server has failed rogue detection. The process completed successfully but it was determined ...
- The Windows Deployment Services server has successfully passed rogue detection. The server is authorized as a valid DHCP/PXE ...
- The Windows Deployment Services server received a request to re-read its configuration settings. The server was unable to ...
- The Windows Deployment Services server successfully applied its configuration settings from the Service Control Point object ...
- The Windows Deployment Services server successfully created a computer account in Active Directory Domain Services, but an ...
- The Windows Deployment Services server successfully created the Service Control Point object in Active Directory Domain Services. ...
- The Windows Deployment Services server successfully read its configuration information. The server will now process incoming ...
- The Windows Deployment Services server successfully read its configuration settings for the Active Directory Connection Manager. ...
- The Windows Deployment Services server successfully read its configuration settings. The Windows Deployment Services server ...
- The Windows Deployment Services server successfully read its settings from Active Directory Domain Services. However, none ...
- The Windows Deployment Services server was able to read its configuration settings. The server will now redetect its rogue ...
- The Windows Deployment Services server was able to successfully read configuration data for the boot images. The Windows ...
- The Windows Deployment Services server was able to successfully read the Auto Add Policy settings. The Windows Deployment ...