Windows 7

  1. The device is being used by another application. Please close any devices that are playing audio to this device and then ...
  2. The device is currently busy and its contents may not be fully displayed. If another application is copying data to or from ...
  3. The device is mounted read-only. This usually happens with write-protected devices/media or when BitLocker group policy settings ...
  4. 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 ...
  5. The Device Manager lists all the hardware devices installed on your computer. Use the Device Manager to change the properties ...
  6. The device name you chose is in use by some other device. Each still image device must have a unique name. Please change ...
  7. The device object parameter is either not a valid device object or is not attached to the volume specified by the file name. ...
  8. The device or resource (%1!s!) is online but isn't responding to connection attempts The remote computer isn't accepting ...
  9. The device reports a device error. Restart the device, and then try again. If you can't resolve the issue, a device update ...
  10. The device requires a codec that supports this media format. A device update might solve the problem. Please contact the ...
  11. The device to which you are connecting has detected possible rogue activity on the network. Registration cannot continue. ...
  12. The device to which you are connecting has disabled registration for security reasons. Refer to the documentation for your ...
  13. The device was in use by another application or is otherwise not available. Pleased stop that application or wait for the ...
  14. The device was not detected because a proxy for this device type was not installed. Please reinstall Scan Management to get ...
  15. The device you just connected is nearly full. The files may be from the device manufacturer or they may have been added from ...
  16. The device, {warndescrip}, cannot start properly. It may not have the correct driver installed or may be experiencing a hardware ...
  17. The device, {warndescrip}, is disabled. If this device is no longer used it may be intentionally disabled. The Plug and Play ...
  18. The device, {warndescrip}, is reporting "{warnerror}". This device will not be available until the issue is resolved. The ...
  19. The device, {warndescrip}, is reporting a bad status value. This device will not be available until the issue is resolved. ...
  20. The DeviceEntriesInAColorTable property indicates the number of color indexes in a color table of a display device. If the ...
  21. The DeviceID property contains a string that uniquely identifies the cache represented by an instance of Win32_CacheMemory. ...
  22. The DeviceID property contains a string that uniquely identifies the disk drive and partition from the rest of the system ...
  23. The DeviceID property indicates the number that uniquely identifies this device with other peripherals using the Plug and ...
  24. The DeviceLoader property indicates the name of the device loader for the modem. A device loader loads and manages device ...
  25. The DeviceMap property indicates the order in which devices are listed with this SCSI controller. The DeviceMap property ...
  26. The DeviceName property indicates the name of the display device. This property has been deprecated in favor of a corresponding ...
  27. The DeviceObject property is the Windows object manager name of the underlying storage device that supports the original ...
  28. The devices listed below are being used by programs and are consuming bandwidth. To obtain updated bandwidth information, ...
  29. The devices shown in bold type are non-HI-SPEED USB devices that can be supported by the hub to which the HI-SPEED USB device ...
  30. The DeviceSpecificPens property indicates the current number of device-specific pens. 0xffff means the device does not support ...
  31. The DeviceSpecificPens property indicates the current number of device-specific pens. A value of 0xFFFFFFFF means the device ...
  32. The DeviceSpecificPens property indicates the current number of device-specific pens. A value of 0xFFFFFFFF means the device ...
  33. The DFS Management snap-in cannot create a namespace on a failover cluster. To create a namespace on a failover cluster, ...
  34. The DFS metadata is corrupt. The type information of the DFS folder (link) is marked as a namespace root when it should be ...
  35. The DFS metadata is corrupt. The type information of the namespace root is marked as a DFS folder (link) when it should be ...
  36. The DFS Namespace server service performance counter set object. This object includes a set of counters related to NetDfs ...
  37. The DFS Namespace server service performance counter set object. This object includes a set of counters related to referral ...
  38. The DFS Namespace server service performance counter set object. This object includes a set of miscellaneous counters that ...
  39. The DFS Namespace service could not initialize cross forest trust information on this domain controller, but it will periodically ...
  40. The DFS Namespace service could not initialize the trusted domain information on this domain controller, but it will periodically ...
  41. The DFS Replication bandwidth savings are computed by determining the total size of data replicated across the network using ...
  42. The DFS Replication detected the ASR instance key has changed on volume %2!s!. Replication has been stopped for all replicated ...
  43. The DFS Replication detected the System State Restore Id has changed on volume %2!s!. Replication has been stopped for all ...
  44. The DFS Replication monitoring provider class. This singleton class has provider-specific settings in addition to computer-wide ...
  45. The DFS Replication reporting mechanism cannot find the WMI (Windows Management Instrumentation) namespace to retrieve certain ...
  46. The DFS Replication service canceled a pending creation / update of the following failover cluster resource: '%4!s!'. No ...
  47. The DFS Replication service canceled a pending deletion of the following failover cluster resource: '%4!s!'. No user action ...
  48. The DFS Replication service cannot replicate the replicated folder at local path because it overlaps with a folder that is ...
  49. The DFS Replication service cannot replicate the replicated folder at local path because it overlaps with the replicated ...
  50. The DFS Replication service cannot verify the root or staging path of a replicated folder that is hosted by a failover cluster. ...
  51. The DFS Replication service cannot write to the debug logs in . The volume might be out of disk space, or the DFS Replication ...
  52. The DFS Replication service cleaned up the oldest staging files at local path %1!s!, and the staging space is now below the ...
  53. The DFS Replication service cleaned up the oldest staging files for the replicated folder at local path %2!s!, and the staging ...
  54. The DFS Replication service could not contact domain controller to access configuration objects. Replication is currently ...
  55. The DFS Replication service could not replicate one or more replicated folders because the staging path is invalid or inaccessible. ...
  56. The DFS Replication service could not replicate the replicated folder at local path %2!s! because the staging path is invalid ...
  57. The DFS Replication service detected a bad parameter in %1!s! %2!s! configuration. The parameter %4!s!. The service has ignored ...
  58. The DFS Replication service detected a bad parameter in %1!s! %2!s! configuration. The parameter is %4!s!. The service cannot ...
  59. The DFS Replication service detected a conflict between two or more %1!s! objects while polling for configuration information. ...
  60. The DFS Replication service detected a conflict between two or more objects while polling Active Directory Domain Services ...
  61. The DFS Replication service detected a valid and consistent replication group configuration. Additional Information: Replication ...
  62. The DFS Replication service detected a valid and consistent volume configuration. Additional Information: Volume: %1!s! Volume ...
  63. The DFS Replication service detected an incompatible Active Directory Domain Services schema version while trying to read ...
  64. The DFS Replication service detected and discarded an inconsistent replication group configuration. Additional Information: ...
  65. The DFS Replication service detected and discarded an inconsistent volume configuration. Additional Information: Error: %2!s! ...
  66. The DFS Replication service detected and discarded inconsistent volume configuration on volume with error ID: ( ). Additional ...
  67. The DFS Replication service detected inconsistent %1!s! object while polling for configuration information. The object at ...
  68. The DFS Replication service detected invalid %1!s! object data while polling for configuration information. Additional Information: ...
  69. The DFS Replication service detected local changes to a read-only replication folder. Changes to the SYSVOL folder (such ...
  70. The DFS Replication service detected that a file was changed on multiple servers. A conflict resolution algorithm was used ...
  71. The DFS Replication service detected that a virtual computer object and a node in the same failover cluster are members of ...
  72. The DFS Replication service detected that an authoritative restore was performed on the replicated folder at local path %2!s! ...
  73. The DFS Replication service detected that required Active Directory Domain Services schema objects are not available on domain ...
  74. The DFS Replication service detected that the connection with partner %2!s! for replication group %3!s! has been removed ...
  75. The DFS Replication service detected that the local path for the following replicated folder is not valid: '%2!s!' . This ...