Change:
<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: yes Hi, I'm not sure why or how this is happening! Since my last update today! Sometimes when files are modified, I can't save them via the menues anymore. This is very useful when I'm working without a keyboard in debug mode. Strangely, i can still select "Save all".... this make no sense ! Also, note that the keyboard shortcut works. <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: Version : 1.90.0 (user setup) Validation : Date : 2024-06-04T19:33:54.889Z Electron : 29.4.0 ElectronBuildId : Chromium : 122.0.6261.156 : 20.9.0 V8 : 12.2.281.27-electron.0 Système d’exploitation : Windows_NT x64 10.0. Steps to Reproduce: IDK sorry, it look like random !? a file dirty by type code menu file and look the save button. !
I'm seeing this as well, I think it's brand new in 1.90. I use "Alt-F S" for save and it doesn't work, because the menu is disabled. Ctrl-S works. Possibly related - Auto-Save had been enabled, possibly by accident. I turned it off and Save was still disabled. Restarted vscode and Save was working again. As soon as I saved the file, Save disabled and wouldn't re-enable when the file was modified. Since I hit "Alt-F S" a lot when editing, I get stuck with the File menu open. This has gotten really tedious really quickly. Reprogramming my finger-macros takes a long time.
Hi! Does this reproduce when disabling all extensions? Press and then choose !
cc for a file save related issue
The F1 Developer: disable extensions test doesn't work since the Save is already grayed out when it reloads. However, I ran and the Save came up enabled. It's also always enabled while a file is loaded - it never goes gray, unless there are no editors open, which is just as well. Weird. Guess I get to search extensions and figure out which one is giving me grief.
Woah, now I run it normally with my extensions enabled and it's working again. Wut? ... Spoke too soon, been working and now it's gray again. I'll try running a few minutes with --disable-extensions and see if it turns up again...
Yep, it turned up again with extensions disabled. It happens pretty quickly, but I'm not sure what the trigger is. Possibly related to focus/unfocus?
Thanks for the quick responses. Can you confirm that this only started happening after you updated to the latest stable release (1.90)?
I'm pretty sure I would've noticed it before, given that I probably hit Alt-F S dozens (or more) times per day.
yes since Version : 1.90.0 (user setup), i also used it everyday.
Moving to for investigation as there were changes last month for context keys in editor groups, so this maybe related.
Nevermind, reload with disabled extensions and re-enabling seems to have fixed it.
This is happening to me as well, just started with the 1.9. If I change tabs and the go back to the dirty file I can save. Doesn't happen all the time, but changing tabs always seems to fix it (for that edit anyway).
Found a new symptom -- super annoying... the Save menu item would become disabled, unless i switch tabs and switch back... whatever you guys did for this release in this area, please please roll it back!!
Just download the .zip file for version 1.88 if you know how, it will setup vscode using your existing temp files and extensions from the current version.
This seems to only happen when you have multiple editor groups and you switch from one group to the other. When you then switch between tabs in the same editor group it works again. I found the issue and fixed it with this PR

Discussion:
let groupRegisteredContextKeys = this.registeredContextKeys.get(group.id); if (!groupRegisteredContextKeys) { groupRegisteredContextKeys = new Map<string, IContextKey>(); <del> this.scopedContextKeys.set(group.id, groupRegisteredContextKeys); </del> <ins> this.registeredContextKeys.set(group.id, groupRegisteredContextKeys); </ins> } let scopedRegisteredContextKey = groupRegisteredContextKeys.get(provider.contextKey.key);