{"id":7147,"date":"2014-04-02T05:00:00","date_gmt":"2014-04-02T13:00:00","guid":{"rendered":"http:\/\/www.sapien.com\/blog\/?p=7147"},"modified":"2014-04-01T15:23:25","modified_gmt":"2014-04-01T23:23:25","slug":"microsoft-windows-8-1-breaks-version-api","status":"publish","type":"post","link":"https:\/\/dev.sapien.com\/blog\/2014\/04\/02\/microsoft-windows-8-1-breaks-version-api\/","title":{"rendered":"Microsoft Windows 8.1 breaks version API."},"content":{"rendered":"

If we need to check what Windows version a PowerShell script run on, we usually use a statement like this:<\/p>\n

\"Shell\"<\/p>\n

So imagine our surprise when we saw what happens when you run this as a script in PrimalScript:<\/p>\n

\"PrimalScript\"<\/p>\n

Instead of reporting the actual Windows version, it appears as if we are running in Windows 8 instead of 8.1
\nTo make sure we didn\u2019t have a glitch in PrimalScript (and because we didn\u2019t quite trust our eyes), we packaged the script as an executable and ran that.<\/p>\n

 <\/p>\n

\"Packaged\"<\/p>\n

Same result, it reports the incorrect version number.<\/p>\n

According to Microsoft this is intentional:<\/p>\n

http:\/\/msdn.microsoft.com\/en-us\/library\/windows\/desktop\/dn302074(v=vs.85).aspx<\/a><\/p>\n

Before you ask, we have no idea what could possibly possess Microsoft to break such a fundamental API call so that it reports an incorrect version.<\/p>\n

As shown on the web page we linked to above, you have to tag your executable in a manifest as supporting Windows 8.1 in order to get a correct version number.<\/p>\n

\"Custom<\/p>\n

In the packager settings you have to switch to a custom manifest and and specify the manifest file.<\/p>\n

\"Settings\"<\/p>\n

If you follow this patch and re-package the executable it will now report the correct version number.<\/p>\n

\"With<\/p>\n

Needless to say, we will update our default manifest and the packager to accommodate this latest \u201cit\u2019s not a bug, it\u2019s a feature\u201d play by Microsoft in the next service build.<\/p>\n","protected":false},"excerpt":{"rendered":"

If we need to check what Windows version a PowerShell script run on, we usually use a statement like this: So imagine our surprise when we saw what happens when you run this as a script in PrimalScript: Instead of reporting the actual Windows version, it appears as if we are running in Windows 8 […]<\/p>\n","protected":false},"author":5,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[703,410,21,25],"tags":[553,897,898,28,1016,37,899],"class_list":["post-7147","post","type-post","status-publish","format-standard","hentry","category-powershell-studio","category-primalscript-software-news","category-software-news","category-windows-powershell","tag-api","tag-getversion","tag-osversion","tag-powershell","tag-powershell-studio","tag-primalscript","tag-windows-8-1"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t