Issue installing the extension for Powershell in VSC (multiple users and PC's)

[JoaTheBalboa]

Prerequisites

• I have written a descriptive issue title.
• I have searched all open and closed issues to ensure it has not already been reported.
• I have read the troubleshooting guide.
• I am sure this issue is with the extension itself and does not reproduce in a standalone PowerShell instance.
• I have verified that I am using the latest version of Visual Studio Code and the PowerShell extension.
• If this is a security issue, I have read the security issue reporting guidance.

Summary

After formatting my workstation, i am having issues regarding the installation of the Powershell extension.
I have tried several ways of installation, including manually through VSIX.
Yet the installation keep failing.

I thought it might be an issue with my pc. However, my Co-worker have a similar experience on his computer with his AD-credentials. And we have a third pc we have testet this on with yet another user.
So 3 users on 3 different pc's alle get this error:

2023-04-21 10:06:36.886 [error] CorruptZip: end of central directory record signature not found
at yt.download (c:\Users\aky3my\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\code\node\sharedProcess\sharedProcessMain.js:93:141)
at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
at async j.y (c:\Users\aky3my\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\code\node\sharedProcess\sharedProcessMain.js:93:20893)
at async j.h (c:\Users\aky3my\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\code\node\sharedProcess\sharedProcessMain.js:93:18962)
2023-04-21 10:06:36.891 [error] end of central directory record signature not found: CorruptZip: end of central directory record signature not found
at yt.download (c:\Users\aky3my\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\code\node\sharedProcess\sharedProcessMain.js:93:141)
at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
at async j.y (c:\Users\aky3my\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\code\node\sharedProcess\sharedProcessMain.js:93:20893)
at async j.h (c:\Users\aky3my\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\code\node\sharedProcess\sharedProcessMain.js:93:18962)

PowerShell Version

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




Name                           Value
----                           -----
PSVersion                      5.1.19041.2673
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.19041.2673
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

Visual Studio Code Version

1.77.3
704ed70d4fd1c6bd6342c436f1ede30d1cff4710
x64

Extension Version

PowerShell
v2023.3.3

Steps to Reproduce

N/A

Visuals

No response

Logs

No response

[andyleejordan]

Duplicate of #4474. You most likely have a corporate firewall / VPN (last instance was Palo Alto) that is intentionally corrupting the VSIX as it's downloaded to be installed. We can't control that, and it's not a great situation as it keeps leading to this. Disable your VPN and try again?

[JoaTheBalboa]

Duplicate of #4474. You most likely have a corporate firewall / VPN (last instance was Palo Alto) that is intentionally corrupting the VSIX as it's downloaded to be installed. We can't control that, and it's not a great situation as it keeps leading to this. Disable your VPN and try again?

Sorry, you are absolutely right that i missed that case.
You are probably right about the firewall issue, since all three users and pc's where on the same network in our corporation.
Thanks for the answer and for pointiing towards the existing case.

[andyleejordan]

If you get more details, I would love to have them. I don't know how to remedy this, it clearly means getting in touch with the team behind the VPN/firewalls and asking them to stop blocking the extension, but I have no contacts with any of them yet.

[ghost]

This issue has been marked as duplicate and has not had any activity in a day. It has been closed for housekeeping purposes.