Proxy setting is ignored by updates downloader and installer

[opzch]

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.18.0 (4774)

Browser version

---

OS version

Windows 10 22H2

Traffic filtering

• [X] yes, I do

Ad Blocking

No response

Privacy

No response

Social

No response

Annoyances

No response

Security

No response

Other

No response

Language-specific

No response

Which DNS server do you use?

DNS protection disabled

DNS protocol

None

Custom DNS

No response

What Stealth Mode options do you have enabled?

No response

Support ticket ID

No response

Issue Details

If update from the app, adguardsvc.exe will ignore system proxy settings and its own proxy setting and download installer file directly (despite saying "Using these proxy settings, Adguard will update filters, get new versions, etc.").

The installer itself (setup-7.18.4774.0.exe, adgsetup.exe) also makes two direct unsolicited connections.

Expected Behavior

The only case when proxy should be ignored is when the system proxy = Adguard proxy, and "Use system proxy settings" or "No proxy" is selected on Settings -> Network -> Proxy Settings

Actual Behavior

Attempts to download the file directly, makes two unnecessary tracking(?) connections directly

Screenshots

Proxy settings

  

Direct connection captured

Direct connection gets force-redirected to proxy 

Additional Information

No response

[yueisme]

I asked about upgrade not use proxy in AdGuard support ticket 774643, tell me use offline installer.

[KolbasovAnton]

@opzch Hello, please, tell us which app do you use for checking connections (second screenshot)?

[opzch]

Proxifier

[KolbasovAnton]

@opzch Could You please reproduce this situation and:

1. Send us logs, as it's [explained here](https://adguard.com/kb/adguard-for-windows/solving-problems/adguard-logs/).
2. Remember the exact time when the issue was reproduced. We will need it to find the corresponding records in the log file.
3. Send the archive to devteam@adguard.com and mention this issue number in the subject.

Also, the setup logs (could be found in "C:\Users\username\AppData\Local\Temp\Adguard") will be very useful.

[AlexandrPkhm]

Hi @opzch

Could you please let us know if you were able to record the app logs for this issue?