| File name: | secedit.exe.mui |
| Size: | 25600 byte |
| MD5: | 35802158453d7fd9920963ed286dd634 |
| SHA1: | c5cec2c1f6c4abbc08affc3968ce687e0f819287 |
| SHA256: | 44a8ce88f956f55bf6cb617a130d272428f4532dafec9f39e3fc865e031d6ccb |
| Operating systems: | Windows 10 |
| Extension: | MUI |
| In x64: | secedit.exe Windows Security Configuration Editor Command Tool (32-bit) |
If an error occurred or the following message in English (U.S.) language and you cannot find a solution, than check answer in English. Table below helps to know how correctly this phrase sounds in English.
| id | English (U.S.) | English |
|---|---|---|
| 7100 | The task has completed successfully. |
The task has completed successfully. |
| 7101 | Can't open the template. |
Can't open the template. |
| 7102 | Template %s is validated |
Template %s is validated |
| 7103 | The task has completed. %s It's okay to ignore the warning. |
The task has completed. %s It's okay to ignore the warning. |
| 7104 | The task has completed with an error. |
The task has completed with an error. |
| 7105 | See log %s for detail info. |
See log %s for detail info. |
| 7106 | See log %windir%\security\logs\scesrv.log for detail info. |
See log %windir%\security\logs\scesrv.log for detail info. |
| 7107 | The file you specified may be corrupted. |
The file you specified may be corrupted. |
| 7115 | Template %s is registered successfully |
Template %s is registered successfully |
| 7116 | Group policy propagation from the domain has been initiated for this computer. It may take a few minutes for the propagation to complete and the new policy to take effect. Please check Application Log for errors, if any. | Group policy propagation from the domain has been initiated for this computer. It may take a few minutes for the propagation to complete and the new policy to take effect. Please check Application Log for errors, if any. |
| 7117 | Error to propagate policy. | Error to propagate policy. |
| 7118 | Analyzing system requires a personal database to store the analysis result. |
Analyzing system requires a personal database to store the analysis result. |
| 7119 | The /DB FileName must be provided. See help for the usage on /DB. |
The /DB FileName must be provided. See help for the usage on /DB. |
| 7120 | Configuring the current system with this template in the /overwrite mode will | Configuring the current system with this template in the /overwrite mode will |
| 7121 | result in losing the existing security records in the database specified. | result in losing the existing security records in the database specified. |
| 7123 | Do you want to continue this operation ? [y/n] | Do you want to continue this operation ? [y/n] |
| 7124 | Some files in the configuration are not found on this system so security cannot be set/queried. | Some files in the configuration are not found on this system so security cannot be set/queried. |
| 7125 | Some files in the configuration are locked exclusively by other processes so security cannot be set/queried. | Some files in the configuration are locked exclusively by other processes so security cannot be set/queried. |
| 7126 | Warnings occurred for some attributes during this operation. | Warnings occurred for some attributes during this operation. |
| 7162 | Configuring system requires a personal database to work with. |
Configuring system requires a personal database to work with. |
| 7163 | The /DB FileName must be provided. See help for usage on /DB. |
The /DB FileName must be provided. See help for usage on /DB. |
| 7167 | Specify verbose progress information in the log (Y/N) ? | Specify verbose progress information in the log (Y/N) ? |
| 7168 | Suppress output in the default log (Y/N) ? | Suppress output in the default log (Y/N) ? |
| 7180 | Completed %d percent (%d/%d) Process %s area | Completed %d percent (%d/%d) Process %s area |
| 7181 | Completed %d percent (%d/%d) Unknown area %x | Completed %d percent (%d/%d) Unknown area %x |
| 7182 | Completed %d percent (%d/%d) Process Security Policy area | Completed %d percent (%d/%d) Process Security Policy area |
| 7183 | Completed %d percent (%d/%d) Process Services area | Completed %d percent (%d/%d) Process Services area |
| 7184 | Y | Y |
| 7185 | Path is not canonicalizable. Please check paths for the files |
Path is not canonicalizable. Please check paths for the files |
| 7186 | Out of memory. |
Out of memory. |
| 7187 | Please check environment variables |
Please check environment variables |
| 7188 | Invalid path | Invalid path |
| 7189 | The template was validated successfully with the following data ignored. |
The template was validated successfully with the following data ignored. |
| 7190 | Rollback requires /cfg and /rbk templates. Additionally, the two templates should be different. |
Rollback requires /cfg and /rbk templates. Additionally, the two templates should be different. |
| 7191 | Rollback template being generated... |
Rollback template being generated... |
| 7192 | Rollback is not supported for File Security and Registry Security. |
Rollback is not supported for File Security and Registry Security. |
| 7193 | The syntax of this command is: secedit [/configure | /analyze | /import | /export | /validate | /generaterollback] |
The syntax of this command is: secedit [/configure | /analyze | /import | /export | /validate | /generaterollback] |
| 7194 | Allows you to configure a system with security settings stored in a database. The syntax of this command is: secedit /configure /db filename [/cfg filename] [/overwrite][/areas area1 area2...] [/log filename] [/quiet] /db filename - Specifies the database used to perform the security configuration. /cfg filename - Specifies a security template to import into the database prior to configuring the computer. Security templates are created using the Security Templates snap-in. /overwrite - Specifies that the database should be emptied prior to importing the security template. If this parameter is not specified, the settings in the security template are accumulated into the database. If this parameter is not specified and there are conflicting settings in the database and the template being imported, the template settings win. /areas - Specifies the security areas to be applied to the system. If this parameter is not specified, all security settings defined in the database are applied to the system. To configure multiple areas, separate each area by a space. The following security areas are supported: SECURITYPOLICY - Includes Account Policies, Audit Policies, Event Log Settings and Security Options. GROUP_MGMT - Includes Restricted Group settings USER_RIGHTS - Includes User Rights Assignment REGKEYS - Includes Registry Permissions FILESTORE - Includes File System permissions SERVICES - Includes System Service settings /log filename - Specifies a file in which to log the status of the configuration process. If not specified, configuration processing information is logged in the scesrv.log file which is located in the %%windir%%\security\logs directory. /quiet - Specifies that the configuration process should take place without prompting the user for any confirmation. Example: secedit /configure /db hisecws.sdb /cfg hisecws.inf /overwrite /log hisecws.log For all filenames, the current directory is used if no path is specified. |
Allows you to configure a system with security settings stored in a database. The syntax of this command is: secedit /configure /db filename [/cfg filename] [/overwrite][/areas area1 area2...] [/log filename] [/quiet] /db filename - Specifies the database used to perform the security configuration. /cfg filename - Specifies a security template to import into the database prior to configuring the computer. Security templates are created using the Security Templates snap-in. /overwrite - Specifies that the database should be emptied prior to importing the security template. If this parameter is not specified, the settings in the security template are accumulated into the database. If this parameter is not specified and there are conflicting settings in the database and the template being imported, the template settings win. /areas - Specifies the security areas to be applied to the system. If this parameter is not specified, all security settings defined in the database are applied to the system. To configure multiple areas, separate each area by a space. The following security areas are supported: SECURITYPOLICY - Includes Account Policies, Audit Policies, Event Log Settings and Security Options. GROUP_MGMT - Includes Restricted Group settings USER_RIGHTS - Includes User Rights Assignment REGKEYS - Includes Registry Permissions FILESTORE - Includes File System permissions SERVICES - Includes System Service settings /log filename - Specifies a file in which to log the status of the configuration process. If not specified, configuration processing information is logged in the scesrv.log file which is located in the %%windir%%\security\logs directory. /quiet - Specifies that the configuration process should take place without prompting the user for any confirmation. Example: secedit /configure /db hisecws.sdb /cfg hisecws.inf /overwrite /log hisecws.log For all filenames, the current directory is used if no path is specified. |
| 7195 | Allows you to analyze current systems settings against baseline settings that are stored in a database. The analysis results are stored in a separate area of the database and can be viewed in the Security Configuration and Analysis snap-in. The syntax of this command is: secedit /analyze /db filename [/cfg filename ] [/overwrite] [/log filename] [/quiet] /db filename - Specifies the database used to perform the analysis. /cfg filename - Specifies a security template to import into the database prior to performing the analysis. Security templates are created using the Security Templates snap-in. /log filename - Specifies a file in which to log the status of the configuration process. If not specified, configuration processing information is logged in the scesrv.log file which is located in the s%%windir%%\security\logs directory. /quiet - Specifies that the analysis process should take place without prompting the user for any confirmation. Example: secedit /analyze /db hisecws.sdb For all filenames, the current directory is used if no path is specified. |
Allows you to analyze current systems settings against baseline settings that are stored in a database. The analysis results are stored in a separate area of the database and can be viewed in the Security Configuration and Analysis snap-in. The syntax of this command is: secedit /analyze /db filename [/cfg filename ] [/overwrite] [/log filename] [/quiet] /db filename - Specifies the database used to perform the analysis. /cfg filename - Specifies a security template to import into the database prior to performing the analysis. Security templates are created using the Security Templates snap-in. /log filename - Specifies a file in which to log the status of the configuration process. If not specified, configuration processing information is logged in the scesrv.log file which is located in the s%%windir%%\security\logs directory. /quiet - Specifies that the analysis process should take place without prompting the user for any confirmation. Example: secedit /analyze /db hisecws.sdb For all filenames, the current directory is used if no path is specified. |
| 7196 | Allows you to generate a rollback template with respect to a configuration template. The syntax of this command is: secedit /generaterollback /cfg filename /rbk filename [/log filename] [/quiet] /db filename - Specifies the database used to perform the rollback. /cfg filename - Specifies a security template with respect to which a rollback template is generated. Security templates are created using the Security Templates snap-in. /rbk filename - Specifies a security template into which the rollback information is written. Security templates are created using the Security Templates snap-in. /log filename - Specifies a file in which to log the status of the rollback process. If not specified, rollback processing information is logged in the scesrv.log file which is located in the %%windir%%\security\logs directory. /quiet - Specifies that the rollback process should take place without prompting the user for any confirmation. Example: secedit /generaterollback /db hisecws.sdb /cfg hisecws.inf /rbk hisecwsrollback.inf /log hisecws.log For all filenames, the current directory is used if no path is specified. |
Allows you to generate a rollback template with respect to a configuration template. The syntax of this command is: secedit /generaterollback /cfg filename /rbk filename [/log filename] [/quiet] /db filename - Specifies the database used to perform the rollback. /cfg filename - Specifies a security template with respect to which a rollback template is generated. Security templates are created using the Security Templates snap-in. /rbk filename - Specifies a security template into which the rollback information is written. Security templates are created using the Security Templates snap-in. /log filename - Specifies a file in which to log the status of the rollback process. If not specified, rollback processing information is logged in the scesrv.log file which is located in the %%windir%%\security\logs directory. /quiet - Specifies that the rollback process should take place without prompting the user for any confirmation. Example: secedit /generaterollback /db hisecws.sdb /cfg hisecws.inf /rbk hisecwsrollback.inf /log hisecws.log For all filenames, the current directory is used if no path is specified. |
| 7197 | Allows you to import a security template into a database so that the settings specified in the template can be applied to a system or analyzed against a system. The syntax of this command is: secedit /import /db filename /cfg filename [/overwrite][/areas area1 area2...] [/log filename] [/quiet] /db filename - Specifies the database that the security template settings will be imported into. /cfg filename - Specifies a security template to import into the database. Security templates are created using the Security Templates snap-in. /overwrite - Specifies that the database should be emptied prior to importing the security template. If this parameter is not specified, the settings in the security template are accumulated into the database. If this parameter is not specified and there are conflicting settings in the database and the template being imported, the template settings win. /areas - Specifies the security areas to export. If this parameter is not specified, all security settings defined in the database are exported. To export specific areas, separate each area by a space. The following security areas are exported: SECURITYPOLICY - Includes Account Policies, Audit Policies, Event Log Settings and Security Options. GROUP_MGMT - Includes Restricted Group settings USER_RIGHTS - Includes User Rights Assignment REGKEYS - Includes Registry Permissions FILESTORE - Includes File System permissions SERVICES - Includes System Service settings /log filename - Specifies a file in which to log the status of the import process. If not specified, import processing information is logged in the scesrv.log file which is located in the %%windir%%\security\logs directory. /quiet - Specifies that the import process should take place without prompting the user for any confirmation. Example: secedit /import /db hisecws.sdb /cfg hisecws.inf /overwrite For all filenames, the current directory is used if no path is specified. |
Allows you to import a security template into a database so that the settings specified in the template can be applied to a system or analyzed against a system. The syntax of this command is: secedit /import /db filename /cfg filename [/overwrite][/areas area1 area2...] [/log filename] [/quiet] /db filename - Specifies the database that the security template settings will be imported into. /cfg filename - Specifies a security template to import into the database. Security templates are created using the Security Templates snap-in. /overwrite - Specifies that the database should be emptied prior to importing the security template. If this parameter is not specified, the settings in the security template are accumulated into the database. If this parameter is not specified and there are conflicting settings in the database and the template being imported, the template settings win. /areas - Specifies the security areas to export. If this parameter is not specified, all security settings defined in the database are exported. To export specific areas, separate each area by a space. The following security areas are exported: SECURITYPOLICY - Includes Account Policies, Audit Policies, Event Log Settings and Security Options. GROUP_MGMT - Includes Restricted Group settings USER_RIGHTS - Includes User Rights Assignment REGKEYS - Includes Registry Permissions FILESTORE - Includes File System permissions SERVICES - Includes System Service settings /log filename - Specifies a file in which to log the status of the import process. If not specified, import processing information is logged in the scesrv.log file which is located in the %%windir%%\security\logs directory. /quiet - Specifies that the import process should take place without prompting the user for any confirmation. Example: secedit /import /db hisecws.sdb /cfg hisecws.inf /overwrite For all filenames, the current directory is used if no path is specified. |
| 7198 | Allows you to validate the syntax of a security template. The syntax of this command is: secedit /validate filename /cfg filename - Specifies a security template to validate. Security templates are created using the Security Templates snap-in. Example: secedit /validate hisecws.inf For all filenames, the current directory is used if no path is specified. |
Allows you to validate the syntax of a security template. The syntax of this command is: secedit /validate filename /cfg filename - Specifies a security template to validate. Security templates are created using the Security Templates snap-in. Example: secedit /validate hisecws.inf For all filenames, the current directory is used if no path is specified. |
| 7199 | Allows you to export security settings stored in a database. The syntax of this command is: secedit /export [/db filename] [/mergedpolicy] /cfg filename [/areas area1 area2...] [/log filename] /db filename - Specifies the database to export data from. If not specified, system security database will be used. /cfg filename - Specifies a security template to export the database contents to. /mergedpolicy - Merges and exports domain and local policy security settings. /areas - Specifies the security areas to export. If this parameter is not specified, all security settings defined in the database are exported. To export specific areas, separate each area by a space. The following security areas are exported: SECURITYPOLICY - Includes Account Policies, Audit Policies, Event Log Settings and Security Options. GROUP_MGMT - Includes Restricted Group settings USER_RIGHTS - Includes User Rights Assignment REGKEYS - Includes Registry Permissions FILESTORE - Includes File System permissions SERVICES - Includes System Service settings /log filename - Specifies a file in which to log the status of the export process. If not specified, export processing information is logged in the scesrv.log file which is located in the %%windir%%\security\logs directory. Example: secedit /export /db hisecws.sdb /cfg hisecws.inf /log hisecws.log For all filenames, the current directory is used if no path is specified. |
Allows you to export security settings stored in a database. The syntax of this command is: secedit /export [/db filename] [/mergedpolicy] /cfg filename [/areas area1 area2...] [/log filename] /db filename - Specifies the database to export data from. If not specified, system security database will be used. /cfg filename - Specifies a security template to export the database contents to. /mergedpolicy - Merges and exports domain and local policy security settings. /areas - Specifies the security areas to export. If this parameter is not specified, all security settings defined in the database are exported. To export specific areas, separate each area by a space. The following security areas are exported: SECURITYPOLICY - Includes Account Policies, Audit Policies, Event Log Settings and Security Options. GROUP_MGMT - Includes Restricted Group settings USER_RIGHTS - Includes User Rights Assignment REGKEYS - Includes Registry Permissions FILESTORE - Includes File System permissions SERVICES - Includes System Service settings /log filename - Specifies a file in which to log the status of the export process. If not specified, export processing information is logged in the scesrv.log file which is located in the %%windir%%\security\logs directory. Example: secedit /export /db hisecws.sdb /cfg hisecws.inf /log hisecws.log For all filenames, the current directory is used if no path is specified. |
| 7220 | You do not have sufficient permissions to perform this command. Make sure that you are running as the local administrator or have opened the command prompt using the 'Run as administrator' option. |
You do not have sufficient permissions to perform this command. Make sure that you are running as the local administrator or have opened the command prompt using the 'Run as administrator' option. |
| File Description: | Windows Security Configuration Editor Command Tool |
| File Version: | 10.0.15063.0 (WinBuild.160101.0800) |
| Company Name: | Microsoft Corporation |
| Internal Name: | SeCEdit |
| Legal Copyright: | © Microsoft Corporation. All rights reserved. |
| Original Filename: | SeCEdit |
| Product Name: | Microsoft® Windows® Operating System |
| Product Version: | 10.0.15063.0 |
| Translation: | 0x409, 1200 |