[Bug]: Changes in the vscode directory caused the reg file to become invalid

[abgox]

Prerequisites

• I have written a descriptive issue title.
• I have searched all issues/PRs to ensure it has not already been reported or fixed.
• I have verified that I am using the latest version of Scoop and corresponding bucket.

Package Name

vscode

Expected/Current Behaviour

• Refer to [Bug]: install-associations.reg DefaultIcon 文件地址错误 abgox/abyss#111
• Starting from version 1.109, VSCode has changed its directory structure. Taking file icons as an example:
  • Before: $code_dir\resources\app\resources\win32\html.ico
  • After: $code_dir\$resources_id\resources\app\resources\win32\html.ico
  • $resources_id seems to be a commit id.
• It causes the reg files that depend on it to become invalid.
• However, I don't know if this is a stable directory structure change, so I only fixed it in my abyss bucket and didn't submit a PR in Extras.
• Maybe we can discuss it or verify if it's a stable change.

Steps to Reproduce

.

Possible Solution

abgox/abyss@51f79cc

Scoop and Buckets Version

PS> scoop --version

Current Scoop version:
bd2e93df (HEAD -> develop, origin/develop) fix(autoupdate): Ensure GitHub API requests use token (#6535)

'main' bucket:
068134ac22 (HEAD -> master, origin/master, origin/HEAD) worktrunk: Update to version 0.23.2

'abyss' bucket:
51f79ccf5 (HEAD, origin/main, origin/HEAD, main) Microsoft.VisualStudioCode.*: fix reg (Closes #111)

Scoop Config

PS> scoop config

abgox-abyss-app-shortcuts-action : 2
abgox-abyss-bucket-name          : abyss
aria2-enabled                    : False
aria2-max-connection-per-server  : 5
aria2-min-split-size             : 5M
aria2-retry-wait                 : 3
aria2-split                      : 5
aria2-warning-enabled            : False
ignore_running_processes         : True
last_update                      : 2026/2/11 20:48:13
scoop_branch                     : develop
scoop_repo                       : https://gitee.com/scoop-installer-mirrors/Scoop
show_update_log                  : True
use_isolated_path                : False
use_sqlite_cache                 : True
root_path                        : D:\@scoop
global_path                      : D:\@scoop-global

PowerShell Version

PS> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      7.5.4
PSEdition                      Core
GitCommitId                    7.5.4
OS                             Microsoft Windows 10.0.26200
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Additional Softwares

No response

[z-Fng]

Relates to:

• feat: create versioned resources for windows setup microsoft/vscode#263998
• Support a better Windows update flow microsoft/vscode#249239

Looks like VSCode is trying to optimize the Windows update flow by creating a version folder since 1.109.

abgox/abyss@51f79cc

It is also necessary to re-write existing registry keys during installation. The previous behavior relied on a stable path (via the 'current' junction).

Extras/bucket/powertoys.json

Lines 50 to 57 in 6a77444

	"$regpath = 'HKCU:\\Software\\Classes\\powertoys'",
	"if ($global) {",
	" $regpath = $regpath.Replace('HKCU', 'HKLM')",
	"}",
	"if (Test-Path -Path $regpath) {",
	" Remove-Item -Path $regpath -Recurse -Force | Out-Null",
	" Invoke-Expression -Command \"& `\"$dir\\install-context.ps1`\"\"",
	"}"

[abgox]

It is also necessary to re-write existing registry keys during installation. The previous behavior relied on a stable path (via the 'current' junction).

• reg import will overwrite them.

• In my manifest, the uninstallation will remove these registries.

• Therefore, there should be no need to remove them during the installation.

• Or, I have overlooked something important?

  https://github.com/abgox/abyss/blob/51f79ccf5f2f1d35be094e8ad5bbc351333c227d/bucket/m/Microsoft/Microsoft.VisualStudioCode.Insiders.json#L73-L77

[z-Fng]

It is also necessary to re-write existing registry keys during installation update. The previous behavior relied on a stable path (via the 'current' junction).

• reg import will overwrite them.

I meant that the registry import needs to be re-run on every update, because the .reg file changes with each version. Previously, it remained the same.

[abgox]

• You're right.
• I checked the reg file and found that all places using $resources_id are some .ico icon files.
• In fact, they are relatively stable and won't change frequently with versions.
• Maybe we can specify the version directory instead of the current directory.
• When it's updated, the old version directory still exists.
• However, if the user cleans up the old versions, they will also become invalid unless the registry is re-imported.

[SorYoshino]

Perhaps we could consider directly copying the icon resources to their original location?

{
    "pre_install": [
        "ensure \"$dir\\resources\\app\\resources\\win32\" | Out-Null",
        "$build_dir = Get-ChildItem -Path $dir -Directory |",
        "        Where-Object { $_.Name -match '^[a-f0-9]{7,}$' } | Select-Object -ExpandProperty FullName -First 1",
        "if (-not [string]::IsNullOrWhiteSpace($build_dir) -and (Test-Path -Path \"$build_dir\\resources\\app\\resources\\win32\\*\")) {",
        "    $resources_dir = \"$dir\\resources\\app\\resources\\win32\"",
        "    $original_resources_dir = \"$build_dir\\resources\\app\\resources\\win32\"",
        "    Copy-Item -Path \"$original_resources_dir\\*\" -Destination \"$dir\\resources\\app\\resources\\win32\" -Force",
        "}"
    ]
}

https://github.com/SorYoshino/unoff-bucket/blob/f44ff32eee5d53b07c660b921e8ebee9e100cfd6/bucket/m/Microsoft/vscode.json#L28-L35

---

The previous behavior relied on a stable path (via the 'current' junction).

Yes, apart from PowerToys, almost all related manifests are based on the 'current' junction. If no_junction is set to true, we would encounter the same issue.

[abgox]

• In fact, even copying is not necessary.
• We can directly create a junction for the $build_dir.
• Like: New-Item -ItemType Junction -Path "$dir\resources" -Target "$build_dir\resources" | Out-Null

[Timabliss]

Thanks for the discussion, everyone. I have a clear idea now on how to fix the update logic based on our conversation. I'm currently away from my keyboard, so I'll push the changes a bit later today. Thanks for your patience!

[SorYoshino]

• In fact, even copying is not necessary.
• We can directly create a junction for the $build_dir.

Yes, directly creating a symbolic link may be the simplest approach. However, I am not sure whether this method is appropriate for the official buckets, so I did not mention it.

[Timabliss]

Hey folks! 👋 Just wanted to share a fun little discovery I made while digging into the VS Code structure. 🕵️‍♂️✨

I was originally trying to implement a way to "sniff" the directory for that elusive random hash folder (you know, the one inside the version folder), but I realized it was a bit... flaky. 😅

Then I stumbled upon the bin/code shell script shipped with VS Code, and guess what? It literally has the answer hardcoded right there!

# Inside bin/code
VERSIONFOLDER="591199df40..."  # <--- The Source of Truth! 🤯

So, instead of guessing directory names with regex, we can just parse this file directly to get the exact hash path. It's way more robust and faster! 🚀

I've updated my PR to use this approach. I also added a little "Hygiene Check" 🧹 — during an update, if the script detects any old version directories (matching ^[0-9.]+$), it proactively runs the uninstall-*.reg logic to keep the registry clean.

No more ghost context menus! 👻🚫

Feel free to check out the code. Cheers! 🍻

[Timabliss]

[abgox]

So, instead of guessing directory names with regex, we can just parse this file directly to get the exact hash path. It's way more robust and faster! 🚀

• https://github.com/abgox/abyss/blob/51f79ccf5f2f1d35be094e8ad5bbc351333c227d/bucket/m/Microsoft/Microsoft.VisualStudioCode.json#L52
• In abyss bucket, the current hot fix is done this way.
• However, it's hard to give an answer as to who is more stable.
• This script file seems more likely to change?
• If they think that VERSION_FOLDER is better than VERSIONFOLDER, or other better name...

---

• Also, in the app directory of vscode, there are only a few folders, and they are rarely added or modified.
• Therefore, does it seem more stable to use regular expressions to match it? I'm not sure.

[Timabliss]

​Hey buddy! 👋
​Glad to see we’re totally on the same page regarding the core issue! It’s awesome that we both caught onto that bin/code trick. 🤝
​Regarding the implementation, I’ve decided to stick with a more "all-in-one" approach in post_install. I personally lean towards using regex to match the version folders for the cleanup part.
​Let's be real—Microsoft isn't likely to overhaul the folder naming convention overnight. As long as it matches ^[0-9.]+$, we're golden. It’s simple, it works, and it keeps the manifest from getting too "busy" with too many pre/post hooks.
​I’m a big fan of the "if it ain't broke, don't over-engineer it" philosophy, you know? 😂