Windows 8

  1. The device %2 (location %3) is offline due to a user-mode device crash. Windows will no longer attempt to restart this device ...
  2. The device %2 (location %3) is offline due to a user-mode driver crash. Windows will attempt to restart the device %5 more ...
  3. The device %2 (location %3) is offline due to a user-mode driver crash. Windows will attempt to restart the device %5 more ...
  4. The device %2 (location %3) is offline due to a user-mode driver crash. Windows will attempt to restart the device in the ...
  5. The device %2 was unable to start due to conflict between the settings for driver %5 (%3 - %4) and the other drivers. Windows ...
  6. The device '%3' cannot be removed from virtual machine '%1' because it belongs to another virtual machine. (Virtual machine ...
  7. The device '%3' failed to mount because the device is already mounted read-only, and an attempt was made to mount it read/write. ...
  8. The device '%3' failed to mount because the device is already mounted read-only, and an attempt was made to mount it read/write. ...
  9. The device '%s' cannot be stopped because it is using a driver that does not support Plug and Play. Since this device is ...
  10. 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. ...
  11. The device (%1) will not be used for a ReadyBoost cache because a ReadyBoost cache already exists (on device %2) and only ...
  12. The device (%1) will not be used for a ReadyBoost cache because it contains a configuration file which explicitly prohibits ...
  13. The device (%1) will not be used for a ReadyBoost cache because it does not exhibit uniform performance across the device. ...
  14. The device (%1) will not be used for a ReadyBoost cache because it does not have enough free space. Free Space %2 MB, required ...
  15. The device (%1) will not be used for a ReadyBoost cache because it is mounted read-only. This is usually caused by one of ...
  16. The device (%1) will not be used for a ReadyBoost cache because it is not attached to a supported interface. For USB devices, ...
  17. The device (%1) will not be used for a ReadyBoost cache because it is not formatted with FAT, FAT32, or NTFS. Current Format:%2 ...
  18. The device (%1) will not be used for a ReadyBoost cache because it is remote, read-only, virtual, or otherwise unsupported. ...
  19. The device (%1) will not be used for a ReadyBoost cache because the device is too small. Size: %2 MB. Minimum Size: %3 MB ...
  20. The device associated with this recorder during the last operation has been exclusively locked, causing this operation to ...
  21. The device certificate on your Extender is invalid. Contact the Extender manufacturer or visit their website for assistance. ...
  22. The device could not allocate one or more required resources due to conflicts with other devices. The device DMA setting ...
  23. The device could not allocate one or more required resources due to conflicts with other devices. The device interrupt setting ...
  24. The device could not allocate one or more required resources due to conflicts with other devices. The device memory setting ...
  25. The device could not allocate one or more required resources due to conflicts with other devices. The device port setting ...
  26. The device driver for the '%s' device is preventing the machine from entering hibernation. Please close all applications ...
  27. The device driver for the '%s' device is preventing the machine from entering standby. Please close all applications and ...
  28. The device driver for the Trusted Platform Module (TPM) encountered a non-recoverable error in the TPM hardware, which prevents ...
  29. The device driver for the Trusted Platform Module (TPM) encountered an error in the TPM hardware, which might prevent some ...
  30. The device driver for {warndescrip} has not been installed. This device will not be available until the correct device driver ...
  31. The device failed to accept the command within the timeout period. This may be caused by the device having entered an inconsistent ...
  32. The device has either stopped responding or has been disconnected. The camera may not support copying files from your computer. ...
  33. The device has either stopped responding or has been disconnected. The camera may not support moving files from your computer. ...
  34. The device is currently busy and its contents may not be fully displayed. If another application is copying data to or from ...
  35. The device is mounted read-only. This usually happens with write-protected devices/media or when BitLocker group policy settings ...
  36. 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 ...
  37. The Device Manager lists all the hardware devices installed on your computer. Use the Device Manager to change the properties ...
  38. The device name you chose is in use by some other device. Each still image device must have a unique name. Please change ...
  39. The device object parameter is either not a valid device object or is not attached to the volume specified by the file name. ...
  40. The device or resource (%1!s!) is online but isn't responding to connection attempts The remote computer isn't accepting ...
  41. The device receives no install image from the specified server. This can occur for several reasons, including: no available ...
  42. The device to which you are connecting has detected possible rogue activity on the network. Registration cannot continue. ...
  43. The device to which you are connecting has disabled registration for security reasons. Refer to the documentation for your ...
  44. The device was in use by another application or is otherwise not available. Pleased stop that application or wait for the ...
  45. The device was not detected because a proxy for this device type was not installed. Please reinstall Scan Management to get ...
  46. The device will not receive a boot image from the specified server because none of the boot images can be applied to the ...
  47. The device you just connected is nearly full. The files may be from the device manufacturer or they may have been added from ...
  48. The device, {warndescrip}, cannot start properly. It may not have the correct driver installed or may be experiencing a hardware ...
  49. The device, {warndescrip}, is disabled. If this device is no longer used it may be intentionally disabled. The Plug and Play ...
  50. The device, {warndescrip}, is reporting "{warnerror}". This device will not be available until the issue is resolved. The ...
  51. The device, {warndescrip}, is reporting a bad status value. This device will not be available until the issue is resolved. ...
  52. The devices listed below are being used by programs and are consuming bandwidth. To obtain updated bandwidth information, ...
  53. The DFS Management snap-in cannot create a namespace on a failover cluster. To create a namespace on a failover cluster, ...
  54. The DFS metadata is corrupt. The type information of the DFS folder (link) is marked as a namespace root when it should be ...
  55. The DFS metadata is corrupt. The type information of the namespace root is marked as a DFS folder (link) when it should be ...
  56. The DFS Namespace server service performance counter set object. This object includes a set of counters for specific to a ...
  57. The DFS Namespace server service performance counter set object. This object includes a set of counters related to NetDfs ...
  58. The DFS Namespace server service performance counter set object. This object includes a set of counters related to referral ...
  59. The DFS Namespace service could not initialize cross forest trust information on this domain controller, but it will periodically ...
  60. The DFS Namespace service could not initialize the trusted domain information on this domain controller, but it will periodically ...
  61. The DFS Namespace service could not obtain site costs for the following Active Directory Domain Services site: %1. This might ...
  62. The DFS Namespace service may not be able to query or recover from a temporary failure of Active Directory Domain Services ...
  63. The DFS Namespace service may put more load than necessary on Active Directory Domain Services (AD DS), or be unable to recover ...
  64. The DFS Namespaces service has successfully initialized the shared folder that hosts the namespace root. Shared folder: %1 ...
  65. The DFS Replication bandwidth savings are computed by determining the total size of data replicated across the network using ...
  66. The DFS Replication detected the ASR instance key has changed on volume %2!s!. Replication has been stopped for all replicated ...
  67. The DFS Replication detected the System State Restore Id has changed on volume %2!s!. Replication has been stopped for all ...
  68. The DFS Replication reporting mechanism cannot find the WMI (Windows Management Instrumentation) namespace to retrieve certain ...
  69. The DFS Replication service canceled a pending creation / update of the following failover cluster resource: '%4!s!'. No ...
  70. The DFS Replication service canceled a pending deletion of the following failover cluster resource: '%4!s!'. No user action ...
  71. The DFS Replication service cannot replicate the replicated folder at local path because it overlaps with a folder that is ...
  72. The DFS Replication service cannot replicate the replicated folder at local path because it overlaps with the replicated ...
  73. The DFS Replication service cannot verify the root or staging path of a replicated folder that is hosted by a failover cluster. ...
  74. The DFS Replication service cannot write to the debug logs in . The volume might be out of disk space, or the DFS Replication ...
  75. The DFS Replication service cleaned up the oldest staging files at local path %1!s!, and the staging space is now below the ...