{"id":49,"date":"2006-08-26T07:32:00","date_gmt":"2006-08-26T11:32:00","guid":{"rendered":"http:\/\/jdhitsolutions.com\/blog\/2006\/08\/26\/reading-the-registry-in-powershell\/"},"modified":"2009-08-05T13:05:20","modified_gmt":"2009-08-05T17:05:20","slug":"reading-the-registry-in-powershell","status":"publish","type":"post","link":"https:\/\/jdhitsolutions.com\/blog\/powershell\/49\/reading-the-registry-in-powershell\/","title":{"rendered":"Reading the Registry in PowerShell"},"content":{"rendered":"<p>One of the great PowerShell features is that it treats the registry like any other location or directory. In PowerShell you can connect directly to the registry and navigate the key hierarchy just as if it as a logical drive with folders. I have a very brief demonstration script you can run to find the registered ower and organization for the local system. At this point in time (RC1), PowerShell's Registry provider doesn't support mapping to a remote system so this script has to be run in PowerShell locally. Here's the script, which is also available for download from my <a href=\"http:\/\/www.jdhitsolutions.com\/scripts.htm\">script library<\/a>.<\/p>\n<p><span style=\"font-family:Courier New;\">#==============================================================<br \/>#<br \/># Microsoft PowerShell Source File -- Created with SAPIEN Technologies PrimalScript 4.1<br \/>#<br \/># NAME: Show-RegisteredUser.ps1<br \/>#<br \/># AUTHOR: Jeffery Hicks , JDH Information Technology Solutions<br \/># DATE : 8\/23\/2006<br \/>#<br \/># COMMENT: Demonstration script for reading the registry in PowerShell<br \/># KEYWORDS: PowerShell, Registry<br \/>#===============================================================<\/span><br \/><span style=\"font-family:Courier New;\">#Show-RegisteredUser.ps1<\/span><br \/><span style=\"font-family:Courier New;\">$path=\"HKLM:\\Software\\Microsoft\\Windows NT\\CurrentVersion\"<br \/>$reg=Get-ItemProperty $path<\/span><br \/><span style=\"font-family:Courier New;\">#$reg #Uncomment this line if you want to see all of the available properties<\/span><br \/><span style=\"font-family:Courier New;\">Write-Host \"Registered Owner:\"$reg.RegisteredOwner<br \/>write-Host \"Registered Organization:\"$reg.RegisteredOrganization<br \/>Write-Host `n #write a blank line to make it easier to read<\/span><\/p>\n<p>This is a short script and you could just as easily run each command interactively in PowerShell. A script just makes things easier. In this case the script will return the registered owner name and organization like this:<\/p>\n<p><span style=\"font-family:Lucida Console;\">Registered Owner: Jeffery D. Hicks<br \/>Registered Organization: JDH Information Technology Solutions<\/span><\/p>\n<p>How does it work?<\/p>\n<p>The first thing we do is define a variable with the registry path. This is not required, it just makes the script easier to work with and re-usable. If at some later date I want information from another key, all I need to do is change the path and redefine the variable. You should be looking for ways in your scripts to modularize code and make it easier to reuse. But I digress...<\/p>\n<p>The script's core is calling the Get-ItemProperty cmdlet. The cmdlet takes our path variable as a parameter. We save the cmdlet's results to a variable, $reg. This variable contains all the parameters for the given path. If you uncomment the next line you would see something like this:<\/p>\n<p><span style=\"font-family:Courier New;\">PSPath : Microsoft.PowerShell.Core\\Registry::HKEY_LOCAL_MACHINE<br \/>\\Software\\Microsoft\\Windows NT\\CurrentVersion<br \/>PSParentPath : Microsoft.PowerShell.Core\\Registry::HKEY_LOCAL_MACHINE<br \/>\\Software\\Microsoft\\Windows NT<br \/>PSChildName : CurrentVersion<br \/>PSDrive : HKLM<br \/>PSProvider : Microsoft.PowerShell.Core\\Registry<br \/>CurrentBuild : 1.511.1 () (Obsolete data - do not use)<br \/>InstallDate : 1116119161<br \/>ProductName : Microsoft Windows XP<br \/>RegDone :<br \/>RegisteredOrganization : JDH Information Technology Solutions<br \/>RegisteredOwner : Jeffery D. Hicks<br \/>SoftwareType : SYSTEM<br \/>CurrentVersion : 5.1<br \/>CurrentBuildNumber : 2600<br \/>BuildLab : 2600.xpsp.051011-1528<br \/>CurrentType : Uniprocessor Free<br \/>CSDVersion : Service Pack 2<br \/>SystemRoot : E:\\WINDOWS<br \/>SourcePath : D:\\I386<br \/>PathName : E:\\WINDOWS<br \/>ProductId : 55274-640-1614466-23527<br \/>DigitalProductId : {164, 0, 0, 0...}<br \/>LicenseInfo : {51, 183, 33, 193...}<br \/>SubVersionNumber :<\/span><\/p>\n<p>However, I'm only after some specific properties. The $reg object that we created can show each registry setting as an object parameter. In PowerShell we can display that property as simply as typing $reg.ProductName. In the script we use:<\/p>\n<p><span style=\"font-family:Courier New;\">write-Host \"Registered Owner:\"$reg.RegisteredOwner<br \/>write-Host \"Registered Organization:\"$reg.RegisteredOrganization<\/span><\/p>\n<p>to display the information.<\/p>\n<p>Again, the script makes it easier to follow what is happening, but you could just as easily get the owner or organization information with a one line command (it's a long line that wraps here but you would type it as one long expression):<\/p>\n<p><span style=\"font-family:Courier New;\">(Get-ItemProperty \"HKLM:\\Software\\Microsoft\\Windows NT\\CurrentVersion\").RegisteredOwner ; (Get-ItemProperty \"HKLM:\\Software\\Microsoft\\Windows NT\\CurrentVersion\").RegisteredOrganization<\/span><\/p>\n<p>In another post I'll show you how to modify the registry in PowerShell as we change these keys.<\/p>\n<p>Technorati Tags : <a href=\"http:\/\/technorati.com\/tag\/PowerShell\" target=\"_blank\" rel=\"tag\">PowerShell<\/a>, <a href=\"http:\/\/technorati.com\/tag\/Scripting\" target=\"_blank\" rel=\"tag\">Scripting<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>One of the great PowerShell features is that it treats the registry like any other location or directory. In PowerShell you can connect directly to the registry and navigate the key hierarchy just as if it as a logical drive with folders. I have a very brief demonstration script you can run to find the&#8230;<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[4,8],"tags":[],"class_list":["post-49","post","type-post","status-publish","format-standard","hentry","category-powershell","category-scripting"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.5 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Reading the Registry in PowerShell &#8226; The Lonely Administrator<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/jdhitsolutions.com\/blog\/powershell\/49\/reading-the-registry-in-powershell\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Reading the Registry in PowerShell &#8226; The Lonely Administrator\" \/>\n<meta property=\"og:description\" content=\"One of the great PowerShell features is that it treats the registry like any other location or directory. In PowerShell you can connect directly to the registry and navigate the key hierarchy just as if it as a logical drive with folders. I have a very brief demonstration script you can run to find the...\" \/>\n<meta property=\"og:url\" content=\"https:\/\/jdhitsolutions.com\/blog\/powershell\/49\/reading-the-registry-in-powershell\/\" \/>\n<meta property=\"og:site_name\" content=\"The Lonely Administrator\" \/>\n<meta property=\"article:published_time\" content=\"2006-08-26T11:32:00+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2009-08-05T17:05:20+00:00\" \/>\n<meta name=\"author\" content=\"Jeffery Hicks\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@JeffHicks\" \/>\n<meta name=\"twitter:site\" content=\"@JeffHicks\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Jeffery Hicks\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"3 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/powershell\\\/49\\\/reading-the-registry-in-powershell\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/powershell\\\/49\\\/reading-the-registry-in-powershell\\\/\"},\"author\":{\"name\":\"Jeffery Hicks\",\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/#\\\/schema\\\/person\\\/d0258030b41f07fd745f4078bdf5b6c9\"},\"headline\":\"Reading the Registry in PowerShell\",\"datePublished\":\"2006-08-26T11:32:00+00:00\",\"dateModified\":\"2009-08-05T17:05:20+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/powershell\\\/49\\\/reading-the-registry-in-powershell\\\/\"},\"wordCount\":575,\"publisher\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/#\\\/schema\\\/person\\\/d0258030b41f07fd745f4078bdf5b6c9\"},\"articleSection\":[\"PowerShell\",\"Scripting\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/powershell\\\/49\\\/reading-the-registry-in-powershell\\\/\",\"url\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/powershell\\\/49\\\/reading-the-registry-in-powershell\\\/\",\"name\":\"Reading the Registry in PowerShell &#8226; The Lonely Administrator\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/#website\"},\"datePublished\":\"2006-08-26T11:32:00+00:00\",\"dateModified\":\"2009-08-05T17:05:20+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/powershell\\\/49\\\/reading-the-registry-in-powershell\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/powershell\\\/49\\\/reading-the-registry-in-powershell\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/powershell\\\/49\\\/reading-the-registry-in-powershell\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"PowerShell\",\"item\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/category\\\/powershell\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Reading the Registry in PowerShell\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/\",\"name\":\"The Lonely Administrator\",\"description\":\"Practical Advice for the Automating IT Pro\",\"publisher\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/#\\\/schema\\\/person\\\/d0258030b41f07fd745f4078bdf5b6c9\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/#\\\/schema\\\/person\\\/d0258030b41f07fd745f4078bdf5b6c9\",\"name\":\"Jeffery Hicks\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg\",\"caption\":\"Jeffery Hicks\"},\"logo\":{\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Reading the Registry in PowerShell &#8226; The Lonely Administrator","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/jdhitsolutions.com\/blog\/powershell\/49\/reading-the-registry-in-powershell\/","og_locale":"en_US","og_type":"article","og_title":"Reading the Registry in PowerShell &#8226; The Lonely Administrator","og_description":"One of the great PowerShell features is that it treats the registry like any other location or directory. In PowerShell you can connect directly to the registry and navigate the key hierarchy just as if it as a logical drive with folders. I have a very brief demonstration script you can run to find the...","og_url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/49\/reading-the-registry-in-powershell\/","og_site_name":"The Lonely Administrator","article_published_time":"2006-08-26T11:32:00+00:00","article_modified_time":"2009-08-05T17:05:20+00:00","author":"Jeffery Hicks","twitter_card":"summary_large_image","twitter_creator":"@JeffHicks","twitter_site":"@JeffHicks","twitter_misc":{"Written by":"Jeffery Hicks","Est. reading time":"3 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/jdhitsolutions.com\/blog\/powershell\/49\/reading-the-registry-in-powershell\/#article","isPartOf":{"@id":"https:\/\/jdhitsolutions.com\/blog\/powershell\/49\/reading-the-registry-in-powershell\/"},"author":{"name":"Jeffery Hicks","@id":"https:\/\/jdhitsolutions.com\/blog\/#\/schema\/person\/d0258030b41f07fd745f4078bdf5b6c9"},"headline":"Reading the Registry in PowerShell","datePublished":"2006-08-26T11:32:00+00:00","dateModified":"2009-08-05T17:05:20+00:00","mainEntityOfPage":{"@id":"https:\/\/jdhitsolutions.com\/blog\/powershell\/49\/reading-the-registry-in-powershell\/"},"wordCount":575,"publisher":{"@id":"https:\/\/jdhitsolutions.com\/blog\/#\/schema\/person\/d0258030b41f07fd745f4078bdf5b6c9"},"articleSection":["PowerShell","Scripting"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/jdhitsolutions.com\/blog\/powershell\/49\/reading-the-registry-in-powershell\/","url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/49\/reading-the-registry-in-powershell\/","name":"Reading the Registry in PowerShell &#8226; The Lonely Administrator","isPartOf":{"@id":"https:\/\/jdhitsolutions.com\/blog\/#website"},"datePublished":"2006-08-26T11:32:00+00:00","dateModified":"2009-08-05T17:05:20+00:00","breadcrumb":{"@id":"https:\/\/jdhitsolutions.com\/blog\/powershell\/49\/reading-the-registry-in-powershell\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/jdhitsolutions.com\/blog\/powershell\/49\/reading-the-registry-in-powershell\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/jdhitsolutions.com\/blog\/powershell\/49\/reading-the-registry-in-powershell\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"PowerShell","item":"https:\/\/jdhitsolutions.com\/blog\/category\/powershell\/"},{"@type":"ListItem","position":2,"name":"Reading the Registry in PowerShell"}]},{"@type":"WebSite","@id":"https:\/\/jdhitsolutions.com\/blog\/#website","url":"https:\/\/jdhitsolutions.com\/blog\/","name":"The Lonely Administrator","description":"Practical Advice for the Automating IT Pro","publisher":{"@id":"https:\/\/jdhitsolutions.com\/blog\/#\/schema\/person\/d0258030b41f07fd745f4078bdf5b6c9"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/jdhitsolutions.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":["Person","Organization"],"@id":"https:\/\/jdhitsolutions.com\/blog\/#\/schema\/person\/d0258030b41f07fd745f4078bdf5b6c9","name":"Jeffery Hicks","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg","url":"https:\/\/secure.gravatar.com\/avatar\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg","caption":"Jeffery Hicks"},"logo":{"@id":"https:\/\/secure.gravatar.com\/avatar\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg"}}]}},"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_likes_enabled":true,"jetpack-related-posts":[{"id":53,"url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/53\/writing-the-registry-in-powershell\/","url_meta":{"origin":49,"position":0},"title":"Writing the Registry in PowerShell","author":"Jeffery Hicks","date":"September 22, 2006","format":false,"excerpt":"Last month I showed you how to read the registry in PowerShell. I went through a script that would read the registered owner and organization. Now I'll show you how to change those properties in PowerShell. Here's the script, which is also available for download from my script library. Here's\u2026","rel":"","context":"In &quot;PowerShell&quot;","block_context":{"text":"PowerShell","link":"https:\/\/jdhitsolutions.com\/blog\/category\/powershell\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":9130,"url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/9130\/configure-sysinternals-eula-acceptance\/","url_meta":{"origin":49,"position":1},"title":"Configure SysInternals EULA Acceptance","author":"Jeffery Hicks","date":"August 24, 2022","format":false,"excerpt":"I just saw a very, very handy thing on Twitter where you can set a registry key that will automatically accept all EULA prompts for the SysInternals tools. I know there is a command-line switch I can use, but I never remember to use it. Setting the registry key appears\u2026","rel":"","context":"In &quot;PowerShell&quot;","block_context":{"text":"PowerShell","link":"https:\/\/jdhitsolutions.com\/blog\/category\/powershell\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1811,"url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/1811\/export-registry-printer-information-i-came\/","url_meta":{"origin":49,"position":2},"title":"Export Registry Printer Information I came&#8230;","author":"Jeffery Hicks","date":"November 2, 2011","format":false,"excerpt":"Export Registry Printer InformationI came across this post http:\/\/www.oncallpros.com\/2011\/11\/02\/powershell-export-your-print-configuration-from-registry\/ on exporting printer information from the registry in PowerShell. I wanted to offer some constructive suggestions but could find no way to comment so I'll do so here.First, the article introduces some good PowerShell concepts. I like that he is using\u2026","rel":"","context":"In &quot;Google Plus&quot;","block_context":{"text":"Google Plus","link":"https:\/\/jdhitsolutions.com\/blog\/category\/google-plus\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1413,"url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/1413\/get-registry-size-and-age\/","url_meta":{"origin":49,"position":3},"title":"Get Registry Size and Age","author":"Jeffery Hicks","date":"May 4, 2011","format":false,"excerpt":"I'm not sure why the registry has been on my mind lately. I probably need a vacation to get out more. But I put together a relatively simple Windows PowerShell function to retrieve registry statistics that you might find useful. My Get-Registry function will return information about the size of\u2026","rel":"","context":"In &quot;PowerShell&quot;","block_context":{"text":"PowerShell","link":"https:\/\/jdhitsolutions.com\/blog\/category\/powershell\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2011\/05\/registry.png?resize=350%2C200","width":350,"height":200},"classes":[]},{"id":455,"url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/455\/get-printer\/","url_meta":{"origin":49,"position":4},"title":"Get-Printer","author":"Jeffery Hicks","date":"October 16, 2009","format":false,"excerpt":"I think Out-Printer is a very handy cmdlet, and one that doesn\u2019t get used much. Pipe any cmdlet to it and the output will be printed to your default printer. You use it the same way you would Out-File except output is printed instead of saved to a file. The\u2026","rel":"","context":"In &quot;PowerShell&quot;","block_context":{"text":"PowerShell","link":"https:\/\/jdhitsolutions.com\/blog\/category\/powershell\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":8612,"url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/8612\/update-registry-os-productname-with-powershell\/","url_meta":{"origin":49,"position":5},"title":"Update Registry OS ProductName with PowerShell","author":"Jeffery Hicks","date":"October 12, 2021","format":false,"excerpt":"I expect many of you are like me and have done, or will do, an in-place upgrade from Windows 10 to Windows 11. It is easy enough to run a PowerShell expression like this to see the operating system name. Get-CimInstance win32_operatingsystem | Select-Object -property Caption I get a value\u2026","rel":"","context":"In &quot;PowerShell&quot;","block_context":{"text":"PowerShell","link":"https:\/\/jdhitsolutions.com\/blog\/category\/powershell\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2021\/10\/set-psproduct2.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2021\/10\/set-psproduct2.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2021\/10\/set-psproduct2.png?resize=525%2C300&ssl=1 1.5x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2021\/10\/set-psproduct2.png?resize=700%2C400&ssl=1 2x"},"classes":[]}],"_links":{"self":[{"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/posts\/49","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/comments?post=49"}],"version-history":[{"count":0,"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/posts\/49\/revisions"}],"wp:attachment":[{"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/media?parent=49"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/categories?post=49"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/tags?post=49"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}