Comprehensive Guide to Retrieving Windows Version Information from PowerShell Command Line

Core Methods for Retrieving Windows Version in PowerShell

Retrieving Windows operating system version information within PowerShell environments is a common requirement for system administration and script development. Unlike traditional CMD command line, PowerShell offers more comprehensive and flexible approaches to access system information.

System.Environment Class OSVersion Property

The most straightforward method involves using the System.Environment class from .NET Framework. This class provides static properties for accessing current runtime environment information, with the OSVersion property specifically designed for obtaining operating system version details.

PS C:\> [System.Environment]::OSVersion.Version

Major  Minor  Build  Revision
-----  -----  -----  --------
6      1      7601   65536

The above code returns a System.Version type object containing four main components: Major version number, Minor version number, Build number, and Revision number. This approach benefits from direct utilization of .NET Framework's underlying APIs, offering fast response times and no dependency on external components.

Version Number to Windows Version Mapping

Understanding version number correspondence is crucial for accurate Windows version identification. Below is a common version mapping table:

Windows 7/Windows Server 2008 R2: 6.1
Windows 8/Windows Server 2012: 6.2
Windows 8.1/Windows Server 2012 R2: 6.3
Windows 10/Windows Server 2016: 10.0

In practical applications, version comparison can be used to implement conditional logic. For example, detecting if the system is Windows 7 or later:

if ([Environment]::OSVersion.Version -ge (New-Object 'Version' 6,1)) {
    Write-Host "System is Windows 7 or later"
}

WMI Query for Detailed Information

While System.Environment.OSVersion provides basic version information, it cannot distinguish between client and server versions, nor can it retrieve the complete operating system name. Windows Management Instrumentation (WMI) can be used to obtain more comprehensive information.

PS C:\> (Get-WmiObject -Class Win32_OperatingSystem).Caption
Microsoft® Windows Server® 2008 Standard

In PowerShell 3.0 and later versions, it's recommended to use Get-CimInstance instead of Get-WmiObject, as the former is based on the newer CIM standard, offering better performance and compatibility:

PS C:\> (Get-CimInstance Win32_OperatingSystem).Version

Windows 10 Specific Version Identification

For Windows 10 systems, Microsoft introduced the concept of Release IDs, such as 1507, 1511, 1607, etc. This information can be retrieved by querying the registry:

PS C:\> (Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion").ReleaseId

This method is particularly useful for scenarios requiring precise identification of specific Windows 10 version numbers, such as compatibility testing or feature enablement checks.

PowerShell Wrapper for System Information Command

The traditional systeminfo command can also be integrated with PowerShell through pipeline and formatting commands to extract specific information:

PS C:\> systeminfo /fo csv | ConvertFrom-Csv | Select-Object OSName, OSVersion, OSManufacturer | Format-List

This approach provides the most comprehensive system information, including operating system name, version, manufacturer, configuration type, and other detailed data.

Compatibility Considerations and Best Practices

When selecting methods for retrieving Windows version information, consider PowerShell version and Windows version compatibility:

• For PowerShell 2.0 environments, System.Environment.OSVersion is the most reliable choice
• In Windows 8.1 and later versions, some traditional APIs may be marked as deprecated, recommending WMI or CIM methods
• For scenarios requiring precise version matching, recommend combining multiple methods for verification

Practical Application Example

The following complete script example demonstrates how to comprehensively use multiple methods to obtain detailed Windows version information:

function Get-WindowsVersionInfo {
    $info = @{}
    
    # Basic version information
    $info.BaseVersion = [Environment]::OSVersion.Version
    
    # Complete operating system name
    try {
        $info.OSName = (Get-CimInstance Win32_OperatingSystem).Caption
    } catch {
        $info.OSName = (Get-WmiObject -Class Win32_OperatingSystem).Caption
    }
    
    # Windows 10 Release ID
    if ([Environment]::OSVersion.Version.Major -eq 10) {
        $info.ReleaseId = (Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion" -ErrorAction SilentlyContinue).ReleaseId
    }
    
    return New-Object PSObject -Property $info
}

# Call function and display results
Get-WindowsVersionInfo | Format-List

This script demonstrates how to create a robust version detection function capable of adapting to different PowerShell and Windows environments.

Conclusion

Through the various methods introduced in this article, users can select the most appropriate approach for retrieving Windows version information based on specific requirements. For simple version number checks, System.Environment.OSVersion is the most direct choice; for scenarios requiring complete operating system names, WMI/CIM queries are more suitable; and for Windows 10 specific version identification, registry queries provide precise solutions. In practical applications, it's recommended to choose corresponding methods based on target environment and specific requirements, and perform multiple verifications in critical scenarios to ensure accuracy.