We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The 'Windows Home Server ' product name is not detected and displayed correctly. EK only detects the core OS code that WHS is based on.
The product key is correctly displayed.
Migrated from https://sourceforge.net/p/ekeyfinder/bugs/8/
The text was updated successfully, but these errors were encountered:
Marcus Stewart said:
It may be possible to pull this information from the WMI repository for the windows version, not sure... I beleive the WMI path is: root\cimv2:Win32_OperatingSystem\Caption However there may be issues doing it this way when doing load hive.
It may be possible to pull this information from the WMI repository for the windows version, not sure...
I beleive the WMI path is: root\cimv2:Win32_OperatingSystem\Caption
root\cimv2:Win32_OperatingSystem\Caption
However there may be issues doing it this way when doing load hive.
Sorry, something went wrong.
Is this something that can be resolved similar to how I wrote the additional information of Office versions based on the GUID?
No branches or pull requests
The 'Windows Home Server ' product name is not detected and displayed correctly.
EK only detects the core OS code that WHS is based on.
The product key is correctly displayed.
Migrated from https://sourceforge.net/p/ekeyfinder/bugs/8/
The text was updated successfully, but these errors were encountered: