workspace files reverted to old versions after the newest update

[Raiccio]

Does this issue occur when all extensions are disabled?: irrelevant

• VS Code Version: May 2025 (version 1.101)
• OS Version: Win11 Pro

Steps to Reproduce:

1. Install the new update from inside the VSCode
2. Launch your workspace

Every single file in my workspace got reverted to a 6th of June version (8 days of progress lost) after updating VSCode today. First time this is happening. Also the VScode started constantly hanging (not responsing) and asking in a prompt window to be reopened/closed/waited for, also a behaviour I see for the first time. Also some notebooks are not loading at all (empty screen)...

What is weird is that all the files got reverted to a point in time I last made an external backup of everything.

[bpasero]

@Raiccio if you right click on a file that got reverted and selected to open timeline, can you find your changes again?

This is unlikely to be an issue with VS Code but maybe an issue with your file system and disk, anything specific there?

[Raiccio]

@bpasero for those that are not to large for the the timeline feature, the last version shown is again 6th of June (a wk ago). Consistent with the reversal. Everything was alright last night and this morning (before I decided to update the app). I have been using VSCode for years and this is the first time that something like this happens.

[bpasero]

VS Code itself cannot revert all your files back to a state from a week ago (at least not to my knowledge), so I suggest you find out what could have caused this on your file system.

[Raiccio]

This is really werid - somehow every file is reverted to a state it was on the date I last backed up manually everything on an external device. The files are identical now and there. Could have VScode stopped saving on disk since then and started only keeping some kind of temp files/states? I am clueless.

[bpasero]

We are not doing any magic tricks here, we use node.js to write to the file system. There is no caching or in-memory state.

[vs-code-engineering[bot]]

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!