Skip to main content

Fresh Install will not initialize protection database

Thread needs solution

On my prior beta machine I completely removed the 2021 beta (uninstall and deleted remnant files and registry keys).

Oddly, my 90 day delay on Windows 10 2004 expired yesterday so I ended up having 2004 installed on the machine. After getting that done I did a fresh install of ATI 2021. The install appeared alright except that it has not been able to download the database. Looking at the Schedule2 logs, I can see that the update task is in an error/retry infinite loop. It seems to be retrying every 10 seconds.

I tried to "tickle" it by unplugging the internet connection. I then plugged it back in and tried to start the UI. It immediately came up with a feedback box (never seen that happen automatically before). I dismissed that and let the UI start. Still no luck.

Next, reboot Windows. Again, on starting the ATI UI I got the feedback so I sent it with a system report. It appeared to be hanging on starting the UI so I went on a shopping trip. Finally got back to the laptop about 2 1/2 hours later. The UI was open, still trying to download the database. At this point there are about 35,000 entries in the latest Schedule2 log. Obviously, this keeps the system from sleep too.

I'll try some experiments later but I may end up doing a complete uninstall/reinstall.

0 Users found this helpful

Bruno, the automatic presentation of the Feedback tool happens when an error happens during the GUI launch - I had the same earlier today but didn't both with feedback as I knew the cause was my own tinkering!

I have seen another issue with the protection database updates in that it appears to be still trying to do these regardless of having any of the new antivirus features enabled - this on my laptop running the perpetual version where I have declined the offer of a 3 month trial of the antivirus, but it still wants to download updates!

My user error generated failure was because I had stopped the aakore agent service!

I discovered that the agent core service did not start. Lots of SCM timeout errors in the event log. Not sure why. I may have tried turning it off and on earlier, but after a couple reboots that should not have been an issue.

I manually started the service and then loaded the UI and it looked correct. Rebooted again and this time the services started OK. Still had to open the UI twice to get past the error feedback request.

I had this happen this morning, no tinkering on my part (other than disabling all protections I could two days earlier). Not sure why it happened but as reported in another thread I did send feedback as they still have not fixed the problem reported during beta testing.

Even with all Protection features turned off in the GUI, the background AAP, AAkore, CyberProtect etc services and processes are still running!  This will Defender set as the provider for antivirus etc.