Repository navigation
Pet.exe not correctly signed #1559
Description
Activity
Deurslingeraar you are on a vscode release right? What version are you on?
Raymond Zhao (@rzhao271) I thought we addressed this here?
Eleanor Boyd (@eleanorjboyd) We are on version : 1.124.0. Removed the second path that i listed copied that out of the other ticket.
I confirmed the pipeline regressed with microsoft/python-environment-tools#374.
Reacted by Deurslingeraar- added this to the milestone
on Jun 15, 2026 Raymond Zhao (@rzhao271) In what release can I expect the new signed version ?
- added a commit that references this issue
on Jun 17, 2026 The fix is out in version 1.36.0 of the extension.
Looks correct
Reacted by DeurslingeraarI will update the extention and whitelist it.
It's now correctly whitelisted and ticket can be closed.
- locked as resolved and limited conversation to collaborators
on Jul 30, 2026
We are currently implementing Application Control for Business and some of our users use the Python vscode extension.
Now we want to whitelist pet.exe but to our surprise it was signed without ProductName see screenshot :
Path : C:\Users\myusername.vscode\extensions\ms-python.vscode-python-envs-1.30.0-win32-x64\python-env-tools\bin\Pet.exe
For now this is a blocking issue since we cannot do proper whitelisting without allowing the full 2011 certificate which means that everything can be installed that has the 2011 MS certificate.
Can you please sign this .exe properly with ProductName in your future deployments.
We also reported this in the past for pet.exe on a different location : microsoft/python-environment-tools#272