5 replies to this topic

[Johannes John]

Hello together,

 

why does the msiexec of the new W10 shows VersionNT = 603 ?

 

What's that???

 

Regards

Johannes

[Stefan Krueger]

I guess that Microsoft did this for backward compatibility...

[BFealy]

As far as I can tell, it looks like the VersionNT will always be 603 from this point onward (Win 8.1/2012 and future versions) and it's intentional by MS.

 

I've had to write in a registry search for the value in 

HKEY_LOCAL_MACHINE\SOFTWARE\\Microsoft\Windows NT\CurrentVersion\CurrentMajorVersionNumber and use the value there in combination with VersionNT=603 to determine if we're running on Win 10.

 

I'm hoping there's a more elegant way to do this, but haven't found it yet.

[ANo]

Hello,
I run in the same problem. So I have to check the registry too.

 

But what I not understand, I have IS 2015 SP1 and the Release Notes say:
"SYSINFO.WINNT.bWin10—This is a new SYSINFO structure member.
If the operating system is Windows 10, this value is TRUE.
(This is applicable to InstallScript event-driven code; it is not applicable to custom actions.)"

 

But this does not work for me on all OS = Windows 10. The return value is always FALSE.
Can somebody recheck this behavior please?

 

Regards
André

[Stefan Krueger]

Works properly for me - only in a (pure) InstallScript project, no MSI whatsoever. What is your project type?

[ANo]

Hello Stefan,

thank you for the answer. You are right.

SYSINFO to query operating systems can be used in InstallScript projects only.

 

Sorry, it is my mistake.

 

(SYSINFO.nUserLangID can be used in a MSI project too.)

 

Thank you to recheck it.

 

Regards

André