aaroncheatsAaron Cheats / Support guide
FC27 PXILOK.
Setup & error fixes.
Check your Windows settings, apply the changes properly and work through the exact error you see. One step at a time.
Guided help / FC27 PXILOK
What does your error say?
Choose the closest match. We will show a few actions at a time, with the full explanation one click away.
Your answers can be added to the editable support message below. Nothing is sent automatically.
Progress is saved in this browser. Your answers are reminders, not a live check of your PC.
For FC27 PXILOK on Windows PC. The reports behind this guide include successful Windows 11 25H2 setups. These are support-case results, not a guarantee for every PC or Windows build.
Start here
Yes, Windows 11 25H2 can work.
Users in our support cases got PXILOK working on 25H2 after correcting their settings. Start with the checklist below.
Correct settings but still getting errors? Background software can also interfere. Check Armoury Crate, MSI Afterburner, RivaTuner and other utilities in step 06.
This guide is for FC27 PXILOK. Using Premium? Follow the Premium tutorial.
These steps include settings from successful support cases. Disabling Windows protections reduces your PC's security; restore them when you no longer need this setup.
Your setup checklist.
Tick each item after checking it on your PC. Saved ticks are reminders, not a live system check. Recheck the settings after rebooting.
Check Windows and your loader
Press Win + R, enter winver and note your version and OS build. Keep this for support if needed. There are successful 25H2 cases in the reports behind this guide.
Use the current PXILOK download from your order delivery or the link provided by Aaron Cheats support. Keep your activation key ready and follow the included extraction and activation instructions.
Keep the game closed while preparing Windows.
Virtualization on. Secure Boot on.
The successful setup reported in support used CPU virtualization enabled, UEFI and Secure Boot enabled. One user had virtualization off throughout troubleshooting; enabling it was part of the final working setup.
- Open Task Manager > Performance > CPU. Check that Virtualization says Enabled.
- Press Win + R, enter
msinfo32and look for BIOS Mode: UEFI and Secure Boot State: On. - If needed, enter your PC's BIOS/UEFI settings. CPU virtualization may be called Intel Virtualization Technology / VT-x or SVM Mode / AMD-V. Enable it, enable Secure Boot on an existing UEFI setup, then save and exit.
BIOS menus depend on your motherboard. Have your BitLocker recovery key available before firmware changes if device encryption is enabled. If BIOS Mode says Legacy or Secure Boot is unsupported, ask support before changing the boot mode.
CPU virtualization and Memory integrity are separate settings. Keep CPU virtualization enabled while switching Memory integrity off in the next step.
Turn Memory integrity off
Windows Security > Device security > Core isolation details
Set Memory integrity to Off. This is the Windows feature also called HVCI. Apply the change with the full shutdown in step 07.
Check it again after changing BIOS settings and rebooting. In one resolved case, the user found Memory integrity enabled again. Turning it off was part of the final fix.
Check the vulnerable driver blocklist
Windows Security > Device security > Core isolation details
The reported working setup had Microsoft Vulnerable Driver Blocklist set to Off. Change the toggle, then apply it with the shutdown step below.
If it is missing, greyed out or remains enabled, send support a screenshot. Memory integrity, Smart App Control or Windows S mode can enforce the blocklist. A registry value alone does not establish the current running state.
Defender and the loader exclusion
Windows Security > Virus & threat protection > Manage settings
- The working setup reported Real-time protection: Off during setup. This setting can turn itself back on, so recheck it if the loader is blocked.
- Under Exclusions, open Add or remove exclusions > Add an exclusion > File. Select the specific PXILOK loader .exe from your verified order download.
- If you see error 225 or a file disappears, open Protection history to find the detection and affected file. Check any third-party antivirus as well. Send an unexpected detection to support before allowing the file.
Use a File exclusion for that executable. Choosing File type and entering .exe would exclude every executable of that type. An exclusion does not restore a file that has already been removed.
Check background software, too
Windows settings are only part of the setup. Monitoring, tuning, RGB and overlay tools are worth checking when PXILOK still fails. Some run background services or drivers, so closing the main window may leave part of the software running.
- ASUS Armoury Crate: removing it resolved the problem for one user in the shared support cases.
- MSI Afterburner and RivaTuner Statistics Server (RTSS): exit both when testing. RTSS is a separate app used for the in-game monitoring overlay and can remain running after you close Afterburner.
- Other monitoring, tuning or RGB utilities: for example MSI Center, ASUS AI Suite, Gigabyte Control Center and Corsair iCUE.
- Other overlays and capture tools: check in-game overlays from Discord, Steam, NVIDIA App or AMD Software, plus FPS counters and game-capture hooks.
- Other anti-cheats: the user who supplied the working settings also reported uninstalling anti-cheat software from other games.
Armoury Crate is a reported fix. The other apps are possible conflicts to test, not confirmed PXILOK incompatibilities on every PC.
Find which app is interfering
- Exit optional utilities completely using their system-tray menu, and temporarily turn their overlays off. For Afterburner, check RTSS separately. Verify in Task Manager that the apps have exited.
- Temporarily disable those utilities in Task Manager > Startup apps, then complete the full shutdown in step 07. Check that they have not restarted before trying PXILOK again.
- If PXILOK now works, re-enable one app at a time and retry. Note the app and version that brings the error back. Restore the other apps once you have isolated the conflict.
- If a suspected app still loads a service or driver, closing its window may not be enough. Use its official uninstaller, reboot and test again. For Armoury Crate, use the ASUS uninstall tool. Keep hardware cooling controls in mind when removing tuning utilities.
- If the cause is still unclear, follow Microsoft's clean-boot troubleshooting guide. Hide Microsoft services before changing third-party services, record what you disable and restore normal startup afterwards. A game or loader may need its own services enabled to run.
For an anti-cheat conflict, use that product's uninstaller and reboot. Keep FC27's required game components installed and leave driver-file removal to the official uninstaller.
Check DMA separately
DMA protection: the user who supplied the working settings also reported DMA off. Open msinfo32 and check Kernel DMA Protection. If it is On and setup still fails, give support your motherboard model for the correct firmware setting. This is a reported setting, not a confirmed requirement for every PC.
DMA protection is separate from CPU virtualization. I/O settings such as VT-d / IOMMU vary by hardware; do not turn off the VT-x / SVM setting from step 02 to try to change DMA.
MSI: Afterburner and RTSS run separately ↗
Microsoft: checking Kernel DMA Protection ↗
Apply the changes with a full shutdown
Save your work and close your apps first. Press Win + R, enter the command below and press Enter. It shuts your PC down immediately.
shutdown /s /t 0Wait until the PC is off, then turn it on using the power button. Reopen Core isolation and check Memory integrity and the blocklist again before retrying PXILOK.
A normal Windows Shut down can use Fast Startup and preserve the kernel session. The command above requests a full shutdown. Windows Restart also performs a full boot cycle. Unplugging the PC is not needed for this step.
Recheck, then run PXILOK
Verify the checklist against your current settings after startup. Open the current PXILOK loader and follow the activation and launch instructions included with your order.
If it reports Setup incomplete, keep the exact line immediately above that message. Choose the matching error below before retrying. That line tells us which part failed.
Find your error
What does the loader say?
HVCI (Memory Integrity) is STILL ACTIVE in kernel!
HVCI (Memory Integrity) is STILL ACTIVE in kernel!
Registry values are set but kernel hasn't applied them yet.
[!] Setup incomplete.The loader reports that HVCI is still running, even if a saved setting says otherwise.
- Open Core isolation and verify Memory integrity is Off.
- Complete step 07: full shutdown, then power on again.
- Check Memory integrity again. One user found it enabled again after changing their setup.
- If the error persists, send support the message and a fresh Core isolation screenshot.
CreateProcess failed with error: 225
[~] Preparing...
CreateProcess failed with error: 225
[!] Setup incomplete.Windows error 225 means the operation was blocked because the file was detected as a virus or potentially unwanted software. The code alone does not tell you whether that detection is a false positive.
- Check Windows Security > Virus & threat protection > Protection history for the affected file and detection name.
- Confirm you are using the current order download and review the Defender and exclusion steps. Check any other installed antivirus.
- If a component has been removed, ask support to verify the detection and supply the current download. Send the full error if it remains blocked.
Driver mapping failed / Driver load failed
[~] Preparing...
Driver mapping failed.
[!] Setup incomplete.The driver failed to load or map. This message does not identify one specific cause.
- Recheck virtualization On, Secure Boot On / UEFI, Memory integrity Off and the blocklist Off.
- Apply pending changes with a full shutdown and verify the settings again.
- Test background software such as Armoury Crate, MSI Afterburner, RTSS and other anti-cheats. Correct Windows settings do not rule out an app conflict.
- Look for a Code Integrity event at the same time as the failure and include it in your support ticket.
Game crashes during injection / all settings are correct, but PXILOK still fails
If FC27 runs without PXILOK but crashes during injection, check Reputation-based protection in step 05: turn all options on that page Off, then retry. This resolved one support case after the other checklist items had been completed.
If it still fails, check background software next. One user's problem was resolved by removing Armoury Crate. MSI Afterburner, RTSS, other hardware utilities and overlays are also candidates to test.
Follow step 06: fully exit optional apps, disable their startup entries, reboot and retry. If that works, restore apps one at a time to find the conflict. If a service or driver remains loaded, use the suspected app's official uninstaller or Microsoft's clean-boot workflow. Include the apps you tested and the result in your support message.
Authenticode signing level / Code Integrity policy error
Code Integrity determined that a process (System)
attempted to load a file that did not meet the
Authenticode signing level requirements
or violated code integrity policy.Windows reports that the driver did not meet a signing or Code Integrity policy requirement. The message alone does not identify which setting or policy caused the block.
Open Event Viewer and go to:
Applications and Services Logs > Microsoft > Windows > CodeIntegrity > Operational
Copy the event at the time of the failure, including its event ID, timestamp, file path and Policy ID. Add your Windows version/build and loader version to the ticket. Mask your personal Windows username in the path if sharing a screenshot.
Work through the checklist first. If the same policy error remains, send the event to support so the loader and driver can be checked.
Does PXILOK work on Windows 11 25H2?
Yes, users in the shared support cases got it working on 25H2. One resolved their setup after enabling virtualization and Secure Boot, then finding and disabling Memory integrity again. Another reported success after shutting down and starting again. Follow the settings and error checks above; 25H2 alone is not a reason to reinstall or downgrade Windows.
I only see “Setup incomplete”
That is the final status, not the cause. Copy the entire output, especially the line immediately above it. Match that line to an error above, or include the full text in your support ticket.
Still stuck? Send the useful details.
Fill in what you know and paste it into a private Discord support ticket. Include a screenshot of the full loader error.
Keep activation keys, passwords and remote-access codes out of screenshots and public messages.