Search

In Visual Studio 2012 Applications compiled for x64 do not run on Windows XP x64 by gc04

Closed
as By Design Help for as By Design

1
0
Sign in
to vote
Type: Bug
ID: 780700
Opened: 3/5/2013 8:40:06 AM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
When you try to run an application that is compiled for x64 on Windows XP x64 you get an error message "C:\application.exe is not a valid Win32 application.".
Details (expand)

Visual Studio/Team Foundation Server/.NET Framework Tooling Version

Visual Studio 2012

Steps to reproduce

Create a new default Win32 project.
Add an x64 configuration.
Set platform toolset to "Visual Studio 2012 - Windows XP (v110_xp)"
Compile for x64.
Run on Windows XP x64.

Product Language

English

Operating System

Windows XP

Operating System Language

English

Actual results

An error message box appears with the message "C:\application.exe is not a valid Win32 application.".

Expected results

The application should run showing the default project window.
File Attachments
File Name Submitted By Submitted On File Size  
XP x64 Test.zip 3/5/2013 40 KB
Sign in to post a comment.
Posted by gc04 on 3/9/2013 at 9:49 PM
Felix,

Setting the /Subsystem fixes the problem.
Posted by Microsoft on 3/8/2013 at 2:58 PM
Hello gc04,
Thank you for opening a connect report with us. In order for the binary to work on Windows XP, it needs to have a subsystem version. This version number is added to the binary during Linking (link.exe). The switch sets the value is /Subsystem (http://msdn.microsoft.com/en-us/library/fcc1zstk.aspx). However for the switch to work, it will need you to set /Subsystem as a pre-requisite.

Let me know if this information fixes your issue.

Thanks

Felix Huang
VC++ Project & Build
Posted by Microsoft on 3/6/2013 at 12:26 AM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by Microsoft on 3/5/2013 at 11:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.