OSVersion , OSServicePack , on Win7 pro 64Bit

[mLipok]

on some clients station with Win7 x64  

I have that strange values of this macro:

@CPUArch = X64

@OSLang = 0415

@OSArch = X64
@OSType = WIN32_NT
@OSVersion = WIN_XP
@OSBuild = 2600

@OSServicePack = Service Pack 3 

 

Remarks:

This app is not running in compability mode

AutoIt 3.3.8.1

 

 

Question:

Does anyone have / had a similar problem?

How to solve it?

 

[UEZ]

I get always

X64
0409
X64
WIN32_NT
WIN_7
7601
Service Pack 1

Br,

UEZ

[guinness]

I have the same system and I don't get that.

[UEZ]

Might be an issue with virtualization or Citrix....

Br,

UEZ

[guinness]

Get them to run this and let us know.

#include <Constants.au3>
#include <WinAPIEx.au3>

MsgBox($MB_SYSTEMMODAL, '', 'Windows Version: ' & _WinAPI_GetVersion() & @CRLF) ; Should be 6.1.

Edited October 24, 2013 by guinness

[mLipok]

Might be an issue with virtualization or Citrix....

Br,

UEZ

 

no

normal instalation 

even not in Domain

 

 

Get them to run this and let us know.

#include <Constants.au3>
#include <WinAPIEx.au3>

MsgBox($MB_SYSTEMMODAl, '', 'Windows Version: ' & _WinAPI_GetVersion() & @CRLF) ; Should be 6.1.

 

ok

I'll check it as soon as it's possible.

I think that, by next week I will have the test.

Although it is possible that tomorrow.

[guinness]

Well if that returns something other than 6.1 then it's the system. It's what (I presume) AutoIt uses but returns it as a user friendly Windows <SOMETHINGVERSIONNUMBER>.

[mLipok]

I use that small script:

#include <Constants.au3>
#include <WinAPIEx.au3>


$sSystemInfo = ''
$sSystemInfo &= '_WinAPI_GetVersion() = ' & _WinAPI_GetVersion() & @CRLF ; fOR WIN7 Should be 6.1.
$sSystemInfo &= '@CPUArch = ' & @CPUArch & @CRLF
$sSystemInfo &= '@OSLang = ' & @OSLang & @CRLF
$sSystemInfo &= '@OSArch = ' & @OSArch & @CRLF
$sSystemInfo &= '@OSType = ' & @OSType & @CRLF
$sSystemInfo &= '@OSVersion = ' & @OSVersion & @CRLF
$sSystemInfo &= '@OSBuild = ' & @OSBuild & @CRLF
$sSystemInfo &= '@OSServicePack = ' & @OSServicePack & @CRLF
ClipPut($sSystemInfo)
ConsoleWrite($sSystemInfo)
MsgBox($MB_SYSTEMMODAL, '', $sSystemInfo )

Results:

_WinAPI_GetVersion() = 6.1
@CPUArch = X64
@OSLang = 0415
@OSArch = X64
@OSType = WIN32_NT
@OSVersion = WIN_7
@OSBuild = 7601
@OSServicePack = Service Pack 1

 

But when I do the same inside other program:

@OSVersion = WinXP and WinApi 5.1

 

On hundreds of workstations, this problem occurs sporadically.

But not all have Win7 (there are Vista and largely still XP), so the percentage of the problem, can be considerable.

 

Do you have any ideas on how to diagnose what is causing the problem?

 

EDIT:

Now I test on Win7 Home Premium 64 Bit

Edited November 22, 2013 by mlipok

[mLipok]

I finally have a solution to this problem.
I found the following:

CRM application used by my clients, allows you to assign F12 to call an external program.
I use this app to call my program.
Prior to this I did not mention because I did not consider this as important information.

Now I know and basically it was always clear to me that the invocation of another, will inherit permissions from the main program.
Of course, as they say "the darkest under the lamp," so I did not check whether this particular CRM client by "accident/mistake" does not run in compatibility mode, and indeed it was.

[mLipok]

And now I have a question:
Is it possible to check that the program (Windows process) is running in compatibility mode ?

[mLipok]

Now I noticed that basically, I created two separate threads about the same topic:
'?do=embed' frameborder='0' data-embedContent>>

I checked and the solution:
FileGetVersion (@ SystemDir & " Winver.exe")

is actually useful.
 

But still the question is whether it is possible to check information about using compatibility mode only based on PID ?

This would be a more practical solution.

Regards

mLipok

 

EDIT:

I found an intresting script made by BrewManNH

'?do=embed' frameborder='0' data-embedContent>>

but unfortunately does not show information about compatibility mode.

As you would expect the system somewhere writes, information about the properties of the file.
This would at least check whether the executable file is to set the property "Run in compability mode".

Edited February 18, 2014 by mLipok