Black Ops 2 on PC (via Steam) is a beloved but technically temperamental game — released in 2012, it was not designed for modern Windows 10 or Windows 11 systems, and several persistent bugs affect new PC players. This guide covers the exact minimum and recommended system requirements, how to save your keybindings in BO2 on Steam (one of the most searched BO2 PC issues), how to fix the unhandled exception caught error, the CMN_ROOT Polish language bug, and every other common PC technical issue.
For Black Ops 2 multiplayer including player count, active servers, and best class setups, see our complete Black Ops 2 multiplayer guide — player count, maps, and class setups.
Black Ops 2 PC System Requirements
Minimum System Requirements
| Component | Minimum Specification |
| OS | Windows Vista SP2 / Windows 7 SP1 (works on Win 10/11 with fixes) |
| CPU | Intel Core 2 Duo E8200 2.66 GHz / AMD Phenom X3 8750 2.4 GHz |
| RAM | 2 GB RAM |
| GPU | NVIDIA GeForce 8800GT 512MB / ATI Radeon HD 3870 512MB |
| DirectX | Version 9.0c |
| Storage | 16 GB available space |
| Internet | Broadband connection for multiplayer |
Recommended System Requirements
| Component | Recommended Specification |
| OS | Windows 7 64-bit (Windows 10/11 works with compatibility fixes) |
| CPU | Intel Core i5-2500K @ 3.3 GHz / AMD Phenom II X6 1100T |
| RAM | 8 GB RAM |
| GPU | NVIDIA GeForce GTX 670 2GB / ATI Radeon HD 7950 |
| DirectX | Version 11 |
| Storage | 16 GB available space |
In 2026: BO2 is a 2012 game — any modern PC, laptop, or even integrated graphics chip significantly exceeds these requirements. Performance issues on modern hardware are almost always caused by software compatibility issues rather than insufficient specifications.
How to Save Keybindings in Black Ops 2 on Steam
Saving keybindings in Black Ops 2 on Steam is a known issue — the game often resets custom keybinds to default when you exit and relaunch, especially on Windows 10 and 11. This is the most frequently searched BO2 PC technical problem. Here are the fixes in order of reliability:
Fix 1: Run the Game as Administrator
- Right-click the Black Ops 2 shortcut or Steam entry → Properties → Compatibility → check Run this program as an administrator
- Launch the game through Steam — administrator privileges allow the game to write keybinding data to its config file, which standard user accounts may block
- This is the most common cause of keybindings not saving — the game cannot write to its config file without admin permissions
Fix 2: Set Config File to Read-Write
- Navigate to Steam\steamapps\common\Call of Duty Black Ops II\players
- Find the config.cfg file (or config_mp.cfg for multiplayer)
- Right-click → Properties → uncheck Read-only if it is checked → Apply
- Launch the game, set your keybindings, and exit normally — check if they persist on next launch
Fix 3: Manually Edit the Config File
If the above methods fail, manually binding keys in the config file is the most reliable solution:
- Navigate to Steam\steamapps\common\Call of Duty Black Ops II\players\
- Open config_mp.cfg (for multiplayer binds) in Notepad or any text editor
- Find lines starting with ‘bind’ — e.g., bind F “weapnext”
- Add or edit bind lines to match your desired keybindings — e.g., bind MOUSE3 “+melee”
- Save the file, then set it to Read-Only (right-click → Properties → Read-only) so the game cannot overwrite it
- Launch the game — your custom binds will be applied and cannot be reset
Fix 4: Verify Game Files
- In Steam: right-click Black Ops 2 → Properties → Local Files → Verify integrity of game files
- Steam will check and repair any corrupted or missing game files
- After verification, try setting and saving keybindings again with administrator mode enabled
Black Ops 2 Multiplayer Unhandled Exception Caught — How to Fix
The ‘Unhandled exception caught’ error in Black Ops 2 multiplayer is one of the most common crash errors on PC. It typically causes the game to crash to desktop when launching multiplayer or during a game. Fixes:
Fix 1: Update DirectX
- Download and install the DirectX End-User Runtime Web Installer from Microsoft
- BO2 requires DirectX 9.0c redistributables — even on Windows 10/11 with DirectX 12, the older DirectX 9 redistributable must be installed separately
- After installing, launch Steam as administrator and try BO2 multiplayer again
Fix 2: Update Visual C++ Redistributables
- Download and install Microsoft Visual C++ 2012 Redistributable (both x86 and x64)
- Also install Visual C++ 2010 Redistributable — BO2 depends on multiple older VC++ runtime versions
- Restart the PC after installing, then launch BO2
Fix 3: Disable Antivirus Temporarily
- Some antivirus programs flag BO2’s .exe files or intercept network calls, causing the unhandled exception
- Temporarily disable real-time protection, launch BO2, and test if multiplayer launches
- If it works, add an exclusion for the Black Ops II folder in your antivirus settings
Fix 4: Run in Compatibility Mode
- Right-click the BO2 .exe in Steam\steamapps\common\Call of Duty Black Ops II\
- Properties → Compatibility → Run this program in compatibility mode for: Windows 7
- Also check Run as administrator → Apply
Fix 5: Disable Steam Overlay
- In Steam: right-click Black Ops 2 → Properties → General → uncheck Enable the Steam Overlay while in-game
- The Steam overlay can conflict with BO2’s older DirectX rendering, causing crashes
CMN_ROOT Polish Language Bug — Black Ops 2
The CMN_ROOT Polish error appears as a crash or text display issue in Black Ops 2 on PC, typically when the system language is set to Polish or when a corrupted language file is present. The error message contains ‘cmn_root’ followed by Polish text or encoding errors.
Fix the CMN_ROOT Bug
- In Steam: right-click Black Ops 2 → Properties → Language → change language to English (United States)
- Steam will download the English language files, replacing the corrupted or mismatched Polish files
- If the language is already set to English, verify game files (Properties → Local Files → Verify integrity) to replace corrupted language files
- Alternatively: navigate to Steam\steamapps\common\Call of Duty Black Ops II\zone\ and delete the ‘polish’ folder if present, then verify game files to restore clean English files
Black Ops 2 Not Launching on Windows 10 and Windows 11
Common causes of BO2 not launching on modern Windows:
- Missing DirectX 9.0c: Install the DirectX End-User Runtime Web Installer from Microsoft
- Missing Visual C++ Redistributables: Install 2010 and 2012 versions (x86 and x64)
- Antivirus blocking: Add an exclusion for the BO2 folder
- Steam not running as administrator: Launch Steam as admin, then launch BO2
- Corrupted game files: Verify game files via Steam
- Windows Defender blocking .exe: Go to Windows Security → Virus and Threat Protection → Exclusions → add the Black Ops II folder
Black Ops 2 Steam — Best Settings for Performance
BO2 on PC benefits from specific settings adjustments for best performance on modern hardware:
| Setting | Recommendation |
| Display Mode | Fullscreen (not borderless window — reduces input lag) |
| Resolution | Your native monitor resolution |
| Refresh Rate | Match your monitor’s refresh rate |
| Vertical Sync | Off — reduces input lag significantly |
| Anti-Aliasing | Off or FXAA — MSAA causes performance issues on modern GPUs with BO2 |
| Texture Quality | Extra (modern GPUs have more than enough VRAM) |
| Shadow Map | Medium — high shadow settings have large performance impact |
| FPS Cap | 250 (BO2’s engine cap) — uncapped can cause issues |
How to Increase FPS in Black Ops 2 PC
- Add launch options in Steam: right-click BO2 → Properties → General → Launch Options → add: +set r_multiGpu 0 +set r_blur 0 +set r_depthPrepass 0
- These launch options disable GPU multi-rendering (buggy in BO2), blur effects, and a rendering pre-pass that adds overhead without visible quality improvement
- Result: typically 20-40% FPS improvement on modern GPUs that struggle with BO2’s engine quirks
For Black Ops 2 editions, DLC packs, and where to buy the game on PC via Steam, see our guide to Black Ops 2 digital editions, DLC packs, and where to buy in 2026.
For current Black Ops 2 player counts on Steam, see SteamCharts — Black Ops 2 concurrent players. For BO2 on the Steam store, see the Black Ops 2 Steam page.
Black Ops 2 Redacted — Private Server Client
What Is Redacted?
Redacted is an unofficial Black Ops 2 client that enables private server hosting, mod support, and offline LAN play without the official Activision servers. It was created by the community to keep BO2 playable as official servers degraded in quality and the player count declined. Redacted allows players to host their own lobbies with custom settings, run custom game modes, and play without a Steam copy of the game.
Is Redacted Legal?
Redacted exists in a legal grey area — it is not authorized by Activision and technically violates BO2’s terms of service. Using it does not risk a ban from official Steam BO2 servers (since Redacted operates independently), but it is not officially supported. The Redacted client is downloaded from community sources rather than official channels. For competitive or standard multiplayer, the official Steam version with current player count is recommended over Redacted.
BO2 on Steam vs Redacted
For players with a legitimate Steam copy of BO2 who want standard multiplayer, the official Steam version provides access to official multiplayer with Valve Anti-Cheat (VAC) protection. Redacted is better for: custom game modes with friends, zombies modding, offline LAN parties, or playing with custom maps and mods that are not available on official servers.
One of the most effective overall fixes for Black Ops 2 PC issues is installing the game’s prerequisites manually rather than relying on the automatic installation. Navigate to Steam\steamapps\common\Call of Duty Black Ops II\_CommonRedist\ — this folder contains the DirectX, Visual C++, and other runtime installers that BO2 requires. Run each installer manually as an administrator. This ensures all prerequisites are correctly installed regardless of what was previously on your system. After running all prerequisites from this folder, restart your PC and launch BO2 as administrator — this resolves the majority of launch and crash issues including the unhandled exception caught error.
BO2’s config files are worth understanding for advanced PC players. The primary config files are located in Steam\steamapps\common\Call of Duty Black Ops II\players\. The config.cfg handles single-player settings; config_mp.cfg handles multiplayer settings including keybindings. A particularly useful config tweak is adding ‘seta cg_fov 80’ (or your preferred value up to 90) to config_mp.cfg — BO2’s in-game FOV slider is limited, and editing the config file directly allows a wider field of view. Add this line to config_mp.cfg, save the file, and set it to Read-Only to prevent the game from resetting it.
The technical quirks of Black Ops 2 on modern PC hardware stem from its age — the game was built for DirectX 11 era hardware and Windows 7, with rendering systems designed for GPUs that are now considered vintage. Modern NVIDIA and AMD GPUs use driver architectures that are fundamentally different from 2012 hardware, and BO2’s rendering engine interacts with these drivers in ways that were never anticipated or tested. The result is that performance issues on a modern RTX 4090 can sometimes be worse than on mid-range 2012 hardware, because the rendering path the game takes on modern hardware is less optimized than on the older hardware it was designed for. The launch options (+set r_multiGpu 0 etc.) and compatibility settings work by forcing BO2 into rendering modes that are more predictable on modern driver stacks.
For players who want to keep Black Ops 2 running smoothly long-term on their gaming PC, a few maintenance steps help prevent issues from developing. After any major Windows update, verify BO2’s game files on Steam — Windows updates sometimes modify or remove DirectX 9 components that BO2 depends on. Keep the config files backed up (copy config.cfg and config_mp.cfg to a separate folder) so a game reinstall does not require rebuilding your settings from scratch. If you use a gaming headset with audio software (Razer Synapse, SteelSeries GG, etc.), try disabling that software before launching BO2 — audio middleware conflicts are a common but overlooked cause of BO2 crashes on modern systems.
Bottom Line
| Keybindings not saving | Run as administrator + set config_mp.cfg to Read-Only after editing |
| Unhandled exception fix | Install DirectX 9.0c + Visual C++ 2010/2012 redistributables |
| CMN_ROOT Polish bug | Steam → BO2 Properties → Language → set to English |
| Not launching Win 10/11 | Install DirectX 9.0c, VC++ redistributables, add antivirus exclusion |
| Min RAM | 2GB (4GB+ recommended) |
| Min GPU | NVIDIA 8800GT or equivalent (any modern GPU far exceeds this) |
| Best launch options | +set r_multiGpu 0 +set r_blur 0 +set r_depthPrepass 0 |
| Disable Steam overlay | Reduces crashes with BO2’s older DirectX rendering |
Frequently Asked Questions
How do I save my keybindings in Black Ops 2 on Steam?
To save keybindings in Black Ops 2 Steam: run the game as administrator (right-click → Properties → Compatibility → Run as administrator), set your keybindings in-game, then exit. For a permanent fix, navigate to Steam\steamapps\common\Call of Duty Black Ops II\players\, open config_mp.cfg in Notepad, manually add your bind lines (e.g., bind MOUSE3 ‘+melee’), save the file, and set it to Read-Only so the game cannot overwrite it.
What are the Black Ops 2 PC system requirements?
Black Ops 2 minimum PC requirements: Intel Core 2 Duo E8200 2.66 GHz, 2GB RAM, NVIDIA GeForce 8800GT 512MB, DirectX 9.0c, 16GB storage. Recommended: Intel Core i5-2500K, 8GB RAM, NVIDIA GTX 670 2GB, DirectX 11. In 2026, any modern PC significantly exceeds these specs — performance issues are almost always software compatibility problems, not hardware limitations.
How do I fix Black Ops 2 multiplayer unhandled exception caught?
To fix the Black Ops 2 unhandled exception caught error: install the DirectX End-User Runtime Web Installer (Microsoft), install Visual C++ 2010 and 2012 Redistributables (both x86 and x64), disable your antivirus temporarily to test, run the game in Windows 7 compatibility mode, and disable the Steam overlay (Steam → BO2 Properties → General → uncheck Enable Steam Overlay).
What is the CMN_ROOT Polish bug in Black Ops 2?
The CMN_ROOT Polish bug is a language/localization error in Black Ops 2 PC that causes crashes or text errors, typically from mismatched or corrupted Polish language files. Fix: in Steam, right-click Black Ops 2 → Properties → Language → set to English (United States). Steam will download correct English language files. If still present, verify game files to replace corrupted files.
What are good launch options for Black Ops 2 on Steam?
Best Steam launch options for Black Ops 2: +set r_multiGpu 0 +set r_blur 0 +set r_depthPrepass 0. These disable multi-GPU rendering (buggy in BO2), motion blur, and a depth pre-pass that adds overhead. Combined with running as administrator and disabling the Steam overlay, these options typically improve FPS by 20-40% on modern hardware.
