Why does XMRig say "no active backends was found"?

XMRig says “no active backends was found” when it has no working mining engine available to process its current job. Usually, CPU mining is disabled, the configuration provides no usable mining threads, or the CPU engine failed to start—so the lines just above this message are your best clue.

What “backend” means here

A backend is the part of XMRig that runs mining calculations on your hardware. XMRig can have separate backends for your CPU, your computer’s main processor, and supported graphics cards.

Monero uses RandomX, a mining algorithm—a set of calculation rules—that favors CPUs. For ordinary Monero mining, the CPU backend is the one you should check first.

This message does not, by itself, mean your wallet address is wrong or your mining pool is offline. A mining pool combines work from multiple miners. Connection failures normally produce separate messages about the server, login, or connection.

Check whether CPU mining is enabled

Open the configuration file XMRig actually loads, usually named config.json. Within its "cpu" section, look for:

"cpu": {
  "enabled": true
}

This is only a configuration fragment, not a complete file. If your existing CPU section has other settings, keep them while checking the "enabled" value.

Also check how you launch XMRig:

• Remove --no-cpu if it appears in your launch command or startup script.
• Check whether --config points to a different file than the one you edited.
• If you use a launcher or management panel, make sure it has not disabled CPU mining.

Restart XMRig after saving changes. Editing one configuration file while launching another can make a correct fix appear ineffective.

Look for missing threads or memory errors

A mining thread is one worker running calculations on your CPU. Custom thread settings can leave XMRig with no workers for RandomX, even when "enabled" is true.

If you recently changed thread profiles, compare your configuration with the sample supplied with your XMRig version. Back up your file, then try automatic CPU configuration rather than copying another computer’s thread settings.

Next, read the startup lines immediately before the error. Look for messages about memory allocation, RandomX initialization, or thread startup.

RandomX’s fast mode needs a dataset of about 2,080 MB, plus cache and other working memory. A dataset is a large collection of data used during mining. A low-memory computer, container, or restricted virtual machine may not have enough available memory.

Close unnecessary apps or review memory limits. RandomX also has a slower light mode, using a 256 MB cache, but it is generally a poor choice for earning rewards.

A huge-pages warning alone is usually not the cause. Huge pages are a memory feature that improves performance; XMRig can normally work without them.

Check the build and mining job

Use a trusted XMRig build intended for your operating system and processor. A custom build may have CPU support removed.

Also confirm that your pool settings request Monero’s RandomX algorithm, commonly identified as rx/0. A configuration copied from another coin may select an algorithm or hardware backend your setup cannot run.

Avoid “repair tools” offered by strangers. Never share wallet recovery words when asking for help.

The bottom line

Check CPU enablement, launch options, thread settings, and the preceding startup errors—in that order. This message is the final symptom; the earlier log lines usually explain why XMRig has no working mining engine.