Neo4j not able to locate PowerShell error

[alcoulon]

Hello,
I have PowerShell installed and updated on my machine. I also went and manually updated the environment variables path and still have had no luck. Are there any other things I could be trying?

Thanks,
Adam

[codemaze]

Hello,

I'm having the same issue that Neo4j Desktop 1.5.6 cannot find PowerShell after the last update (Version: 5.1.22621.608). I already looked into the environment variables, but it's still not working...

[bart]

Ok dudes.. Here is your fix. Just worked this bug today. So it is an easy fix. see below.

Stack Overflow Question

Title

Neo4j Desktop says “PowerShell is incompatible” on Windows even though PowerShell works fine

---

Body

I’m running into an issue with Neo4j Desktop on Windows 10 after a system restart/update.

Neo4j Desktop starts, but when I try to run a DBMS it fails with:

PowerShell is incompatible. Enabling alternative Neo4j starter.

From the logs:

PowerShell compatibility check
PowerShell is incompatible. Enabling alternative Neo4j starter.

---

Environment

• Windows 10 (build 10.0.26200)

• Neo4j Desktop 1.6.3

• AMD Ryzen system

• Conda / Anaconda installed

• Custom dev environment (Node, Ollama, etc.)

---

What I verified

PowerShell itself works fine:

powershell -NoProfile -NonInteractive -Command "Write-Output CLEAN"

Output:

CLEAN

Execution policy:

CurrentUser    RemoteSigned

So it doesn’t seem like a PowerShell or policy issue.

---

Additional odd behavior

From CMD:

where powershell

returns:

'where' is not recognized as an internal or external command

But manually:

C:\Windows\System32\where.exe

works.

---

PATH (before fix)

C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe;
C:\ProgramData\anaconda3\condabin;
C:\Windows\System32\wbem;
...

---

Question

Why does Neo4j Desktop think PowerShell is incompatible when it clearly works from the terminal?

---

Stack Overflow Answer (Accepted)

This issue is not actually a Neo4j bug—it’s caused by a corrupted Windows PATH environment variable.

---

Root Cause

The PATH variable contained an invalid entry:

C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe

PATH must contain directories, not executable files.

Because of this:

• Windows command resolution breaks (where fails)

• Subprocesses (like those launched by Neo4j Desktop / Electron) cannot reliably locate system tools

• Neo4j fails its internal PowerShell compatibility check and reports:

PowerShell is incompatible

---

Why Neo4j fails even though PowerShell “works”

Running PowerShell manually works because:

• Your interactive shell already has context

• It may resolve binaries differently

But Neo4j Desktop:

• Spawns PowerShell as a subprocess

• Requires a clean, predictable environment

• Relies on correct PATH resolution

---

Fix

1. Correct PATH entries

Ensure PATH contains directories only, especially:

C:\Windows\System32
C:\Windows
C:\Windows\System32\WindowsPowerShell\v1.0\
C:\Windows\System32\wbem

---

2. Remove invalid entries

Remove:

C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe

---

3. Clean duplicates / bad entries

Also remove:

• duplicate paths

• broken tool entries

• leftover entries from Conda or PowerShell 7 uninstall

---

4. Reboot system

This is required—environment variables are cached by processes like Neo4j Desktop.

---

Verification

After fixing PATH:

where powershell

should return:

C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe

---

Then Neo4j Desktop should start DBMS normally without the error.

---

Bonus: Related Issue

In this case, there was also a Conda registry hook:

HKCU\Software\Microsoft\Command Processor\AutoRun

which injected environment changes globally. Removing that prevented further shell pollution.

---

Summary

This issue happens when:

• PATH is malformed (especially with .exe entries)

• System32 is missing or deprioritized

• Shell environments (Conda, PowerShell 7, etc.) modify global behavior

Fixing PATH restores normal subprocess behavior and resolves the Neo4j error.