Windows Server 2008

  1. The scheme "%s" has fonts not suitable for your language settings. Select "OK" to replace these with a suitable font and ...
  2. The scope for the Terminal Services license server was set successfully, but an error occurred while starting the Terminal ...
  3. The scope parameters are incorrect. Either the scope already exists or its subnet address and mask is inconsistent with the ...
  4. The screen saver can't run because it requires functionality that is not available on your video card with the current desktop ...
  5. The screen saver can't run because it requires hardware-acceleration functionality that is not available on the video card. ...
  6. The screen saver was dismissed. Subject: Security ID: %1 Account Name: %2 Account Domain: %3 Logon ID: %4 Session ID: %5 ...
  7. The ScreenHeight property specifies the height of the physical screen. This property has been deprecated in favor of a corresponding ...
  8. The screening minifilter driver detected and deleted an invalid screening configuration record on volume "%2 (%3)". The minifilter ...
  9. The screening minifilter driver failed to attach to volume "%2 (%3)" because the minifilter metadata on the volume is corrupt. ...
  10. The screening minifilter driver failed to attach to volume "%2 (%4)" because of an unexpected error. Error status: 3 While ...
  11. The screening minifilter driver failed to attach to volume "%2 (%5)" because the minifilter metadata on the volume is the ...
  12. The screening minifilter driver failed to load. Error status: 2 File screen enforcement and management will be unavailable ...
  13. The screening minifilter driver was detached from volume "%2 (%3)". Most likely this occurred as a result of a manual minifilter ...
  14. The screening minifilter driver was successfully attached to volume "%2 (%3)" and has received file screen and file group ...
  15. The screening minifilter driver was successfully attached to volume "%2 (%3)" and has received file screen and file group ...
  16. The screening minifilter driver was successfully attached to volume "%2 (%4)" but has not received file screen and file group ...
  17. The screening minifilter driver was unloaded outside the context of a system shutdown. Most likely this occurred as a result ...
  18. The ScreenSaverActive property indicates whether the screen saver is active. Values: TRUE or FALSE. A value of TRUE indicates ...
  19. The ScreenSaverSecure property determines whether the password is enabled for the screen saver. Values: TRUE or FALSE. If ...
  20. The ScreenWidth property specifies the width of the physical screen. This property has been deprecated in favor of a corresponding ...
  21. The script '{0}' cannot be run because it contained a "#requires" statement at line {1} for Windows PowerShell version {2} ...
  22. The script '{0}' cannot be run because it contained a "#requires" statement at line {1} with a shell ID of {2} that is incompatible ...
  23. The script '{0}' cannot be run because it contained a "#requires" statement at line {1} with a shell ID of {2} that is incompatible ...
  24. The script '{0}' cannot be run because it contained a "#requires" statement for which there was no valid registration in ...
  25. The script '{0}' cannot be run because the following Windows PowerShell snap-ins that are specified by its "#requires" statements ...
  26. The script block cannot be invoked because it contains more than one clause. The Invoke() method can only be used on script ...
  27. The ScriptPath property indicates the directory path to the user's logon script. A logon script automatically executes a ...
  28. The Scripts configuration file is not in a valid format. Script command and parameter settings are incorrectly specified. ...
  29. The SCSILogicalUnit property indicates the SCSI logical unit number (LUN) of the disk drive. The LUN is used to designate ...
  30. The search for objects in the schema directory partition failed during the following phase. Phase: %1 Additional Data Error ...
  31. The search provider could not be installed. This might have happened because: - A required file could not be downloaded - ...
  32. The search server cannot read or write to the registry. Check that the search server is running with administrative privileges. ...
  33. The search server does not exist. This error is obsolete and should no longer be reported. Call Microsoft Product Support. ...
  34. The search server is unable to accept the propagation because the disk has less than %2 MB of free disk space on drive %3. ...
  35. The search server was added successfully, but cannot be contacted. Check that the search service is executing on the remote ...
  36. The search server was not found. Stop and restart the search service. If propagation is being used, stop and restart the ...
  37. The search service is running as a local System service. To access Exchange documents, check that the search service is running ...
  38. The second authentication list must contain only user authentications or only computer authentication methods. The authentication ...
  39. The SecondValue parameter is not necessary for a member of type "{0}" and should not be specified. Do not specify the SecondValue ...
  40. The SecondValue parameter should not be null for a member of type "{0}". Specify a non-null value for the SecondValue parameter ...
  41. The secret allows the initiator to authenticate targets when performing mutual CHAP. Targets must also be configured with ...
  42. The secure channel (SC) verification on Active Directory Domain Controller %2 of domain %3 to domain %4 failed with error: ...
  43. The secure channel reset to %1 failed as the server does not support naming a Domain Controller. Establishing the secure ...
  44. The Secure Socket Tunneling Protocol (SSTP) negotiation has failed. The failure code is stored in the Data section of this ...
  45. The Secure Socket Tunneling Protocol (SSTP) service could not find either a Server Authentication certificate or an Any Purpose ...
  46. The Secure Socket Tunneling Protocol (SSTP) service could not initialize the HTTP layer for setting up the configuration. ...
  47. The Secure Socket Tunneling Protocol server has provided a certificate with an Enhanced Key Usage that is neither Server ...
  48. The Secure Socket Tunneling Protocol service could not be configured to accept incoming connections. The detailed error message ...
  49. The Secure Socket Tunneling Protocol service could not configure the following certificate for use with Internet Protocol ...
  50. The Secure Socket Tunneling Protocol service could not configure the following certificate for use with Internet Protocol ...
  51. The Secure Socket Tunneling Protocol service could not configure the route to the VPN server, which is required for the proper ...
  52. The Secure Socket Tunneling Protocol service could not get the network address of the remote server. This address is required ...
  53. The Secure Socket Tunneling Protocol service could not open the ConfigStore that is used for storing service-specific information. ...
  54. The Secure Socket Tunneling Protocol service could not open the Parameters section of the registry to read the configuration ...
  55. The Secure Socket Tunneling Protocol service could not secure the default URL. This can prevent the servicing of the SSTP ...
  56. The Secure Socket Tunneling Protocol service could not secure the URL with the new service configuration. Other applications ...
  57. The Secure Socket Tunneling Protocol service either could not read the SHA1 certificate hash from the registry or the data ...
  58. The Secure Socket Tunneling Protocol service either could not read the SHA256 certificate hash from the registry or the data ...
  59. The Secure Socket Tunneling Protocol service was not able to allocate memory for setting up the configuration for accepting ...
  60. The Secure Socket Tunneling Protocol service was not able to get the hash for the certificate configured with HTTP. The detailed ...
  61. The Security Account Database detected that the well known account %1 does not exist. The account has been recreated. Please ...
  62. The Security Account Database detected that the well known group or localgroup %1 does not exist. The group has been recreated. ...
  63. The security account manager (SAM) has determined that the security identifier (SID) for this computer is already in use ...
  64. The security account manager (SAM) has determined that the security identifier (SID) for this computer is already in use ...
  65. The security account manager (SAM) or local security authority (LSA) server was in the wrong state to perform the security ...
  66. The Security Account Manager failed a KDC request in an unexpected way. The error is in the data field. The account name ...
  67. The Security Accounts Manager failed to add the Enterprise Admins group to the local Administrators alias. To ensure proper ...
  68. The Security Center has reported that on-access spyware scanning is disabled. Either on-access scanning is disabled, or the ...
  69. The Security Center has reported that on-access virus scanning is disabled. Either on-access scanning is disabled, or the ...
  70. The Security Center is unable to identify an active anti-spyware application. Either there is no anti-spyware product installed, ...
  71. The Security Center is unable to identify an active anti-virus application. Either there is no anti-virus product installed ...
  72. The Security Center service failed to disconnect from external dependencies. wscsvc.dll will not be unloaded from svchost.exe. ...
  73. The security certificate presented by this website is valid, but Internet Explorer was unable to contact the issuer to ensure ...
  74. The security certificate was issued by a company you have not chosen to trust. View the certificate to determine whether ...
  75. The security certificate was issued by a company you have not chosen to trust. View the certificate to determine whether ...