CoD Black Ops II - Windows 10 Unhandled Exception FIX

[JakeHekesFists]

OK, I'm writing this guide as this is a problem that continues to occur, with every update to the tech preview for Windows 10

The "Error during initialisation" "unhandled exception caught" errors that happen everytime windows 10 updates.

Many supposed 'fixes' for this problem are "revert to windows 7"
That is not a fix, That is uninformed people providing bad advice.

I will teach you now, how to fix the issue. Properly, without uninstalling windows 10 and going back to 7 or 8.
I am writing this guide to help anyone that will encounter this issue, particularly as we get closer to the official release of Windows 10.

-------------------------------

HOW TO FIX

-------------------------------

First thing you need to do is ensure your visual c libraries are up to date and installed.

you can locate the correct redist for Visual C. only the x86 version is required here.
you can find this in your black ops 2 folder, under redist

eg. mine is located here:
"E:\Steam\steamapps\common\Call of Duty Black Ops II\redist\vcredist_x86.exe"

run that, install it. now the next thing to do, is make sure you have the correct DX9 libraries installed.
these are also located in the redist folder. run dxsetup.exe which is located in the redist\directx folder,
eg. mine is here:
"E:\Steam\steamapps\common\Call of Duty Black Ops II\redist\DirectX\DXSETUP.exe"

after this is done,
right click on t6mp.exe
click on the compatability tab, check the following options.

run this program in compatability mode for windows 8 or 7, -if one doesn't work, try the other.
(and run this program as an administrator)
(Note: These instructions were written when windows 10 was still Tech Preview only. you no longer need to run as admin)
click apply

now you're almost done.
go into steam, right click on call of duty: black ops ii - multiplayer, go to properties.
click on the Local Files tab, and then "verify integrity of game cache"

let this process complete, and once done. run the game.
it will likely pop up that the game is installing for a few seconds, and then it will work.

I have been running windows 10 for a while now, and with every update, I have needed to perform these actions to make Black Ops II work again.

I hope this helps at least one of you.

Cheers.
Jedish3ep.

[Lardinator]

AkiraJkr a écrit :

Yeah, tried all ♥♥♥♥♥♥♥ like changing timezones, installing those things, offline mode, verifying, putting 1 processor, did everything in the order suggested too, like-- seriously, I've tried everything this thread throws at you. Still get the stupid unhandled exception at startup.

Here's the complete waste of time I've went through:

- Blocked the game entirely from the firewall.
- Changing date and time between many different combinations.
- Trying compatibility settings
- Cleaning my players folder
- Verified game files, countless, many times
- Running with PC at 1 processor in msconfig, multiple times.
- Having both SP, MP and ZM installed
- Offline mode
- Detection off in RivaTuner or just straight up killing MSI Afterburner
- Trying to play in the original/non-family shared account.(Which by the way, the owner can play just fine)
- Disabled all overlays.
- Deleted the game's appmanifests with Steam closed.
Don't bother. None of it works.

EDIT

Disable VoiceMeeter devices, one. By. One.

Thank you so much, It was ♥♥♥♥♥♥♥ voicemeeter all allong.

[NOODLE]

yes, bro finally. It was ♥♥♥♥♥♥♥ Voicemeeter!

lardinator a écrit :

AkiraJkr a écrit :

Yeah, tried all ♥♥♥♥♥♥♥ like changing timezones, installing those things, offline mode, verifying, putting 1 processor, did everything in the order suggested too, like-- seriously, I've tried everything this thread throws at you. Still get the stupid unhandled exception at startup.

Here's the complete waste of time I've went through:

- Blocked the game entirely from the firewall.
- Changing date and time between many different combinations.
- Trying compatibility settings
- Cleaning my players folder
- Verified game files, countless, many times
- Running with PC at 1 processor in msconfig, multiple times.
- Having both SP, MP and ZM installed
- Offline mode
- Detection off in RivaTuner or just straight up killing MSI Afterburner
- Trying to play in the original/non-family shared account.(Which by the way, the owner can play just fine)
- Disabled all overlays.
- Deleted the game's appmanifests with Steam closed.
Don't bother. None of it works.

EDIT

Disable VoiceMeeter devices, one. By. One.

Thank you so much, It was ♥♥♥♥♥♥♥ voicemeeter all allong.

THIS.

[Slightlyunbound]

does not work

[arielrc11]

And how I solve it in crossover? I can’t change the compatability

[Kamul]

That worked on me during a few missions. Now I've still got the same error right after a mission's over.

[Spook]

None of this worked for me but see my post in the thread below with a further possible solution (which also fits in with the voicemeeter solution posts above).

https://steamcommunity.com/app/202970/discussions/0/4751948774785934227/

[Xbox_17]

Thanks, bro❤️❤️

[JackSmacks]

2025 and this post is still helping people, thanks