Overview
What Installed Apps collects
The script builds one combined software list from two Windows sources: the machine-level uninstall registry and the current user's Appx package inventory.
Traditional desktop programs
The script reads HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall and collects Display Name, Display Version, Publisher/Vendor, Install Date, and Install Location. Entries without both a program name and vendor are filtered out.
Windows Appx packages
It also runs Get-AppxPackage for the current user and records Name, Version, Publisher, Install Date, and Install Location.
Sorted software inventory
Traditional programs are sorted by name before being combined with the sorted Appx package list, providing a convenient reference when rebuilding or auditing a PC.
Local-only reporting
The current script reads Windows registry/package information and writes local files. It does not contain code that uploads the inventory to a website or cloud service.
Output
Files created on the Desktop
The script creates an Installed Apps folder on the current user's Desktop and separates its two output formats into clearly named subfolders.
CSV / text-friendly output
Desktop\Installed Apps\Open with Notepad\InstalledApps.csv
Excel workbook
Desktop\Installed Apps\Open with Excel\InstalledApps.xlsx
The folder name says “Open with Notepad” for the CSV copy, but CSV is a standard text-based format and can also be opened with Excel, LibreOffice Calc, spreadsheet applications, and many text editors.
Excel Requirement
The XLSX export uses Microsoft Excel
After the CSV is written, the script creates an Excel.Application COM object, opens a new workbook, writes the collected software information into worksheet cells, auto-fits the used columns, and saves the workbook as an XLSX file.
Microsoft Excel required for XLSX
Because the script automates the desktop Excel application through COM, Microsoft Excel must be installed and available for the XLSX creation step to work.
CSV is created first
The script exports InstalledApps.csv before it attempts to start Excel, so the CSV output is not dependent on Excel being installed.
Workbook formatting
After filling the worksheet, the script uses Excel's UsedRange and AutoFit functionality so the exported columns are easier to read.
Excel is closed afterward
The workbook is saved in XLSX format, closed, and the Excel application is quit. The script then explicitly releases the worksheet, workbook, and Excel COM objects from memory.
How It Works
Running Installed Apps
- Download and extract Installed Apps.zip.
- Run Run Me.bat.
- The launcher starts PowerShell with
-ExecutionPolicy Bypass and requests administrator elevation through UAC.
- The script inventories traditional programs from the Windows uninstall registry.
- It inventories current-user Appx packages with
Get-AppxPackage.
- The two lists are combined.
- The Desktop output folders are created if they do not already exist.
- The combined inventory is exported to CSV.
- Microsoft Excel is automated to create and save the XLSX copy.
The included Read Me notes that Windows 11 may display a “Windows protected your PC” SmartScreen message because the script was downloaded. Review the script before choosing “More info” and “Run anyway.”
Use Cases
When the inventory is useful
Before reinstalling Windows
Save a reference of installed software before resetting, replacing, or reinstalling a Windows PC.
New PC migration
Keep a software checklist while moving from an older computer to a new Windows system.
Technician documentation
Create a quick local snapshot of application names, versions, vendors, dates, and install locations before service work.
General software review
Use the CSV or workbook as a convenient reference when reviewing what software is present on a PC.
FAQ
Frequently asked questions
Where are the files saved?
Inside an Installed Apps folder on the current user's Desktop.
What information is recorded?
The script collects software name, version, publisher/vendor, install date, and install location when those values are available.
Does the XLSX export require Excel?
Yes. The current script creates the workbook by automating Excel.Application, so the desktop Microsoft Excel application is required for that step.
Can I still use the CSV without Excel?
Yes. The CSV is created before the Excel automation step and can be opened with a text editor or another application that supports CSV files.
Does it inventory Appx packages for every Windows user?
No. The current script uses Get-AppxPackage without -AllUsers, so the Appx portion reflects the current user's package inventory.
Does it upload my software list?
No. The current script contains no upload or web-request code. Its output is written locally to the Desktop.