stablyai/orca · error · Error

${result.detail} No PATH changes were made.

Error message

${result.detail} No PATH changes were made.

What it means

Thrown by readWindowsUserPathForMutation when the userPathMutationReader fails to read the Windows user PATH registry value. The error message includes result.detail from the reader. This is a fail-safe: PATH is read-modify-write, so continuing after a failed read could clobber the user's PATH with a partial value.

Source

Thrown at src/main/cli/cli-installer.ts:875

      (entry) =>
        !samePathEntry('win32', entry, pathDirectory, this.windowsEnvironment, current.expandable)
    )
    if (nextEntries.length === entries.length) {
      return
    }
    await this.writeWindowsUserPathEntry(nextEntries.join(';'), pathDirectory, 'remove')
  }

  private async readWindowsUserPathForMutation(): Promise<{
    value: string | null
    expandable: boolean
  }> {
    const result = await this.userPathMutationReader()
    if (result.state === 'success') {
      return { value: result.value, expandable: result.expandable }
    }
    // Why: PATH is read-modify-write; continuing after a failed read could clobber the user's PATH with a partial value.
    throw new Error(`${result.detail} No PATH changes were made.`)
  }

  // Why: raw PowerShell errors reach the UI, so translate denied PATH writes (keeping the original as cause).
  private async writeWindowsUserPathEntry(
    value: string,
    pathDirectory: string,
    action: 'add' | 'remove'
  ): Promise<void> {
    try {
      await this.userPathWriter(value)
      this.userPathCacheInvalidator()
    } catch (error) {
      if (!isWindowsUserPathPermissionError(error)) {
        throw error
      }
      const guidance =
        action === 'add'
          ? `Add this folder to your PATH manually: ${pathDirectory}. Or run Orca as an administrator and try again.`

View on GitHub (pinned to 1136503c6a)

Solutions

1. Check result.detail in the error message for the specific read failure.
2. Manually verify the PATH key: open 'reg query HKCU\Environment /v Path' in a terminal.
3. If PowerShell is blocked, check execution policy: 'Get-ExecutionPolicy -List'.
4. Temporarily disable antivirus interference or add an exclusion for Orca's PowerShell usage.

try {
  await installer.ensureWindowsPathEntry(dir)
} catch (error) {
  if (error instanceof Error && error.message.includes('No PATH changes were made')) {
    // PATH read failed; do not attempt writes; show manual instructions
    showManualPathGuidance(dir)
  } else { throw error }
}

When it happens

Trigger: The PowerShell or registry read of HKCU\Environment PATH returns an error state (not 'success'). This happens when the registry key is inaccessible, PowerShell fails to execute, or the PATH value is unreadable.

Common situations: Group Policy restricts registry access to HKCU\Environment. PowerShell execution policy blocks the read script. Antivirus interferes with PowerShell child process spawning. Corrupted PATH registry value.

Related errors

• Windows blocked updating your user PATH (access denied). Thi
• ${result.stderr || 'PowerShell process enumeration failed'}
• PowerShell did not return signature JSON.
• PowerShell returned malformed signature JSON: ${error.messag
• PowerShell wrote to stderr while checking signature:\n${resu

AI-assisted analysis of stablyai/orca@1136503c6a (2026-08-12). Data as JSON: /api/errors/ba1331c56dea125e. Report an issue: GitHub.