Windows 8

  1. The Microsoft DHCP Server was successfully configured to co-exist with the Windows Deployment Services Server. For more information ...
  2. The Microsoft Distributed Transaction Coordinator (DTC) failed. The Message Queuing service cannot continue. Please restart ...
  3. The Microsoft Exchange 5.5 server name specified in the address does not match the one specified in the Microsoft Exchange ...
  4. The Microsoft Failover Cluster Virtual Adapter (NetFT.sys) startup type on node {0} is not set to the default and recommended ...
  5. The Microsoft Federation Gateway metadata could not be downloaded from %1. Make sure that the AD RMS server can access this ...
  6. The Microsoft internal 32-bit version of the Steps Recorder is not supported on 64-bit Windows. Please use the 64-bit version ...
  7. The Microsoft iSCSI service is not running. The service is required to be started for iSCSI to function correctly. To start ...
  8. The Microsoft iSCSI Software Target service could not assign virtual disk %1 to iSCSI target %2. The operation failed with ...
  9. The Microsoft iSCSI Software Target service could not bind to network address %1, port %2. The operation failed with error ...
  10. The Microsoft iSCSI Software Target service could not create a clustered virtual disk using %1. The operation failed with ...
  11. The Microsoft iSCSI Software Target service could not create a snapshot of virtual disk %1. The operation failed with error ...
  12. The Microsoft iSCSI Software Target service could not create iSCSI target %1 for the cluster resource group. The operation ...
  13. The Microsoft iSCSI Software Target service could not create or open registry key %1. The operation failed with error code ...
  14. The Microsoft iSCSI Software Target service could not create the virtual disk using device %1. The operation failed with ...
  15. The Microsoft iSCSI Software Target service could not online iSCSI target %1. Another target with the same name is already ...
  16. The Microsoft iSCSI Software Target service could not retrieve disk information from the system. The operation failed with ...
  17. The Microsoft iSCSI Software Target service could not retrieve volume information from the system. The operation failed with ...
  18. The Microsoft iSCSI Software Target service could not roll back virtual disk %1 to the snapshot taken on %2. The operation ...
  19. The Microsoft iSCSI Software Target service detected conflicting virtual disk index %1 assigned to %2 and %3. The service ...
  20. The Microsoft iSCSI Software Target service encountered an error indicating that too many sessions are sharing device %1. ...
  21. The Microsoft iSCSI Software Target service failed to complete service initialization due to reason %1. The operation failed ...
  22. The Microsoft iSCSI Software Target service failed to generate security key. The operation failed with error code %1. %2 ...
  23. The Microsoft iSCSI Software Target service failed to initialize security key. The operation failed with error code %1. %2 ...
  24. The Microsoft iSCSI Software Target service failed to initialize security keys. The operation failed with error code %1. ...
  25. The Microsoft iSCSI Software Target service failed to load the Cryptography API: Next Generation (CNG) library used for encryption. ...
  26. The Microsoft Licensing Diagnostic Tool provides detailed information about the Windows licensing components and settings ...
  27. The Microsoft Report Viewer 2008 Redistributable is required for this feature. Please close the console before installing ...
  28. The Microsoft Report Viewer control is not installed on current machine. Click the following link to download and install ...
  29. The Microsoft Report Viewer control is not installed on current machine. Please download the component from http://go.mi ...
  30. The Microsoft-Windows-DiskDiagnosticResolver warns users about faults reported by hard disks that support the Self Monitoring ...
  31. The Microsoft/Windows/ClusterAwareUpdating BPA model is not found on "{0}". To run Test-CauSetup, you might need to reinstall ...
  32. The middle-tier application server can process transactions on behalf of network clients, coordinate distributed transactions, ...
  33. The Migrate a Cluster Wizard copies settings only. You must copy or move any data or folders (including file share settings) ...
  34. The Migrate a Cluster Wizard could not check whether a disk has mount points. For any disk that has mount points, be sure ...
  35. The Migrate a Cluster Wizard could not determine the available drive letters because some nodes in the new cluster are down. ...
  36. The migration engine is already in use. To run this cmdlet, close the current Windows PowerShell session, and then open another ...
  37. The migration of licenses has completed. Because the source Remote Desktop license server %1!s! is running an operating system ...
  38. The migration of licenses has completed. Because the source Remote Desktop license server %1!s! was not available on the ...
  39. The migration of licenses has completed. During the migration, the source Remote Desktop license server was specified as ...
  40. The migration operation cannot be performed. The versions of Windows Server Migration Tools on the source and destination ...
  41. The migration store cannot be accessed. Verify the following: the store path is specified correctly and does not include ...
  42. The migration store cannot be created. Verify that the migration store location is available (for example, verify that the ...
  43. The migration store that is specified is corrupted or incomplete. Specify another migration store, and then run the Import-SmigServerSetting ...
  44. The MIME boundary string '%1' is invalid. It is either zero length, longer than 70 characters, or contains an invalid character. ...
  45. The minimum size for the new partition is %1!d! megabytes. Please specify a size of at least %1!d!. Example: -size %1!d! ...
  46. The mobile broadband data service is not available in this area Data service is required to transfer data over mobile networks. ...
  47. The mobile device is already in use. Wait until the current task finishes or quit other programs that might be using the ...
  48. The Mobile page cannot be displayed. Message Queuing may not be properly installed. Please reinstall Message Queuing using ...
  49. The modem failed to respond. Make sure it is properly connected and turned on. If it is an internal modem or is connected, ...
  50. The modem is already in use or is not configured for Remote Access dial out. For troubleshooting information, click Help. ...
  51. The modified date for one or more GPOs on this domain controller are not in sync with the modified dates for the GPOs on ...
  52. The modifiers can be combined to get compound results: %~dp1 - expands %1 to a drive letter and path only %~nx1 - expands ...
  53. The module "%1" failed to load. Make sure the binary is stored at the specified path or debug it to check for problems with ...
  54. The module "%1" may not compatible with the version of Windows that you're running. Check if the module is compatible with ...
  55. The module "%1" was loaded but the call to %2 failed with error code %3. For more information about this problem, search ...
  56. The module "%1" was loaded but the entry-point %2 was not found. Make sure that "%1" is a valid DLL or OCX file and then ...
  57. The module "%1" was loaded but the entry-point %2 was not found. Make sure that "%1" is a valid DLL or OCX file and then ...
  58. The module cannot be loaded because it has been generated with an incompatible version of {0} cmdlet. Generate the module ...
  59. The module encountered an invalid parameter or a valid parameter with an invalid value or an expected module parameter is ...
  60. The module encountered an invalid parameter or a valid parameter with an invalid value, or an expected module parameter was ...
  61. The module manifest '{0}' could not be processed because it is not a valid Windows PowerShell restricted language file. Please ...
  62. The module manifest cannot contain both 'ModuleToProcess' member and 'RootModule' member. Please fix the module manifest ...
  63. The module manifest member 'NestedModules' cannot be used if 'ModuleToProcess' member is a binary module. Please fix the ...
  64. The module to process '{0}', listed in field '{1}' of module manifest '{2}' was not processed because no valid module was ...
  65. The MOF file created for the %1!s! service cannot be deleted as requested. The automatic recovery function requires the MOF ...
  66. The MOF file created for the %1!s! service could not be loaded. The record data contains the error code returned by the MOF ...
  67. The Monitor Configuration API only works with monitors that support the MCCS 1.0 specification, MCCS 2.0 specification or ...
  68. The Monitor Configuration API only works with monitors which support the MCCS 1.0 specification, MCCS 2.0 specification or ...
  69. The monitor displays network performance between the Extender and the Windows Media Center computer while you make changes. ...
  70. The monitor returned a DDC/CI capabilities string that did not comply with the ACCESS.bus 3.0, DDC/CI 1.1 or MCCS 2 Revision ...
  71. The monitor returned a DDC/CI capabilities string which did not comply with the ACCESS.bus 3.0, DDC/CI 1.1, or MCCS 2 Revision ...
  72. The monitor returned an invalid monitor technology type. CRT, Plasma and LCD (TFT) are examples of monitor technology types. ...
  73. The most appropriate broadcast standard for your region is selected. If your video is black and white or is missing audio, ...
  74. The most likely cause of this error is that the DCOM server is not registered or has been deleted. Reregister the Rrasprxy.dll ...
  75. The most recent {0} session did not close normally. All files {1} that were open during the previous session will be reopened. ...