Windows 8

  1. The Scenario Event Mapper was unable to start a new scenario for provider %1 (event ID %2) because the maximum number of ...
  2. The schedule attribute of the following site link object is configured in a way that the sites it references are never connected. ...
  3. The schedule attribute of the following site link object is not valid. Site link object: %1 As a result, this schedule will ...
  4. The schedule name contains characters that are not valid. The name cannot start with a hyphen (-) and cannot contain spaces ...
  5. The schedule on the following Connection object has been updated. This object represents a replication connection between ...
  6. The schedule type (subaction) was not specified. You must specify one of the following schedule types: full, empty, default, ...
  7. The scheduled backup configuration conflicts with current Group Policy settings, error - '%1' ('%2'). The scheduled backup ...
  8. The scheduled backup configuration conflicts with current Group Policy settings, error - '%1' ('%6'). The scheduled backup ...
  9. The scheduled backup configuration conflicts with current Group Policy settings, error - '%1'. The scheduled backup operation ...
  10. The scheduled backup configuration conflicts with current Group Policy settings, error - '%1'. The scheduled backup operation ...
  11. The scheduled backup configuration conflicts with current Group Policy settings, error - '%2'. The scheduled backup operation ...
  12. The scheduled backup operation that started at '%1' has failed because the schedule settings were not found. Please reconfigure ...
  13. The scheduled backup settings: Bare metal recovery : %1 System state backup: %2 Volumes in backup: %3 Components in backup: ...
  14. The scheduled backup was canceled. To create a new backup, you must reconfigure scheduled backups or run a one-time backup ...
  15. The scheduled job definition {0} cannot be removed because one or more instances are currently running. You can remove and ...
  16. The scheduled job definition {0} could not be saved because one of the values in the ArgumentList parameter cannot be converted ...
  17. The scheduled replication did not take place because the system was too busy to execute the request within the schedule window. ...
  18. The ScheduledCast namespace %1 using content provider %2 could not be registered as it starts in the past. The namespace ...
  19. The schema document root element is not 'schema', or is missing the 'targetNamespace' attribute, or elementFormDefault is ...
  20. The schema for the Windows Assessment Services inventory database is corrupt. Initialize the Windows Assessment Services ...
  21. The schema is invalid. You will not be able to import it. More details are in the log window below. Do you want to continue? ...
  22. The schema operations master role and the domain naming operations master role (also known as flexible single master operations ...
  23. The schema version of the database is from a newer version of WSUS than currently installed. You must either patch your WSUS ...
  24. The schemaIdGuid attribute value for the following schema class duplicates the schemaIdGuid value for an existing class. ...
  25. The schemaIdGuid value for the following attribute duplicates the schemaIdGuid value for an existing attribute. Attribute: ...
  26. The scope parameters are incorrect. Either the scope already exists or its subnet address and mask is inconsistent with the ...
  27. The scope prefix "$WORKFLOW:" cannot be used in an InlineScript activity. To reference a workflow variable in an InlineScript ...
  28. The scratch directory size might be insufficient to perform this operation. This can cause unexpected behavior. Use the /ScratchDir ...
  29. The screen saver can't run because it requires functionality that is not available on your video card with the current desktop ...
  30. The screen saver can't run because it requires hardware-acceleration functionality that is not available on the video card. ...
  31. The screen saver was dismissed. Subject: Security ID: %1 Account Name: %2 Account Domain: %3 Logon ID: %4 Session ID: %5 ...
  32. The screening minifilter driver detected and deleted an invalid screening configuration record on volume "%2 (%3)". The minifilter ...
  33. The screening minifilter driver failed to attach to volume "%2 (%3)" because the minifilter metadata on the volume is corrupt. ...
  34. The screening minifilter driver failed to attach to volume "%2 (%4)" because of an unexpected error. Error status: 3 While ...
  35. The screening minifilter driver failed to attach to volume "%2 (%5)" because the minifilter metadata on the volume is the ...
  36. The screening minifilter driver failed to load. Error status: 2 File screen enforcement and management will be unavailable ...
  37. The screening minifilter driver was detached from volume "%2 (%3)". Most likely this occurred as a result of a manual minifilter ...
  38. The screening minifilter driver was successfully attached to volume "%2 (%3)" and has received file screen and file group ...
  39. The screening minifilter driver was successfully attached to volume "%2 (%3)" and has received file screen and file group ...
  40. The screening minifilter driver was successfully attached to volume "%2 (%4)" but has not received file screen and file group ...
  41. The screening minifilter driver was unloaded outside the context of a system shutdown. Most likely this occurred as a result ...
  42. The script '{0}' cannot be run because it contained a "#requires" statement for Windows PowerShell version {1}. The version ...
  43. The script '{0}' cannot be run because it contained a "#requires" statement with a shell ID of {1} that is incompatible with ...
  44. The script '{0}' cannot be run because it contained a "#requires" statement with a shell ID of {1} that is incompatible with ...
  45. The script '{0}' cannot be run because the following modules that are specified by the "#requires" statements of the script ...
  46. The script '{0}' cannot be run because the following snap-ins that are specified by the "#requires" statements of the script ...
  47. The script block cannot be converted because it contains more than one clause. Expressions or control structures are not ...
  48. The script block cannot be converted to an open generic type. Please define an appropriate closed generic type and retry. ...
  49. The script block cannot be invoked because it contains more than one clause. The Invoke() method can only be used on script ...
  50. The Scripts configuration file is not in a valid format. Script command and parameter settings are incorrectly specified. ...
  51. The search for objects in the schema directory partition failed during the following phase. Phase: %1 Additional Data Error ...
  52. The search provider could not be installed. This might have happened because: - A required file could not be downloaded - ...
  53. The search server cannot read or write to the registry. Check that the search server is running with administrative privileges. ...
  54. The search server does not exist. This error is obsolete and should no longer be reported. Call Microsoft Product Support. ...
  55. The search server was added successfully, but cannot be contacted. Check that the search service is executing on the remote ...
  56. The search server was not found. Stop and restart the search service. If propagation is being used, stop and restart the ...
  57. The search service has detected corrupted data files in the index {id=%2}. The service will attempt to automatically correct ...
  58. The search service is running as a local System service. To access Exchange documents, check that the search service is running ...
  59. The second authentication list must contain only user authentications or only computer authentication methods. The authentication ...
  60. The second node is not accessible due to the following error: {0}. If the Cluster Name and Domain Join Wizard is applying ...
  61. The second node name "{0}" is not in a valid DNS format. DNS names must contain only alphanumeric characters. The following ...
  62. The second node name does not exist in the Windows registry. Refer to the product troubleshooting documentation or contact ...
  63. The second node named "{0}" is not a valid NetBIOS name. NetBIOS names must contain only alphanumeric characters. The following ...
  64. The secondary server {1} is configured to receive zone update notifications for the zone {0}, but it does not host the zone. ...
  65. The SecondValue parameter is not necessary for a member of type "{0}" and should not be specified. Do not specify the SecondValue ...
  66. The SecondValue parameter should not be null for a member of type "{0}". Specify a non-null value for the SecondValue parameter ...
  67. The secure channel (SC) verification on Active Directory Domain Controller %2 of domain %3 to domain %4 failed with error: ...
  68. The secure channel reset to %1 failed as the server does not support naming a Domain Controller. Establishing the secure ...
  69. The Secure Socket Tunneling Protocol (SSTP) service could not find either a Server Authentication certificate or an Any Purpose ...
  70. The Secure Socket Tunneling Protocol (SSTP) service could not initialize the HTTP layer for setting up the configuration. ...
  71. The Secure Socket Tunneling Protocol service could not be configured to accept incoming connections. The detailed error message ...
  72. The Secure Socket Tunneling Protocol service could not configure the following certificate for use with Internet Protocol ...
  73. The Secure Socket Tunneling Protocol service could not configure the following certificate for use with Internet Protocol ...
  74. The Secure Socket Tunneling Protocol service could not configure the route to the VPN server, which is required for the proper ...
  75. The Secure Socket Tunneling Protocol service could not get the network address of the remote server. This address is required ...