How to Check the Version of Any Software on Windows

Knowing which version of a software application you're running matters more than most people realize. It affects compatibility, security patching, troubleshooting accuracy, and whether a feature you've read about actually exists on your install. Windows gives you several ways to find this information — and which method works best depends on the software itself.

Why Software Version Numbers Matter

Software versioning isn't just bookkeeping. Version numbers tell you where a program sits in its development lifecycle — what bugs have been fixed, what features are available, and whether your copy is still receiving security updates.

When you contact support, the first thing most tech teams ask is: what version are you running? When you read a tutorial, the steps often only apply to specific versions. When a vulnerability is disclosed, the patch coverage is defined by version number. Getting this information quickly and accurately is a basic but valuable skill.

Method 1: Check Through the Application's Own Menu

The most straightforward approach for most desktop software is to look inside the program itself.

Steps:

  1. Open the application
  2. Click Help in the menu bar (or the application's name on some newer apps)
  3. Look for About [App Name] or About This Program
  4. The version number is typically displayed prominently on the screen that opens

This works reliably for most traditional Windows desktop applications — browsers, office suites, media players, design tools, and more. The version string may appear as a simple number like 14.0, a build number like 14.0.7268.5000, or a release name alongside a number.

Some applications display this under File → Help, others under a gear icon or hamburger menu. Modern apps that follow a ribbon or minimal-chrome design (like Microsoft Edge or newer Office apps) often place it under Settings → About.

Method 2: Use Windows Settings (For Installed Apps) ⚙️

Windows keeps a registry of installed applications, and you can browse version numbers directly from Settings.

On Windows 10:

  1. Open SettingsAppsApps & Features
  2. Scroll to find the application
  3. Click on it — some apps display the version directly beneath the name; others require clicking Advanced options

On Windows 11:

  1. Open SettingsAppsInstalled Apps
  2. Scroll or search for the application
  3. Version information appears beneath the app name for most entries

This method is especially useful when you need to check the version of a program without opening it, or when an app doesn't have a traditional menu structure.

Method 3: Check File Properties in File Explorer

Every executable file on Windows carries metadata, including version information embedded by the developer at build time.

Steps:

  1. Navigate to the application's installation folder (commonly C:Program Files or C:Program Files (x86))
  2. Find the main .exe file for the application
  3. Right-click the file → select Properties
  4. Click the Details tab
  5. Look for File version or Product version

File version refers to the specific build of that executable. Product version refers to the broader release of the software product. These numbers are sometimes identical, sometimes different — particularly in larger software suites where individual components are updated independently.

This method works even for portable apps (software that doesn't install formally) and gives you granular version data that the in-app "About" screen sometimes rounds or summarizes.

Method 4: Use PowerShell or Command Prompt for Precision

For IT professionals, developers, or anyone managing multiple machines, the command line offers fast, scriptable version lookups.

Using PowerShell:

Get-Item "C:PathToApplication.exe" | Select-Object -ExpandProperty VersionInfo 

This returns detailed version metadata including FileVersion, ProductVersion, CompanyName, and more.

For apps installed via Windows Package Manager (winget):

winget list 

This outputs a full list of installed applications with their current and available versions — useful for spotting outdated software at a glance.

Using WMIC (older but still functional on most systems):

wmic datafile where name="C:\Path\To\Application.exe" get Version 

These approaches are particularly valuable when auditing software across an enterprise environment or automating update checks.

Method 5: Check Through Windows Registry

The Windows Registry stores installation metadata for most traditionally installed software.

Path to check:

HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionUninstall 

Or for 32-bit apps on a 64-bit system:

HKEY_LOCAL_MACHINESOFTWAREWOW6432NodeMicrosoftWindowsCurrentVersionUninstall 

Each installed application typically has its own subkey containing DisplayVersion, DisplayName, and Publisher values. This is raw data — useful for deep diagnostics, but more involved than the other methods.

How Version Numbers Are Structured

Understanding the format helps you read what you find. 🔢

FormatExampleWhat It Means
Major.Minor14.2Major = significant release, Minor = feature update
Major.Minor.Patch14.2.1Patch = bug/security fix
Build number14.0.7268.5000Granular internal build, common in enterprise software
Year-based2024.3.1Release year as the primary identifier
Semantic versioning3.12.4Follows strict increment rules (common in developer tools)

Not all developers follow the same convention, so the same number structure can mean different things depending on who published the software.

Variables That Affect Which Method Works Best

No single method covers every scenario. The right approach depends on:

  • How the software was installed — traditional installer, Microsoft Store, portable app, or package manager all behave differently
  • Whether the app has a traditional menu structure — modern minimal-UI apps may not have a Help menu at all
  • Your Windows version — Settings UI and available tools differ between Windows 10 and Windows 11
  • Your technical comfort level — command-line methods are faster but require more familiarity
  • Whether you need one version or many — checking a single app by hand is fine; auditing a fleet of machines calls for scripted approaches

A home user checking their browser version and a sysadmin verifying software compliance across 200 machines are technically asking the same question — but the practical answer looks very different depending on their environment and what they need to do with the information.