| Facter 4's current behavior for Windows 10 is:
"os": { |
"architecture": "x64", |
"family": "windows", |
"hardware": "x86_64", |
"name": "windows", |
"release": { |
"full": "10", |
"major": "10" |
}, |
"windows": { |
"edition_id": "Enterprise", |
"installation_type": "Client", |
"product_name": "Windows 10 Enterprise", |
"release_id": "2004", |
"system32": "C:\\Windows\\system32" |
} |
},
|
and Windows 11
"os": { |
"architecture": "x64", |
"family": "windows", |
"hardware": "x86_64", |
"name": "windows", |
"release": { |
"full": "11", |
"major": "11" |
}, |
"windows": { |
"display_version": "21H2", |
"edition_id": "EnterpriseEval", |
"installation_type": "Client", |
"product_name": "Windows 10 Enterprise Evaluation", |
"release_id": "21H2", |
"system32": "C:\\Windows\\system32" |
} |
}
|
The "product_name" being set to Windows 10 is a well known Microsoft issue. But from facter's perspective we are accurately reporting what is in the registry, so we're going to close this. However, the original request was to be able to differentiate between 10 and 11, and it is currently possible to use "os.release.full" or "os.release.major" for that purpose. And for Windows 11, the "release_id" can be used to distinguish between 21H2 and 22H2. |
