Open dbaeumer opened 1 year ago
We now run a powershell command during uninstall to remove the appx package and this can take longer if file explorer is actively holding reference to the COM object. I don't have ideas now to make this better since this flow happens outside the application and not much we can intervene in this flow.
How long approximately?
@dbaeumer Is this still an issue?
Yes, still repros for me.
Would running that PS command only after the next OS restart help?
I was unable to repro with latest insiders but not sure if it has to do with canary channel of windows I am using, @dbaeumer can you help confirm if this is still an issue. Thanks!
I can still reproduce the hang in a Windows Sandbox.
@dbaeumer thanks for confirming, what is the build version of your OS ?
@dbaeumer can you capture a profile following the steps below, it would help moving this issue forward https://github.com/microsoft/vscode/issues/204696
Windows Performance Recorder
from the OS start menu, if you don't have it installed set it up following the instructions here@deepak1556 I checked out the #187015 that tried to fix this issue, and your comment that justifies the use of double {{
.
So that's why i'm interested if the ScriptBlock
on this line shouldn't end with double }}
as well?
Like this: {{Remove-AppxPackage -Package ""{#AppxPackageFullname}""}}
No idea if it's important, i just hope it helps.
Tried to install the profile and get this:
Any tips?
Sorry, try with this new profile CloudFileExplorerLogs.zip
If import was successful, you should see the following entry
@deepak1556 still the same problem with the new profile
Thanks for trying it out, I have reached out to the file explorer team, will follow up.
Can anyone else reproduce and confirm this issue? Maybe this is single system issue Can't reproduce on my system
Edition Windows 11 Pro
Version 23H2
Installed on 05.08.2023
OS Build 22631.3155
Experience Windows Feature Experience Pack 1000.22684.1000.0
This feature is not been added because
When uninstalling VS Code with enabled Open menu entry the uninstaller seems to hang at the beginning and it takes quite some time until it finishes. I never experienced this when testing the final Windows bits during endgame.
So, I request the developers to let users decide whether they want the option to add Visual Studio Code
to the Windows 11 Primary/Main Context Menu
during installation. Users should be able to check a box if they want this feature, with the box being unchecked by default.
I was unable to reproduce in Beta, Dev and Canary and also in Sandbox.
Should this be a blocker? The lack of an entry in the context menu affects way more users than this potential issue.
Should this be a blocker? The lack of an entry in the context menu affects way more users than this potential issue.
I couldn't agree more! For me, I will probably never uninstall it once I have downloaded it. However, I need this feature to save time.
Testing #164465
When uninstalling VS Code with enabled Open menu entry the uninstaller seems to hang at the beginning and it takes quite some time until it finishes. I never experienced this when testing the final Windows bits during endgame.