After installing NOD32 on several work stations in the office, about 3 of them have now exhibited a problem with the print spooler service. All systems have a printer installed as a local printer on a standard tcp/ip port. The systems in question, when all printer drivers are removed, will function normally. You can add regular local printers all day long. As soon as you try to add back the network printer (local printer, standard tcp/ip port). The spooler service app errors. These systems are running on the same OS version and printer driver versions as systems that have no issues: Problem System Example: Error: Spooler SubSystem App has encountered a problem and needs to close. We are sorry for the inconvenience. Error Details: szAppName : spoolsv.exe szAppVer : 5.1.2600.2696 szModName : imon.dll szModVer : 220.127.116.11 offset : 0000f259 NOD32 antivirus system information Virus signature database version: 1.1809 (2006101 Dated: Wednesday, October 18, 2006 Virus signature database build: 8202 Information on other scanner support parts Advanced heuristics module version: 1.037 (20060926) Advanced heuristics module build: 1122 Internet filter version: 1.002 (2004070 Internet filter build: 1013 Archive support module version: 1.050 (20060926) Archive support module build version: 1176 Information about installed components NOD32 for Windows NT/2000/XP/2003/x64 - Base Version: 2.51.26 NOD32 for Windows NT/2000/XP/2003/x64 - Internet support Version: 2.51.26 NOD32 for Windows NT/2000/XP/2003/x64 - Standard component Version: 2.51.26 Operating system information Platform: Windows XP Version: 5.1.2600 Service Pack 2 Version of common control components: 5.82.2900 RAM: 383 MB Processor: x86 Family 6 Model 8 Stepping 3 (803 MHz) One of the non-problematic systems has the exact same version of XP, and the exact same printer driver installed. The only work around so far is to share the printer on a working system and connect the non-working system to this printer via the network share. This works fine, but is not optimal. I have also tried to disable the imon module on a whim as that is the dll that appears to be related to the problem, no luck. Any ideas anyone? I have submitted a similar request for support to eset, but I thought I would go ahead and post here too, if they get back to me first I will post their answer in case it can help someone here out.