All articles
Setup Guides
8 min read
2026-10-03
Scoped Apex fight showing health, name, and distance on the target

Apex Cheat Setup: Secure Boot, TPM and the Order That Boots First Time

Every failed install is a firmware setting or a Windows setting. Do the checks in order, then follow the install and launch sequence exactly.

A failed install is almost always one of four things: virtualization off in firmware, Hyper-V missing, a Windows security setting switched off, or the launch order done backwards. None of them are the cheat.

Fifteen minutes of checks below beats an evening of guessing. Do them in order.

Step 1: Windows version and edition

Windows 10 or 11, 64-bit, current build. Cloud DMA provisions a Hyper-V environment, and Hyper-V is a proper feature on Pro, Enterprise and Education. On Home it is more work and the installer notes for your edition matter.

If your build is old and never updated, update first, then come back. EA Javelin also wants Windows 10 build 19041 or newer, so an ancient build fails twice over.

Step 2: Virtualization in firmware

Intel VT-x or AMD-V, enabled in BIOS or UEFI. This is the step people skip because it is not in Windows.

Reboot, enter firmware, find the virtualization entry, enable, save, reboot. It usually sits under CPU configuration or advanced features. Greyed out means Secure Boot state or an old firmware is blocking it.

Confirm it took. Task Manager, Performance, CPU, virtualization line should read enabled.

Step 3: The four security settings

These are requirements for the stack. Not suggestions, and the build will not behave correctly without them.

  • HVCI on, labelled Memory Integrity under Core Isolation
  • Core Isolation on
  • TPM on and visible to Windows
  • Secure Boot on

Worth clearing up a common confusion: EA states Secure Boot is not currently required for Apex under Javelin, though other Javelin titles like Battlefield 6 do require it. Our stack needs it because Cloud DMA does. Turn it on for the product, not for EA.

If Memory Integrity will not stay on, a driver is blocking it. Update or remove the driver. Leaving it off and pressing on is how you end up with a partial load later.

Step 4: Memory

8 GB is the floor, 16 GB is the sensible number. You are running Windows, a virtual environment and a heavy Source engine game on one machine. Close the browser.

Step 5: Kill the overlays

Discord overlay, GeForce overlay, the Steam overlay, anything with a capture hook. Off for the first launch. Add them back one at a time afterwards if you want them.

Step 6: Install in order

Cloud DMA first, as administrator, then the supporting pieces, then the game if it is not already installed.

Cloud DMA is its own purchase and it is not the whole stack. GREENWARD, Static Server and AWS are separate products, all required, and Static Server and AWS are not the same thing. Neither is bundled into the Cloud DMA checkout. Get all of it in place before the first run. Read what Cloud DMA is before you pay.

Let the installer provision. Let activation finish over the service link. Follow the installer notes for your Windows edition rather than clicking through prompts.

Step 7: Launch sequence

Reboot cleanly first so the environment starts fresh.

  • Boot and let the machine settle for a minute
  • Confirm the Cloud DMA layer is up
  • Launch Apex from Steam or the EA app
  • Reach the lobby or a match
  • Start the loader and wait for the menu

Loader before the game process is the number one cause of an empty menu.

Step 8: First run checks

Menu key is INSERT. If the menu appears, verify four things before configuring anything:

  • player ESP boxes on a dummy or in the firing range
  • toggles responding
  • a slider accepting a value
  • panic key hiding the menu

All four behaving means the stack is live. Menu up with nothing drawing is a partial load and the troubleshooting page covers that exact symptom.

Mistakes worth naming

Launching straight from the installer. Provisioning needs a clean reboot.

Leaving an old loader in the tray. Check before every launch.

Turning Memory Integrity off to fix something. It makes the next problem worse.

Installing with the game open. Close it.

Skipping firmware. If virtualization is off, reinstalling is pointless.

When to stop

If virtualization is on, all four settings are on, overlays are off and the menu still will not appear, open a ticket with your Windows edition and build, the virtualization state, the four settings, and what the installer showed at the end.

Setup is the boring part. Do it once properly and the rest is aim tuning. If it still fails, use the diagnostic order.

FAQ

Questions about this page

Answers for this page. The FAQ page holds the rest.