Change:
"git": { "name": "electron", "repositoryUrl": "https://github.com/electron/electron", <del> "commitHash": "0e6da36264d52656d5cd36a4c15937a6a6ca778e" </del> <ins> "commitHash": "83077e9b97c55cd4f9f641530442bcfd1c2ab949" </ins> } }, "isOnlyProductionDependency": true, "license": "MIT", <del> "version": "19.0.17" </del> <ins> "version": "19.1.3" </ins> }, { "component": {

Discussion:
Type: <bBug</bAfter recently I've updated to latest Insiders, nothing works anymore. I tried resetting from scratch, disabling all extensions and removing all custom settings, but nothing works. I can't even enable settings sync. The following results are form basically a brand new insider version (installed using ) <details<summaryWindow logs </summary</details<details<summarySettings sync logs</summary</detailsVS Code version: Code - Insiders 1.72.0-insider (, 2022-09-30T10:53:16.316Z) OS version: WindowsNT x64 10.0. Modes: Sandboxed: Yes <details<summarySystem Info</summary </detailsExtensions: none<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --PS: there's a typo in the log text outisde instead of outside Steps to reproduce: .
Thanks for creating the issue, please set the following setting until this issue is resolved.
Thanks for the answer. I did it in User settings, but I'm still experiencing the same problem :(
Hello I'm on the latest insider, but I'm still experiencing the same problem:
I am not familiar with how scoop maintains the symlink but from the error it looks like you are still using an older version of the runtime. Can you try uninstalling the insiders and try again. Thanks!
Uninstalling / reinstalling fixed the problems. Thanks

Type: <bBug</bAfter updating to vscode 1.71.0, the Window Controls Overlay (WCO) becomes enabled by default, and the maximize/restore button no longer responds to hover / clicks. The button works when WCO is disabled. Video: ! VS Code version: Code 1.71.0 (, 2022-09-01T07:36:10.600Z) OS version: WindowsNT x64 10.0. Modes: Sandboxed: No Remote OS version: Linux x64 5.15.57.1-microsoft-standard-WSL2 <details<summarySystem Info</summary </details<details<summaryExtensions (34)</summaryExtensionVersion ------ language-gas-x860.0.2 vscode-drawio1.6.4 discord-vscode5.8.0 better-cpp-syntax1.15.19 remote-containers0.251.0 remote-ssh0.84.0 remote-ssh-edit0.80.0 remote-wsl0.66.3 rewrap1.16.3 vim1.23.2 vscode-markdownlint0.48.1 vscode-new-file4.0.2 gitlens12.2.1 copilot1.43.6621 vscode-pull-request-github0.50.0 go0.35.2 todo-tree0.0.215 latex-workshop8.29.0 plantuml2.17.3 better-cpp-syntax1.15.19 serenity-dsl-syntaxhighlight0.2.1 cpptools1.12.4 wordcount0.1.0 rust-analyzer0.3.1186 crates0.5.10 comment-divider0.4.0 even-better-toml0.18.1 latex-utilities0.4.6 shellcheck0.21.4 cmake0.0.17 vscode-lldb1.7.4 markdown-all-in-one3.4.3 grammarly0.22.1 vscode-proto30.5.5 (4 theme extensions excluded) </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
I have the same problem on Windows 11.
I'm unable to reproduce the issue on Windows 10 + Ubuntu WSL. Added Windows 11 label.

It turns out that has some code that disables the maximize/restore button when touch mode is enabled. is determined by , which is determined partially by . There's also a comment in the last link about the Surface 4 always returning tablet mode. I'm curious whether you are using a tablet, or whether Chromium thinks you are using a tablet (or in tablet mode) when you're not actually using one?
That appears to be the issue! My laptop (Asus Flow X13) has a touch screen with a 360 degree hinge (like the Lenovo Yoga laptops). I typically have it standing on my desk in "tent mode" where the screen is folded almost all the way to the back, like this: ∧ When I folded it back and used it as a normal laptop, the maximize/restore button functions as expected.
Thanks for confirming the issue, this is same as Electron should allow the window to be maximized if the window is not already maximized when changing to tablet mode.
<!-- AUTHORVERIFICATIONREQUEST --This bug has been fixed in the latest release of ! you can help us out by commenting if things are now working as expected. If things still don't seem right, please ensure you're on version of Insiders (today's or later - you can use in the command palette to check), and leave a comment letting us know what isn't working as expected. Happy Coding!
I'm on the newest version of insiders on Windows 11 and I'm still getting this error ! I'm trying to click, but the window isn't changing.
were you testing on a touch device ?
I can also repro the issue on Windows 11 while in tablet mode.
Yeah! Interesting, I tested on a surface laptop studio in "stage mode", so I guess that counts as a tablet mode?
I just tested this issue again. The issue is not fixed with the exploration build, but it is potentially as-designed. When restored (unmaximized), one is able to maximize the window. After the window has been maximized, one cannot restore it. This behaviour actually lines up with Chrome, because Chrome completely disables the restore button while in touch mode after the user maximizes it. The minimize and close buttons are still available. On Edge, one can maximize and restore the window while in touch mode. I find this behaviour more intuitive.

the original issue is about maximize button not working when entering touch mode which has been addressed. As for aligning the restore behavior either with edge or chrome should be a separate issue, also this needs discussion in upstream electron.
In that case, closing this issue as verified