Combat Arms installation guide

This guide covers the official Combat Arms Classic client and launcher, from account creation to the first game. Updated 15 November 2026. Nexus access and future Nexus builds may have different requirements.
Requirements
The hardware baseline comes from our download page. The storage budget below accounts for the complete installation and updates.
| Component | Minimum | Recommended |
|---|---|---|
| System | Windows 10, 64-bit | Windows 11, 64-bit, updated |
| Processor | Dual-core, 2.0 GHz | Quad-core, 3.0 GHz |
| Memory | 4 GB RAM | 8 GB RAM |
| Graphics | DirectX 9.0c compatible, 512 MB; published examples: Intel HD 4000, GeForce 8800, Radeon HD 3850 | 1 GB or more; GeForce GTX 660, Radeon RX 460 or newer |
| Storage | Reserve 50 GB free for setup and updates; recommended working space | SSD, with extra room for updates and backups |
| Connection | Broadband internet for download, updates and play | Ethernet or stable 5 GHz Wi-Fi |
The hardware figures describe Classic and do not guarantee a particular frame rate. The complete client exceeds 10 GB before personal files and retained backups. The 50 GB figure is a planning budget, not a measured or enforced minimum: setup, update downloads and a previous installation can coexist. Leave extra room for existing backups and personal files, and keep space on the Windows temporary-files drive too.
You need a website account, a verified email address and a created character. On Windows, installation and uninstallation always require administrator rights. The launcher runs as administrator; the game and updates use the same permissions. Approve UAC when prompted. Your Windows account must be able to write to the installation folder. The modern setup supplies the .NET runtime and installs Microsoft Edge WebView2 if needed. You do not need the .NET SDK.
Windows 7 and 8.1
Package compatibility and Microsoft support are separate: check the current Windows/runtime support list for your edition. This matters for Windows 10 too.
The account download selector also lists Windows 7 SP1 / 8.1, 64-bit. Use only the dedicated legacy package when it is available; the Windows 10/11 installer cannot be made compatible by changing a compatibility setting. Older Windows versions and their legacy runtimes no longer receive normal Microsoft support. Prefer a supported Windows 11 PC. Legacy availability does not establish compatibility with every computer, Nexus or a future update. Windows XP, Vista, 8.0 and 32-bit Windows are outside this installation path. Windows on ARM has not been qualified by this guide.
Before downloading
- Open combatarms.world. Register if necessary, verify the email and finish character creation. Check spam if the verification message does not arrive.
- Sign in and open Account, then the download control. Choose the package for your Windows version. The Downloads page also leads to your account.
- Use your own personal link. Do not share it or use attachments, mirrors or links sent by strangers. A familiar filename does not prove that a file is authentic.
- Update Windows and your antivirus, finish any pending restart, check the system date and time, and close the game and launcher before installing.
If downloading is disabled, check email verification, character creation and server status. An expired or revoked personal link requires staff help; requesting the same email again does not necessarily renew it. A 419 page means the website session expired: reload, sign in again and retry from the account. For 429, wait before retrying.
Download and check the setup
- Save the complete setup to a local folder. Use
CombatArmsClassic-Windows10-11-x64.exefor Windows 10/11, orCombatArmsClassic-Windows7-8.1-x64.exefor Windows 7 SP1/8.1. Wait for the browser to finish. Do not open a partial.crdownloador.partfile. - If interrupted, use the browser's resume control. If that fails, return to your account and retry. Avoid several simultaneous downloads of the same personal link.
- Scan the completed file with your updated antivirus. With Microsoft Defender, use Windows Security → Virus & threat protection → Scan options → Custom scan and select the download folder. Windows 11 may also offer Scan with Microsoft Defender under Show more options in the file's context menu. See Microsoft's scan instructions.
- If staff provide a SHA-256 for that exact release, compare it with your file. A hash from an old news article does not validate today's installer. A matching hash verifies the copy against that reference; it is not antivirus certification.
Understand Windows security messages
SmartScreen: unrecognized app
For the ordinary blue unrecognized-app warning, verify the official source and scan the file. If you trust it, check the displayed details before choosing More info → Run anyway, when offered. If unavailable, or a threat/policy is named, stop. Keep SmartScreen enabled. Unknown publisher does not establish safety. See Microsoft's explanation.
Defender or another antivirus detects a threat
- Stop the installation or game. Leave the detected file quarantined.
- Open Windows Security → Protection history, or your antivirus's detection history. Record the exact threat name, affected filename, time and action. Reviewing threat details may require an administrator. See Microsoft's protection-history instructions.
- Update the antivirus and contact support with those details. Staff must check the exact release and, where appropriate, request a vendor review. A possible false positive is not a confirmed false positive.
Do not disable real-time protection, cloud protection or tamper protection, restore a detected file to force play, or exclude the game folder, Downloads, a drive or all EXE/DLL files. The same rule applies to Avast, AVG, Bitdefender, Kaspersky, Norton and other antivirus products; menus vary by version. A clean historical scan applies only to the scanned file and definitions.
Smart App Control, App Control or a blocked driver
0xC0E90002 means Windows Application Control blocked a file. A message naming CShell.dll does not, by itself, mean that the DLL is missing or damaged. Reinstalling or repairing cannot change the Windows policy. Do not switch off Smart App Control, Memory integrity, Secure Boot or the vulnerable-driver blocklist to run the game.
Send the exact message and Windows build to support. On a managed PC, ask its administrator. If requested, inspect Event Viewer → Applications and Services Logs → Microsoft → Windows → CodeIntegrity → Operational and provide only the relevant event details, such as 3077, 3033 and associated 3089 events. Review paths and personal information before sharing. Staff may need to correct the package or its signing. See Microsoft's event reference.
Install on Windows
- Close every running game and launcher instance. Open the verified full setup.
- Follow the installer. The recommended folder is
%LOCALAPPDATA%\Programs\CombatArmsClassic; choose another local drive if needed. Keep the folder writable by your Windows account and run the setup and launcher as administrator. Avoid protected system folders, network shares and folders synchronized by OneDrive. - Allow the setup to extract the client and check its files. WebView2 needs an internet connection if it is missing. Approve a Microsoft prerequisite only after checking its displayed publisher. Do not install DLLs from download sites.
- Wait for completion before opening the game. If installation fails, read the message and preserve
setup-verification.login the installation folder. Correct the reported cause before retrying. - Open Combat Arms Classic from Start or its installed shortcut. Keep the complete Client and Launcher folders together; copying only the launcher EXE is insufficient.
First start and updates
- Sign in with the same account used on the website. If you forgot the password, use the official password reset.
- Wait for launcher and game downloads, installation and verification to finish. Do not start a second instance or overwrite files during an update.
- Choose the available language and start in windowed mode if you have display problems. Press Game Start and choose Classic. Nexus may be restricted or unavailable; its presence in the selector does not grant access.
- Always launch through Combat Arms Classic. Opening
Client\Engine.exeor other internal executables directly is unsupported and can be rejected.
Use the launcher's file verification/repair control if the catalog reports missing or changed managed files. It checks the files listed in the current catalog; it does not repair Windows policies, all system components or every personal file. Keep the launcher open while playing.
Common problems
- Windows S mode or “This app can’t run on your PC”: check your Windows version and the x64 package. S mode accepts Store apps; our EXE cannot install in that mode. On a managed device, ask its administrator or use an approved compatible PC. See Microsoft’s S mode explanation.
- The browser blocks the download: record its exact reason. A network failure is different from a virus detection or a device policy. For a named threat, stop and follow the antivirus section. Do not turn off browser protection or switch to an unofficial mirror.
- Download is HTML, empty or incomplete: return to your account instead of renaming the file to EXE. Check connection, space and link status.
- Extraction, CRC or hash failure: do not use the damaged package. Check space, download again from the official account and report repeated failures.
- Access denied, file in use or installation folder unavailable: close the game and launcher; restart Windows if they remain locked. Use the default writable folder. Check protection history for a blocked write. Do not take ownership of system folders or disable ransomware protection.
- WebView2 error or blank launcher: finish Windows updates and restart, then rerun the official setup online. If needed, obtain WebView2 only from Microsoft. Send the exact error if it continues.
- Missing VCRUNTIME/MSVCP or DirectX DLL: record the complete filename. Use the official Microsoft Visual C++ runtime appropriate to that component; a 32-bit game can require an x86 runtime on 64-bit Windows. For legacy DirectX components use Microsoft's DirectX June 2010 runtime when the error calls for it. Do not replace individual DLLs or install every runtime at random.
- Bad Image, 0xc000007b or another startup code: send the exact code and module name. Causes differ; do not assume every DLL error has the same fix. For
0xC0E90002, follow the policy-block section. - UPDATE NOT COMPLETED, repeated update or missing file: close the game, reopen the launcher and retry once. Use verification/repair. If the launcher cannot recover, read the historical recovery notice and ask support which package applies to your current version. Do not downgrade. A launcher-only package is not the full game.
- Server unavailable, timeout or login fails: check server status, account verification, password and Windows clock. Try a stable connection. Report whether the failure affects the website, updater or game. Never disable certificate checks.
- Firewall prompt: check the executable path and official installation before allowing only the app on the network you use. On managed devices consult the administrator. Keep the firewall on; do not open all ports or configure a router DMZ.
- Black screen, crash, low FPS or mouse problems: try windowed mode and a lower resolution, update graphics drivers from the manufacturer, and close optional overlays. Preserve the crash message and log if it repeats.
- CAPro / HWShield blocks launch: read the named program, driver or altered file. Close the conflicting tool normally, restart if requested and verify official game files. Do not rename tools, inject DLLs or bypass the anti-cheat. Report suspected mistakes to staff.
Mac and Chromebook
These are beta compatibility paths using the Windows client through Wine or CrossOver, rather than native game builds. Follow the platform tab on Downloads for the current scripts and checksums.
- Mac: published baseline macOS 13+, Apple silicon M1 or an Intel Mac with Metal graphics, 8 GB RAM and a 50 GB installation/update budget. The page lists Wine 9+ or CrossOver 25+; CrossOver is paid with a vendor trial. On Apple silicon Rosetta 2 may be needed. Install the compatibility layer, download your personal Windows 10/11 setup, review the official macOS script, run it as instructed on Downloads, then open the created Combat Arms Classic app and let the launcher update.
- Chromebook: published baseline ChromeOS 120+, Intel Core i3 8th generation / AMD Ryzen 3 or newer, x86-64, 4 GB RAM, Linux environment with a 50 GB installation/update budget and working GPU acceleration. ARM Chromebooks are excluded. Enable Linux if the device permits it, share the setup's Downloads folder with Linux, review and run the official ChromeOS script, then open the Linux app shortcut. A school or workplace administrator may prohibit Linux.
Use only scripts linked by the official site; read them before running them. Do not disable Gatekeeper, device management or system security to force installation. If the launcher opens its interface in a browser, keep its small host window open. ChromeOS website links may not open the Linux game; use its app shortcut. Report compatibility issues with device model, OS, compatibility-layer version and the last relevant error lines. Beta availability does not guarantee every game feature or hardware combination.
Repair, reinstall and uninstall
Try launcher repair before a complete reinstall unless support identifies a different cause. Back up personal screenshots, recordings and profiles before removing the installation. Close the game and launcher. On Windows use Settings → Apps → Installed apps → Combat Arms Classic → Uninstall and approve the administrator request. Then install a fresh official full package if needed. Reinstalling does not remove an account or resolve a security-policy block. For Mac/ChromeOS, use the platform-specific removal instructions on Downloads and preserve personal files first.
Ask for help
Open a support ticket, use the official Discord, or email [email protected]. Include OS edition/build and architecture, setup filename, launcher version if visible, exact error, time and timezone, step that failed, and a cropped screenshot. Add only relevant lines from setup-verification.log or %LOCALAPPDATA%\Nepix\Launcher logs after reviewing them. Never publish your password, personal download URL, session token or full unreviewed logs.
Related notices
- Windows setup warnings and signing — 3 November. Its scan, hash and signing update describe that dated release.
- Launcher recovery without reinstalling the client — 2 November.
- Languages, HWShield, controls and mouse fixes — 9 November.
- Arena and launcher update — 9 November.