Cannot Print in MS Edge with NOD32 V9

[zenmota 0]

I have Windows 10 Pro Build 10240 (an upgrade from Windows 8.1) After installing NOOD32 Antivirus V9.0.318.0 I am unable to print from MS Edge web browser. I cannot print to the printer, to a pdf file or anything else. I can print fine from IE 11, Word, Notepad or anything else. Also, I could print form MS EDGE fine with NOD32 Antivirus V8. I have added C:\Windows\System32\spoolsv.exe to the exclusions and added C:\Windows\System32\spoolsv.exe to Protocol filtering to excluded applications and this did no fix the problem. However, if I Pause Protection (for whatever time) I can print fine from MS Edge. Also, If I tried to print from MS Edge with NOD32 turned on and it's not printing, If I Pause Protection it will start printing. It is like with NOD32 turned on, the file to print is stuck in the print spooler. Pretty sure it is not a printer driver problem as I cannot print to a PDF file in MS Edge with NOD32 turned on either. But I do have a Brother MFC-J5520DW printer with latest drives. It would seem that there is a problem with NOD32 Antivirus and the printing in MS Edge.

 

Please advise if there is a fix. If not, I n\may want to go back to using V8 of NOD32.

 

Thanks...

 

 

[shocked 60]

i tried to print a site to pdf from Edge and it automatically saved it to my documents folder.

 

go to the classic control panel > uninstall a program > find the eset entry, and double click it. then select to repair the installation in case something wasn't configured correctly. after it finishes reboot and try again.

[zenmota 0]

Tried the Repair option and reboot. Did not fix the problem. Only way I can print from MS Edge is to Pause Protection in NOD32 V9, then it works fine. I even tried uninstalling doPDF thinking maybe it was the problem, it wasn't. Tried to print to PDF using the MS Print to PDF in Edge. Would not work unless I Pause Protection in NOD32  V9.

 

Like I said, NOD32 V8 worked fine. Was able to print in EDGE. Not sure what the problem is.

 

Thanks for any help

 

 

 

[threepwood 0]

Same thing has been happened to me on 2 workstations that have NOD32 Antivirus (9.0.318.0) installed on Windows 10.

 

Printing a small .jpg or .pdf file, be it from Google Chrome or File Explorer causes havoc on the printer spooler and takes forever to print. Rebooting, pausing NOD32 protection and printing the same file again works normally as should (almost instantaneously).

 

Just hope support can have a look at this since this is really annoying.

[zenmota 0]

I sent email to Eset about the printing problem in MS Edge. ESET doesn't seem to do a very good job about replying to problems in the forums. Here is what they sent back in reply:

 

1. Open the main ESET program

 

 

2. Press the 'F5' to get to the Advanced setup page

 

3. Expand 'Antivirus' > 'Real time protection'

 

4. Under 'Scan on', click on the box next to 'File Open' to disable it

 

5. Press 'OK' to save and close the Advanced setup page

 

 

Unfortunately we're received a couple of reports in regards to this issue recently and we've opened a ticket with our developers to investigate. Disabling 'File Open' will not open you up for vulnerability as HIPS and Real-time protection will still actively protect you.

 

I would recommend leaving that disabled or going back down to version 8 for the time being while our developers investigate further.

 

This does fix the problem and you can print fine from Edge with the "File Open" disabled.

 

Hope this helps.....

Edited November 12, 2015 by Marcos

[Julianinho 1]

I tried your fix zenmota but it didn't work for me, and i this topic : hxxp://support.eset.com/kb5675/not work for me to.

It not possible to scan and print on wifi since Eset v9.

[Marcos 5,074]

4. Under 'Scan on', click on the box next to 'File Open' to disable it

 

This is dangerous, please nobody do this or your real-time protection will not protect you from threats that could make it to your disk. 

Rather than this, downgrade to v8 until a new service build of v9 becomes available for the public.

[zenmota 0]

To pavilion, Maybe the fix did not work for you because your printer is connected wireless and mine is connected USB? Just know the disabling "File Open" option worked for me.

 

To ESET support people, maybe you people should communicate with each other. I emailed your tech support (because I got no reply here!) about the printing problem. I was told my a Technical Support Level 2 person to disable the "File Open" option and it WOULD NOT leave me open to vulnerability. Here is a paste of the whole email:

 

An ESET Customer Care Representative has updated this case with the following information:

Hello Dennis,

Thanks for your reply. Below is additional information to help resolve your issue.

Unfortunately we're received a couple of reports in regards to this issue recently and we've opened a ticket with our developers to investigate. Disabling 'File Open' will not open you up for vulnerability as HIPS and Real-time protection will still actively protect you.

I would recommend leaving that disabled or going back down to version 8 for the time being while our developers investigate further.

For more information and support for ESET products, please visit the ESET Knowledgebase at hxxp://kb.eset.com.


Please tell us how we are doing. At the bottom of this email, you will see a link to our customer satisfaction survey. We appreciate your feedback!

Thank you for using ESET security products,
ESET Customer Care
North America

------------------------------------------------------------------------------
ESET Knowledgebase | articles | videos | manuals | support
hxxp://kb.eset.com


Is your Android device protected by ESET?
https://play.google.com/store/apps/details?id=com.eset.ems2.gp&intcmp=zapml-ems

 

 

 

Mychal
Technical Support Level 2
Customer Care

 

And how about not releasing a program that is not full of bugs? I call not being able to print a serious problem and should be fixed quickly. And ESET's response of "well, we have this new version but it doesn't work so just go back to using the old version" isn't acceptable either.

 

Sorry, but after NOD32 V9 I am really considering looking for another anti-virus programs.

 

Thanks......

[zenmota 0]

In my last post I meant to say:

 

To Julianinho (not to pavilion_alex), Maybe the fix did not work for you because your printer is connected wireless and mine is connected USB? Just know the disabling "File Open" option worked for me.

 

 

Also, I put the xps in the Exclusions under Real-time file system protection and then expand Threatsense Parameters. I then turned on The "File Open" option and was able to print. Take the xps out of The exclusions and I could not print from MS Edge. Guess this is better than turning off the "File Open" option.

 

Thanks...
 

 

[Julianinho 1]

Yes for me it doesn't work, the main proble fo rme it the scan on wifi.

I think i wait to a fix for the program in few day.

[BJB 1]

Has this issue been resolved?  I just spent the better part of an afternoon trying to figure this out during a new windows install....thought it was the Brother printer driver and thankfully found this thread.

 

Can someone form ESET please pro-actively post here when it is fixed?  I also excluded the XPS file type just to get printing to work from Microsoft Edge.

 

Thanks,
BJB
​

[Marcos 5,074]

If temporarily disabling real-time protection helps, I'd suggest downgrading to v8 until a new service release of v9 becomes available. It should address this issue as well.

[BJB 1]

What worked is excluding the XPS file type as noted above. Everything is now working.  I would prefer not to mess with it and hopefully a new version comes out quickly.  But again, hope that is posted because how do we know when it is fixed?

 

I also recall in V8 a setting where you could download and install definitions automatically but have program upgrades prompt you. Did that option go away? Is it all or nothing now?
Thanks,

 

BJB
​