When you try to export local security policy settings in Microsoft Windows XP by using the Secedit.exe command-line utility, the security policy settings do not export. For example, if you type SecEdit /export /cfg c:\cfg.txt, the Cfg.txt file does not contain the information that you want to export.

Back to the top

This problem occurs because of a design change in the Windows XP architecture. In Microsoft Windows 2000, the security policy settings are stored in the Secedit.sdb database before the settings are applied. Windows XP does not store the security policy settings in the Secedit.sdb database. Therefore, when you run the SecEdit.exe utility in Windows XP, the utility does not find security policy settings in the Secedit.sdb database.

Back to the top

To resolve this problem, install the hotfix that is available in the following MIcrosoft Knowledge Base article:This hotfix contains an updated version of the Secedit.exe utility that can export the local security policy settings on a Windows XP-based computer.

Back to the top

To work around this problem, manually export and then save the Security Options list from the Local Security Settings snap-in. To do this, follow these steps:

1.	In Control Panel, double-click Administrative Tools, and then double-click Local Security Policy.
2.	In the left pane, expand Local Policies, and then click Security Options.
3.	On the Action menu, click Export List.
4.	In the Save in box, specify the location where you want to save the text file.
5.	In the File name box, type a name for the text file, and then click Save.
6.	On the File menu, click Exit to close Local Security Settings.

Back to the top

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Back to the top

For more information about how to use Secedit.sdb database to perform security analysis of your computer, click the following article numbers to view the articles in the Microsoft Knowledge Base:

Back to the top