System command

secedit export command

Exports security settings stored in a database configured with security templates. This guide lists the documented syntax and parameters for secedit export; check Microsoft Learn for version, role and execution-context requirements.

Availability: Microsoft Learn command reference spanning Windows client and Windows Server releases; some entries are legacy, role-specific, optional-feature or interactive subcommands.中文

Documented syntax

secedit /export [/db <database file name>] [/mergedpolicy] /cfg <configuration file name> [/areas [securitypolicy | group_mgmt | user_rights | regkeys | filestore | services]] [/log <log file name>] [/quiet]

The linked Microsoft Learn article is the upstream authority. Availability may depend on Windows release, role, optional feature or interactive tool context.

Syntax pattern

Syntax pattern from Microsoft Learn; replace placeholders and choose only one documented alternative before use.

secedit /export [/db <database file name>] [/mergedpolicy] /cfg <configuration file name> [/areas [securitypolicy | group_mgmt | user_rights | regkeys | filestore | services]] [/log <log file name>] [/quiet]

Parameters, options and clauses

Option / clauseDescription
/dbMicrosoft documents this switch; use the linked reference for accepted values, effects and version limits.
/exportMicrosoft documents this switch; use the linked reference for accepted values, effects and version limits.
/mergedpolicyMicrosoft documents this switch; use the linked reference for accepted values, effects and version limits.
/cfgMicrosoft documents this switch; use the linked reference for accepted values, effects and version limits.
/areasMicrosoft documents this switch; use the linked reference for accepted values, effects and version limits.
/logMicrosoft documents this switch; use the linked reference for accepted values, effects and version limits.
/quietMicrosoft documents this switch; use the linked reference for accepted values, effects and version limits.
Safety note

Review a command and its target before running it. Commands that alter files, services, accounts, disks, permissions or databases may be difficult to reverse. Test in a safe environment and keep backups.

Official reference ↗Back to directory