Use PowerShell to Quickly Find Installed Software

November 13th, 2011

Summary: Learn how to use Windows PowerShell to quickly find installed software on local and remote computers.

Microsoft Scripting Guy Ed Wilson here. Guest Blogger Weekend concludes with Marc Carter. The Scripting Wife and I were lucky enough to attend the first PowerShell User Group meeting in Corpus Christi, Texas. It was way cool, and both Marc and his wife Pam are terrific hosts. Here is what Marc has to say about himself.

I am currently a senior systems administrator with the Department of the Army. I started in the IT industry in 1996 with DOS and various flavors of *NIX. I was introduced to VBScript in 2000, and scripting became a regular obsession sometime in 2005. In 2008, I made the move to Windows PowerShell and have never looked back. My daily responsibilities keep me involved with Active Directory, supporting Microsoft Exchange, SharePoint, and various ASP.NET applications. In 2011, I founded the Corpus Christi PowerShell User Group and try to help bring others up to speed on Windows PowerShell.

Take it away, Marc!

One of the life lessons I have learned over the years working in the IT field as a server administrator is that there are often several different valid responses to a situation. It’s one of the things that makes work interesting. Finding the “best” solution to a problem is one of the goals that I think drives many people who are successful at what they do. Occasionally, the best solution is the path of least resistance.

This is one things I love most about working with Windows PowerShell (and scripting in general) is that most problems have more than one solution. Sometimes the “right” way to do something comes down to a matter of opinion or preference. However, sometimes the best solution is dictated by the environment or requirements you are working with.

For instance, let us talk about the task of determining which applications are installed on a system. If you’re familiar with the Windows Management Instrumentation (WMI) classes and the wealth of information that can be gathered by utilizing the Get-WmiObject cmdlet, an obvious choice might be referencing the Win32_product class . The Win32_Product represents products as they are installed by Windows Installer. It is a prime example of many of the benefits of WMI. It contains several useful methods and a variety of properties. At first glance, Win32_Product would appear to be one of those best solutions in the path of least resistance scenario. A simple command to query Win32_Product with the associated output is shown in the following image.

The benefits of this approach are:

• This is a simple and straightforward query: Get-WmiObject -Class Win32_Product.
• It has a high level of detail (for example, Caption, InstallDate, InstallSource, PackageName, Vendor, Version, and so on).

However, because we are talking about alternative routes, let us look at another way to get us to arrive at the same location before we burst the bubble on Win32_Product. Remember, we are simply looking for what has been installed on our systems, and because we have been dealing with WMI, let’s stay with Get-WmiObject, but look at a nonstandard class, Win32Reg_AddRemovePrograms.

What is great about Win32Reg_AddRemovePrograms is that it contains similar properties and returns results noticeably quicker than Win32_Product. The command to use this class is shown in the following figure.

Unfortunately, as seen in the preceding figure, Win32Reg_AddRemovePrograms is not a standard Windows class. This WMI class is only loaded during the installation of an SMS/SCCM client. In the example above, running this on my home laptop, you will see the “Invalid class” error if you try querying against it without an SMS/SCCM client installation. It is possible (as Windows PowerShell MVP Marc van Orsouw points out) to add additional keys to WMI using the Registry Provider, and mimic what SMS/SCCM does behind the scenes. Nevertheless, let us save that for another discussion.

One other possibly less obvious and slightly more complicated option is diving into the registry. Obviously, monkeying with the registry is not always an IT pro’s first choice because it is sometimes associated with global warming. However, we are just going to query for values and enumerate subkeys. So let’s spend a few moments looking at a method of determining which applications are installed courtesy of another Windows PowerShell MVP and Honorary Scripting Guy Sean Kearney (EnergizedTech). In a script that Sean uploaded to the Microsoft TechNet Script Center Repository , Sean references a technique to enumerate through the registry where the “Currently installed programs” list from the Add or Remove Programs tool stores all of the Windows-compatible programs that have an uninstall program. The key referred to is HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall. The script and associated output are shown in the following figure.

