You can try loading it in Windows Sandbox, Hyper-V, vmware or virtualbox.

DosFreak wrote on 2022-11-02, 20:13:

You can try loading it in Windows Sandbox, Hyper-V, vmware or virtualbox.

It crashed the same way in Sandbox as well.

You can check Event Viewer and see if any events are logged at the same time and see if they're related. Or try to use Process Explorer / Process Monitor to find out what the last thing it did before it crashed was.

ZellSF wrote on 2022-11-03, 10:45:

You can check Event Viewer and see if any events are logged at the same time and see if they're related. Or try to use Process Explorer / Process Monitor to find out what the last thing it did before it crashed was.

I used Process Monitor and saw some SMT related stuff going on before the exe crashed, so I thought that disabling all the cores in the BIOS minus four (making it a 4 core/8 thread system) would help. Did that and it started instantly, woot! So it seems like it WAS related to the CPU, but simply parking the e-cores through the game compatibility option in the BIOS wasn't enough.

Hell, even tested it by enabling all the P-Cores and only 8 E-Cores to emulate a 12900k, and it still worked! So, I was right about it being CPU related!

Hmm try leaving all cores enabled and try start /affinity 1 moha_setup.exe

DosFreak wrote on 2022-11-03, 22:45:

Hmm try leaving all cores enabled and try start /affinity 1 moha_setup.exe

That works as well.
It seems this problem starts at exactly 32 cores. Using different CPU affinity masks which result in 31 cores (such as having it launch just with all cores minus core 0/1/2/3/etc) lets it launch no problem.

*24 cores. Your CPU has 24 cores and 32 threads.

My CPU (AMD 5950x) has 32 threads too, but does not have this issue. Seems Intel really likes introducing weird compatibility issues lately? At least the fix is easy and not too harmful in terms of performance.

I wonder how older Intel 32 thread CPUs fare. I'm guessing better.

MrEWhite wrote on 2022-11-04, 00:39:

DosFreak wrote on 2022-11-03, 22:45:

Hmm try leaving all cores enabled and try start /affinity 1 moha_setup.exe

That works as well.
It seems this problem starts at exactly 32 cores. Using different CPU affinity masks which result in 31 cores (such as having it launch just with all cores minus core 0/1/2/3/etc) lets it launch no problem.

I know this thread is old but I thought replying to it was my best shot at getting a reply. I am having exactly the same issue as you were. I can use a shortcut to set the processor affinity and get MOHA_setup to launch but using the same method on the MOHA.exe just makes the EA app act like it is launching the game and then nothing. I wondered how you got past this step or do I just need to get a non ea app version?
This seems to be an issue with several old games with the i9-13900K and 32 cores.

Any help greatly appreciated.

