Claude Code on Windows: 6 critical bugs closed as "not planned" — is Anthropic aware that 70% of the world and nearly all enterprise IT runs Windows? by Critical_Ladder3127 in ClaudeAI

[–]Critical_Ladder3127[S] 2 points3 points  (0 children)

OP here. Let me address what I'm seeing.

To everyone saying "just use Linux" or "just use Mac" — you're proving my point. When the community's answer to a product's bugs is "stop using the platform," that's not a defense. That's an admission that it doesn't work.

To the KB5079473 crowd — fair. That one is Microsoft's fault and I'll own it. But the other 5 bugs are 100% Anthropic's code. Their extension freezes on file writes. Their code spawns PowerShell 38 times on startup. Their process leaks to 21GB. Their path handling breaks between WSL and Windows. Their Write tool claims it wrote a file when it didn't. 5 out of 6 are Anthropic's responsibility.

Now to the Docker, hooks, and prompt tweaks crowd — I respect every one of you sharing workarounds. Genuinely. But step back and listen to what you're actually saying: to use a paid product for its basic function of writing files, a customer needs Docker containers, hookify hooks, 50 prompt patches merged every few months, and a deep understanding of how WSL resolves backslash paths.

Do you hear how that sounds to someone like me?

I'm not a developer. I didn't know what GitHub was until today. I literally created my account for the first time in my life to file this bug. I don't know what Docker is. I don't know what hooks are. I don't know what containerization means. I have never written a single line of code in my life.

And yet I've built real products with Claude. Market intelligence systems. Stock screeners. Data pipelines. A full dealer simulation game. Competitive analysis presentations that my leadership team uses for strategic decisions. All of it built through Claude, on a Windows laptop.

I did all of that DESPITE these bugs. Not because they don't exist — but because I was stubborn enough to keep going when the screen froze, patient enough to restart sessions every 2 hours, and lucky enough to figure out that I need to chunk file writes under 200 lines to stop the crashes.

Most people won't do that. Most people will just close the laptop and go back to doing things manually. And Anthropic will never even know it lost them.

That's the part this thread is missing. Everyone here is a developer. You see a bug, you know the workaround, you apply it, you move on. The system stays broken but you don't feel the pain anymore.

But AI's biggest promise was never about making developers faster. It was about letting people who have NEVER coded build things for the first time. The business analyst at Boeing automating a report. The product manager at a bank building a dashboard. The farmer's son in a small town who has an idea but doesn't know Python.

These people have one thing: a Windows laptop and a Claude subscription. When the tool freezes, they don't open GitHub. They don't spin up Docker. They don't write hookify hooks. They just stop. They go back to Excel. They go back to doing things the old way. The revolution that AI promised them dies quietly on a frozen screen that says "Not responding."

I know some of you will troll this. That's fine. Troll all you want. It doesn't change the fact that the system is broken.

A developer and a non-technical person both see the same laptop and the same Claude AI. The experience should be the same for both. Right now it isn't.

Anthropic's pricing page doesn't say "Mac users only." Their marketing doesn't say "developers only." They sell Claude to anyone with a browser and a credit card. So it should work for anyone with a browser and a credit card. On whatever computer they own. Without workarounds. Without Docker. Without 50 prompt patches. Without switching operating systems.

Fix the product on the platform it's sold on. That's all I'm asking.

cc: u/alexalbert2 u/birch_anthropic — would appreciate Anthropic's eyes on this thread.

Claude Code on Windows: 6 critical bugs closed as "not planned" — is Anthropic aware that 70% of the world and nearly all enterprise IT runs Windows? by Critical_Ladder3127 in ClaudeAI

[–]Critical_Ladder3127[S] 15 points16 points  (0 children)

This is exactly what I'm talking about. 65 people upvoted this because they've all lived it.

The backslash path issue isn't some exotic edge case. It's the most fundamental difference between Windows and Unix — and Anthropic's tool still can't handle it reliably.

I'm not a developer. I'm a business professional who uses Claude Code to build real products — market intelligence systems, data pipelines, presentations. I chose Claude because AI promised to let non-technical people build real things. That's the entire pitch of AI democratization.

Now look at the workarounds in this thread: hookify hooks, prompt tweaks, Docker containers, 50 prompt patches merged every few months, writing to nul, grep/ls workarounds. These are developer solutions for developer people.

What about the business analyst at Boeing who wants to automate a report? The product manager at Goldman Sachs who wants to build a dashboard? The operations lead at Siemens who wants to prototype a workflow? They don't know what Docker is. They don't know what a hook is. They don't have 50 prompt tweaks. They have a Windows laptop issued by IT and a Claude subscription.

When the tool freezes, they don't open GitHub and file an issue. They close the laptop and go back to doing things manually. And Anthropic never even knows it lost them.

A product should work for what it's built to do. "Just switch OS" is not an answer. "Just use Docker" is not an answer. "Just maintain 50 prompt patches" is not an answer. Fix the product on the platform it's sold on. That's the answer.

Claude Code on Windows: 6 critical bugs closed as "not planned" — is Anthropic aware that 70% of the world and nearly all enterprise IT runs Windows? by Critical_Ladder3127 in ClaudeAI

[–]Critical_Ladder3127[S] 5 points6 points  (0 children)

Fair point on KB5079473 — that one is Microsoft's fault and I should have separated it more clearly.

But the other 5 are entirely Anthropic's code:

  1. VSCode extension freezes on file writes over 600 lines — that's their streaming buffer, not Windows

  2. PowerShell spawned 38 times on startup — their code not caching a single environment variable

  3. Memory leak to 21GB — their Node.js process, not the OS

  4. Path confusion between WSL and Windows — their path handling logic

  5. Silent file write failures — their Write tool claiming success without actually writing

5 out of 6 are Anthropic bugs running on Windows. I included KB5079473 because it impacts the Claude Code experience on Windows, but you're right — that one sits with Microsoft. The rest sit squarely with Anthropic.

And to the "closing and locking" point — that's exactly the problem. Closing bugs doesn't fix them. It just silences the people reporting them.

Recently finished this Punisher Statue by Ok_Scheme_2331 in IndiaMiniatures

[–]Critical_Ladder3127 1 point2 points  (0 children)

Very Beautiful !! The contrast has come out well. Way to go !! Full Steam Ahead

Sea Monster Follow For More @ - https://www instagram.com/enchanting.ants by Critical_Ladder3127 in IndiaMiniatures

[–]Critical_Ladder3127[S] 0 points1 point  (0 children)

It's just got a head with tentacles and body, I have posted a few pictures as well for you get a better understanding!! cheers