#Im on windows and i cant start openclaw

1 messages Β· Page 1 of 1 (latest)

frail dust
#

PS C:\WINDOWS\system32> powershell -c "irm https://openclaw.ai/install.ps1 | iex"

OpenClaw Installer

[OK] Windows detected
[] Existing OpenClaw installation detected
[OK] Node.js v24.15.0 found
[] Installing OpenClaw (openclaw@latest)...
[OK] OpenClaw installed
[*] Running doctor to migrate settings...
[OK] Migration complete

OpenClaw installed successfully (OpenClaw 2026.5.12 (f066dd2))!

Upgraded! Peter fixed stuff. Blame him if it breaks.

Upgrade complete. Run openclaw doctor to check for additional migrations.
PS C:\WINDOWS\system32> openclaw
openclaw : File C:\Users\miles\AppData\Roaming\npm\openclaw.ps1 cannot be loaded because running scripts is disabled
on this system. For more information, see about_Execution_Policies at https:/go.microsoft.com/fwlink/?LinkID=135170.
At line:1 char:1

  • openclaw
  •   + CategoryInfo          : SecurityError: (:) [], PSSecurityException
  + FullyQualifiedErrorId : UnauthorizedAccess

PS C:\WINDOWS\system32>

digital frostBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> βœ… Mark Solution

south birchBOT
south birchBOT
frail dust
#

setup

Plan: bootstrap OpenClaw setup for workspace C:\WINDOWS\system32. Say yes to apply.
Model choice: none found yet. I will only set the workspace; install/login Codex or Claude Code, or set
OPENAI_API_KEY/ANTHROPIC_API_KEY, then run setup again.

Apply this operation: bootstrap OpenClaw setup for workspace C:\WINDOWS\system32?

yes

β ™ moseying… β€’ 0s | local ready
agent crestodian (Crestodian) | session main (Crestodian) | unknown | tokens ?
────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
[crestodian] queued: crestodian.setup
[crestodian] running: crestodian.setup
Updated C:\Users\miles.openclaw\openclaw.json
Workspace: C:\WINDOWS\system32
Default model: not configured yet
[crestodian] done: crestodian.setup
local ready | idle
agent crestodian (Crestodian) | session main (Crestodian) | unknown | tokens ?
────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────

───────

south birchBOT
# frail dust setup Plan: bootstrap OpenClaw setup for workspace C:\WINDOWS\system32. Say ye...

That completed, but it picked a bad workspace: C:\WINDOWS\system32. That folder is for Windows system files, not your OpenClaw agent memory/workspace.

I’d rerun setup with a normal user workspace and the full wizard so it can also configure model/auth:

$ws = Join-Path $env:USERPROFILE ".openclaw\workspace"
openclaw setup --wizard --workspace $ws
openclaw models status
openclaw doctor

If PowerShell blocks openclaw again, use openclaw.cmd in those commands.

The important part from your output is: Default model: not configured yet. Until you configure provider auth/model in the wizard, OpenClaw can create the workspace but won’t have a model to run. Docs: https://docs.openclaw.ai/start/wizard and https://docs.openclaw.ai/concepts/agent-workspace

frail dust
#

how do i change the ai provider

south birchBOT
# frail dust how do i change the ai provider

Use the model config flow:

openclaw configure --section model

That lets you pick/add provider auth and set the default model. Afterward check it with:

openclaw models status

You can also do it from the models command:

openclaw models auth add
south birchBOT
frail dust
#

i want to change it to gemini

south birchBOT
# frail dust i want to change it to gemini

For Gemini you have two routes.

API key route, usually simplest:

openclaw onboard --auth-choice gemini-api-key
openclaw models list --provider google
openclaw models status

It accepts GEMINI_API_KEY / GOOGLE_API_KEY from Google AI Studio.

Gemini CLI OAuth route:

npm install -g @google/gemini-cli