Windows 8

  1. The volume from which backup was done, no longer exists or is offline. Specify an alternate recovery target for recovery. ...
  2. The volume ID for %1: has been reset, since it was a duplicate of that on %2:. This volume ID is used by Distributed Link ...
  3. The volume mounted at '%1' ('%2') for namespace root '%3' is not a valid volume for reporting or classification. Make sure ...
  4. The volume mounted at '%s' ('%s') for namespace root '%s' is not a valid volume for reporting or classification. Make sure ...
  5. The volume mounted at {0} ({1}) for report namespace root {2} is located on a non-fixed drive (CD-ROM, etc). Make sure that ...
  6. The volume mounted at {0} ({1}) for report namespace root {2} is not formatted with NTFS. Make sure that you include only ...
  7. The volume mounted at {0} specified in the report configuration is invalid (The volume type is reported as {1}). This volume ...
  8. The volume of the specified mount path does not support reparse points. Please mount to a volume that supports reparse points. ...
  9. The volume repair could not be performed while it is online. Please schedule to take the volume offline so that it can be ...
  10. The volume selected is also the Windows system volume. For best performance and data reliability, the remote installation ...
  11. The volume selected is BitLocker encrypted. Formatting will remove the BitLocker encryption and the encrypted data on the ...
  12. The Volume Shadow Copy Service was unable to load the provider with identifier %1. Reinstall the provider and retry the operation. ...
  13. The volume specified in the -RecoveryTargetVolume parameter no longer exits or has been recreated as the unique indentifier ...
  14. The volume specified to back up has a file system which is not supported. Only NTFS/ReFS-formatted volumes or EFI system ...
  15. The volume was created successfully but it was not assigned an access path. Retry assigning the access path by using the ...
  16. The volume was repaired but the underlying partition was not marked active because another partition on the disk is already ...
  17. The volume will be momentarily unavailable during the repair. Do you want to disconnect all users and repair the volume now? ...
  18. The volume will be unavailable for several minutes during the repair. Do you want to disconnect all users and repair the ...
  19. The volume you have selected to shrink does not have a recognizable file system. Shrinking this volume will erase any data ...
  20. The volume you have selected to shrink may be corrupted. Use Chkdsk to fix the corruption problem, and then try to shrink ...
  21. The volume you have selected to shrink may be corrupted. Use Chkdsk to fix the corruption problem, and then try to shrink ...
  22. The volume you selected to delete has been encrypted with BitLocker Drive Encryption. If you delete the volume, all data ...
  23. The volume you selected to delete has been encrypted with BitLocker Drive Encryption. If you delete the volume, all data ...
  24. The volume you selected to format is encrypted with BitLocker Drive Encryption. BitLocker encryption will be removed and ...
  25. The volume you specified cannot be formatted because the system is busy formatting another volume. Wait until that format ...
  26. The volume {0} on the destination server is not using the NTFS file system. The permissions on the file share will be migrated ...
  27. The VPN connection between your computer and the VPN server could not be completed. The most common cause for this failure ...
  28. The VPN connection cannot be completed because the 'IKE and AuthIP IPSec Keying Modules' service and/or the 'Base Filtering ...
  29. The VPN Connection is still connecting or reauthenticating because of Quarantine state change. Initiate mobike update only ...
  30. The wait-events-timers could not be registered with the wait server thread. Alertable threads might not have been initialized ...
  31. The WBENGINE service is used by Windows Backup to perform backup and recovery operations. If this service is stopped by a ...
  32. The WBPolicy object must be in edit mode for you to set parameters. To put the WBPolicy object in edit mode for a policy ...
  33. The WcsPlugInService service hosts third-party Windows Color System color device model and gamut map model plug-in modules. ...
  34. The Web Management Service enables remote and delegated management capabilities for administrators to manage for the Web ...
  35. The Web page or template %2!.1023ls! installed on your computer is requesting %1!.1023ls! access rights to your digital media ...
  36. The web server interrupted the request. This may be caused by a time-out while trying to establish a connection to the destination ...
  37. The web server received a request that contains potentially malicious data. This could be an attempt to perform a cross-site ...
  38. The web server you're trying to reach is temporarily unavailable This could be due to communication issues between your network's ...
  39. The Web site that the Remote Desktop Gateway (RD Gateway) server is configured to use is not started on the Web (IIS) server. ...
  40. The web.config file does not contain a connection string used to connect to the database. Verify that the web.config file ...
  41. The website "%ls" has requested to save a file on your computer called a "cookie." This file may be used to track usage information. ...
  42. The weighted paths policy allows the user to specify the relative processing load of each path. A large number means that ...
  43. The Welcome screen shows the names of everyone with a user account for this computer. This screen appears when you start ...
  44. The well-known container for the DS name shown below is misconfigured or missing. Please have an administrator reconfigure ...
  45. The WIA driver for this imaging device returned an invalid property attribute for this property. This is a driver bug, please ...
  46. The WIM image specified requires a reference WIM. Use the /ReferenceWimSourceFile and /ReferenceWimDirectPath parameters ...
  47. The Win32 internal error "{0}" 0x{1:X} occurred while attaching to parent console. Contact Microsoft Customer Support Services. ...
  48. The Win32 internal error "{0}" 0x{1:X} occurred while detaching from the console. Contact Microsoft Customer Support Services. ...
  49. The Win32 internal error "{0}" 0x{1:X} occurred while filling the console output buffer with attributes. Contact Microsoft ...
  50. The Win32 internal error "{0}" 0x{1:X} occurred while filling the console output buffer with characters. Contact Microsoft ...
  51. The Win32 internal error "{0}" 0x{1:X} occurred while flushing the console input buffer. Contact Microsoft Customer Support ...
  52. The Win32 internal error "{0}" 0x{1:X} occurred while getting console font information. Contact Microsoft Customer Support ...
  53. The Win32 internal error "{0}" 0x{1:X} occurred while getting console output buffer information. Contact Microsoft Customer ...
  54. The Win32 internal error "{0}" 0x{1:X} occurred while getting cursor information. Contact Microsoft Customer Support Services. ...
  55. The Win32 internal error "{0}" 0x{1:X} occurred while getting input about the console handle. Contact Microsoft Customer ...
  56. The Win32 internal error "{0}" 0x{1:X} occurred while getting the console mode. Contact Microsoft Customer Support Services. ...
  57. The Win32 internal error "{0}" 0x{1:X} occurred while getting the largest console window size. Contact Microsoft Customer ...
  58. The Win32 internal error "{0}" 0x{1:X} occurred while getting the number of events in the console input buffer. Contact Microsoft ...
  59. The Win32 internal error "{0}" 0x{1:X} occurred while reading characters from the console input buffer. Contact Microsoft ...
  60. The Win32 internal error "{0}" 0x{1:X} occurred while reading input records from the console input buffer. Contact Microsoft ...
  61. The Win32 internal error "{0}" 0x{1:X} occurred while reading the contents of the console input buffer. Contact Microsoft ...
  62. The Win32 internal error "{0}" 0x{1:X} occurred while retrieving the handle for the active console output buffer. Contact ...
  63. The Win32 internal error "{0}" 0x{1:X} occurred while scrolling the console output buffer. Contact Microsoft Customer Support ...
  64. The Win32 internal error "{0}" 0x{1:X} occurred while sending keyboard input. Contact Microsoft Customer Support Services. ...
  65. The Win32 internal error "{0}" 0x{1:X} occurred while setting character attributes for the console output buffer. Contact ...
  66. The Win32 internal error "{0}" 0x{1:X} occurred while setting console font information. Contact Microsoft Customer Support ...
  67. The Win32 internal error "{0}" 0x{1:X} occurred while setting the console mode. Contact Microsoft Customer Support Services. ...
  68. The Win32 internal error "{0}" 0x{1:X} occurred while setting the console output buffer size. Contact Microsoft Customer ...
  69. The Win32 internal error "{0}" 0x{1:X} occurred while setting the console window information. Contact Microsoft Customer ...
  70. The Win32 internal error "{0}" 0x{1:X} occurred while setting the console window title. Contact Microsoft Customer Support ...
  71. The Win32 internal error "{0}" 0x{1:X} occurred while trying to remove a break handler. Contact Microsoft Customer Support ...
  72. The Win32 internal error "{0}" 0x{1:X} occurred while trying to set the cursor position. Contact Microsoft Customer Support ...
  73. The Win32 internal error "{0}" 0x{1:X} occurred while writing to the console output buffer at the current cursor position. ...
  74. The Win32 internal error "{0}" 0x{1:X} occurred while writing to the console output buffer. Contact Microsoft Customer Support ...
  75. The Win32_PnPEntity WMI class represents the properties of a Plug and Play device. Plug and Play entities are shown as entries ...