Change:
<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: It requires at least the remote SSH extension to be enabled due to the nature of the bug, all other extensions can be disabled/uninstalled. <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: 1.75.0 OS Version: Local Windows 10 21H2 / Remote Fedora 29 Steps to Reproduce: -up VS Code with Remote SSH Python Extension in to Remote SSH error message and get asked to download manually opens link: the following error text: it's because the extension hasn't been published for 2023.2.0 for Linux yet so try installing older version same error and browser instead opens this link: very similar error text: I have had to revert to 1.74.3 where I am not getting this error so can I continue to work, but if you need me to test things again I can install 1.75.0 again and retest.
I am having the same issue since upgrading to VSCode 1.75.0. When trying to update the Python extension on the remote server I get an with the log Trying to download manually brings me to the as reported above. I am getting the same errors for the Jupyter extension. I could successfully update the extensions locally. VSCode: 1.75.0 OS: local openSUSE Tumbleweed / remote Red Hat Enterprise Linux 8.5 (Ootpa)
I have the same problem.
Same issue. Downgraded VSCode to 1.74.3 to restore functionality. VS Code Version: 1.75.0 OS Version: Local: macOS Monterey 12.6.3 Remote: Amazon Linux 2 w/ Kernel 5.4
Triaging this issue I am unsure if the initial post with the error message of is the same as the error with the message . Therefore all conversation on the issue should be moved to this other issue: Thanks
This issue is related to target platform and not related to sign verification.
Yes, I am initial poster, I also get the signature untrusted error. I assumed the two errors had the same underlying cause, i.e. when VS Code made the web request it got the above error which does not have the signature of the extension and therefore throws a red herring of "Untrusted: Signature", then when VS Code prompts you to download it manually you can see the actual underlying error. This is why I posted the latter error and not the former error. But if you are convinced they are two separate errors then it makes sense to track them separately. But be aware I got both errors, and everyone else who has posted seems to have also got both errors.
Thanks for the info It seems that the root cause is signature error for you too. Being said that the manual download shall work. Can you please share the link you are using to download the VSIX?
From the marketplace web page. Version History -2023.3. -Download Manual download and install work for me.
As per my original post the link that VS Code to manually download the extension is: Which gives this error:
It seems VS Code is generating an invalid download link. Updating this issue for fixing the update link. For signing related, please refer to
I'm not sure how to get this, are there repro steps?
To verify Open extensions view Browse for eslint extension (any non platform specific extension) Disable network connection Click on install, you shall see a prompt to Download Manually Enable network connection and click on that Download Manually button Make sure the VSIX is downloaded/

Discussion:
return undefined; } let targetPlatform = this.extension.gallery.properties.targetPlatform; <del> if (this.extensionManagementServerService.remoteExtensionManagementServer) { </del> <ins> if (targetPlatform !== TargetPlatform.UNIVERSAL && targetPlatform !== TargetPlatform.UNDEFINED && this.extensionManagementServerService.remoteExtensionManagementServer) { </ins> try { const manifest = await this.galleryService.getManifest(this.extension.gallery, CancellationToken.None); if (manifest && this.extensionManifestPropertiesService.prefersExecuteOnWorkspace(manifest)) {