Benjamin Pasero

@meganrogge a simple example works for me, here are my changes: In [`windowImpl.ts.reload()`](https://github.com/microsoft/vscode/blob/c2bb0cdb01fd7c52c62ae30da7a3f11ff6b1e8d7/src/vs/platform/windows/electron-main/windowImpl.ts#L1069): ```ts configuration.verbose = true; ``` In constructor of [`window.ts`](https://github.com/microsoft/vscode/blob/c2bb0cdb01fd7c52c62ae30da7a3f11ff6b1e8d7/src/vs/workbench/electron-sandbox/window.ts#L128): ```ts console.log(this.environmentService.verbose); ``` On first start I get...

I am not sure the issue here, but it sounds unlikely its a VS Code issue, rather an issue with your configuration. Maybe an Antivirus running?

Is there a reliable reproduce or does it happen randomly?

I wonder if this issue is being caused by an installed extension. Can you try to run VS Code without extensions? From the command line (NOT the integrated terminal in...

Hm, just to make sure, would it reproduce when you do the same with a `txt` file instead of `tsx`?

Thanks, I suspect the typescript extension to install a watcher on dedicated folders that on Windows may result in folder locking.

👋 we are experimenting with using VS Codes core file watcher in the TypeScript extension (https://github.com/microsoft/vscode/issues/208872). There is a new setting `typescript.tsserver.experimental.useVsCodeWatcher` available starting with todays VS Code insider release....

I cannot say if it ever worked, probably not.

Keep

Here is a concrete reproducible example. The window is left like this:  And restarted with the bounds I got from Electron:  Gist files with a simple file based...