Windows 8.1

  1. The Windows Push Notification Platform has started loading file data: count applications %1, count allocated entries %2, ...
  2. The Windows RE image cannot be stored in the specified volume. Use the RETAIN command in DISKPART to prepare the volume and ...
  3. The Windows Registry key {0} cannot be changed. Verify that that you are logged on by using an account that has permissions ...
  4. The Windows Registry key {0} does not exist. No action is required to reverse the registration of Windows Server Migration ...
  5. The Windows Remote Management (WinRM) service cannot be configured for remote access because Group Policy does not allow ...
  6. The Windows Remote Shell cannot process the request because it requires the following selector: %1. Retry with the correct ...
  7. The Windows Remote Shell cannot process the request. It is not permitted for other users then the initial creator to make ...
  8. The Windows Remote Shell cannot process the request. The computed response packet size exceeds the maximum envelope size ...
  9. The Windows Remote Shell cannot process the request. The resource URI is not valid or the service cannot find the resource ...
  10. The Windows Remote Shell cannot process the request. The server attempted to apply the quota limits for the Remote Shell ...
  11. The Windows Remote Shell cannot process the request. The server exceeded the maximum number of users concurrently performing ...
  12. The Windows Remote Shell cannot process the request. The server is already executing the maximum number of concurrent shells ...
  13. The Windows Remote Shell cannot process the request. The SOAP packet contains an element %1 that is invalid. Retry the request ...
  14. The Windows Remote Shell cannot process the request. The WS-Addressing action URI is invalid. The valid actions are Command, ...
  15. The Windows Remote Shell received a request to perform an operation on a command identifier that does not exist. Either the ...
  16. The Windows Resource Exhaustion Resolver received a notification that the computer is low on virtual memory. This notification ...
  17. The Windows Resource Exhaustion Resolver received a notification to perform memory leak diagnosis. This notification was ...
  18. The Windows Rights Management Client software could not be accessed correctly. This could be a problem with the viewer and ...
  19. The Windows Rights Management Client software could not be configured correctly. This could be a problem with the viewer ...
  20. The Windows Rights Management Client software could not be opened correctly. Contact your system administrator for help in ...
  21. The Windows Rights Management Client software could not read the certificate. This could indicate a problem in XPS Viewer ...
  22. The Windows Rights Management Client software is not installed correctly. Reinstall the Windows Rights Management Client ...
  23. The Windows Rights Management client software is out-of-date. Install a current version of the Windows Rights Management ...
  24. The Windows Rights Management Client software was not installed correctly. Reinstall the Windows Rights Management Client ...
  25. The Windows Scheduled Maintenance Task performs periodic maintenance of the computer system by fixing problems automatically ...
  26. The Windows Scripted Diagnostic Provider API IDiagnosticProvider failed to cancel the connected diagnostic provider with ...
  27. The Windows Scripted Diagnostic Provider API IDiagnosticProvider failed to cancel the local diagnostic provider with error ...
  28. The Windows Scripted Diagnostic Provider API IDiagnosticProvider FindDiagnosticsBySearchMetadata method failed because the ...
  29. The Windows Scripted Diagnostic Provider API IDiagnosticProvider FindDiagnosticsBySearchMetadata method failed because the ...
  30. The Windows Scripted Diagnostic Provider API IDiagnosticProvider FindDiagnosticsBySearchMetadata method failed with error ...
  31. The Windows Scripted Diagnostic Provider API IDiagnosticProvider FindDiagnosticsBySearchMetadata method failed. The input ...
  32. The Windows Scripted Diagnostic Provider API IDiagnosticProvider FindDiagnosticsBySearchMetadata method succeeded. The input ...
  33. The Windows Scripted Diagnostic Provider API IDiagnosticProvider FindDiagnosticsBySearchMetadata method was canceled by the ...
  34. The Windows Scripted Diagnostic Provider API IDiagnosticProvider object property QueryRemoteServer is being overridden by ...
  35. The Windows Scripted Diagnostic Provider API IDiagnosticProvider object property QueryRemoteServer is being overridden by ...
  36. The Windows Search Service cannot initialize multi-instancing in Jet. If the application is used in a cluster environment, ...
  37. The Windows Search Service failed to move Index files from %2 to %3 with the following error: . This might be because the ...
  38. The Windows Search Service has failed to create one or more path rules. The service will continue creating the SystemIndex ...
  39. The Windows Search service stopped the Protocol Host process because it was consuming too many resources. A new Protocol ...
  40. The Windows Security Center detected a system health state change. The change in state was also successfully detected by ...
  41. The Windows Security Center Service was unable to establish event queries with WMI to monitor third party AntiVirus, AntiSpyware ...
  42. The Windows Security Health Agent failed to notify the Windows Network Access Protection Service of a change in the security ...
  43. The Windows Security Health Agent failed to process a response from the Windows Security Health Validator. Failure Code: ...
  44. The Windows Security Health Agent failed to specify a new security health state for the computer. Failure Code: %1. The correlation ...
  45. The Windows Security Health Agent notified the Windows Network Access Protection Service of a change in the security health ...
  46. The Windows Security Health Agent specified a new security health state for the computer. The correlation id for this transaction ...
  47. The Windows Security Health Agent successfully processed a response from the Windows Security Health Validator. The correlation ...
  48. The Windows Security Health Agent was initialized successfully. Scan Interval: %1 minutes. Time delay before first scan: ...
  49. The Windows Security Health Validator could not process the latest Statement of Health (SoH) because the SoH is invalid. ...
  50. The Windows Server 2012 R2 forest functional level provides all the features that are available in the Windows Server 2012 ...
  51. The Windows Server Backup engine is not accessible on the computer that you want to manage backups on. Make sure that you ...
  52. The Windows Server Backup engine is not accessible. Make sure that you are a member of the Administrators or Backup Operators ...
  53. The Windows Server Backup infrastructure encountered an error that prevented the wizard from retrieving the backup information. ...
  54. The Windows Server Backup snap-in cannot connect to the Block Level Backup Engine Service on a computer that is running a ...
  55. The Windows Server Backup snap-in cannot connect to the Block Level Backup Engine Service on a computer that is running the ...
  56. The Windows Server Essentials Client Computer Management Service is the long running service on client computers that helps ...
  57. The Windows Server Essentials Client Computer Monitoring Service is the centralized monitoring pivot for client computer ...
  58. The Windows Server Essentials Computer Backup Service encountered an error when reading a cluster during the restore operation. ...
  59. The Windows Server Essentials Computer Backup Service encountered the following error: Error code: %1 API name: %2 Error: ...
  60. The Windows Server Essentials Computer Backup Service encountered the following error: Error code: %1 API name: %2 File: ...
  61. The Windows Server Essentials Computer Backup Service helps you backup data from and restore data to a client computer. If ...
  62. The Windows Server Essentials Computer Backup Service is currently busy. If you move this folder now, the backup or restore ...
  63. The Windows Server Essentials Computer Backup service is not running. You cannot back up client computers until you start ...
  64. The Windows Server Essentials Email Service may not start if the startup type is not set to the default value of Automatic. ...
  65. The Windows Server Essentials has already been deployed and configured as virtual machine {0}. Please open or create a remote ...
  66. The Windows Server Essentials has been installed as virtual machine {0}. Please continue to configure the Windows Server ...
  67. The Windows Server Essentials Health Service evaluates key health criteria and generates alert notifications when an important ...
  68. The Windows Server Essentials Management Service is the centralized management pivot for Windows Server Essentials Experience ...
  69. The Windows Server Essentials Notifications Provider Service manages the Notifications Provider Service for the Windows Server ...
  70. The Windows Server Essentials Provider Registry Service registers and enables discoverability of server role services and ...
  71. The Windows Server Migration Tools deployment folder could not be created. Verify that you are logged on by using an account ...
  72. The Windows Server Migration Tools deployment folder was created successfully at {0}. For more information about how to set ...
  73. The Windows Server virtual machine you are about to create for use as a domain controller has an End User License Agreement ...
  74. The Windows Setup component cannot be added. The answer file is not associated with a Windows image. The configuration set ...
  75. The Windows Store Service cannot process requests after a rearm until the machine has been rebooted to avoid creating a bad ...