Lỗi game is not a valid win32 application

What causes the error that .exe is not a valid Win32 application? How to fix the error not a valid Win32 application? This post from MiniTool will show you the solutions. In addition, you can visit MiniTool to find more Windows tips and solutions.

On This Page :

When the file or program you are trying to run is corrupt or missing, Windows is unable to execute the file properly. Hence, you may encounter the error that .exe is not a valid Win32 application, as the following picture:

So, when coming across this error, do you know how to solve it? Keep on your reading to find the answers.

How to Fix the Error Not a Valid Win32 Application?

In this part, we will demonstrate how to solve the error that .exe is not a valid Win32 application.

Before proceeding with the solutions, please check the program is compatible with your version of Windows. If you downloaded a wrong version of program, you will come across the error that .exe is not a valid Win32 application.

Method 1. Reinstall Program Again

If the program you downloaded has been verified that it is complete and compatible with your version of Windows (What Version of Windows Do I Have? Check Version and Build Number). The error not a valid Win32 application may be caused by the corrupt file during downloading.

So, in order to fix the error that .exe is not a valid Win32 application, you can try to download the program again and reinstall it.

And then run it and check whether the error not a valid Win32 application is solved. If it is not effective, try other solutions.

Method 2. Run the Program as Administrator

In order to fix the error that .exe is not a valid Win32 application, you can choose to run the program as administrator.

Now, here is the tutorial.

1. Right-click the program encountering the error not a valid Win32 application.
2. Then choose Properties.
3. Go to the Compatibility tab and check the option Run this program as an administrator.

Then run the program and check whether the error that .exe is not a valid Win32 application.

Method 3. Check Bad File

And file can be changed or renamed as the .exe file. If you’re downloading the file, make sure the file is supposed to be .exe file and it is not being changed. If you want to create a .exe file, please make sure that you are compiling the file for Windows and never rename a file to a.exe file directly.

Otherwise, the file would not be executable and you may encounter the error not a valid Win32 application. For a file to become an executable file, it needs to either be compiled or converted through a software program designed to convert the file.

So, in order to fix the error that .exe is not a valid Win32 application, you can try checking whether the file has been renamed or changed.

Final Words

To sum up, this post has introduced 3 ways to fix the error that .exe is not valid Win32 application. If you come across the same error, try these solutions. If you have any better solution to fix it, you can share it in the comment zone.

About The Author

Position: Columnist

Tina is a technology enthusiast and joined MiniTool in 2018. As an editor of MiniTool, she is keeping on sharing computer tips and providing reliable solutions, especially specializing in Windows and files backup and restore. Besides, she is expanding her knowledge and skills in data recovery, disk space optimizations, etc. On her spare time, Tina likes to watch movies, go shopping or chat with friends and enjoy her life.

I have developed an C#, ASP.NET web application in a Windows 7 machine using Visual Studio 2012. Now i had imported the entire project into VS 2017 running on windows 10 machine, and when i try to enter the debugging mode to analyze my code it shows the following error:

I guess the project configurations are conflicting hence it throws this error. Any suggestions??

Rufus L

36.4k5 gold badges31 silver badges46 bronze badges

asked Feb 3, 2018 at 22:47

4

The same error happens when Visual Studio solution has selected the wrong Startup Project. The bold project is the designated startup project.

Go to the Solution Explorer > Right click on the correct project and select "Set as StartUp Project" in the context menu.

answered Apr 21, 2020 at 15:48

ThomasThomas

3813 silver badges5 bronze badges

I also got this error. I ultimately got to know that I was not selecting .sln file.

In VS, you should select .sln file and it automatically loads the complete project structrue is what I learnt.

Selecting .sln file worked for me

answered Nov 13, 2019 at 10:35

1

These errors are mostly because you are not selecting the .sln or solution file. In your solution explorer tree, double click the solution file and then build and run.

This runs contrary to a users intuition that simply opening a file and running it would work. Consider it a poor user interface. Jet Brains Rider, for instance, does not have this issue.

answered Apr 29, 2021 at 18:58

Dean PDean P

1,88123 silver badges23 bronze badges

Don't export the project folder. upload the .sln file. It will work.

Dino

7,92112 gold badges46 silver badges88 bronze badges

answered Oct 21, 2019 at 3:48

1

DLLs cannot be ran/debugged directly. You have to specify host application in the Configuration Properties>Debugging>Command and then let it load the DLL by itself.

You will most likely need to copy the DLL to the directory searchable by the host application e.g. its root or ./plugins folder. In the Configuration Properties>Build Events>Post-Build Event>Command Line simply enter something like:

copy "$(TargetPath)" "$(HOST_APP)\plugins" 

answered Jan 13, 2020 at 7:54

Soyal7Soyal7

3915 silver badges10 bronze badges

The Startup Item needs to be a .exe file. It's looking at BusinessLayer.dll because BusinessLayer is currently the Startup Project.

First, build the solution. Then, set the Solution Explorer to folder view and find the .exe in one of you project's /bin folders. Right click on it and set it to the Startup Item.

Finally, click the play button in Visual Studio top bar.

EDIT: Basically the same as Thomas' answer, but I'm pointing out that the "correct project" is the one with the .exe file. I would have commented on his answer, but I have less than 50 rep right now.