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
Windows 10: Target Windows 10 via app manifest #4760
Comments
Comment 1 by nvdakor on 2014-12-29 22:31
|
Comment 2 by jteh on 2015-01-05 23:09 |
Comment 3 by nvdakor on 2015-01-05 23:12 |
Comment 4 by nvdakor on 2015-01-05 23:15 |
Comment 5 by Joseph Lee <joseph.lee22590@... on 2015-02-20 06:14
|
Comment 6 by James Teh <jamie@... on 2015-02-20 06:14
Changes:
|
Comment 7 by jteh on 2015-02-20 06:36 |
Comment 8 by James Teh <jamie@... on 2015-03-26 05:27
Changes:
|
Comment 9 by jteh on 2015-03-26 05:28 |
This means that correct Windows version information will be reported on Windows 10. Fixes #4760.
Reported by nvdakor on 2014-12-29 22:22
Hi,
Spin-off from #3793:
The fix for #3793 also applies to Windows 10: it has its own GUID (globally unique identifier). Various comments inMSDN articles says the GUI is:
Microsoft intends to use GUID's to test for OS targeting, according to a remark in MSDN article on version helper API's.
Reference:
Thanks (hope the GUID stays between kernel version changes, as WinTen is now NT 10.0 instead of 6.4).
The text was updated successfully, but these errors were encountered: