Next.js 16 dev server exits on Windows 11 silently when opening localhost:3000.

Recently I've got the vunerability notice from the vercel regarding the critical RCE vulnerability affecting React Server Components and upgraded my project's Next.js version to 16.0.7. After upgrading it, I faced very weird things. I tried to run a Next.16 project on Windows 11 with Node 22.20.0 and 20.19.5. The dev server starts normally, but as soon as I open http://localhost:3000, the server exits with no error unless debugging is enabled.

With debugging turned on, I get:

 ✓ Starting...
Node.js fs rename failed after 101 retries with error Error: EBUSY: resource busy or locked, rename 'E:\DevWorks\Public_ShowCase\auto-buyer-vercel\.next\dev\server\server-reference-manifest.json.tmp.71noimr4mvk' -> 'E:\DevWorks\Public_ShowCase\auto-buyer-vercel\.next\dev\server\server-reference-manifest.json'
E:\DevWorks\Public_ShowCase\auto-buyer-vercel\node_modules\next\dist\lib\fs\rename.js: Invalid source map. Only conformant source maps can be used to find the original code. Cause: Error: sourceMapURL could not be parsed
Error: EBUSY: resource busy or locked, rename 'E:\DevWorks\Public_ShowCase\auto-buyer-vercel\.next\dev\server\server-reference-manifest.json.tmp.71noimr4mvk' -> 'E:\DevWorks\Public_ShowCase\auto-buyer-vercel\.next\dev\server\server-reference-manifest.json'
    at ignore-listed frames {
  errno: -4082,
  code: 'EBUSY',
  syscall: 'rename',
  path: 'E:\\DevWorks\\Public_ShowCase\\auto-buyer-vercel\\.next\\dev\\server\\server-reference-manifest.json.tmp.71noimr4mvk',
  dest: 'E:\\DevWorks\\Public_ShowCase\\auto-buyer-vercel\\.next\\dev\\server\\server-reference-manifest.json'
}

This happens consistently, the dev server shuts down instantly when trying to connect to localhost:3000

Environment:

• Windows 11
• Node 22.20.0
• next.js 16.0.7
• React 19
• Running via npm run dev

What I've tried:

• Dleteing .next, node_modules, package.lock.json and reinstalling packages and run again

Question: What causes this failure in Next.js 16 on Windows, and how can I prevent or resolve this issue on my local dev environment?