Here are the various registry keys:

#Define the variable to hold the location of Currently Installed Programs
$UninstallKey=”SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Uninstall”
#Create an instance of the Registry Object and open the HKLM base key
$reg=[microsoft.win32.registrykey]::OpenRemoteBaseKey(‘LocalMachine’,$computername)
#Drill down into the Uninstall key using the OpenSubKey Method
$regkey=$reg.OpenSubKey($UninstallKey)
#Retrieve an array of string that contain all the subkey names
$subkeys=$regkey.GetSubKeyNames()
#Open each Subkey and use the GetValue Method to return the string value for DisplayName for each

At this point, if you are anything like me, you are probably thinking, “I’ll stick with a one-liner and use Win32_Product.” But this brings us back to why we started looking at alternatives in the first place. As it turns out, the action of querying Win32_Product has the potential to cause some havoc on your systems . Here is the essence of KB974524.

The Win32_product class is not query optimized. Queries such as “select * from Win32_Product where (name like ‘Sniffer%’)” require WMI to use the MSI provider to enumerate all of the installed products and then parse the full list sequentially to handle the “where” clause:,

• This process initiates a consistency check of packages installed, and then verifying and repairing the installations.
• If you have an application that makes use of the Win32_Product class, you should contact the vendor to get an updated version that does not use this class.

On Windows Server 2003, Windows Vista, and newer operating systems, querying Win32_Product will trigger Windows Installer to perform a consistency check to verify the health of the application. This consistency check could cause a repair installation to occur. You can confirm this by checking the Windows Application Event log. You will see the following events each time the class is queried and for each product installed:

Event ID: 1035
Description: Windows Installer reconfigured the product. Product Name:

. Product Version: . Product Language: . Reconfiguration success or error status: 0.

Event ID: 7035/7036
Description: The Windows Installer service entered the running state.

Windows Installer iterates through each of the installed applications, checks for changes, and takes action accordingly. This would not a terrible thing to do in your dev or test environment. However, I would not recommend querying Win32_Product in your production environment unless you are in a maintenance window.

So what is the best solution to determine installed applications? For me, it is reading from the registry as it involves less risk of invoking changes to our production environment. In addition, because I prefer working with the ISE environment, I have a modified version of Sean’s script that I store in a central location and refer back to whenever I need an updated list of installed applications on our servers. The script points to a CSV file that I keep up to date with a list of servers from our domain.

$computers = Import-Csv “D:\PowerShell\computerlist.csv”

foreach($pc in $computers)<

#Define the variable to hold the location of Currently Installed Programs

#Create an instance of the Registry Object and open the HKLM base key

#Drill down into the Uninstall key using the OpenSubKey Method

#Retrieve an array of string that contain all the subkey names

#Open each Subkey and use GetValue Method to return the required values for each

foreach($key in $subkeys)<

$obj = New-Object PSObject

$obj | Add-Member -MemberType NoteProperty -Name “ComputerName” -Value $computername

$obj | Add-Member -MemberType NoteProperty -Name “DisplayName” -Value $($thisSubKey.GetValue(“DisplayName”))

$obj | Add-Member -MemberType NoteProperty -Name “DisplayVersion” -Value $($thisSubKey.GetValue(“DisplayVersion”))

$obj | Add-Member -MemberType NoteProperty -Name “InstallLocation” -Value $($thisSubKey.GetValue(“InstallLocation”))

$obj | Add-Member -MemberType NoteProperty -Name “Publisher” -Value $($thisSubKey.GetValue(“Publisher”))

$array | Where-Object < $_.DisplayName >| select ComputerName, DisplayName, DisplayVersion, Publisher | ft -auto

My modified version of Sean’s script creates a PSObject to hold the properties I am returning from each registry query, which then get dumped into an array for later use. When I am done, I simply output the array and pass it through a Where-Object to display only those entries with something in the DisplayName. This is handy because I can then refer back to just the array if I need to supply different output. Say I want to only report on a specific server. I’d change Where-Object to something like this:

In conclusion, if you have added Windows PowerShell to your IT tool belt, you have plenty of go-to options when someone asks you, “What’s the best solution to a problem?”

Thank you, Marc, for writing this post and sharing with our readers

4 Ways to Get List of Installed Programs For Backup in Windows 10

Saving the list of installed programs is an important part of backup strategy. Just suppose suddenly you have a Windows failure or any software issue and you need to reinstall Windows. On reinstalling the OS, you’ll miss all the programs installed on your System. If you are having list of your installed Software, you can easily re-install them by getting know that which programs you were previously having.

In this article we will discuss about 4 different ways to get and save a list of installed programs in Windows. We will focus on Windows 10 but these methods can be used for earlier versions of Windows.

Getting the list of installed programs

Through PowerShell Command

Users can easily get list of all installed programs through entering following simple command in PowerShell. Write PowerShell in start menu and open the first result you get.

And write following command into PowerShell

Get-ItemProperty HKLM:\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion, Publisher, InstallDate |Format-Table -AutoSize

The list of all installed programs with the install date and name of publisher will be on your PowerShell Screen. Now next step is to export this list to somewhere. Again paste the same command and after this command write

Get-ItemProperty HKLM:\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion, Publisher, InstallDate |Format-Table –AutoSize > C:\Users\MahamMukhtar\Documents\InstalledPrograms-PS.txt.

And the file will be saved into required folder. Format of file will be text file.

Through Command Line

Open your Command Line as Administrator. And type the following command.

It will shortly display you all the installed programs and its version on command line prompt. And to export the list

Write simple “wmic”

Then after “wmic:root\cli”, paste following command /output:C:/InstallList.txt product get name, version.

Then List will be saved into C drive of your System.

Through CCleaner

CCleaner is small tool that helps you to make your PC’s performance better by removing some unnecessary and temporary files. The CCleaner utility can also give you list of all installed program of your System.

After installation open it, and go to tools and then click on Uninstall and it will show you the lit of all Programs which is installed into your System. Then click to “save as txt file”.

Then it will ask you to save this txt file anywhere you want to in your System.

Through Control Panel

You can also view all of your Installed programs easily by going to “Control Panel” and then “Programs” and “Uninstall a Program”. And make it in Detail view.

Now you can take a screenshot of it and save it anywhere in your System so that you can later get view of your installed program in time of need.

So these all are easy and handy ways to have view of all installed programs of your System and save them anywhere in text format or in snapshot format. What do you do to save the list of installed programs in Windows?

Continue Reading:

One thought on “ 4 Ways to Get List of Installed Programs For Backup in Windows 10 ”

I’ve been surfig onlije mor tthan 4 hourss today, yeet I never founhd aany innteresting article like yours.
It’s pretty worth enoigh for me. In myy opinion, iif all sitee owners annd
bloggers made goold content aas yoou did,
thhe intesrnet will bbe a lott mopre useful than ever before.
I havve been broowsing on-line greater than thrree hours
ass of late, yeet I byy no means discovered aany fascinating artyicle lik yours.
It iss beauitiful valuue suficient foor me. In my opinion, iff alll
wedbsite ownrs annd bloggers made good content maerial as
yoou did, thee weeb caan bee muhh moe useful thazn evr
before. I wwill immeddiately grtab our rsss as I can’t iin finding youjr ekail subscription hyperlkink
oor newsletter service. Do yyou havge any?
Please allow me recogmize soo thhat I mayy juat subscribe.
Thanks. http://cspan.org

Leave a Reply Cancel reply

Recent Posts

Microsoft has released Windows PowerShell 7.2 Preview 5, bringing in a few changes and fixes to the command line. You can download and install this release on your device using the given guide down.

Google has released Chrome version 90 for everyone to download and use. You can update your existing Chrome version using the guide given in the article, or download Google Chrome 90 from the given.

About Itechtics

iTechtics is a technology blog focusing on Windows news, software and downloads, software tips and tricks, Web services, Security and Office productivity.