Skip to main content

PowerShell working with registry keys




Basic PowerShell commands to work with Windows Registry.

Don't mess up with the registry, if you're not sure of what you are doing.

Messing up with the registry for fun is just good in a virtual environment with no important data at all.
 
To list software registry keys on path HKCU type this command below:

Get-ChildItem -Path hkcu:\software  | Select Name


It will list all the software registry keys, it's good to list all the software registry keys and check for any illicit software installed by malwares or viruses.

If there's a lot of software installed on the PC it will be a long list.

But PowerShell comes handy when it comes to filtering.

Code below will filter for any Keys in HKCU path that has "Ad" values on it.

Use the parameter "-like" and not "-eq", -eq or equal will match 100% and will not return any value if no match at all.

Get-ChildItem -Path hkcu:\software  | Where-Object {$_.Name -like '*Ad*'}

Sample output:

    Hive: HKEY_CURRENT_USER\software


Name                           Property                                                                                                          
----                           --------                                                                                                          
Adobe                             

Below is another code filtering example that will look for any keys with "Win" string.

Sample output:

Get-ChildItem -Path hkcu:\software  | Where-Object {$_.Name -like '*Win*'}

    Hive: HKEY_CURRENT_USER\software

Name                           Property                                                                                                           
----                           --------                                                                                                          
Cygwin
GnuWin32
Windows Live Writer
Winpolicies
WinRAR
WinRAR SFX                     C%%Program Files%WinRAR : C:\Program Files\WinRAR

Those are just basics way of handling registry keys, using PowerShell.

If want to learn some more using PowerShell on messing up with the registry check out cmdlets: Start-Transaction, Use-Transaction, Complete-Transaction

 To check out some more tips on how to play around or edit the registry using PowerShell refer to Technet links below.

Check out links below for Technet references:
http://technet.microsoft.com/en-us/library/hh849774.aspx
http://technet.microsoft.com/en-us/library/dd315270.aspx


Hope it helps you to get started on how to edit the Windows registry using PowerShell.


Cheers!!!

Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

WMIC get computer name

WMIC get computer model, manufacturer, computer name and  username. WMIC is a command-line tool and that can generate information about computer model, its manufacturer, its username and other informations depending on the parameters provided. Why would you need a command line tool if there’s a GUI to check? If you have 20 or 100 computers, or even more. It’s quite a big task just checking the GUI to check the computer model and username. If you have remote computers, you need to delegate someone in the remote office or location to check. Or you can just write a batch file or script to automate the task. Here’s the code below on how get computer model, manufacturer and the username. Open an elevated command prompt and type:     wmic computersystem get "Model","Manufacturer", "Name", "UserName" Just copy and paste the code above, the word “computersystem” does not need to be change to a computer name. A...
Post a Comment
Read more

Print error 016-799 - Fuji Film Xerox

016-799 Fuji Xerox or Fuji Film print error code. That shows a description error as “Print instruction Fail detected in decomposer.” The error code and error description are alien languages for users and even system administrators who are not familiar with Fuji Xerox error code. The error code is quite simple and easy to fix, if the job print goes to the printer but print out doesn’t come out. So, basically the print job was received by the printer, but the printer just doesn’t know what type of paper or what size to use or which tray to utilize for the print out. In some instances, this is just a paper mismatch but the error description; if using Windows 10 to print does not exactly points to what is the issue. First thing to check, is the paper size selected by the user to print. Example, if the printer configuration is A3 and A4 sizes only. But then the person printing the file accidentally chooses “A4 Cover” then this error 016-799 will occur. ...
6 comments
Read more

How to check office version from command line

The are quite a few ways to check office version it can be done via registry, PowerShell or VBScript and of course, good old command line can also do it. Checking Windows office version whether it is Office 2010, Office, 2013, Office 2016 or other version is quite important to check compatibility of documents; or just a part of software inventory. For PowerShell this simple snippet can check the office version: $ol = New-Object -ComObject Excel.Application $ol . Version The command line option will tell you where’s the path located; the result will also tell whether office is 32-bit, 64-bit and of course the version of the office as well. Here’s the command that will check the office version and which program directory the file is located which will tell whether it’s 32-bit or 64-bit. Command to search for Excel.exe: DIR C:\ /s excel.exe | find   /i "Directory of"  Above command assumes that program files is on  C: drive. Sample O...
Post a Comment
Read more