Windows 10

  1. The destination Active Directory Lightweight Directory Services instance logging this event processed a link value update ...
  2. The destination Active Directory Lightweight Directory Services instance logging this event processed a link value update ...
  3. The destination address is an IPv6 address.PPTP does not work over IPv6. The VPN connection type will be set to Automatic. ...
  4. The destination computer "{0}" is not configured to receive live migrations. To enable migrations, modify the Hyper-V network ...
  5. The destination computer "{0}" is not configured to send or receive live migrations of virtual machines. To fix this problem, ...
  6. The destination computer"{0}" is not configured to receive live migrations. To enable migrations, modify the Hyper-V network ...
  7. The destination file system volume is not available. Verify that another program, such as CheckDisk, is not running, which ...
  8. The destination host is not configured for live migration. Use the Enable-VMMigration cmdlet to modify the Hyper-V settings ...
  9. The destination log defined in this subscription cannot be found in the list of valid destination logs on this computer. ...
  10. The destination LUN could not be resynchronized from the source volume because it did not report a unique SCSI storage storage ...
  11. The destination volume has changed. If the disk is removable, it might have been replaced with a different disk. Reinsert ...
  12. The details for this conflict could not be found. The conflict may no longer exist, or the device it occurred on is not available. ...
  13. The details for this conflict could not be opened. The conflict may no longer exist, the device it occurred on is not available, ...
  14. The detected device is of unknown type. Be sure that: 1. The device is properly configured. 2. The address on the previous ...
  15. The detected filter driver might cause stability problems with this version of Windows. Real-time virus protection will be ...
  16. The developer license on this computer expires on {0}. If you remove the developer license from this computer, some apps ...
  17. The device "%hs" has detected a CardBus card in its slot, but the firmware on this system is not configured to allow the ...
  18. The device %1 %2 supports more than one port. Printbrm.exe (the Printer Migration Wizard or the command-line tool) will convert ...
  19. The device %2 (location %3) is offline due to a user-mode device crash. Windows will no longer attempt to restart this device ...
  20. The device %2 (location %3) is offline due to a user-mode driver crash. Windows will attempt to restart the device %5 more ...
  21. The device %2 (location %3) is offline due to a user-mode driver crash. Windows will attempt to restart the device %5 more ...
  22. The device %2 (location %3) is offline due to a user-mode driver crash. Windows will attempt to restart the device in the ...
  23. The device %2 was unable to start due to conflict between the settings for driver %5 (%3 - %4) and the other drivers. Windows ...
  24. The device '%3' cannot be removed from virtual machine '%1' because it belongs to another virtual machine. (Virtual machine ...
  25. The device '%3' failed to mount because the device is already mounted read-only, and an attempt was made to mount it read/write. ...
  26. The device '%3' failed to mount because the device is already mounted read-only, and an attempt was made to mount it read/write. ...
  27. The device '%s' cannot be stopped because it is using a driver that does not support Plug and Play. Since this device is ...
  28. The device (%1) is suitable for a ReadyBoost cache. The random read speed is %3 KB/sec. The random write speed is %4 KB/sec. ...
  29. The device (%1) will not be used for a ReadyBoost cache because a ReadyBoost cache already exists (on device %2) and only ...
  30. The device (%1) will not be used for a ReadyBoost cache because it contains a configuration file which explicitly prohibits ...
  31. The device (%1) will not be used for a ReadyBoost cache because it does not exhibit uniform performance across the device. ...
  32. The device (%1) will not be used for a ReadyBoost cache because it does not have enough free space. Free Space %2 MB, required ...
  33. The device (%1) will not be used for a ReadyBoost cache because it is mounted read-only. This is usually caused by one of ...
  34. The device (%1) will not be used for a ReadyBoost cache because it is not attached to a supported interface. For USB devices, ...
  35. The device (%1) will not be used for a ReadyBoost cache because it is not formatted with FAT, FAT32, or NTFS. Current Format:%2 ...
  36. The device (%1) will not be used for a ReadyBoost cache because it is remote, read-only, virtual, or otherwise unsupported. ...
  37. The device (%1) will not be used for a ReadyBoost cache because the device is too small. Size: %2 MB. Minimum Size: %3 MB ...
  38. The device associated with this recorder during the last operation has been exclusively locked, causing this operation to ...
  39. The device attempted to start a session using an unsupported authentication algorithm. The supported Authentication algorithms ...
  40. The device attempted to start a session using an unsupported confidentiality algorithm. The supported confidentiality algorithms ...
  41. The device attempted to start a session using an unsupported integrity algorithm. The supported integrity algorithms are ...
  42. The device cannot be assigned to a virtual machine as the firmware (BIOS or UEFI) on this host computer system indicates ...
  43. The Device Control Block (DCB) property contains the control settings for a serial communications device, in this case, the ...
  44. The device could not allocate one or more required resources due to conflicts with other devices. The device DMA setting ...
  45. The device could not allocate one or more required resources due to conflicts with other devices. The device interrupt setting ...
  46. The device could not allocate one or more required resources due to conflicts with other devices. The device memory setting ...
  47. The device could not allocate one or more required resources due to conflicts with other devices. The device port setting ...
  48. The device could not locate the media content. Make sure that the device is connected to the network and can access the desired ...
  49. The device could not locate the media. Please make sure the media storage device is connected to the network and the media ...
  50. The device detected is not compatible with this driver. Enter a new Host Name or IP Address for a different device and click ...
  51. The device does not support the UPnP command format. A device update might solve the problem. Please contact the device manufacturer ...
  52. The device does not support the UPnP command. A device update might solve the problem. Please contact the device manufacturer ...
  53. The device does not support the UPnP variable. A device update might solve the problem. Please contact the device manufacturer ...
  54. The device driver for the '%s' device is preventing the machine from entering hibernation. Please close all applications ...
  55. The device driver for the '%s' device is preventing the machine from entering standby. Please close all applications and ...
  56. The device driver for the Trusted Platform Module (TPM) encountered a non-recoverable error in the TPM hardware, which prevents ...
  57. The device driver for the Trusted Platform Module (TPM) encountered an error in the TPM hardware, which might prevent some ...
  58. The device driver for {warndescrip} has not been installed. This device will not be available until the correct device driver ...
  59. The device failed to accept the command within the timeout period. This may be caused by the device having entered an inconsistent ...
  60. The device failed to execute the UPnP command. Make sure that your media device is turned on and connected to the network, ...
  61. The device has either stopped responding or has been disconnected. The camera may not support copying files from your computer. ...
  62. The device has either stopped responding or has been disconnected. The camera may not support moving files from your computer. ...
  63. The device identifier should be entered in the form "Vendor ID-Product ID" where "Vendor ID" is the Institute of Electrical ...
  64. The device is being used by another application. If you continue, that application may stop working. Do you want to continue? ...
  65. The device is being used by another application. Please close any devices that are playing audio to this device and then ...
  66. The device is currently busy and its contents may not be fully displayed. If another application is copying data to or from ...
  67. The device is currently locked. Close any other apps that use this device or wait for the device to finish scanning and then ...
  68. The device is mounted read-only. This usually happens with write-protected devices/media or when BitLocker group policy settings ...
  69. The device is not found on the network. Be sure that: 1. The device is turned on. 2. The network is connected. 3. The device ...
  70. The Device Manager lists all the hardware devices installed on your computer. Use the Device Manager to change the properties ...
  71. The device name is used to join the device to a domain. Joining a domain is optional, but if you plan to join we need a device ...
  72. The device name you chose is in use by some other device. Each still image device must have a unique name. Please change ...
  73. The device naming setting only applies to synthetic network adapters on Generation 2 virtual machines with configuration ...
  74. The device naming setting only applies to synthetic network adapters on Generation 2 virtual machines with configuration ...
  75. The device object parameter is either not a valid device object or is not attached to the volume specified by the file name. ...