Failed to check for update notification when windows boots up

[takattowo]

Please answer the following questions for yourself before submitting an issue

• Filters were updated before reproducing an issue
• I checked the knowledge base and found no answer
• I checked to make sure that this issue has not already been filed

AdGuard version

7.20.0 Beta 1 (4904)

Browser version

Edge, 124

OS version

Windows 11, 24H2

Traffic filtering

• yes, I do

Ad Blocking

AdGuard Base filter, AdGuard Mobile Ads filter, EasyList

Privacy

AdGuard Tracking Protection filter, AdGuard URL Tracking filter

Social

No response

Annoyances

AdGuard Annoyances filter, AdGuard Cookie Notices filter, AdGuard Other Annoyances filter

Security

No response

Other

No response

Language-specific

No response

Which DNS server do you use?

AdGuard DNS

DNS protocol

None

Custom DNS

No response

What Stealth Mode options do you have enabled?

Block trackers, Remove tracking parameters, Remove X-client-Data header from HTTP request, Protect from DPI

Support ticket ID

No response

Issue Details

When I boot up the machine, Adguard always throw a notification that says its unable to update, this issue wasn't happening until the latest beta version. I also manually hit the check update for both filter and program and it works without issue.

Expected Behavior

No response

Actual Behavior

Notification always throw.

Screenshots

Screenshot 1


Additional Information

No response

[chengnan049]

This bug has been around for a long time

[takattowo]

This bug has been around for a long time

Is it? I have been using Adguard for a long time and this is the first time i saw it after update to the lastest beta version, welp i guess you can go ahead and close the case if its duplicated.

[AlexandrPkhm]

@chengnan049 Hello! In order to troubleshoot this issue, we need to get your application logs.

Here's what we need you to do:

1. Collect the debug log as it's explained here.
2. Remember the exact time when the issue was reproduced.
3. Send the archive to [email protected]:
   — include [windows] keyword and ISSUE_NUMBER in the subject of your email
   — specify the exact time when the issue occurred

[AlexandrPkhm]

@chengnan049 Could you please let us know if you were able to record the logs?

[chengnan049]

@chengnan049 Could you please let us know if you were able to record the logs?

Okay, when I get home tonight

[chengnan049]

It looks like it's fixed on my device. 7.20.0 Beta 1 (4904) (CL 1.16.48, DL 2.5.51 )