Zardoc 4 Posted December 12, 2019 Share Posted December 12, 2019 (edited) Hi all,  Created a new windows install. Added NOD32 latest version 13.0.24 (new install) and I get this message every time. BOTH ANTIVIRUS ARE DISABLED 😥  I uninstalled and reinstalled but to no avail.😩 Edited December 12, 2019 by Zardoc Link to comment Share on other sites More sharing options...
itman 1,038 Posted December 12, 2019 Share Posted December 12, 2019 Do you have any other security software installed other than Eset? Also with Eset uninstalled, does WD Security Center show that WD is active? Link to comment Share on other sites More sharing options...
Zardoc 4 Posted December 13, 2019 Author Share Posted December 13, 2019 4 hours ago, itman said: Do you have any other security software installed other than Eset? Also with Eset uninstalled, does WD Security Center show that WD is active? Nope and Yes. Link to comment Share on other sites More sharing options...
Zardoc 4 Posted December 13, 2019 Author Share Posted December 13, 2019 (edited) Message change. Still there but not as often. This is a total new install. I don't see that with my main machine with updated version. Edited December 13, 2019 by Zardoc Thought it was gone Link to comment Share on other sites More sharing options...
itman 1,038 Posted December 13, 2019 Share Posted December 13, 2019 9 hours ago, Zardoc said: I don't see that with my main machine with updated version. Are both devices running the same Win 10 version; e.g. Win 10 x(64) 1909? Link to comment Share on other sites More sharing options...
itman 1,038 Posted December 13, 2019 Share Posted December 13, 2019 Also checkout this posting: https://forum.eset.com/topic/20839-eset-v12229-bug/?do=findComment&comment=102268 . Make sure the two Window Defender Antivirus services are set to Manual. Only the Window Defender Firewall service should be set to Automatic. Link to comment Share on other sites More sharing options...
Zardoc 4 Posted December 13, 2019 Author Share Posted December 13, 2019 8 hours ago, itman said: Are both devices running the same Win 10 version; e.g. Win 10 x(64) 1909? Yes. but one is an ESET upgrade the other clean install of 0.24 Link to comment Share on other sites More sharing options...
Zardoc 4 Posted December 13, 2019 Author Share Posted December 13, 2019 7 hours ago, itman said: Also checkout this posting: https://forum.eset.com/topic/20839-eset-v12229-bug/?do=findComment&comment=102268 . Make sure the two Window Defender Antivirus services are set to Manual. Only the Window Defender Firewall service should be set to Automatic. They are. Link to comment Share on other sites More sharing options...
Zardoc 4 Posted December 15, 2019 Author Share Posted December 15, 2019 I have just noticed that on boot Eset shows as running and about 10 minutes later I get the warning that it's not running and when I look that is effectively the case. Marcos, any idea please ? Link to comment Share on other sites More sharing options...
itman 1,038 Posted December 15, 2019 Share Posted December 15, 2019 (edited) 38 minutes ago, Zardoc said: I have just noticed that on boot Eset shows as running Verify at this time in Windows Security Center Antivirus section that Windows Defender is turned off. This is done via Windows Security Center Virus & Threat Protection section. Scroll down the page and click on "Manage Providers." Edited December 15, 2019 by itman Link to comment Share on other sites More sharing options...
Zardoc 4 Posted December 16, 2019 Author Share Posted December 16, 2019 Defender is set to off. Now eset is showing as active. Very weird. Link to comment Share on other sites More sharing options...
Zardoc 4 Posted December 23, 2019 Author Share Posted December 23, 2019 Hi all, I wanted to see if this issue would go away after a few updates but it doesn't. On boot Eset is not recognized as active and after 10-15 minutes or more, everything falls into place. This is a full clean install of a Z390-A Asus board and latest image of Windows 10 18563. I have built a whole bunch of these machines and this is a first. I must say that I really don't care about the message but it makes the customers nervous. Can anybody tell me why this is happening and is there is a fix? Thanks. Link to comment Share on other sites More sharing options...
Most Valued Members Nightowl 116 Posted December 24, 2019 Most Valued Members Share Posted December 24, 2019 12 hours ago, Zardoc said: Hi all, I wanted to see if this issue would go away after a few updates but it doesn't. On boot Eset is not recognized as active and after 10-15 minutes or more, everything falls into place. This is a full clean install of a Z390-A Asus board and latest image of Windows 10 18563. I have built a whole bunch of these machines and this is a first. I must say that I really don't care about the message but it makes the customers nervous. Can anybody tell me why this is happening and is there is a fix? Thanks. It takes time for Windows to detect that ESET is running Link to comment Share on other sites More sharing options...
Zardoc 4 Posted December 24, 2019 Author Share Posted December 24, 2019 5 hours ago, Rami said: It takes time for Windows to detect that ESET is running Well that's a first. Why am I not seeing this on all the other machines that run the same set-up except they aren't new installs ? Link to comment Share on other sites More sharing options...
itman 1,038 Posted December 25, 2019 Share Posted December 25, 2019 (edited) On 12/23/2019 at 8:01 AM, Zardoc said: On boot Eset is not recognized as active and after 10-15 minutes or more, everything falls into place. This is not normal. Eset sets up itself in Windows Security Center shortly after boot time. In fact by the time the WCSÂ desktop taskbar icon appears, it should be no more than a minute or two at most till Eset establishes itself as the active real-time AV solution. Do you have Memory Integrity enabled in WCS Device Security Core Isolation section? Edited December 25, 2019 by itman Link to comment Share on other sites More sharing options...
Most Valued Members peteyt 203 Posted December 25, 2019 Most Valued Members Share Posted December 25, 2019 While it probably won't make any difference have you tried on one of the installations to enable pre release updates? Could be a fix has been supplied but it isn't fully around yet. People have reported warnings similar in the past but I think they got fixed a while back and I don't think it took 10 to 15 minutes which is weird Link to comment Share on other sites More sharing options...
Zardoc 4 Posted December 25, 2019 Author Share Posted December 25, 2019 6 hours ago, itman said: Do you have Memory Integrity enabled in WCS Device Security Core Isolation section? I don't see settings for this in 1909 and I don't use virtualisation. Link to comment Share on other sites More sharing options...
Recommended Posts