You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AppLocker update files are not correctly signed. When running PortMaster on Windows 11 Pro with AppLocker it should be possible to define an issuer rule in AppLocker for update files (C:\ProgramData\Safing\Portmaster\updates\windows_amd64). This is currently not possible as the update .exe files do not have a working signature / issuer information. When trying to add the update exe file to AppLocker rules (e.g. C:\ProgramData\Safing\Portmaster\updates\windows_amd64\notifier\portmaster-notifier_v0-3-6.exe) the following error is shown. "The issuer information cannot be extracted from the .exe"
The text was updated successfully, but these errors were encountered:
Greetings and welcome to our community! As this is the first issue you opened here, we wanted to share some useful infos with you:
🗣️ Our community on Discord is super helpful and active. We also have an AI-enabled support bot that knows Portmaster well and can give you immediate help.
📖 The Wiki answers all common questions and has many important details. If you can't find an answer there, let us know, so we can add anything that's missing.
griesi007
changed the title
Portmaster no
Portmaster - not compatible with Applocker on Windows 11 Pro
Mar 9, 2024
AppLocker update files are not correctly signed. When running PortMaster on Windows 11 Pro with AppLocker it should be possible to define an issuer rule in AppLocker for update files (C:\ProgramData\Safing\Portmaster\updates\windows_amd64). This is currently not possible as the update .exe files do not have a working signature / issuer information. When trying to add the update exe file to AppLocker rules (e.g. C:\ProgramData\Safing\Portmaster\updates\windows_amd64\notifier\portmaster-notifier_v0-3-6.exe) the following error is shown. "The issuer information cannot be extracted from the .exe"
The text was updated successfully, but these errors were encountered: