Select the product you need help with
How to add, modify, or delete registry subkeys and values by using a .reg fileArticle ID: 310516 - View products that this article applies to. This article was previously published under Q310516 On This PageSummaryImportant 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: 322756
This step-by-step article describes how to add, modify, or delete registry subkeys and values by using a Registration Entries (.reg) file. Regedit.exe uses .reg files to import and export registry subkeys and values. You can use these .reg files to remotely distribute registry changes to several Windows-based computers. When you run a .reg file, the file contents merge into the local registry. Therefore, you must distribute .reg files with caution.
(http://support.microsoft.com/kb/322756/
)
How to back up and restore the registry in WindowsSyntax of .Reg FilesA .reg file has the following syntax:RegistryEditorVersion Blank line [RegistryPath1] "DataItemName1"="DataType1:DataValue1" DataItemName2"="DataType2:DataValue2" Blank line [RegistryPath2] "DataItemName3"="DataType3:DataValue3" where: RegistryEditorVersion is either "Windows Registry Editor Version 5.00" for Windows 2000, Windows XP, and Windows Server 2003, or "REGEDIT4" for Windows 98 and Windows NT 4.0. The "REGEDIT4" header also works on Windows 2000-based, Windows XP-based, and Windows Server 2003-based computers. Blank line is a blank line. This identifies the start of a new registry path. Each key or subkey is a new registry path. If you have several keys in your .reg file, blank lines can help you to examine and to troubleshoot the contents. RegistryPathx is the path of the subkey that holds the first value you are importing. Enclose the path in square brackets, and separate each level of the hierarchy by a backslash. For example: [ A .reg file can contain several registry paths.
If the bottom of the hierarchy in the path statement does not exist in the registry, a new subkey is created. The contents of the registry files are sent to the registry in the order you enter them. Therefore, if you want to create a new subkey with another subkey below it, you must enter the lines in the correct order.HKEY_LOCAL_ MACHINE\SOFTWARE\Policies\Microsoft\Windows\System ]DataItemNamex is the name of the data item that you want to import. If a data item in your file does not exist in the registry, the .reg file adds it (with the value of the data item). If a data item does exist, the value in your .reg file overwrites the existing value. Quotation marks enclose the name of the data item. An equal sign (=) immediately follows the name of the data item. DataTypex is the data type for the registry value and immediately follows the equal sign. For all the data types other than REG_SZ (a string value), a colon immediately follows the data type. If the data type is REG_SZ , do not include the data type value or colon. In this case, Regedit.exe assumes REG_SZ for the data type. The following table lists the typical registry data types: Collapse this table
256986 DataValuex immediately follows the colon (or the equal sign with REG_SZ) and must be in the appropriate format (for example, string or hexadecimal). Use hexadecimal format for binary data items.
(http://support.microsoft.com/kb/256986/
)
Description of the Microsoft Windows registry
Note You can enter several data item lines for the same registry path. Note the registry file should contain a blank line at the bottom of the file. Adding Registry Subkeys or Adding and Changing Registry ValuesTo add a registry subkey or add or change a registry value, make the appropriate changes in the registry, and then export the appropriate subkey or subkeys. Exported registry subkeys are automatically saved as .reg files. To make changes to the registry and export your changes to a .reg file, follow these steps:
Deleting Registry Keys and ValuesTo delete a registry key with a .reg file, put a hyphen (-) in front of the RegistryPath in the .reg file. For example, to delete the Test subkey from the following registry key:HKEY_LOCAL_MACHINE\Software HKEY_LOCAL_MACHINE\Software\Test [
To delete a registry value with a .reg file, put a hyphen (-) after the equals sign following the DataItemName in the .reg file. For example, to delete the TestValue registry value from the following registry key:-HKEY_LOCAL_MACHINE\Software\Test ]HKEY_LOCAL_MACHINE\Software\Test HKEY_LOCAL_MACHINE\Software\Test "TestValue"=- Renaming Registry Keys and ValuesTo rename a key or value, delete the key or value, and then create a new key or value with the new name.Distributing Registry ChangesYou can send a .reg file to users in an e-mail message, put a .reg file on a network share and direct users to the network share to run it, or you can add a command to the users' logon scripts to automatically import the .reg file when they log on. When users run the .reg file, they receive the following messages:If the user clicks Yes, the user receives the following message: Regedit.exe supports a /s command-line switch to not display these messages. For example, to silently run the .reg file (with the /s switch) from a login script batch file, use the following syntax:regedit.exe /s path of .reg file You can also use Group Policy or System Policy to distribute registry changes across your network. For additional information, visit the following Microsoft Web site:http://msdn2.microsoft.com/en-us/library/ms954395.aspx Note If the changes work, you can send the registration file to the appropriate users on the network.
(http://msdn2.microsoft.com/en-us/library/ms954395.aspx)
PropertiesArticle ID: 310516 - Last Review: June 5, 2013 - Revision: 10.0 Applies to
| Article Translations
|


Back to the top








