Introduction

RabbitMQ on Windows depends on Erlang being installed in a location that RabbitMQ can actually find. When the installer or service startup complains about ERLANG_HOME, the issue is usually one of a few concrete problems: the variable points to the wrong directory, the PATH still references an older Erlang version, the architecture does not match, or the service is running with stale environment data.

Understand what ERLANG_HOME should contain

ERLANG_HOME should point to the root folder of the Erlang installation, not to the bin directory and not to a shortcut.

A typical value looks like this:

$env:ERLANG_HOME = "C:\Program Files\Erlang OTP"

The exact folder name depends on how Erlang was installed, but the key point is that RabbitMQ expects the installation root. If the variable points at the wrong place, RabbitMQ may install but fail to start.

Verify Erlang before touching RabbitMQ

Before reinstalling anything, confirm that Erlang itself is usable from a fresh shell:

where.exe erl
echo $env:ERLANG_HOME

If where.exe erl cannot find erl.exe, then the PATH or installation is incomplete. If ERLANG_HOME is empty or wrong, fix that first.

Also verify architecture. A 64-bit RabbitMQ installation should be paired with a 64-bit Erlang installation. Mixed 32-bit and 64-bit setups on Windows are a common source of confusing errors.

Set the environment variable correctly

The safest fix is to set the variable at the user or machine level and then open a brand-new shell.

For the current user:

1[Environment]::SetEnvironmentVariable(
2    "ERLANG_HOME",
3    "C:\Program Files\Erlang OTP",
4    "User"
5)

You may also need Erlang's bin directory on PATH:

1$erlangBin = "C:\Program Files\Erlang OTP\bin"
2$currentPath = [Environment]::GetEnvironmentVariable("Path", "User")
3[Environment]::SetEnvironmentVariable(
4    "Path",
5    "$currentPath;$erlangBin",
6    "User"
7)

Then close the terminal and open a new one. Existing shells do not automatically pick up environment-variable changes.

Check the RabbitMQ service after the fix

If RabbitMQ is already installed as a Windows service, remember that the service may still be running with the old environment.

After correcting Erlang:

rabbitmq-diagnostics status

If needed, restart the service:

Stop-Service RabbitMQ
Start-Service RabbitMQ

If the original installation was performed while ERLANG_HOME was broken, uninstalling RabbitMQ, fixing Erlang, and then reinstalling RabbitMQ is sometimes faster than trying to repair a half-broken service registration.

Watch for stale versions and compatibility mismatches

Not every ERLANG_HOME-looking error is literally caused by the variable alone. Similar symptoms come from:

• an old ERLANG_HOME that points to an uninstalled Erlang version
• PATH entries that still find the wrong erl.exe
• a RabbitMQ version that does not support the installed Erlang release
• commands run from a shell opened before the environment changed

That is why checking both the variable and the executable resolution matters. One tells you what the environment claims. The other tells you what Windows will actually launch.

A practical troubleshooting order

The clean order is:

1. confirm Erlang is installed
2. confirm ERLANG_HOME points to the installation root
3. confirm PATH resolves the intended erl.exe
4. confirm 64-bit RabbitMQ matches 64-bit Erlang
5. restart or reinstall RabbitMQ after the environment is fixed

Following that order prevents random reinstall loops that never address the actual problem.

Common Pitfalls

The most common mistake is setting ERLANG_HOME to the bin subdirectory instead of the Erlang installation root.

Another common issue is updating the variable but continuing to use an old terminal session or already-running Windows service.

People also overlook stale PATH entries. ERLANG_HOME may point to the new version while where.exe erl still resolves an older one.

Finally, do not ignore version compatibility. A correct path cannot fix a RabbitMQ release that does not support the installed Erlang runtime.

Summary

• 'ERLANG_HOME should point to the Erlang installation root, not to bin.'
• Verify both the variable and erl.exe resolution from a fresh shell.
• Match 64-bit RabbitMQ with 64-bit Erlang on Windows x64.
• Restart or reinstall the RabbitMQ service after fixing the environment.
• Check PATH and version compatibility before assuming the installer itself is broken.