Windows 8.1

  1. Windows was unable to read the drive header for physical drive %1. If you know the drive is still usable, then resetting ...
  2. Windows was unable to read the Windows Management Instrumentation (WMI) filter information associated with the Group Policy ...
  3. Windows was unable to remove properties from the new copies of the selected files. Before sharing these files, you should ...
  4. Windows was unable to remove properties from the selected files. Before sharing these files, you should review them for unwanted ...
  5. Windows was unable to save data for file %2. The data has been lost. This error may be caused by a failure of your computer ...
  6. Windows was unable to save the changes to the device. Make sure the device is connected to the computer, and then try again. ...
  7. Windows was unable to scan the drive. Close this dialog box, and then try to scan the drive again. If the problem persists, ...
  8. Windows was unable to successfully evaluate whether this computer is a primary computer for this user. This may be due to ...
  9. Windows was unable to successfully evaluate whether this computer is a primary computer for this user. This may be due to ...
  10. Windows will attempt to rebuild any virtual disks that store data on this physical disk. For this to succeed, the storage ...
  11. Windows will automatically search for the latest drivers and applications for your hardware and download them to your computer. ...
  12. Windows will back up data files saved in libraries, on the desktop, and in default Windows folders. These items will be backed ...
  13. Windows will back up data files saved in libraries, on the desktop, and in default Windows folders. Windows will also create ...
  14. Windows will check for routine maintenance issues and remind you when the System Maintenance troubleshooter can help fix ...
  15. Windows will create a system image, which can be used to restore your computer if it stops working. These items will be backed ...
  16. Windows will now log you off to finish moving Temporary Internet Files. Do you want to continue? (All other changes have ...
  17. Windows will send a description of each problem to Microsoft and look for steps you can take to solve it. Sending information ...
  18. Windows won't install unless each of these things is taken care of. Close Windows Setup, take care of each one, and then ...
  19. Windows(R) failed a request to access system resources associated with the Network File System (NFS) network provider. If ...
  20. Windows(R) failed a request to allocate memory. RPC Port Mapper cannot start. Network File System (NFS) clients use RPC Port ...
  21. Windows(R) failed a request to clean up after completing tasks for client %1. To ensure internal consistency, Client for ...
  22. Windows(R) failed a request to communicate with the Network File System (NFS) redirector. If this problem persists, users ...
  23. Windows(R) failed a request to create a security descriptor %1. Client for NFS cannot start. Windows may be low on system ...
  24. Windows(R) failed a request to create a supporting process thread %1. Client for NFS cannot start. Windows may be low on ...
  25. Windows(R) failed a request to initialize the Network File System (NFS) redirector %1. Client for NFS cannot start. Windows ...
  26. Windows(R) failed a request to load the Network File System (NFS) driver. Server for NFS cannot start. Windows may be low ...
  27. Windows(R) failed a request to open a communications port to the Network File System (NFS) redirector %1. Client for NFS ...
  28. Windows(R) failed a request to provide RPC Port Mapper with the IP address for the local host. RPC Port Mapper cannot start. ...
  29. Windows(R) failed a request to register RPC Port Mapper on TCP port 111. RPC Port Mapper cannot start. Network File System ...
  30. Windows(R) failed a request to register RPC Port Mapper on User Datagram Protocol (UDP) port 111. RPC Port Mapper cannot ...
  31. Windows(R) failed a request to unload the Network File System (NFS) redirector while Client for NFS was stopping %1. Client ...
  32. Windows(R) Lightweight Directory Access Protocol (LDAP) failed a request to connect to Active Directory Domain Services(R) ...
  33. Windows(R) RPC Port Mapper service (also known as Portmap and Rpcbind) has completed registration of all dynamic interfaces. ...
  34. Windows(R) RPC Port Mapper service has completed starting but has not yet registered any interfaces. Interface registration ...
  35. Windows(R) Sockets failed a request to initialize %1. Client for NFS cannot start. Windows may be low on system resources. ...
  36. Windows.Graphics.Printing.PrintManager must be retrieved and initialized with a PrintTaskRequested event handler prior to ...
  37. Windows.System.Launcher.LaunchFileAsync failed because the current group policy settings prohibit launching desktop programs ...
  38. Windows.System.Launcher.LaunchUriAsync failed because the current group policy settings prohibit launching desktop programs ...
  39. Windows.System.Launcher.LaunchUriAsync failed because URI %1 points to a local resource. Local zone URIs are not supported ...
  40. Windows.System.Launcher.LaunchUriAsync failed because URI %1 points to an intranet network resource. In order to launch intranet ...
  41. Wingate 4.1.0 has a known compatibility issue with this version of Windows. For an update that is compatible with this version ...
  42. WinHTTP implements the client HTTP stack and provides developers with a Win32 API and COM Automation component for sending ...
  43. Winmd file %1 is missing "WindowsRuntime 1.3" or "WindowsRuntime 1.2" in its version string. The version string in the file ...
  44. WinRM cannot complete the operation. Verify that the specified computer name is valid, that the computer is accessible over ...
  45. WinRM cannot make the configuration change because the Issuer used for the certificate mapping operation is not valid. The ...
  46. WinRM cannot make the configuration change. The credential used for updating or creating the certificate mapping configuration ...
  47. WinRM cannot make the configuration change. The Password used for updating the certificate mapping configuration is not valid. ...
  48. WinRM cannot make the configuration change. The Password used for updating the certificate mapping configuration is not valid. ...
  49. WinRM cannot make the configuration change. The Subject used for the certificate mapping operation is not valid. It must ...
  50. WinRM cannot make the configuration change. The URI supplied for the certificate mapping operation is not valid. It must ...
  51. WinRM cannot process the configuration request. The hostname pattern is invalid: "%1" Hostname patterns must contain one ...
  52. WinRM cannot process the configuration request. The service resource URI (%1) only supports the following actions: %2 and ...
  53. WinRM cannot process the configuration request. This action requires input XML containing an element name of %1 with value ...
  54. WinRM cannot process the request because a non-array WMI option occurred more than once. WMI array options must use the prefix ...
  55. WinRM cannot process the request because a selector set contains an unrecognized element. Selector sets must contain only ...
  56. WinRM cannot process the request because a WMI option was defined both as an array option and as a non-array option. WMI ...
  57. WinRM cannot process the request because an option contains a name attribute which is either " (blank or empty string) or ...
  58. WinRM cannot process the request because an option set contains an unrecognized element. Option sets must contain only '%1' ...
  59. WinRM cannot process the request because an XML element has content or child elements but is marked as NULL with the xsi:nil ...
  60. WinRM cannot process the request because the input XML contains a mismatched element. The ending name does not match the ...
  61. WinRM cannot process the request. The following error occurred while using %1 authentication: Cannot find the computer %2. ...
  62. WinRM cannot process the request. The following error occurred while using Kerberos authentication: The computer %1 is unknown ...
  63. WinRM cannot process the request. The following error with error code 1!x! occurred while using Negotiate authentication: ...
  64. WinRM cannot process the request. The following error with errorcode 1!x! occurred while using %2 authentication: %3 Possible ...
  65. WinRM failed to load the plugin DLL for %1. Loading the DLL failed for the path %2 with error code %3!d!. The plugin may ...
  66. WinRM firewall exception will not work since one of the network connection types on this machine is set to Public. Change ...
  67. Winrs error: remote shell has been closed due to timeout or deleted by the administrator. The current command has been terminated. ...
  68. WINS adjusted the Maximum Records at a time parameter of the ConsistencyCheck key. The value specified, %2, was changed to ...
  69. WINS adjusted the scavenging related time interval, %1, so that it is compatible with the replication time intervals. The ...
  70. WINS adjusted the scavenging related time interval, %1. The adjusted value for this scavenging parameter is given in the ...
  71. WINS cannot start because the existing WINS database needs conversion to the Windows 2000 format. WINS has initiated the ...
  72. WINS could not close an open key. Check to see if the permissions on the key are set properly, system resources are low, ...
  73. WINS could not come up because the existing WINS database needs conversion to the Windows 2000 format. If this is the first ...
  74. WINS could not create a heap because of a resource shortage. Check to see if the computer is running short of virtual memory. ...
  75. WINS could not create the TCP socket for listening to TCP connections. Make sure the TCP/IP driver is installed and running ...