Article ID: 815424 - View products that this article applies to.
You may experience one or more of the following symptoms when you apply the "Password protect the screen saver" Group Policy setting to Windows XP and Windows XP Service Pack 1 (SP1)-based computers:
The "Password protect the screen saver" Group Policy setting is set in the following registry entry:
When the value is set to 0 (zero), password protection for the screen saver is turned off. When the value is set to 1, password protection for the screen saver is turned on.
In Windows XP, the
ScreenSaverIsSecureregistry entry is a REG_DWORD (numeric) value. Other operating systems, including Windows Server 2003, Windows 2000, and Windows XP SP1, store
ScreenSaverIsSecureas a REG_SZ (string) value. This type mismatch can cause Windows XP client computers and Windows XP SP1 client computers to misinterpret the policy setting.
Service pack informationTo resolve this problem, obtain the latest service pack for Microsoft Windows XP. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/322389/EN-US/ )How to obtain the latest Windows XP service pack
Hotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Date Time Version Size File name ----------------------------------------------------- 17-Mar-2003 20:05 5.1.2600.112 430,080 Winlogon.exe
Windows XP Service Pack 1
Date Time Version Size File name ----------------------------------------------------- 07-Mar-2003 13:22 5.1.2600.1182 518,144 Winlogon.exe
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756To work around this problem, turn on the local password-protection setting for the screen saver by editing the registry. To do so:
(http://support.microsoft.com/kb/322756/ )How to back up and restore the registry in Windows
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Microsoft Windows XP Service Pack 2.
When you install Windows XP SP1 or the hotfix that is documented in the following Microsoft Knowledge Base article, the
ScreenSaverIsSecureGroup Policy setting is changed to a REG_SZ value.
318449The hotfix that is documented in this article permits Windows XP client computers to correctly interpret the
(http://support.microsoft.com/kb/318449/EN-US/ )PowerPoint Slide Show Turns Off Screen Saver and Ignores System Group Policy
ScreenSaverIsSecureregistry entry regardless of whether it is stored as a REG_DWORD or a REG_SZ value. This eliminates any inconsistencies that may occur when policies are created or edited on different operating systems.
Article ID: 815424 - Last Review: May 17, 2007 - Revision: 3.8
Contact us for more help
Connect with Answer Desk for expert help.