{"id":2446,"date":"2013-12-10T00:01:00","date_gmt":"2013-12-10T00:01:00","guid":{"rendered":"https:\/\/blogs.technet.microsoft.com\/heyscriptingguy\/2013\/12\/10\/use-powershell-to-create-registry-keys\/"},"modified":"2013-12-10T00:01:00","modified_gmt":"2013-12-10T00:01:00","slug":"use-powershell-to-create-registry-keys","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/scripting\/use-powershell-to-create-registry-keys\/","title":{"rendered":"Use PowerShell to Create Registry Keys"},"content":{"rendered":"

Summary<\/strong>: Use Windows PowerShell to create and manage registry keys.<\/p>\n

Microsoft Scripting Guy, Ed Wilson, is here. Today I am happy to provide you with an excerpt from my book, Windows PowerShell 3.0 Step by Step<\/a>, published by Microsoft Press.<\/p>\n

\"Image<\/a><\/p>\n

Note <\/strong> The registry contains information that is vital to the operation and configuration of your computer. Serious problems could arise if you edit the registry incorrectly. Therefore, it is important to back up your system prior to attempting to make any changes. For information about backing up your registry, see article 322756<\/a> in the Microsoft Knowledge Base. For general information about working with the registry, see article 310516<\/a>.<\/p>\n

Creating a new registry key by using Windows PowerShell is the same as creating a new file or a new folder. All three processes use the New-Item<\/strong> cmdlet. In addition, you might use the Test-Path<\/strong> cmdlet to determine if the registry key already exists. You may also want to change your working location to one of the registry drives. If you do this, you might use the Push-Location<\/strong>, Set-Location<\/strong>, and Pop-Location<\/strong> cmdlets. This is, of course, the long way of doing things…<\/p>\n

Just the steps<\/strong><\/p>\n

    \n
  1. Store the current working location by using the Push-Location<\/strong> cmdlet.<\/li>\n
  2. Change the current working location to the appropriate registry drive by using the Set-Location<\/strong> cmdlet.<\/li>\n
  3. Use the Test-Path<\/strong> cmdlet to determine if the registry key already exists.<\/li>\n
  4. Use the New-Item<\/strong> cmdlet to create the new registry key.<\/li>\n
  5. Use the Pop-Location<\/strong> cmdlet to return to the starting working location.<\/li>\n<\/ol>\n

    The following example creates a new registry key named hsg off the HKEY_CURRENT_USERS software registry hive. It illustrates each of the five steps previously detailed.<\/p>\n

    Push-Location
    Set-Location HKCU:
    Test-Path .\\Software\\test
    New-Item -Path .\\Software -Name test
    Pop-Location<\/p>\n

    The commands and the associated output from the commands are shown in the following image:<\/p>\n

    \"Image<\/a><\/p>\n

    The short way to create a new registry key<\/h3>\n

    It is not always necessary to change the working location to a registry drive when you create a new registry key. In fact, it is not even necessary to use the Test-Path<\/strong> cmdlet to determine if the registry key exists. If the registry key already exists, an error generates. If you want to overwrite the registry key, use the Force<\/strong> <\/em>parameter.<\/p>\n

    Note <\/strong> How you choose to deal with an already existing registry key is one of those design decisions <\/em>that confront IT pros who venture very far into the world of scripting. Software developers are very familiar with these types of decisions, and they usually deal with them during the analyzing requirements portion of the development lifecycle. IT pros who open the Windows PowerShell ISE first, and think about the design requirements second, become easily stymied, or else write-in problems. For more information about this, see my Microsoft Press book, Windows PowerShell 2.0 Best Practices<\/a>. <\/em><\/p>\n

    The following example creates a new registry key named test<\/strong> in the HKCU:\\Software location. Because the command includes the full path, it does not need to execute from the HKCU drive. Because the command uses the Force<\/strong> <\/em>switched parameter, the command overwrites the HKCU:\\Software\\test registry key if it already exists.<\/p>\n

    New-Item -Path HKCU:\\Software -Name test –Force<\/p>\n

    Just the steps: The short way to create a new registry key<\/strong><\/p>\n

      \n
    1. Include the full path to the registry key to create.<\/li>\n
    2. Use the Force<\/strong> <\/em>parameter to overwrite any existing registry key of the same name.<\/li>\n<\/ol>\n

      In the following image, the first attempt to create a test registry key fails because it already exists. The second command uses the Force<\/strong> <\/em>parameter, which causes the command to overwrite the existing registry key, and therefore it succeeds without creating an error.<\/p>\n

      \"Image<\/a><\/p>\n

      Setting the default value for the key<\/h3>\n

      The previous examples do not set the default value for the newly created registry key. If the registry key already exists (as it does in this specific case), use the Set-Item<\/strong> cmdlet to assign a default value to the registry key. The steps to accomplish this are shown here:<\/p>\n

      Just the steps: Assign a default value to an existing registry key<\/strong><\/p>\n

        \n
      1. Use the Set-Item<\/strong> cmdlet and supply the complete path to the existing registry key.<\/li>\n
      2. Supply the default value in the Value<\/strong> <\/em>parameter of the Set-Item<\/strong> cmdlet.<\/li>\n<\/ol>\n

        The following command assigns the value “test key”<\/strong> to the default property value of the hsg registry key contained in the HKCU:\\Software location.<\/p>\n

        Set-Item -Path HKCU:\\Software\\test -Value “test key”<\/p>\n

        Join me tomorrow when I will talk about more cool Windows PowerShell stuff.<\/p>\n

        I invite you to follow me on Twitter<\/a> and Facebook<\/a>. If you have any questions, send email to me at scripter@microsoft.com<\/a>, or post your questions on the Official Scripting Guys Forum<\/a>. See you tomorrow. Until then, peace.<\/p>\n

        Ed Wilson, Microsoft Scripting Guy<\/strong><\/p>\n","protected":false},"excerpt":{"rendered":"

        Summary: Use Windows PowerShell to create and manage registry keys. Microsoft Scripting Guy, Ed Wilson, is here. Today I am happy to provide you with an excerpt from my book, Windows PowerShell 3.0 Step by Step, published by Microsoft Press. Note  The registry contains information that is vital to the operation and configuration of your […]<\/p>\n","protected":false},"author":596,"featured_media":87096,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[51,3,4,45],"class_list":["post-2446","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-scripting","tag-getting-started","tag-scripting-guy","tag-scripting-techniques","tag-windows-powershell"],"acf":[],"blog_post_summary":"

        Summary: Use Windows PowerShell to create and manage registry keys. Microsoft Scripting Guy, Ed Wilson, is here. Today I am happy to provide you with an excerpt from my book, Windows PowerShell 3.0 Step by Step, published by Microsoft Press. Note  The registry contains information that is vital to the operation and configuration of your […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/2446","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/users\/596"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/comments?post=2446"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/2446\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media\/87096"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media?parent=2446"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/categories?post=2446"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/tags?post=2446"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}