Jon79 Posted February 17, 2019 Report Share Posted February 17, 2019 Hi there, Every time I boot my PC, I get this error "security center failed to validate caller with error DC040780". I'm on Windows 10 home 64bit 1809 ( build 17763.316 ) and using immunet 6.2.4.10819. Security center says it can't check the virus protection status and I have to open immunet for more information. Both Immunet and my PC are working fine. Thanks. Link to comment Share on other sites More sharing options...
ritchie58 Posted February 18, 2019 Report Share Posted February 18, 2019 Hi Jon79, have you tried to add exclusion rules for Immmunet's processes which are sfc.exe, iptray.exe (and freshclam.exe if you have the ClamAV module enabled) to Win 10's Security Center? Info on how to create custom allow rule sets for Security Center can be found at this Microsoft Knowledge Base article if you're not sure how this is accomplished. https://support.microsoft.com/en-us/help/4028485/windows-10-add-an-exclusion-to-windows-security Regards, Ritchie... Link to comment Share on other sites More sharing options...
Jon79 Posted February 18, 2019 Author Report Share Posted February 18, 2019 Hi ritchie58, thanks for your answer, but I think your suggestion is to set an exclusion on Windows Defender rather than on Security Center. Well, I can't do it because Immunet disables Windows Defender, so "Manage settings" is not available. I think the problem is that Immunet can't set itself as provider of virus and threat protection in the security center, so the security center can't check Immunet status. In attachment you can see the difference of security center icon with Windows Defender and with Immunet Link to comment Share on other sites More sharing options...
chaozz Posted February 18, 2019 Report Share Posted February 18, 2019 This seems to happen to other users with different antivirus software as well, so my guess is that it's more likely to be an issue with Windows Security Center. See: https://answers.microsoft.com/en-us/windows/forum/all/event-id-17-security-center-failed-to-validate/1fe0f4d7-8b4e-40a6-b607-e1895bfc7535?auth=1 Link to comment Share on other sites More sharing options...
Jon79 Posted February 18, 2019 Author Report Share Posted February 18, 2019 Hi chaozz, it could be, but with other AVs I only got the "status unavailable" on "virus & threat protection", with Immunet I also get the error on Event Viewer. By the way, it's not a big deal, as I said both Immunet and my PC are working fine (my PC is super fast actually ) Link to comment Share on other sites More sharing options...
Guest Wookiee Posted February 21, 2019 Report Share Posted February 21, 2019 as of right now, I cannot re-produce this error at all. Though, it could be because I am using an older windows defender (I am upgrading the version right now) I've made sure that SecurityCenter is running- googling shows a ton of people having issues with any anti-virus product installed along side windows defender though, which is what @chaozz said. It could very well be Windows SecurityCenter not playing nice. Though, I will still try and get this to error for me. Link to comment Share on other sites More sharing options...
Guest Wookiee Posted February 22, 2019 Report Share Posted February 22, 2019 by chance, can you turn Immunet into debug mode, and reboot and send me the logs ? Link to comment Share on other sites More sharing options...
Rob.T Posted March 8, 2019 Report Share Posted March 8, 2019 Thank you very much for reporting this Jon. I've successfully reproduced it, and at this point my only advice is to steer clear of win 10 1809. as far as I can MS pulled it after release due to driver incompatibilities and potentially deleting user data when upgrading from previous versions. I was able to obtain a 1809 iso through MSDN and it ended up bootlooping during install of both home& pro win 10 versions (installing to vmware workstation). I had to use a workaround just to complete the OS install: https://luyentap.blogspot.com/2017/10/windows-installation-cannot-proceed.html. After that I was able to install Immunet and repro your bug. 1 Link to comment Share on other sites More sharing options...
Guest Wookiee Posted June 17, 2019 Report Share Posted June 17, 2019 this is fixed. Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now