Skip to content

Signature verification failed with 'PackageIntegrityCheckFailed' error. #230816

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
pdpark opened this issue Oct 8, 2024 · 45 comments
Open

Signature verification failed with 'PackageIntegrityCheckFailed' error. #230816

pdpark opened this issue Oct 8, 2024 · 45 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug extension-signature Issues related to extension signature verification
Milestone

Comments

@pdpark
Copy link

pdpark commented Oct 8, 2024

Type: Bug

Ever since upgrading to the most recent release of vscode I cannot install or upgrade any vscode extensions.

Cannot install ... extension because Visual Studio Code cannot verify the extension signature

Signature verification failed with 'PackageIntegrityCheckFailed' error.

VS Code version: Code 1.94.0 (Universal) (d78a74b, 2024-10-02T13:08:12.626Z)
OS version: Darwin arm64 23.6.0
Modes:

System Info
Item Value
CPUs Apple M1 Pro (10 x 2400)
GPU Status 2d_canvas: enabled
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled
webgpu: enabled
webnn: disabled_off
Load (avg) 2, 2, 2
Memory (System) 32.00GB (1.83GB free)
Process Argv --crash-reporter-id dfc65e10-fbb4-4b6c-919e-dce0edfa49eb
Screen Reader no
VM 0%
Extensions (23)
Extension Author (truncated) Version
unique-lines bib 1.0.0
ruff cha 2024.50.0
gitlens eam 15.5.1
terraform has 2.32.3
vscode-duplicate mrm 1.2.1
vscode-docker ms- 1.29.3
debugpy ms- 2024.10.0
isort ms- 2023.10.1
python ms- 2024.14.1
vscode-pylance ms- 2024.9.2
datawrangler ms- 1.10.0
jupyter ms- 2024.8.1
jupyter-renderers ms- 1.0.19
vscode-jupyter-cell-tags ms- 0.1.9
remote-ssh ms- 0.114.3
remote-ssh-edit ms- 0.87.0
remote-explorer ms- 0.4.3
vscode-thunder-client ran 2.27.0
vscode-xml red 0.27.1
vscode-yaml red 1.15.0
stardog-rdf-grammars sta 0.2.1
even-better-toml tam 0.19.2
gistfs vsl 0.6.0
A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
a9j8j154:30646983
962ge761:30959799
pythongtdpath:30769146
pythonnoceb:30805159
asynctok:30898717
pythonmypyd1:30879173
2e7ec940:31000449
pythontbext0:30879054
accentitlementsc:30995553
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
bdiig495:31013172
a69g1124:31058053
dvdeprecation:31068756
dwnewjupytercf:31046870
2f103344:31071589
impr_priority:31102340
nativerepl1:31139838
refactort:31108082
pythonrstrctxt:31112756
flighttreat:31134774
wkspc-onlycs-t:31132770
nativeloc2:31134642
wkspc-ranged-t:31151552
cf971741:31144450
defaultse:31146405
iacca2:31150323
notype1:31151523
cc771715:31146322

@sandy081
Copy link
Member

sandy081 commented Oct 9, 2024

  • Are you seeing this error for all extensions or specific extensions?
  • Can you please enable log level to trace (F1 > Developer: Set Log Level... > Trace) and reproduce the issue and share with us following log - F1 > Open View... > Shared

CC @isidorn

@sandy081 sandy081 added the info-needed Issue requires more information from poster label Oct 9, 2024
@pdpark
Copy link
Author

pdpark commented Oct 10, 2024

  • It is happening with all extensions. Started after installing the September update.
  • Here's what I can share from the trace for now - will share the rest if needed/approved:
2024-10-09 19:06:28.809 [info] Extension signature verification result for ms-python.python: PackageIntegrityCheckFailed. Executed: true. Duration: 240ms.
2024-10-09 19:06:28.809 [trace] Extension signature verification output for ms-python.python:
Package file size:  10570071
Signature archive file size:  119770
Manifest file size:  486193
Signature file size:  19230
Manifest file hash:  CdPiqhl5ahk57W3WOKcac5245LyJvHXI8MB7hGdYG/4=
Signature file hash:  shC5tAmkkyNxA2KADbhjX5VEMqaiMejTJptzbP6HkIs=
Package file hash:  CH90EsBQko8Wvpq5yAuarkad4fvroPfj9mstl9qS7/M=
ManifestPackageIntegrityPolicy failed:  unexpected package size.
Exit code:  PackageIntegrityCheckFailed

