Jester

Okay this exact problem is happening to me starting yesterday afternoon it looks like. Gmail will not synch with in Windows 10 Mail. It brings up a that error after trying to synch for a while. I have disabled the IMAP and IMAPS checker and it does fix this (or was it disabling checking for WIndows Mail I should check my settings again). Not the best solution with no email protection. How do I fix this for real?

Yeah I wanted to see how the upgrade went first. I wanted to save some time but in the end I didn't ;-) I usually worry about tools like you mention above for the reasons you mention (they are just more spyware).

Okay... I couldn't take it anymore so I reinstalled Windows 10 doing a fresh install (formatted HD). I am glad I did as the laptop boots up a lot quicker and the Nod32 issue seems to have disappeared. I will know more in a few days as I put back on all the software, etc. I use. So from this I am assuming that Nod32 was conflicting with something that was either a hold over from my Windows 7 install or installed during the upgrade of Windows 10. To hopefully prevent any issues before the Windows 10 install I did uninstall a lot of old software and features that came with the Laptop and Windows 7. Most of it was bloat ware and features I never really used (from Asus).

I just tried using Autoruns and changing the 2 startup entries before reinstalling Nod32. It didn't help. Next I will try the following when I get some more time: (it takes some time because of all the crashes before I can actually get the dang laptop booted and me logged in) 1, disable real-time protection 2, disable protocol filtering 3, rename C:\Windows\System32\drivers\eamonm.sys in safe mode 4, rename C:\Windows\System32\drivers\ehdrv.sys in safe mode

Okay. I will give that a shot and report back the results. Thanks Tom

Windows defender was disabled. I had to enable it through the control panel after I finished uninstalling Nod32 for the last time. Not sure what you are referring to with its 2 startup entries?

Okay thanks. I will try this tomorrow and get back to you on which one seems to be causing my problem.

I recently upgraded my laptop from Windows 7 to Windows 10 Home. At the time I was using version 8 of Nod 32 but not the latest version. Windows 10 upgraded fine but I was plagued with either the screen freezing (or blue screen) near the end of the bootup, at the login screen, or during logging in while the rest of the startup applications bootup. If I got through all of that half the time the Windows taskbar would stop responding within a minute or so of using Windows. I would say about 7 out of 10 times of me booting up my laptop I would encounter problems. After looking over several things and upgrading a few applications I narrowed it down to Nod32. Even after upgrading to the latest version I have run into these problems. I have installed Nod32 3 times and still have the same problems. During one of my uninstalls there was a problem with the taskbar freezing so Nod32 didn't complete the uninstall so I did have to use the special uninstall program provided by Eset which worked fine and I was able to reinstall Nod32. I currently have Nod32 uninstalled and am running Windows Defender. I have had no problems with Windows 10 during use or booting up with Defender running and Nod32 uinstalled. How should we go about getting this issue figured out? I want to upgrade my other desktops but all of them use Nod32 and I don't want to run into the same situation. Thanks Tom

I currently have the Email client prevention disabled. I re-enabled it and unchecked "Enable POP3 protocol checking" and just tried sending the email again and it is the correct size I also rescanned the sent email message and it scanned fine So it appears to be the pop3 protocol filtering for just certain emails that causes the problem. Eset support just replied to my case today. I have sent them the log files they requested (along with the email samples). I guess I will continue on with them but I will post the solution here for others when one is found. Thanks for the reply Tom

I have had to disable my scanning of emails by Eset Anti Virus (version 8 and I am using Windows 7). It automatically scans the email in Outlook 2010 but for some reason starting a few mornings (I haven't updated Outlook or Windows recently) emails from my websites (using php to send the emails) on my local network went from 5kb to 3mb (as reported by Outlook). These are text emails with no attachments and should be around 3kb. When I attempted to open these emails Outlook crashes. This is happening both on my Desktop and laptop (very similar setups). If I send and receive emails from the same accounts through outlook (not through the website using PHP) they are the proper size. If these emails sent from my website are sent to outside email accounts they are fine and the correct size. If I disable Eset antivirus outlook retrieves the emails fine and they are the correct size. If I then rescan these emails with Eset no problems are reported and the size of the emails stay the same. For some reason it appears that Eset Antivirus when it scans incoming email over pop3 it increases the size of certain emails and makes it so outlook cannot open those emails. This just started Monday morning around 8am Do you know what is happening (BTW I have tagging of emails disabled unless a virus is found) These are also pop3 email accounts and pop3 filter is enabled in the Advanced setup of Eset antivirus. I have no other virus scanner running except Windows Defender Thanks Tom I also sent this messge to your Tech Support on Monday but no one has contacted me beyond the initial message. I can send samples of the before and after emails if need be.