Windows 8.1

  1. The ModulationBell property contains the command string used to instruct the modem to use Bell modulations for 300 and 1200 ...
  2. The ModulationCCITT property contains the command string used to instruct the modem to use CCITT modulations for 300 and ...
  3. The module "%1" failed to load. Make sure the binary is stored at the specified path or debug it to check for problems with ...
  4. The module "%1" may not compatible with the version of Windows that you're running. Check if the module is compatible with ...
  5. The module "%1" was loaded but the call to %2 failed with error code %3. For more information about this problem, search ...
  6. 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 ...
  7. 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 ...
  8. The module '{0}' is a core module for Windows PowerShell. Add the Force parameter to your command to remove core modules. ...
  9. The module cannot be loaded because it has been generated with an incompatible version of the {0} cmdlet. Generate the module ...
  10. The module encountered an invalid parameter or a valid parameter with an invalid value or an expected module parameter is ...
  11. The module encountered an invalid parameter or a valid parameter with an invalid value, or an expected module parameter was ...
  12. The module manifest '{0}' could not be processed because it is not a valid Windows PowerShell restricted language file. Remove ...
  13. The module manifest cannot contain both the 'ModuleToProcess' and 'RootModule' members. Change the module manifest file to ...
  14. The module manifest member 'NestedModules' cannot be used if the 'ModuleToProcess' member is a binary module. Edit the module ...
  15. The module manifest path '{0}' is not valid. The value of the Path argument must resolve to a single file that has a '.psd1' ...
  16. The module to process '{0}', listed in field '{1}' of module manifest '{2}' was not processed because no valid module was ...
  17. The module version {0} for module {1} is not in a valid format. Please use a module version with any of the following formats ...
  18. The MOF file created for the %1!s! service cannot be deleted as requested. The automatic recovery function requires the MOF ...
  19. The MOF file created for the %1!s! service could not be loaded. The record data contains the error code returned by the MOF ...
  20. The MofSelfInstallDirectory property contains the directory path for applications that install MOF files to the CIM repository. ...
  21. The Monitor Configuration API only works with monitors that support the MCCS 1.0 specification, MCCS 2.0 specification or ...
  22. The Monitor Configuration API only works with monitors which support the MCCS 1.0 specification, MCCS 2.0 specification or ...
  23. The monitor displays network performance between the Extender and the Windows Media Center computer while you make changes. ...
  24. 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 ...
  25. 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 ...
  26. The monitor returned an invalid monitor technology type. CRT, Plasma and LCD (TFT) are examples of monitor technology types. ...
  27. The monitored folders on media server '%1!S!' changed. Windows Media Player is updating security permissions for any included ...
  28. The MonitorManufacturer property indicates the name of the manufacturer of the display device. Example: NEC This property ...
  29. The MonitorProcessId property provides the process ID of the Resource Host Service that is currently hosting the resource. ...
  30. The MonitorType property indicates the model name of the display device. Example: NEC 5FGp This property has been deprecated ...
  31. The most appropriate broadcast standard for your region is selected. If your video is black and white or is missing audio, ...
  32. The most likely cause of this error is that the DCOM server is not registered or has been deleted. Reregister the Rrasprxy.dll ...
  33. The most recent {0} session did not close normally. All files {1} that were open during the previous session will be reopened. ...
  34. The mount directory is already associated with another volume. Unmount the other volume before using this mount directory. ...
  35. The mount directory of the specified image has changed. All the files in this image will be extracted, and this image cannot ...
  36. The mount operation failed. When mounting, you must disable any software (for example, antivirus or search indexer) that ...
  37. The mount point identified in the source volume of the backup you are about to recover is different from the mount point ...
  38. The mouse is available in a Remote Desktop session when integration services are installed in the guest operating system. ...
  39. The move operation completed, but Hyper-V could not delete a temporary version of this virtual machine that was created on ...
  40. The move table quota for Distributed Link Tracking in this domain has been exceeded. This table is used by Distributed Link ...
  41. The MoveFiles action allows the author to locate files that already exist on the user's machine, and move or copy those files ...
  42. The MPEG-2 Video Encoder MFT has received the input from the application and is passing it into the encoder. Sample: %1 Sample ...
  43. The MPU401Address property indicates the starting I/O address assigned to the MPU-401 port of the sound device. Example: ...
  44. The MS DTC administrative component has failed to start. You may not have permissions to manage the remote MS DTC, MS DTC ...
  45. The MS DTC Connection Manager is unable to register with RPC to use one of LRPC, TCP/IP, or UDP/IP. Please ensure that RPC ...
  46. The MS DTC log file is unreadable. After ensuring that all Resource Managers coordinated by MS DTC have no indoubt transactions, ...
  47. The MS DTC Service is terminating because it didnt startup in a timely manner. This may be because MS DTC took too long to ...
  48. The MS DTC Service may be hung during startup. MSDTC will eventually terminate if it cannot startup. Debugging context follows: ...
  49. The MS DTC service was started before the cluster service on this cluster node. This service will now be stopped. If MSDTC ...
  50. The MS DTC Transaction Manager could not create the MS DTC XA Transaction Manager object. MS DTC is being started but the ...
  51. The MS DTC Transaction Manager is in an inconsistent state and cannot proceed. A bad message value was received. Please contact ...
  52. The MS DTC Transaction Manager is in an inconsistent state and cannot proceed. An incorrect message length was received. ...
  53. The MS DTC Transaction Manager is in an inconsistent state and cannot proceed. An unexpected message type was received. Please ...
  54. The MS DTC Transaction Manager is in an inconsistent state and cannot proceed. An unknown message type was received. Please ...
  55. The MS DTC Transaction Manager is in an inconsistent state and cannot proceed. Please contact Microsoft Product Support. ...
  56. The MS DTC Transaction Manager received a TIP "ERROR COMMAND" for a "Prepared" transaction that is being coordinated by another ...
  57. The MS DTC Transaction Manager received a TIP "ERROR COMMAND" for an Active transaction that is being coordinated by another ...
  58. The MS DTC Transaction Manager received a TIP "ERROR COMMAND" for an Active transaction that was created with the "BEGIN ...
  59. The MS DTC Transaction Manager received an unknown or unexpected TIP command (%1) for a "Prepared" transaction that is being ...
  60. The MS DTC Transaction Manager received an unknown or unexpected TIP command (%1) for an Active transaction that is being ...
  61. The MS DTC Transaction Manager received an unknown or unexpected TIP command (%1) for an Active transaction that was created ...
  62. The MS DTC Transaction Manager sent a TIP "ABORT COMMAND" to another transaction manager and received a TIP "ERROR COMMAND" ...
  63. The MS DTC Transaction Manager sent a TIP "ABORT COMMAND" to another transaction manager and received an unknown or unexpected ...
  64. The MS DTC Transaction Manager sent a TIP "COMMIT, QUERY, or RECONNECT COMMAND" to another transaction manager and received ...
  65. The MS DTC Transaction Manager sent a TIP "COMMIT, QUERY, or RECONNECT COMMAND" to another transaction manager and received ...
  66. The MS DTC Transaction Manager sent a TIP "PREPARE COMMAND" to another transaction manager and received a TIP "ERROR COMMAND" ...
  67. The MS DTC Transaction Manager sent a TIP "PREPARE COMMAND" to another transaction manager and received an unknown or unexpected ...
  68. The MS DTC Transaction Manager sent a TIP "PULL COMMAND" to another transaction manager and received a TIP "ERROR COMMAND" ...
  69. The MS DTC Transaction Manager sent a TIP "PULL COMMAND" to another transaction manager and received an unknown or unexpected ...
  70. The MS DTC Transaction Manager sent a TIP "PUSH COMMAND" to another transaction manager and received a TIP "ERROR COMMAND" ...
  71. The MS DTC Transaction Manager sent a TIP "PUSH COMMAND" to another transaction manager and received an unknown or unexpected ...
  72. The MS DTC XA Transaction Manager called the XA resource manager's xa_close function. The call to the xa_close function failed ...
  73. The MS DTC XA Transaction Manager called the XA resource manager's xa_commit function with the TMONEPHASE flag set. The call ...
  74. The MS DTC XA Transaction Manager called the XA resource manager's xa_commit function. The call to the xa_commit function ...
  75. The MS DTC XA Transaction Manager called the XA resource manager's xa_commit function. The call to the xa_commit function ...