Summary<\/b>: Microsoft Scripting Guy, Ed Wilson, shows how to use Windows PowerShell to enumerate all the properties and their values under a registry key.<\/p>\n
![\"Hey,](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/29\/2019\/02\/q-for-powertip.jpg\")
Hey, Scripting Guy! I have a question. It seems that getting the property values under a registry key is a tedious process. It looks like I need to know the exact property value to find out its value. Often I do not have this information. I would like a way to say, “Just give me the property values and their associated value.” I do not want to do a lot of work to get this information. Is it possible?<\/p>\n
—BW<\/p>\n
![\"Hey,](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/29\/2019\/02\/a-for-powertip.jpg\")
Hello BW,<\/p>\n
Microsoft Scripting Guy, Ed Wilson, is here. I just checked on the status of an order of Monkey Picked Oolong Tea that the Scripting Wife ordered for me. It arrives tomorrow. Charlotte, North Carolina in the United States is not a huge tea market—but hey, I have great Internet access at home and that gives me access to some of the best tea brokers in the world. I first ran across Monkey Picked tea in a small tearoom while the Scripting Wife and I were on our way to the Mark Minasi Conference<\/a>. I had the Monkey Picked Oolong; she had hot chocolate. But she remembered how much I kept going on and on about the light and delicate flavor, and next thing I know, we have a package arriving tomorrow.<\/p>\n Note<\/b> This is the fifth blog in a series of Hey, Scripting Guy! Blogs that discuss using the Registry provider. The first blog, Using the Registry Provider to Simply Registry Access<\/a> <\/i>posted on Monday. Tuesday I discussed using the *restore* cmdlets<\/a> to perform a system state backup of a computer prior to manipulating the registry. On Wednesday I talked about creating new registry keys and assigning default values<\/a>. In the fourth blog, I talked about creating new registry keys on remote computer systems<\/a>. I also discussed creating registry property values. For additional information about working with the registry via Windows PowerShell, see this collection of blogs<\/a>.<\/p>\n Note<\/b> For a VBScript version of this blog, see Hey, Scripting Guy! How Can I Retrieve All the Values in a Registry Key?<\/a><\/p>\n Because of the hierarchical nature of the registry in Windows, the file system metaphor sort of breaks down. On a file system drive, you can use the New-Item<\/b> cmdlet to create a folder (directory), and then go back and create a file inside the folder by using the same cmdlet. With the registry, that is not the case. New-Item<\/b> creates the registry keys, but it is the New-ItemProperty<\/b> cmdlet that creates the properties that are associated with the registry keys. This concept is shown in the image that follows.<\/p>\n Yesterday’s Hey, Scripting Guy! Blog talked about retrieving registry properties<\/a>. In that blog, I discussed using the Get-ItemProperty<\/b> cmdlet to retrieve registry property values, in addition to the specific registry property value value. (I know, it gets a little redundant). But as you pointed out, BW, from the perspective of perusing preset registry values, knowing an exact registry property value name is not the most efficient way of doing things.<\/p>\n The image that follows illustrates the Winlogon <\/i>registry key. This registry key has four registry properties (in addition to the Default<\/i> registry property, which is not set in this example). <\/i><\/p>\n There are several steps involved in obtaining the value of the registry property values under a specific registry key.<\/p>\n Only the steps…<\/p>\n Enumerating registry property values:<\/p>\n Note<\/b> When you are typing the path to the specific registry key, remember that you can use tab expansion. The use of the Windows PowerShell tab expansion feature not only saves time typing, but it also invariably saves time troubleshooting mistyped commands. It is essential that you train yourself to use tab expansion everywhere it is available.<\/p>\n The Get-RegistryKeyPropertiesAndValues.ps1 script follows the previous Enumerating registry property values <\/i>steps, but it adds a bit of extra power to the equation by creating a custom object for each registry property\/value combination. The script creates a new custom object for each key\/property pair. To do this, the script creates the object inside the Foreach-Object<\/b> cmdlet. The resulting object pipes to the Format-Table<\/b> for display to the console. The script then returns to the original working location by using the Pop-Location<\/b> cmdlet. The complete Get-RegistryKeyPropertiesAndValues.ps1 script is shown here.<\/p>\n Get-RegistryKeyPropertiesAndValues.ps1<\/p>\n Push-Location<\/p>\n Set-Location ‘HKCU:\\Software\\Microsoft\\Windows NT\\CurrentVersion\\Winlogon’<\/p>\n Get-Item . |<\/p>\n Select-Object -ExpandProperty property |<\/p>\n ForEach-Object {<\/p>\n New-Object psobject -Property @{“property”=$_;<\/p>\n “Value” = (Get-ItemProperty -Path . -Name $_).$_}} |<\/p>\n Format-Table property, value -AutoSize<\/p>\n Pop-Location<\/p>\n It is rather easy to convert the above script to a function. The Get-RegistryKeyPropertiiesAndValues function appears here.<\/p>\n Get-RegistryKeyPropertiesAndValues Function<\/p>\n <\/p>\n Function Get-RegistryKeyPropertiesAndValues<\/p>\n {<\/p>\n <#<\/p>\n .Synopsis<\/p>\n This function accepts a registry path and returns all reg key properties and values<\/p>\n .Description<\/p>\n This function returns registry key properies and values.<\/p>\n .Example<\/p>\n Get-RegistryKeyPropertiesAndValues -path ‘HKCU:\\Volatile Environment’<\/p>\n Returns all of the registry property values under the \\volatile environment key<\/p>\n .Parameter path<\/p>\n The path to the registry key<\/p>\n .Notes<\/p>\n NAME: Get-RegistryKeyPropertiesAndValues<\/p>\n AUTHOR: ed wilson, msft<\/p>\n LASTEDIT: 05\/09\/2012 15:18:41<\/p>\n KEYWORDS: Operating System, Registry, Scripting Techniques, Getting Started<\/p>\n HSG: 5-11-12<\/p>\n .Link<\/p>\n Http:\/\/www.ScriptingGuys.com\/blog<\/p>\n #Requires -Version 2.0<\/p>\n #><\/p>\n Param(<\/p>\n [Parameter(Mandatory=$true)]<\/p>\n [string]$path)<\/p>\n Push-Location<\/p>\n Set-Location -Path $path<\/p>\n Get-Item . |<\/p>\n Select-Object -ExpandProperty property |<\/p>\n ForEach-Object {<\/p>\n New-Object psobject -Property @{“property”=$_;<\/p>\n “Value” = (Get-ItemProperty -Path . -Name $_).$_}}<\/p>\n Pop-Location<\/p>\n } #end function Get-RegistryKeyPropertiesAndValues<\/p>\n To use the Get-RegistryKeyPropertiesAndValues<\/b> function to obtain registry key properties and their associated values, pass the path to it. For example, the image that follows illustrates the Volatile Environment <\/i>registry key. On the right are a large number of registry key properties.<\/p>\n Open the Windows PowerShell ISE and load the function by opening the script that contains it. Next load the function into memory by clicking the run button (or pressing F5). When it is loaded into memory, call the function by typing the function name in the immediate window and providing a path to a specific registry key. For this example, use the HKCU:\\Volatile Environment registry key (make sure you put quotation marks around the entire path to the registry key). Use the Format-Table<\/b> cmdlet to display the property name and then the property value. The following command illustrates a typical command line.<\/p>\n Get-RegistryKeyPropertiesAndValues -path ‘HKCU:\\Volatile Environment’ | ft property, value -AutoSize<\/p>\n This technique is shown in the following image.<\/p>\n BW, that is all there is to obtaining the value of the registry property values under a specific registry key. Registry Week will continue tomorrow when I will talk about modifying registry property values.<\/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<\/b> <\/p>\n","protected":false},"excerpt":{"rendered":" Summary: Microsoft Scripting Guy, Ed Wilson, shows how to use Windows PowerShell to enumerate all the properties and their values under a registry key. Hey, Scripting Guy! I have a question. It seems that getting the property values under a registry key is a tedious process. It looks like I need to know the exact […]<\/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,31,26,3,4,45],"class_list":["post-9461","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-scripting","tag-getting-started","tag-operating-system","tag-registry","tag-scripting-guy","tag-scripting-techniques","tag-windows-powershell"],"acf":[],"blog_post_summary":" Summary: Microsoft Scripting Guy, Ed Wilson, shows how to use Windows PowerShell to enumerate all the properties and their values under a registry key. Hey, Scripting Guy! I have a question. It seems that getting the property values under a registry key is a tedious process. It looks like I need to know the exact […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/9461","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=9461"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/9461\/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=9461"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/categories?post=9461"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/tags?post=9461"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Working with registry property values<\/h2>\n
![\"Image](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/29\/2019\/02\/6305.hsg-5-11-12-01.png\" "\\"Image")
<\/a><\/p>\nEnumerating registry property values<\/h2>\n
![\"Image](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/29\/2019\/02\/5756.hsg-5-11-12-02.png\" "\\"Image")
<\/a><\/p>\n\n
![\"Image](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/29\/2019\/02\/3644.hsg-5-11-12-03.png\" "\\"Image")
<\/a><\/p>\n![\"Image](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/29\/2019\/02\/8831.hsg-5-11-12-04.png\" "\\"Image")
<\/a><\/p>\n