0.12.3 on Windows XP give not valid win32 application error

[deliverymanager]

I tested on a Windows XP platform.
a) 0.10.33 works fine.
b) 0.12.2 works fine
c) 0.12.3 after installing without a problem, I try to open the Node.exe and it gives me an error "node.exe is not a valid win32 application"

I have also tested the same win32 x86 0.12.3 version on a windows 7 platform and it works fine.
So, probably, this is related to a windows XP problem.

[jasnell]

duplicate of #25347

[misterdjules]

@orangemocha Do you have some time to investigate?

[orangemocha]

Not a dupe of #25347, as that one was reported on Windows 7, and this issue is specific to Windows XP.

Most likely would need to backport nodejs/node@e8d0850

[jasnell]

@orangemocha ah... ok.. missed that distinction entirely.

[JimHolloman]

I have the same issue on XP, 32-bit. Both the installation (.msi) package and the stand-alone node.exe file (I downloaded both) provide the message "node.exe is not a valid win32 application". The npm provides the same error with the program name changed to npm.exe.

I wonder if someone packaged the 64-bit code as a 32-bit install (.msi) and stand-alone program (node.exe).

Looking forward to getting a copy that will run on Windows XP, 32-bit. I can provide testing once an update is available.

[orangemocha]

Ok, the problem is the gyp/project files don't explicitly specify a subsystem version, which results in the default being used. The default changed from VS 2010 to VS 2012 and later. So this means that one of the release machines still has VS 2010. (@misterdjules we should probably fix that or at least try to document it in an asset sheet). nodejs/node@e8d0850 fixes the issue. Opening a PR shortly.