Windows 8.1

  1. The virtual machines might not start if their network settings have changed. After recovery is complete use Hyper-V Manager ...
  2. The virtual switch '%1' cannot be deleted because it is being used by running virtual machines or assigned to child pools. ...
  3. The virtual switch '%1' cannot be removed from resource pool '%2' because it is being used by running virtual machines or ...
  4. The virtual switch cannot be bound to the WiFi adapter because the network bridge is already in use. You can configure at ...
  5. The virtualization infrastructure driver has encountered an error. Could not find the requested partition. Restarting the ...
  6. The virtualization infrastructure driver has encountered an error. The requested partition does not exist. Restarting the ...
  7. The VirtualSize property specifies the current size in bytes of the virtual address space the process is using. Use of virtual ...
  8. The VM has been live migrated with missing LUNs for virtual HBA %3 (%4) due to the VM setting to allow reduced FC redundancy. ...
  9. The VMMonitorModeExtensions property determines whether the processor supports Intel or AMD Virtual Machine Monitor extensions. ...
  10. The VMR has not yet created a mixing component. That is, IVMRFilterConfig::SetNumberofStreams has not yet been called.%0 ...
  11. The VoiceSwitchFeature property contains the command strings used to activate the voice capabilities of a voice modem. Example: ...
  12. The VoltageCaps property specifies the voltage capabilities of the processor. Bits 0-3 of the field represent specific voltages ...
  13. The volume %s is currently in use. If you continue, the drive letter will be freed; however, it will still be available for ...
  14. The volume %s is currently in use. If you continue, the new drive letter will be assigned, but you can still use the old ...
  15. The volume %s is currently in use. To force the deletion of this volume, click Yes. WARNING: Forcing a deletion might cause ...
  16. The volume %s is currently in use. To force the format of this volume, click Yes. WARNING: Forcing a format might cause unexpected ...
  17. The volume %s is currently in use. To forcibly extend this volume, click Yes. WARNING: Forcibly extending a volume might ...
  18. The volume %s is too small to contain a storage area. Please click the Settings button and pick a storage area location before ...
  19. The volume cannot be created because the volume identifier (GUID) already exists. Define a new identifier, and then try the ...
  20. The volume cannot be created because the volume tag is a predefined tag. Choose a different tag, and then try the operation ...
  21. The volume cannot be extended because another volume is located immediately after this volume on the disk. To extend the ...
  22. The volume cannot be extended because it resides on a dynamic disk. To extend a volume that resides on a dynamic disk, use ...
  23. The volume cannot be extended because the number of clusters will exceed the maximum number of clusters supported by the ...
  24. The volume containing boot critical files is not formatted with a supported filesystem. Bare metal recovery is not supported ...
  25. The volume containing sysvol share has only %d bytes free for policy to use. Please free space (above 5MB) in order for policy ...
  26. The volume could not be extended because it is encrypted by BitLocker and Fveapi.dll could not be loaded to determine its ...
  27. The volume could not be extended because it is locked due to a BitLocker error. Use BitLocker tools to recover the volume ...
  28. The volume could not be extended because it is marked for BitLocker recovery. Use BitLocker tools to recover the volume and ...
  29. The volume could not be shrunk because it is encrypted by BitLocker and Fveapi.dll could not be loaded to determine its status. ...
  30. The volume could not be shrunk because it is locked due to a BitLocker error. Use BitLocker tools to recover the volume and ...
  31. The volume could not be shrunk because it is marked for BitLocker recovery. Use BitLocker tools to recover the volume and ...
  32. The volume does not contain a recognized file system. Please make sure that all required file system drivers are loaded and ...
  33. The volume does not contain a recognized file system. Please make sure that all required file system drivers are loaded and ...
  34. The volume from which backup was done, no longer exists or is offline. Specify an alternate recovery target for recovery. ...
  35. 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 ...
  36. The volume is not configured correctly. Ensure that the volume is configured correctly, and then try the operation again. ...
  37. The volume mounted at '%1' ('%2') for namespace root '%3' is not a valid volume for reporting or classification. Make sure ...
  38. The volume mounted at '%s' ('%s') for namespace root '%s' is not a valid volume for reporting or classification. Make sure ...
  39. The volume mounted at {0} ({1}) for report namespace root {2} is located on a non-fixed drive (CD-ROM, etc). Make sure that ...
  40. The volume mounted at {0} ({1}) for report namespace root {2} is not formatted with NTFS. Make sure that you include only ...
  41. The volume mounted at {0} specified in the report configuration is invalid (The volume type is reported as {1}). This volume ...
  42. The volume of the specified mount path does not support reparse points. Please mount to a volume that supports reparse points. ...
  43. The volume repair could not be performed while it is online. Please schedule to take the volume offline so that it can be ...
  44. The volume selected is also the Windows system volume. For best performance and data reliability, the remote installation ...
  45. The volume selected is BitLocker encrypted. Formatting will remove the BitLocker encryption and the encrypted data on the ...
  46. The Volume Shadow Copy Service was unable to load the provider with identifier %1. Reinstall the provider and retry the operation. ...
  47. The volume specified in the -RecoveryTargetVolume parameter no longer exits or has been recreated as the unique indentifier ...
  48. The volume specified to back up has a file system which is not supported. Only NTFS/ReFS-formatted volumes or EFI system ...
  49. The volume was created successfully but it was not assigned an access path. Retry assigning the access path by using the ...
  50. The volume was not created because it could not be expanded. This possibly occurred because of a timing problem. Try the ...
  51. The volume was repaired but the underlying partition was not marked active because another partition on the disk is already ...
  52. The volume will be momentarily unavailable during the repair. Do you want to disconnect all users and repair the volume now? ...
  53. The volume will be unavailable for several minutes during the repair. Do you want to disconnect all users and repair the ...
  54. The volume you have selected to shrink does not have a recognizable file system. Shrinking this volume will erase any data ...
  55. The volume you have selected to shrink may be corrupted. Use Chkdsk to fix the corruption problem, and then try to shrink ...
  56. The volume you have selected to shrink may be corrupted. Use Chkdsk to fix the corruption problem, and then try to shrink ...
  57. The volume you selected to delete has been encrypted with BitLocker Drive Encryption. If you delete the volume, all data ...
  58. The volume you selected to delete has been encrypted with BitLocker Drive Encryption. If you delete the volume, all data ...
  59. The volume you selected to format is encrypted with BitLocker Drive Encryption. BitLocker encryption will be removed and ...
  60. The volume you specified cannot be formatted because the system is busy formatting another volume. Wait until that format ...
  61. The volume {0} on the destination server is not using the NTFS file system. The permissions on the file share will be migrated ...
  62. The VolumeDirty property indicates whether the disk requires chkdsk to be run at next boot up time. The property is applicable ...
  63. The VolumePath property indicates the name of the volume that disk quotas are on. It can be volume name, volume path (ex ...
  64. The VolumeSerialNumber property indicates the volume serial number of the logical disk. Constraints: Maximum 11 characters ...
  65. The VPN connection between your computer and the VPN server could not be completed. The most common cause for this failure ...
  66. The VPN connection cannot be completed because the 'IKE and AuthIP IPSec Keying Modules' service and/or the 'Base Filtering ...
  67. The VPN Connection is still connecting or reauthenticating because of Quarantine state change. Initiate mobike update only ...
  68. The VSS Writer for Storage Service is not running, which will prevent storage configuration information from being included ...
  69. The wait-events-timers could not be registered with the wait server thread. Alertable threads might not have been initialized ...
  70. The Wait-Job cmdlet cannot finish working, because one or more jobs are blocked waiting for user interaction. Process interactive ...
  71. The WaitHint property specifies the estimated time required (in milliseconds) for a pending start, stop, pause, or continue ...
  72. The Wallpaper property indicates the file name for the wallpaper design on the background of the desktop. Example: WINNT.BMP ...
  73. The WallpaperStretched property indicates whether the wallpaper is stretched to fill the entire screen. Microsoft Plus! must ...
  74. The WallpaperTiled property indicates whether the wallpaper is tiled or centered. Values: TRUE or FALSE. A value of TRUE ...
  75. The WarningExceedNotification property indicates whether or not events will be written to the event log when warnings are ...