Please replace with a clear and descriptive title

Describe the bug

after successfully connecting to a project, I ran the prompt netlify dev. It worked shortly as shown below:
PS C:\Users\bdrap> netlify dev
⬥ Injecting environment variable values for all scopes
⬥ No app server detected. Using simple static server
⬥ Running static server from "bdrap.next"
⬥ Setting up local dev server

⬥ Static server listening to 3999

╭─────────────────────── ⬥  ────────────────────────╮
│ │
│ Local dev server ready: http://localhost:8888 │
│ │
╰───────────────────────────────────────────────────╯

» Error: Netlify CLI has terminated unexpectedly.

Steps to reproduce

after connecting to your netlify project, run netlify dev and I immediately had my CLI discnonected

Configuration

Error: EPERM: operation not permitted, watch 'C:\Users\bdrap\Application Data'
at FSWatcher. (node:internal/fs/watchers:321:19)
at watch (node:fs:2548:36)
at createFsWatchInstance (file:///C:/Users/bdrap/AppData/Roaming/npm/node_modules/netlify-cli/node_modules/chokidar/esm/handler.js:126:16)
at setFsWatchListener (file:///C:/Users/bdrap/AppData/Roaming/npm/node_modules/netlify-cli/node_modules/chokidar/esm/handler.js:171:19)
at NodeFsHandler._watchWithNodeFs (file:///C:/Users/bdrap/AppData/Roaming/npm/node_modules/netlify-cli/node_modules/chokidar/esm/handler.js:325:22)
at NodeFsHandler._handleDir (file:///C:/Users/bdrap/AppData/Roaming/npm/node_modules/netlify-cli/node_modules/chokidar/esm/handler.js:546:27)
at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
at async NodeFsHandler._addToNodeFs (file:///C:/Users/bdrap/AppData/Roaming/npm/node_modules/netlify-cli/node_modules/chokidar/esm/handler.js:591:26)

Environment

System:
OS: Windows 11 10.0.26200
CPU: (16) x64 AMD Ryzen 7 8745HS w/ Radeon 780M Graphics
Memory: 36.70 GB / 61.78 GB
Binaries:
Node: 24.18.0 - C:\Program Files\nodejs\node.EXE
npm: 11.17.0 - C:\Program Files\nodejs\npm.CMD

Start by reproducing netlify dev on Windows 11 with the reported project setup, then trace the file-watching path from the netlify dev entry point to the Chokidar stack shown in the error. Determine why it attempts to watch C:\Users\bdrap\Application Data; done means the CLI remains running and serves the project without terminating unexpectedly.