XMRig on Windows 10 and Windows 11

What changes when you run XMRig on a Windows desktop: compatibility, where files belong, the permission prompts, the settings that matter, and the failures Windows users hit most often.

Compatibility

XMRig runs as a normal 64-bit Windows application. Windows 10 (1809 and later) and Windows 11 both work with the same archive, and the corresponding Server editions behave identically. There is no separate Windows 11 build — if a site offers one, it is not the project's.

Windows 11

Windows 11 adds nothing that blocks the miner, but two of its defaults get in the way. Memory integrity (core isolation) can prevent the WinRing0 driver used for MSR tuning from loading, which costs RandomX performance. Smart App Control, on clean installs, may refuse to start an unsigned executable until you allow it explicitly.

Windows 10

Windows 10 is the simpler host: older defaults, fewer prompts. Its power plan is more likely to throttle a long-running CPU load, so check that the plan is not set to a battery-saving profile on laptops and small-form-factor desktops.

x64 and hardware expectations

All useful Windows builds are x86-64. RandomX performance is bound by cache and memory bandwidth rather than clock speed: a CPU with 2 MB of L3 per thread will feed its threads properly, one with less will not, no matter how many threads you configure. Plan on roughly 2.5 GB of free RAM per mining thread if you want fast mode.

Installation, Windows style

There is nothing to install. Extract the archive to a stable path such as C:\Mining\xmrig, keep the executable and config.json together in that folder, and run the executable from a command prompt opened in the same directory. Because the miner is portable, moving that folder moves the whole setup, and deleting it removes everything.

Where the configuration lives

XMRig reads config.json from its own directory by default; nothing is written to the registry or to AppData. You can keep several files side by side — pool-a.json, test.json — and select one at launch. Full detail is on the configuration page.

Command-line basics on Windows

cd C:\Mining\xmrig
xmrig.exe                       rem uses config.json in this folder
xmrig.exe -c pool-a.json        rem alternative config file
xmrig.exe --help                rem full option list

Starting the miner by double-clicking works, but if it exits with an error the window closes before you can read it. Running it from a prompt keeps the message visible. Our command-line guide covers the options worth knowing.

Large pages and administrator rights

The biggest Windows-specific gain comes from large pages. XMRig can request the required privilege itself, which triggers a User Account Control prompt and, on some systems, a sign-out before the setting applies. Without it the miner still runs, just noticeably slower, and the log will say so. MSR tuning on Ryzen and recent Intel parts also needs administrator rights and loads a helper driver.

Problems Windows users report

  • The window flashes and disappears. A configuration error. Run it from a command prompt to read the message.
  • "MEMORY ALLOCATED" shows no large pages. Launch as administrator, or accept light mode's lower speed.
  • Antivirus removed the file. Expected for mining software; see the explanation before excluding anything.
  • The driver fails to load. Usually memory integrity in Windows 11 Security settings.
  • Speed drops after a few minutes. Thermal or power limits, not the miner. The performance guide explains how to tell them apart.
  • Connection failures. Pool host, port or TLS mismatch, or a firewall rule blocking the outbound connection.

Anything not listed here is likely covered in troubleshooting.

Windows questions

Does XMRig work on Windows 11?

Yes, with the standard 64-bit build. Memory integrity and Smart App Control may need attention for full performance.

Do I need administrator rights?

Only for large pages and MSR tuning. The miner runs without them at reduced speed.

Is there a 32-bit version?

Not in any practical sense; current releases target x86-64.