@sandy081
Copy link
Member

@dtivel Can you please check what is going wrong here?

@pdpark
Copy link
Author

pdpark commented Oct 10, 2024

Full trace log attached: vscode_ext_install_trace.log

BTW: a colleague is seeing the same thing in his trace log - Exit code: PackageIntegrityCheckFailed - when he installs an extension, but his install succeeds.

@dtivel
Copy link
Member

dtivel commented Oct 11, 2024

@sandy081, this is the important clue:

ManifestPackageIntegrityPolicy failed:  unexpected package size.

The signature and manifest files look to be correct for the desired version. However, the VSIX file size is unexpected. Any idea why?

From the log, I see Microsoft.VisualStudio.Code.Manifest and Microsoft.VisualStudio.Services.VsixSignature assets being downloaded, but I don't see Microsoft.VisualStudio.Services.VSIXPackage assets being downloaded. Is there a stale VSIX package on disk? A partially downloaded package on disk?

@sandy081
Copy link
Member

but I don't see Microsoft.VisualStudio.Services.VSIXPackage assets being downloaded. Is there a stale VSIX package on disk? A partially downloaded package on disk?

Let me ask the user

@pdpark Can you please open following folder and let us know what files you have there

  • F1 > Developer: Open User Data Folder > CachedExtensionVSIXs

@pdpark
Copy link
Author

pdpark commented Oct 11, 2024

There were a number of files, like this one: Image

I moved all the files in the cache folder to the trash and tried the installs again. They failed with the same error, and there are now new files in the cache folder.

BTW: I also tried downloading the VSIX files for a few extensions and installing those with the extensions menu option: "Install from VSIX...". These attempts also failed with the same message.

@pdpark
Copy link
Author

pdpark commented Oct 15, 2024

I have confirmed two vscode users get this error in their trace log but the install succeeds. One is is on the same version I am, the other is on 1.93.

In both cases, when they open their settings.json file, they have no settings.

I have this in the left pane when viewing my settings.json file:

  // When enabled, extensions are verified to be signed before getting installed.
  "extensions.verifySignature": true,

If the default for this setting is true, why would the extension install succeed for them even though the trace shows the signature validation failed?

@pdpark
Copy link
Author

pdpark commented Oct 17, 2024

I'm not the only developer impacted by this at our company. Any suggestions for moving forward other than just setting "extensions.verifySignature": false?

@pdpark
Copy link
Author

pdpark commented Oct 17, 2024

FYI: a developer not having this issue does not even see extensions.verifySignature as an option in the left pane when viewing his settings.json file after setting:

"workbench.settings.useSplitJSON": true,
"workbench.settings.editor": "json",

@sandy081
Copy link
Member

I also tried downloading the VSIX files for a few extensions and installing those with the extensions menu option: "Install from VSIX...". These attempts also failed with the same message.

Can you please share those VSIXs with us?

@geethavaleti
Copy link

Still happening to me, Can't update copilot, many extensions. Is this issue fixed?

@pdpark
Copy link
Author

pdpark commented Oct 31, 2024

I also tried downloading the VSIX files for a few extensions and installing those with the extensions menu option: "Install from VSIX...". These attempts also failed with the same message.

Can you please share those VSIXs with us?

They should be the same as you would get if you download them yourself, but I've attached the files to this comment. I had to change the file extensions to .txt - github would not allow the selection of .vsix files for upload.

GitHub.copilot-1.238.0.txt
[email protected]
ms-python.vscode-pylance-2024.10.100.txt

@sandy081
Copy link
Member

They should be the same as you would get if you download them yourself,

I believe they are not as they seem to be verified properly for me. Thanks for the zips.

@pdpark
Copy link
Author

pdpark commented Oct 31, 2024

They should be the same as you would get if you download them yourself,

I believe they are not as they seem to be verified properly for me. Thanks for the zips.

I'm not sure why you believe that they are not the same files you would have gotten had you downloaded them when I did. They could be identical to the files you would have downloaded at the time and the signature verification could still fail for me and succeed for you if the problem is somewhere in the signature verification process and occurs only under specific circumstances which happen to differ between us.

