skip to Main Content

I’ve been having this problem for a while, does anyone have a solution?

It’s not a DNS error, Ipv6 or something like that, and the command to turn off certified check doesn’t work anymore.

I’m literally trying to download official Microsoft Plugins and I get a certificate error
Like:

2023-03-22 17:08:35.669 [error] SignatureIntegrityCheckFailed,SignatureIntegrityCheckFailed,SignatureIntegrityCheckFailed,SignatureIntegrityCheckFailed,SignatureIntegrityCheckFailed,SignatureIntegrityCheckFailed: Error: SignatureIntegrityCheckFailed,SignatureIntegrityCheckFailed,SignatureIntegrityCheckFailed,SignatureIntegrityCheckFailed,SignatureIntegrityCheckFailed,SignatureIntegrityCheckFailed
    at vscode-file://vscode-app/c:/Users/USER/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:88:89716
    at Array.reduce (<anonymous>)

Really need some workable solution.

I’ve tried things related to WiFi and commands in the Program but nothing worked, not that they’ve mentioned so far.
It should just install normally and work

2

Answers


  1. VS Code 1.77 includes a "patch" (more like a workaround I think) for this, and the maintainers are working on fixing the underlying issues in the meantime. See the release notes, which state:

    Extension installation not blocked by signature verification failures

    Extension signature verification is incorrectly reporting errors for a small number of valid extensions and preventing them from being installed. These failures are caused by bugs in the VS Marketplace and VS Code and we are actively working on fixes. In order to unblock extension use, VS Code will install extensions even if signing verification fails. We will reenable signature verification checking once VS Marketplace issue #619 is fixed, most likely in our next Stable release.

    See also this related issue ticket: update/install extensions got the SignatureIntegrityCheckFailed error
    #173250
    .

    Login or Signup to reply.
  2. In my case, the issue was resolved by running vscode as an administrator, as the standard user did not have sufficient permissions to read the file that indicates the path of the error.

    Login or Signup to reply.
Please signup or login to give your own answer.
Back To Top
Search