INSTALL HELP

Installing ColorfulVibe

VERIFIED 2026-10-31 WITH COLORFULVIBE 0.6.4 AND CLAUDE CODE 2.1.316

• Which versions of Windows work?
• The installer is stuck on "Installing WebView2..."
• Do I need Node.js or Git?
• "Installing the newer Claude Code failed (npm install exited -1073740791)"
• "Assertion failed: new_time >= loop->time" on a virtual machine
• Install Claude Code without Node.js
• "EPERM: operation not permitted, rm …"
• "The property 'Statement' cannot be found on this object"
• "claude is not recognized" or "not in your PATH"
• ColorfulVibe still says Claude Code is missing
• Windows Server and LTSC: winget and the Microsoft Store
• Windows error codes in plain words
• Asking for help

Before you start

Which versions of Windows work?

Windows 11, and Windows 10 version 1809 or newer (64-bit). Windows Server 2019 and 2022 also work. They come without two things most PCs have, WebView2 and winget, so read the notes for WebView2 and Windows Server.

To see your version, press Windows+R, type winver and press Enter.

Do I need Node.js or Git?

No. ColorfulVibe brings what it needs. If Git isn't installed, ColorfulVibe sets up its own copy and shows a progress strip while it does. Claude Code can also be installed without Node.js at all.

The ColorfulVibe installer

The installer is stuck on "Installing WebView2..."

Applies to: Windows Server 2019/2022, and some Windows 10 PCs.

WebView2 is the Microsoft component that draws ColorfulVibe's window. It is not the Edge browser: nothing new appears in your Start menu and your default browser doesn't change. Windows 11 always has it. Windows Server doesn't, so the installer downloads it from Microsoft first. That is a large download (often 150–200 MB) and the installer shows no progress while it happens, so it can look stuck for several minutes.

• Wait. In Task Manager you will see a process named MicrosoftEdgeWebview2Setup or Microsoft Edge Update working.
• Or install the WebView2 Runtime yourself from Microsoft's WebView2 page (the "Evergreen" runtime), then run the ColorfulVibe installer again. It skips the step when WebView2 is already there.

You only wait once. Later installs and updates skip this step.

Claude Code

Claude Code is Anthropic's coding agent. ColorfulVibe installs it for you; when that fails, these answers get you running. You need a Claude account to sign in the first time. Anthropic's own guide: setting up Claude Code, and its troubleshooting page.

"Installing the newer Claude Code failed (npm install exited -1073740791)"

Seen on: Windows Server 2019 virtual machines.

-1073740791 is the Windows code 0xC0000409: the Node.js runtime that installs Claude Code crashed. On a virtual machine the usual cause is the VM clock problem. Install Claude Code with Anthropic's own installer instead; it does not use Node.

"Assertion failed: new_time >= loop->time, file …\deps\uv\src\win\core.c"

Applies to: some virtual machines (Hyper-V, VMware, cloud VMs), with any Node.js from version 20 on.

Node.js checks that Windows' high-precision timer only ever moves forward. On some virtual machines it occasionally steps backwards, and Node stops itself on purpose. This is a property of the machine, not of ColorfulVibe or Node: every program built on Node can hit it, at random. Running the same command again sometimes gets through.

To confirm you are on a virtual machine, run this in PowerShell; the Model will say "Virtual Machine", "VMware…", "KVM", "Amazon EC2" or similar:

Get-CimInstance Win32_ComputerSystem | Select-Object Manufacturer, Model

Things that help, from least to most involved:

• Install Claude Code with Anthropic's installer, which doesn't use Node. Claude Code itself runs without Node, and it worked on a VM with this problem.
• Restart the virtual machine.
• Make Windows use the platform timer. This changes a Windows boot setting: run it in a Command Prompt opened as administrator, then restart. Reports are mixed: it fixes some VMs and not others.

  bcdedit /set useplatformclock true

  To undo it later, run bcdedit /deletevalue useplatformclock as administrator and restart.
• Ask whoever runs the virtual machine to give it a stable CPU timer (an "invariant TSC") and to check its time-sync settings.

Install Claude Code without Node.js

Anthropic's native installer downloads Claude Code as a single program and doesn't need Node.js. In a Command Prompt (this is the one that worked on Windows Server 2019):

curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd

Or in PowerShell:

irm https://claude.ai/install.ps1 | iex

Both put claude.exe in %USERPROFILE%\.local\bin. ColorfulVibe looks there, so after installing, press Re-check in ColorfulVibe's setup checklist. To use claude in your own terminals too, add the folder to your PATH.

"EPERM: operation not permitted, rm '…\.cache\claude\staging\…'"

Seen with: Anthropic's PowerShell installer on Windows Server 2019.

The installer downloaded Claude Code but couldn't remove its temporary download folder, usually because antivirus was still scanning the new file. Use the Command Prompt installer from the answer above, ideally in a Command Prompt opened as administrator. Or wait a minute and run the PowerShell installer again.

"The property 'Statement' cannot be found on this object" (from npm)

Applies to: Windows PowerShell 5.1 (built into Windows) with npm older than 11.6.0, which ships with Node.js before 24.8.

This is a bug in npm's PowerShell launcher, npm.ps1, not in what you asked it to install. Run npm.cmd instead of npm, or use a Command Prompt:

npm.cmd install -g @anthropic-ai/claude-code

On a virtual machine with the clock problem, npm may then crash the same way, because npm runs on Node. In that case use Anthropic's installer.

"'claude' is not recognized" or "… is not in your PATH"

Claude Code is installed, but the folder it lives in isn't on your PATH. Add it for your user, then open a new window. In PowerShell:

[Environment]::SetEnvironmentVariable('Path', [Environment]::GetEnvironmentVariable('Path','User') + ";$env:USERPROFILE\.local\bin", 'User')

Or in a Command Prompt:

powershell -NoProfile -Command "[Environment]::SetEnvironmentVariable('Path', [Environment]::GetEnvironmentVariable('Path','User') + ';%USERPROFILE%\.local\bin', 'User')"

Paste only the command, not the label above it. Avoid setx for this: it can cut a long PATH short. Check it worked with where claude in a new window.

ColorfulVibe still says Claude Code is missing

Wait a minute after installing, then press Re-check. If it still says missing, quit ColorfulVibe from its tray icon (closing the window isn't enough) and start it again. If claude --version works in a new Command Prompt and ColorfulVibe still can't find it after a restart, tell us.

Windows Server and LTSC

"Fix winget" and "Open Microsoft Store" don't work

Applies to: Windows Server 2019 and 2022, and Windows 10 LTSC.

These editions don't come with winget or the Microsoft Store, and can't get them the usual way, so those two buttons can't help there. Use the direct download buttons in ColorfulVibe's setup checklist instead, or install the tool from its publisher's website. ColorfulVibe sets up Git itself and doesn't need winget for it.

Windows Server also has only Windows PowerShell 5.1. See the npm launcher bug above.

Windows error codes in plain words

Windows reports a crashed program as a large number, sometimes negative. The same code, three ways:

Asking for help

Email hello@colorfulvibe.com with:

• your Windows edition and version, from winver;
• whether it's a virtual machine (the PowerShell line in the clock answer);
• your ColorfulVibe version;
• the exact message, or a screenshot.

Please never send a licence key, password or token.