@juantarquino-ssb
Copy link

Same thing is happening to our team with the recent update. The error seems to be due to a different package size. Trace below:

2024-11-07 10:08:12.217 [trace] Verifying extension signature for github.copilot...
2024-11-07 10:08:12.471 [info] Extension signature verification result for github.copilot-chat: PackageIntegrityCheckFailed. Executed: true. Duration: 365ms.
2024-11-07 10:08:12.471 [trace] Extension signature verification output for github.copilot-chat:
Package file size:  5189517
Signature archive file size:  14209
Manifest file size:  9149
Signature file size:  19226
Manifest file hash:  N/XgOx08PlR6Q4ZSqGonNx3Cc7jwNbWjYECl+lDO0sU=
Signature file hash:  eS+cJ9p35E4mX2+oIdlBOjueVBc3p7akCLC4r3H2yA0=
Package file hash:  x4Tyzd8pggHzUsCIygHjKQWfkkIknSPpH4lnf2v/rfY=
ManifestPackageIntegrityPolicy failed:  unexpected package size.
Exit code:  PackageIntegrityCheckFailed

@sandy081
Copy link
Member

@juantarquino-ssb Does this happens with all extensions or only with copilot chat extension?

@juantarquino-ssb
Copy link

@juantarquino-ssb Does this happens with all extensions or only with copilot chat extension?

It happens with all of the extensions, not just the copilot chat extension.

@sandy081
Copy link
Member

@juantarquino-ssb Can you please try our insiders and let us know if you are able to reproduce the same?

@dtivel
Copy link
Member

dtivel commented Nov 13, 2024

I see from the original post that this reproed on macOS. Is anyone experiencing the same issue on Linux or Windows?

@jordanjohnson56
Copy link

I am experiencing the same issue on Windows 10 trying to install any extensions. I am on 64-bit VS Code version 1.95.3.

2024-12-02 11:08:55.050 [info] Extension signature verification result for ms-toolsai.jupyter: PackageIntegrityCheckFailed. Executed: true. Duration: 108ms.
2024-12-02 11:08:55.050 [trace] Extension signature verification output for ms-toolsai.jupyter:
Package file size:  7151890
Signature archive file size:  19837
Manifest file size:  26414
Signature file size:  19225
Manifest file hash:  o4sdIPr87N1D5L8QiA8+E1/7Qe5DganJUJ6UEEmJUaE=
Signature file hash:  LW5izGfuWuseBdkXWvXRXCJYLrkqpkiiQ979vMk8x/8=
Package file hash:  Q9ahcHNv41jNI/6BjKdWbtnXwSg68RGp9QYUDq7Kuok=
ManifestPackageIntegrityPolicy failed:  unexpected package size.
Exit code:  PackageIntegrityCheckFailed

@chucknelson
Copy link

Same issue on MacOS with all extension updates - noticed a few weeks ago when none of the extensions were auto-updating as expected.

Version info:

Version: 1.95.3 (Universal)
Commit: f1a4fb101478ce6ec82fe9627c43efbf9e98c813
Date: 2024-11-13T14:50:04.152Z (2 wks ago)
Electron: 32.2.1
ElectronBuildId: 10427718
Chromium: 128.0.6613.186
Node.js: 20.18.0
V8: 12.8.374.38-electron.0
OS: Darwin arm64 23.6.0

@sandy081
Copy link
Member

sandy081 commented Dec 4, 2024

Can you please try our insiders and let me know if you are seeing the issue?

@juantarquino-ssb
Copy link

The insider's version results in the same issue for me (PackageIntegrityCheckFailed).

@sandy081
Copy link
Member

sandy081 commented Dec 4, 2024

@juantarquino-ssb Can you please share the VSIX of the extension that is causing PackageIntegrityCheckFailed error. You can get the VSIX from following location

  • Run command F1 > Developer: Open User Data Folder
  • Navigate to CachedExtensionVSIXs/.trash/ folder
  • Share the VSIX from there

@juantarquino-ssb
Copy link

github.copilot-1.246.0.zip

Here is the GitHub copilot VSIX from that CachedExtensionVSIXs/.trash/ folder. Please note that the PackageIntegrityCheckFailed issue happens with all extensions, not just GitHub copilot, I just used this one as an example.

@sandy081
Copy link
Member

