This page covers how to install and uninstall the Portmaster on Windows 7, 8 and 10. The installer is the same for all supported Windows versions.
Please note that we currently only support the 64bit CPU Architecture, which is the current main standard. In case of Windows 7, you require the 2015 security update KB3033929 for correctly verifying driver signatures.
The Portmaster is installed to
%PROGRAMDATA%\Safing\Portmaster, which resolves to
C:\ProgramData\Safing\Portmaster on most systems.
In order to reduce confusion, a symlink to this location is placed in the usual install location
The Portmaster UI and the Notifier are added to the Start Menu at
Safing\Portmaster. The Notifier is added to Autostart.
The uninstaller is registered at
In order to integrate with the Windows Notification Center, a special ID is placed in the registry to link back to the Notifier at
The Portmaster Core Service is registered as a system service that starts automatically on boot and is named
In order to gain the required system integration for the Portmaster to function properly, the Installer needs to deactivate the system’s DNS Cache Service - the Portmaster replaces this service. This may break/impair some other software that depends on special functionality of said service.
This is done by setting the registry key
4 and rebooting.
You can easily uninstall the Portmaster by using the system preferences or by executing the
portmaster-uninstaller.exe, which you can find in
The uninstaller reverts all steps mentioned above and also requires a reboot afterwards.
Notifications are not working on Windows 7 and 8.
Microsoft added a notification service that supports actions with Windows 10 so Portmaster’s notifications won’t work on Windows 7 or 8. We will push alternatives as we find solutions and time to do so. In the meantime we recommend not to use the “prompt” action as a default when running on Windows 7 or 8.
Portmaster fails to restart
In some cases the Portmaster will fail to restart, because the Portmaster Kernel Extensions cannot be loaded and returns the error code 0x422. This stems from a known issue in Windows, where system services are not completely removed when something is monitoring the system services. When the Portmaster restarts, it is then unable to initialize the Kernel Extension, because the system thinks it is still unloading.
If you experience this issue, please follow this workaround:
Quoting from https://stackoverflow.com/a/20565337
There may be several causes which lead to the service being stuck in “marked for deletion”.
SysInternals’ Process Explorer is opened. Closing it should lead to automatic removal of the service.
Microsoft Management Console (MMC) is opened. To ensure all instances are closed, run
taskkill /F /IM mmc.exe.
Services console is opened. This is the same as the previous point, since Services console is hosted by MMC.
Event Viewer is opened. Again, this is the same as the third point.
Someone else is logged into the server and has one of the previously mentioned applications opened.
An instance of Visual Studio used to debug the service is open.
Portmaster Core does not start at boot
While we haven’t experienced this in a while, it might just happen that the Portmaster will not start at boot, although it is configured to do so. If that is the case, you can check its status in the “Services” Desktop App. There, search for the Service “Portmaster Core” and inspect and start it as needed.