Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Get-ComputerInfo's 'WindowsProductName' property | Non-correct Windows product name reported #20032

Closed
5 tasks done
Ricky-Tigg opened this issue Jul 27, 2023 · 1 comment
Closed
5 tasks done

Comments

@Ricky-Tigg
Copy link

Prerequisites

Steps to reproduce

Hello. Non-correct Windows product name reported by Get-ComputerInfo's WindowsProductName property. Note: computer manually upgraded from edition 10 to 11, hence not via the channel provided by Windows Updates.

Correct Windows product name reported:

> Get-WmiObject -Class Win32_OperatingSystem | Format-List -Property Caption

Caption : Microsoft Windows 11 Home

Expected behavior

PS> Get-ComputerInfo | Format-List -Property WindowsProductName

WindowsProductName : Microsoft Windows 11 Home

Actual behavior

PS> Get-ComputerInfo | Format-List -Property WindowsProductName

WindowsProductName : Windows 10 Home

Error details

_

Environment data

Name                           Value
----                           -----
PSVersion                      7.3.6
PSEdition                      Core
GitCommitId                    7.3.6
OS                             Microsoft Windows 10.0.22000
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Visuals

@Ricky-Tigg Ricky-Tigg added the Needs-Triage The issue is new and needs to be triaged by a work group. label Jul 27, 2023
@mklement0
Copy link
Contributor

mklement0 commented Jul 27, 2023

This has been reported before, in:

The short of it is that the WindowsCurrentVersion and WindowsProductName properties are apparently frozen for backward compatibility; the workaround is to use OSVersion and OSName instead.

@microsoft-github-policy-service microsoft-github-policy-service bot removed the Needs-Triage The issue is new and needs to be triaged by a work group. label Jul 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants