AdguardTeam
Adguard does not start with windows
Please answer the following questions for yourself before submitting an issue
- [X] Filters were updated before reproducing an issue
- [X] I checked the knowledge base and found no answer
- [X] I checked to make sure that this issue has not already been filed
AdGuard version
7.17.1
Browser version
Firefox 127
OS version
Windows 11, 22H2
Traffic filtering
- [X] yes, I do
Ad Blocking
AdGuard Base filter
Privacy
AdGuard Tracking Protection filter
Social
AdGuard Social Media filter
Annoyances
AdGuard Cookie Notices filter, AdGuard Popups filter, AdGuard Mobile App Banners filter, AdGuard Other Annoyances filter, AdGuard Widgets filter
Security
No response
Other
No response
Language-specific
No response
Which DNS server do you use?
Cloudflare DNS
DNS protocol
DNS-over-HTTPS
Custom DNS
No response
What Stealth Mode options do you have enabled?
No response
Support ticket ID
No response
Issue Details
Steps to reproduce:
- Turn off PC
- Turn PC on
Expected Behavior
Adguard should start with Windows.
Actual Behavior
Adguard does not start with Windows.
Screenshots
Screenshot 1
Additional Information
No response
@takmilihsan @tonypham9981 Hi,
have you updated to v7.18 beta 1 before rebooting? If so, that could have been the problem. Could you try a new build please.
The logs will be also helpful:
- Collect the debug log as it's explained here.
- Remember the exact time when the issue was reproduced. We will need it to find the corresponding records in the log file.
- Send the archive to
[email protected]and mention this issue number in the subject.
@Aydinv13 I have downloaded the latest version "AdGuard-7.18.0-Beta-2-.4751". After installing and restarting my PC, I tried to run AdGuard, but nothing happens. Do you need any information from my machine to assist me?
I received a response to collect the debug log and send it to [email protected], but I can't open the AdGuard interface. Could you provide instructions on how to collect the log in this situation?
@tonypham9981
Sorry, didn't take that detail into account.
Open %programdata%/adguard and archive the Logs folder
@tonypham9981 @takmilihsan unfortunately as @Aydinv13 previously said we had the dramatically issue described here, seems that you've faced it. Please follow the instructions there, and if the issue persist (if I understood the post correctly) please send the logs from %programdata%/adguard
@Aydinv13 @adbuker I have tried installing "Windows Beta" and "Windows Nightly" but still could not start AdGuard. I have sent an email with the software logs. Thank you.
@adbuker from your linked blog post,
Fortunately, it did not affect the release versions of the apps.
So probably not related to my issue.
@Aydinv13 I think I'll continue to manually start adguard until a fix comes in release. Unfortunately the beta and nightly versions come with their own problems and I keep having to downgrade (have had to do it multiple times in the past year). I hope I don't come off as snarky but if using adguard becomes such an involved process and needs continuous checking, I'd rather use something else. My target is more of a set it and forget it solution like adguard android.
@takmilihsan, could you please check whether the AdGuard.exe is contained in the list for one or more registry hive's values below
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Windows\CurrentVersion\Run
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Windows\CurrentVersion\Run
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Run
Computer\HKEY_CURRENT_USER\SOFTWARE\Windows\CurrentVersion\Run
Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
Computer\HKEY_CURRENT_USER\SOFTWARE\WOW6432Node\Windows\CurrentVersion\Run
Computer\HKEY_CURRENT_USER\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Run
and please check whether the AdGuard is in in Autorun tab within the Task manager. For the privacy reasons please send the answer to the [email protected]
This issue has been closed due to no response. Can be reopened if relevant.