sandy081 commented Dec 5, 2024

Can you also please share the file github.copilot-1.246.0.sigzip from that folder?

@juantarquino-ssb
Copy link

github.copilot-1.246.0.sigzip

That is interesting, I do not see a "github.copilot-1.246.0.sigzip" in that folder. Is there a way to check if VS Code was able to download that github.copilot-1.246.0.sigzip file?

@sandy081
Copy link
Member

sandy081 commented Dec 9, 2024

If you are able to reproduce the problem with VS Code Insiders Edition, can you please share following data

  • Try to install an extension that fails with the reported error
  • Run command F1 > Developer: Open User Data Folder
  • Navigate to CachedExtensionVSIXs/.trash/ folder
  • Share the VSIX and .sigzip files of the corresponding extension

@sprowell
Copy link

sprowell commented Dec 10, 2024

If you are able to reproduce the problem with VS Code Insiders Edition, can you please share following data

* Try to install an extension that fails with the reported error 
* Run command `F1 > Developer: Open User Data Folder`
* Navigate to `CachedExtensionVSIXs/.trash/` folder
* Share the VSIX and .sigzip files of the corresponding extension

Installed Insiders Edition (downloaded today, 9 December 2024, 1.96.0-insider, commit 475a...6b0e). Tried to install Vim extension (vscodevim.vim, 1.29.0). Failed with the same error ("Signature verification failed with 'PackageIntegrityCheckFailed' error.").

Here are the files from .trash: vscodevim.vim-1.29.0.zip

@sandy081 sandy081 removed the info-needed Issue requires more information from poster label Dec 16, 2024
@sandy081 sandy081 added this to the January 2025 milestone Dec 16, 2024
@rzhao271 rzhao271 added bug Issue identified by VS Code Team member as probable bug extension-signature Issues related to extension signature verification labels Dec 16, 2024
@sandy081 sandy081 modified the milestones: January 2025, February 2025 Jan 27, 2025
@sandy081 sandy081 modified the milestones: February 2025, March 2025 Feb 25, 2025
@NirmalManoj
Copy link

Facing the same issue with 1.98.0-insider on Manjaro.

@bulletmark
Copy link

Decided to try 1.98.0-insider on Arch. Every extension exhibits this bug on new install and/or on any update. If I press "Install anyway (Don't verify signature)", then each extension seems to install and run fine. I've run the regular release (currently 1.97.2) on my machine for ages and it has no issues installing and/or updating extensions.

@sandy081
Copy link
Member

sandy081 commented Mar 6, 2025

@NirmalManoj and @bulletmark Can you please share to which Marketplace you are connecting to? You can see that by doing following

  • Open developer tools in VS Code
  • Open Extensions View
  • Search for extensions
  • Share the marketplace URL

@bulletmark
Copy link

@sandy081 earlier today I reinstalled vscode insiders and the problem went away.

@NirmalManoj
Copy link

@sandy081 I'm having trouble easily locating the marketplace URL. Could you please elaborate on the steps (perhaps with screenshots)?

@NirmalManoj
Copy link

@sandy081
I monitored the network requests while searching for extensions, and the request URL I observed is:

https://marketplace.visualstudio.com/_apis/public/gallery/extensionquery

Is this the URL you're looking for? Please let me know if you need any further details!

@sandy081
Copy link
Member

sandy081 commented Mar 7, 2025

@NirmalManoj Thanks for sharing the information. If you are still able to reproduce the issue, please share following logs

  • Reproduce the issue
  • Share F1 > Open View... > Shared

Also your System information

Thanks

@NirmalManoj
Copy link

@sandy081 Still able to reproduce the issue.
Here's the log and system info you requested.