RTX 4090 (drivers ver 555.99
i9-3900K 3.00
64Gb Ram
Windows 11 23H2

The Ms compatibility toolkit might have a flag that limits max reported cpus

https://learn.microsoft.com/en-us/windows/win … y-toolkit--act-

myne wrote on 2024-06-16, 01:24:

The Ms compatibility toolkit might have a flag that limits max reported cpus

https://learn.microsoft.com/en-us/windows/win … y-toolkit--act-

This also works. Used this to fix some older Ubisoft games (Far Cry 2 & 3 and Rocksmith 2014 Remastered) that wouldn't launch on a 13900KS by just enabling the "ProcessorCountLieForHybridCPU" compatibility fix. It also works for MOHA no problem.

Absolute geniuses. I did not even know this kit existed but not only has it got Medal of Honor Airborne running but I used it for Wings of Prey which similarly stopped working when I changed processor and it worked of that too.
It will know enter my tool kit of fixes alongside dgvooodoo.
Thank you both so much.

Should post the fixes you made.
Someone is bound to have the same problem and find this thread.

myne wrote on 2024-06-19, 23:49:

Should post the fixes you made.
Someone is bound to have the same problem and find this thread.

Fair enough.
Firstly I do not claim to fully understand the fix. From what I can tell it just "lies" to the program about the number of cores you have. It does seem to change the registry so it is best to back that up before applying the fix.
Secondly some threads I have read say you should then set the exe to read only or verifying files or downloading and update will undo the fix.

The Fix is for Wings of Prey and for Medal of Honor Airborne (EA app version, the steam version works without it) based on the suggestions above and I followed steps I found for similar issues with Child of Light and Technomancer.

The PCgamingwiki has it listed for the technomancer here:
https://www.pcgamingwiki.com/wiki/Child_of_Light

Search for "windows adk"
The top result should take you to a microsoft page with a link to the latest Assessment and Development Kit (ADK)
Download this and run, but install only the compatibility tools.
Run the 32 bit version of the compatibility administrator (on the start programs menu it is under windows kits)
In the left column right click on the "new databases" below "custom database" rename it to Game Fix
With it highlighted click "fix" on the toolbar near the top.
Type in the name of the game you are fixing and the vendor (I have no idea if this matters, for Medal of Honor Airborne I did EA and for Wings of Prey, Gaijin)
Then browse for the game exe. (for wing of prey this is acess.exe in the main game directory, for Medal of Honor Airborne it is in /unrealengine3/binaries and you will need to repeat the steps for both MOHA.exe and moha_setup.exe (The EA app launches the setup program each time and it also won't launch without this)
Then click "next"
I changed nothing on the next screen so click "next" again
On the next screen scroll down and tick and highlight "processorcountlie" then click "parameter"
In the command line type "16" then press ok
Then tick and highlight "processorcountlieforhybridCPU" and click "parameter"
In the command line type "16" then press ok
Click "auto-generate"
Then click finish
Back on the main screen click the "save" button in the toolbar (I save it to the game directory)
Then right click your "Game fix" database and click "install"
The game should now launch.

If anyone with more knowledge wants to explain the fix more clearly or knows if any of the steps are harmful or unnecessary please comment.

Oh, very detailed.
I meant post the sdb file it makes/you made

Cloister56 wrote on 2024-06-20, 18:09:

Fair enough. Firstly I do not claim to fully understand the fix. From what I can tell it just "lies" to the program about the nu […]
Show full quote

myne wrote on 2024-06-19, 23:49:

Should post the fixes you made.
Someone is bound to have the same problem and find this thread.

Fair enough.
Firstly I do not claim to fully understand the fix. From what I can tell it just "lies" to the program about the number of cores you have. It does seem to change the registry so it is best to back that up before applying the fix.
Secondly some threads I have read say you should then set the exe to read only or verifying files or downloading and update will undo the fix.

The Fix is for Wings of Prey and for Medal of Honor Airborne (EA app version, the steam version works without it) based on the suggestions above and I followed steps I found for similar issues with Child of Light and Technomancer.

The PCgamingwiki has it listed for the technomancer here:
https://www.pcgamingwiki.com/wiki/Child_of_Light

Search for "windows adk"
The top result should take you to a microsoft page with a link to the latest Assessment and Development Kit (ADK)
Download this and run, but install only the compatibility tools.
Run the 32 bit version of the compatibility administrator (on the start programs menu it is under windows kits)
In the left column right click on the "new databases" below "custom database" rename it to Game Fix
With it highlighted click "fix" on the toolbar near the top.
Type in the name of the game you are fixing and the vendor (I have no idea if this matters, for Medal of Honor Airborne I did EA and for Wings of Prey, Gaijin)
Then browse for the game exe. (for wing of prey this is acess.exe in the main game directory, for Medal of Honor Airborne it is in /unrealengine3/binaries and you will need to repeat the steps for both MOHA.exe and moha_setup.exe (The EA app launches the setup program each time and it also won't launch without this)
Then click "next"
I changed nothing on the next screen so click "next" again
On the next screen scroll down and tick and highlight "processorcountlie" then click "parameter"
In the command line type "16" then press ok
Then tick and highlight "processorcountlieforhybridCPU" and click "parameter"
In the command line type "16" then press ok
Click "auto-generate"
Then click finish
Back on the main screen click the "save" button in the toolbar (I save it to the game directory)
Then right click your "Game fix" database and click "install"
The game should now launch.

If anyone with more knowledge wants to explain the fix more clearly or knows if any of the steps are harmful or unnecessary please comment.

You don't need to do the ProcessorCountLie fix nor the 16 parameter for ProcessorCountLieForHybrid CPU.

[/quote]
You don't need to do the ProcessorCountLie fix nor the 16 parameter for ProcessorCountLieForHybrid CPU.
[/quote]

Which bits do I need to do please?

Personally I don't think it matters. It works. So what if it does more then strictly necessary.

Cloister56 wrote on 2024-06-23, 11:00:

You don't need to do the ProcessorCountLie fix nor the 16 parameter for ProcessorCountLieForHybrid CPU.
[/quote]

Which bits do I need to do please?
[/quote]
Follow all the directions, but just use tick ProcessorCountLieForHybridCPU and it will work.