"Connecting" during startup

[randomusername]

I have Adguard in my auto-start (Windows 8.1 x64). The latest beta updated itself during startup (which is OK) and stayed in my tray with a yellow icon. I noticed it when I saw an ad banner appearing on a website. (Weird, I totally forgot they exist...)

When I opened Adguard, it said "Preparing the application start" (headline) and "connecting..." (in German, of course), and suddenly it worked.
It seems like Adguard does its first-time startup maintenance tasks best when being displayed, the tray seems to deny something.

I couldn't reproduce it yet, just wanted to report it.

edit: After update to today's beta, it happens again.

edit: About two minutes later, "connected to the service". Yay...?

 

[avatar]

Could you please send AG logs to me?

On the first run after program update AG startup is slow indeed.
Sometimes it should update database scheme and it may take time.

 

[randomusername]

Which logs do you need?

 

[avatar]

Which logs do you need?

These files:
https://kb.adguard.com/index.php?/Knowledgebase/Article/View/23/10/how-can-i-get-adguard-log-files

Hope they are alive (we store last 3 days only).

 

[randomusername]

Seems so.
View attachment Logs.zip

BTW: Currently: Yellow tray icon but "protection enabled".

 

[avatar]

Thank you!

Something is wrong with certutil.exe util call in your case - it is very slow.

Could you please check it in "cmd.exe" manually?

certutil.exe is located in %programfilesx86%\Adguard\nss folder.
Command to check:

certutil.exe -L -d "C:\Users\hp\AppData\Roaming\Mozilla\Firefox\Profiles\74s3ht6d.OpenDownload²-Test"

 

[randomusername]

Whoa. You see too many things in the logs.

Anyway:

DigiCert High Assurance EV CA-1 ,,
DigiCert High Assurance CA-3 ,,
VeriSign Class 3 Secure Server CA - G3 ,,
Thawte SSL CA ,,
thawte Primary Root CA ,,
DigiCert Secure Server CA ,,
Google Internet Authority G2 ,,
GeoTrust SSL CA ,,
www.google.com ,,
www.google.de ,,
GeoTrust Global CA ,,
DigiCert SHA2 Secure Server CA ,,
Adguard CA R99 CT,,

 

[avatar]

How fast was this command? In the log I see that 10 seconds timeout was not enough.

 

[randomusername]

Actually, it took me around 2 seconds.

 

[avatar]

Actually, it took me around 2 seconds.

Hm, then it's not likely to be the cause.

Can you reproduce this issue with the newest beta?

 

[randomusername]

If I knew how to safely reproduce it with any version ...

 

[randomusername]

Update to the newest build went smooth and without notable issues.