2025-03-09 01:06:35.944 [info] [Shared] Getting Manifest... ms-python.autopep8
2025-03-09 01:06:36.268 [info] [Shared] Installing extension: ms-python.autopep8 {"pinned":false,"productVersion":{"version":"1.99.0-insider","date":"2025-03-07T05:06:46.743Z"},"operation":3,"isApplicationScoped":false,"profileLocation":{"$mid":1,"external":"vscode-userdata:/home/username/.vscode-insiders/extensions/extensions.json","path":"/home/username/.vscode-insiders/extensions/extensions.json","scheme":"vscode-userdata"},"installOnlyNewlyAddedFromExtensionPack":true}
2025-03-09 01:06:37.700 [info] [Shared] Getting Manifest... ms-python.python
2025-03-09 01:06:38.377 [info] [Shared] Extension signature verification result for ms-python.autopep8: UnknownError. Executed: true. Duration: 25ms.
2025-03-09 01:06:38.387 [error] [Shared] Error while installing the extension ms-python.autopep8 Signature verification failed with 'UnknownError' error. vscode-userdata:/home/username/.vscode-insiders/extensions/extensions.json
2025-03-09 01:06:38.388 [error] [Shared] [uncaught exception in sharedProcess]: Signature verification failed with 'UnknownError' error.: SignatureVerificationInternal: Signature verification failed with 'UnknownError' error.
    at uh.ub (file:///opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-utility/sharedProcess/sharedProcessMain.js:74:63762)
    at async uh.tb (file:///opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-utility/sharedProcess/sharedProcessMain.js:74:62340)

Help --> About info:

Version: 1.98.0-insider
Commit: 44028decf1ca81a0cbf99a65ab72cca6735449f2
Date: 2025-02-14T05:04:46.748Z
Electron: 34.1.0
ElectronBuildId: 10990655
Chromium: 132.0.6834.194
Node.js: 20.18.1
V8: 13.2.152.38-electron.0
OS: Linux x64 6.12.12-2-MANJARO

Linux distro is Manjaro KDE 25.0.0.

@sandy081
Copy link
Member

You are on old insider and which is not logging some necessary information. Can you please update to latest insiders and retry?

@HearseDev
Copy link

HearseDev commented Mar 15, 2025

Got a log from MacOS to help with this issue:

Machine Information:
Apple M2 Pro
15.3.1 (24D70)
System Integrity Protection status: disabled

VSCode Information:
Version: 1.98.2 (Universal)
Commit: ddc367e
Date: 2025-03-12T13:32:45.399Z (3 days ago)
Electron: 34.2.0
ElectronBuildId: 11161602
Chromium: 132.0.6834.196
Node.js: 20.18.2
V8: 13.2.152.36-electron.0
OS: Darwin arm64 24.3.0

Log level set to trace:

2025-03-15 15:32:16.747 [trace] [Shared] Extension signature verification output for github.copilot:

2025-03-15 15:32:16.748 [error] [Shared] Error while installing the extension github.copilot Signature verification failed with 'UnknownError' error. vscode-userdata:/Users/redacted/.vscode/extensions/extensions.json
2025-03-15 15:32:16.749 [error] [Shared] [uncaught exception in sharedProcess]: Signature verification failed with 'UnknownError' error.: SignatureVerificationInternal: Signature verification failed with 'UnknownError' error.
    at fh.ub (file:///Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-utility/sharedProcess/sharedProcessMain.js:74:63564)
    at async fh.tb (file:///Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-utility/sharedProcess/sharedProcessMain.js:74:62108)
2025-03-15 15:32:17.768 [trace] [Network] resolveShellEnv(): running (macOS/Linux)

Note: Reproducing inside VSCode insider with default settings produces the same log on log level set to trace.

Here's that log:
Version: 1.99.0-insider
Commit: 2c7a028
Date: 2025-03-14T05:04:14.195Z
Electron: 34.3.2
ElectronBuildId: 11161073
Chromium: 132.0.6834.210
Node.js: 20.18.3
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.3.0

2025-03-15 15:46:43.931 [trace] [Shared] Verifying extension signature for ms-toolsai.jupyter-keymap...
2025-03-15 15:46:43.954 [info] [Shared] Extension signature verification result for ms-toolsai.jupyter-keymap: UnknownError. Internal Code: 137. Executed: true. Duration: 25ms.
2025-03-15 15:46:43.955 [trace] [Shared] Extension signature verification output for ms-toolsai.jupyter-keymap:

2025-03-15 15:46:43.956 [error] [Shared] Error while installing the extension ms-toolsai.jupyter-keymap Signature verification failed with 'UnknownError' error. vscode-userdata:/Users/redacted/.vscode-insiders/extensions/extensions.json
2025-03-15 15:46:43.957 [error] [Shared] [uncaught exception in sharedProcess]: Signature verification failed with 'UnknownError' error.: SignatureVerificationInternal: Signature verification failed with 'UnknownError' error.
    at fh.wb (file:///private/var/folders/jv/7dv2r9c90k3d6h5_nwgfcj6w0000gn/T/AppTranslocation/DF8BC2A4-DE62-4123-BB5C-BE8EDAAEB3B2/d/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/code/electron-utility/sharedProcess/sharedProcessMain.js:74:64166)
    at async fh.vb (file:///private/var/folders/jv/7dv2r9c90k3d6h5_nwgfcj6w0000gn/T/AppTranslocation/DF8BC2A4-DE62-4123-BB5C-BE8EDAAEB3B2/d/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/code/electron-utility/sharedProcess/sharedProcessMain.js:74:62630)
2025-03-15 15:46:45.749 [trace] [Network] resolveShellEnv(): running (macOS/Linux)

@NirmalManoj
Copy link

NirmalManoj commented Mar 17, 2025

@sandy081 Thanks, I tried after updating to 1.99.0. The issue got resolved automatically.

Version: 1.99.0-insider
Commit: b59ae26ad3882edfec6493e280784f5395978dbd
Date: 2025-03-13T09:44:45.504Z
Electron: 34.3.2
ElectronBuildId: 11161073
Chromium: 132.0.6834.210

@sandy081
Copy link
Member

@HearseDev You seems to have a different issue - Internal Code: 137. Can you please file separate issue with logs?

@sandy081 sandy081 modified the milestones: March 2025, April 2025 Mar 23, 2025
@sandy081 sandy081 modified the milestones: April 2025, May 2025 Apr 28, 2025
@franzos
Copy link

franzos commented May 28, 2025

I'm having a similar issue; Logs after clicking "Update":

log.ts:460   ERR lock() request could not be registered.: InvalidStateError: lock() request could not be registered.
error @ log.ts:460
error @ log.ts:565
error @ logService.ts:51
mc @ workbench.ts:116
(anonymous) @ workbench.ts:97
onUnexpectedError @ errors.ts:65
mt @ errors.ts:110
(anonymous) @ workbench.ts:90
log.ts:460   ERR SignatureVerificationInternal: Signature verification failed with 'ENOENT' error.
    at yh.xb (file:///gnu/store/9rhs4wjaz1vxxgbds6znbf81hljn2hvm-vscode-1.100.2/opt/vscode/resources/app/out/vs/code/electron-utility/sharedProcess/sharedProcessMain.js:74:64415)
    at async yh.wb (file:///gnu/store/9rhs4wjaz1vxxgbds6znbf81hljn2hvm-vscode-1.100.2/opt/vscode/resources/app/out/vs/code/electron-utility/sharedProcess/sharedProcessMain.js:74:62886)
error @ log.ts:460
error @ log.ts:565
error @ logService.ts:51
run @ extensionsActions.ts:106
run @ extensionsActions.ts:1043
await in run
u @ actions.ts:194
run @ actions.ts:185
onClick @ actionViewItems.ts:173
(anonymous) @ actionViewItems.ts:153
log.ts:460   ERR Signature verification failed with 'ENOENT' error.: SignatureVerificationInternal: Signature verification failed with 'ENOENT' error.
    at yh.xb (file:///gnu/store/9rhs4wjaz1vxxgbds6znbf81hljn2hvm-vscode-1.100.2/opt/vscode/resources/app/out/vs/code/electron-utility/sharedProcess/sharedProcessMain.js:74:64415)
    at async yh.wb (file:///gnu/store/9rhs4wjaz1vxxgbds6znbf81hljn2hvm-vscode-1.100.2/opt/vscode/resources/app/out/vs/code/electron-utility/sharedProcess/sharedProcessMain.js:74:62886)
error @ log.ts:460
error @ log.ts:565
error @ logService.ts:51
mc @ workbench.ts:116
(anonymous) @ workbench.ts:97
onUnexpectedError @ errors.ts:65
mt @ errors.ts:110
(anonymous) @ workbench.ts:90

Release

Version: 1.100.2
Commit: 848b80aeb52026648a8ff9f7c45a9b0a80641e2e
Date: 2025-05-14T21:47:40.416Z
Electron: 34.5.1
ElectronBuildId: 11369351
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Linux x64 6.12.29

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug extension-signature Issues related to extension signature verification
Projects
None yet
Development

No branches or pull requests