OpenClaw installation hurdles on Windows 11 and how to overcome them
Installing OpenClaw on a fresh Windows 11 machine isn't as simple as running the official quick-start script. A user who tried installing it on a budget mini PC encountered three specific hurdles that prevented the "one-click" installation from working.
The three installation obstacles
The user purchased a refurbished mini desktop PC ($200 CAD, Core i5, 16GB RAM, 256GB SSD) to serve as an isolated AI sandbox. When attempting the OpenClaw installation, these issues emerged:
- PowerShell Execution Policy Block: Windows refuses to run the install script by default. To fix this, open PowerShell as Administrator and run:
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser - Windows Defender Blocking: Even after fixing PowerShell, Windows Antivirus flags and blocks the install.ps1 file. You must manually go into the file properties and unblock it, explicitly telling Windows the script is safe.
- Missing Dependencies: The installation assumes a developer environment is already set up. On a bare-bones PC, you need to install Node.js, NPM, and Git using winget before attempting the OpenClaw install. Without these, the installation crashes halfway through.
The user notes that these issues aren't mentioned in the official documentation and required weeks of forum digging to resolve. They created a video breakdown showing how to bypass the security blocks and set up the mini PC.
This experience highlights that while developers might breeze through the installation, recreational tinkerers or those setting up isolated AI sandboxes on budget Windows hardware will encounter these specific technical obstacles.
📖 Read the full source: r/LocalLLaMA
👀 See Also
OpenClaw Ollama Cloud: Three-Layer Fix for Missing Models and Doctor Delete Bug
A clean install of OpenClaw with Ollama Cloud models failed: only kimi-k2.5 worked, configs disappeared. Root cause: providers list missing, name field required, and 'openclaw doctor --fix' deletes your provider block.
Claude Code Structure That Survived Multiple Real Projects
A developer shares a Claude Code setup that held up across 2-3 real projects with multiple skills, MCP servers, and agents. Key findings include using CLAUDE MD for consistency, splitting skills by intent, implementing hooks, and keeping context usage under 60%.
OpenClaw Memory Journey: Built-in Search vs MemPalace for Real-Time Session Recall
A developer benchmarks built-in memorySearch, QMD, and MemPalace on Intel Mac. Real-time session indexing hits snags; settles on split recall strategy with cron'd reindex.
System Architecture for Vibe Coders: A Senior Engineer's Guide
A 10-year engineer shares how to approach app building with Claude Code: start at the system level, not the code. Covers the four components — frontend, backend, database, plumbing — with a deep dive into the plumbing: APIs, hosting, deployment, secrets, and security.