FAQ TFORMer Server
Crash in PrintServer.exe after security update KB3170455
Crash in PrintServer.exe after security update KB3170455
Problem
The PrintServer.exe process terminates periodically during printer initialization. This leads to a restart loop. You need to stop the TECLauncher service or rename the TFORMer Server spool directory (this automatically sets the PrintServer to passive) to stabilize the system.
Cause: When printing to network printers (e.g. to \\server\printer), the Windows Spooler automatically downloads and installs the required printer drivers in the background. After installing KB3170455, new rules for driver installation apply, which can cause a crash in PrintServer.exe (especially with older, unsigned drivers).
Workarounds and solutions
- A quick workaround for production use would be to uninstall the KB3170455 security patch. Alternatively, you can disable the printers in the spool that trigger the crash (activate spools step by step, or use tfprint separately to identify the problematic printer).
- If you use TFORMer Server 6.1.3, you can request a hotfix from our Support. This fixes the crash and restart loop issue — however, you still won't be able to print on the affected printers. As an alternative to the hotfix, you can update to the latest TFORMer Server version (> 6.1.4), which also includes the fix.
- Update the printer driver and make sure to install one that either ships with Windows or is available as a digitally signed printer driver package.
- For correct driver installation, the user account under which TFORMer Server runs should have local admin rights.
The problem does not necessarily occur immediately after installing KB3170455. Systems that already have a driver installed can continue to work until it is updated or reinstalled. Printers that trigger the problem usually do not have "Packaged" status (see printer management, driver tab).