AdguardTeam / AdGuardHome

Network-wide ads & trackers blocking DNS server
https://adguard.com/adguard-home/overview.html
GNU General Public License v3.0
25.68k stars 1.84k forks source link

The permission issue with the Windows operating system remains unresolved. Whenever the computer is restarted, it prompts that there is no permission. #7454

Closed chinaniupai closed 16 hours ago

chinaniupai commented 3 days ago

Prerequisites

Platform (OS and CPU architecture)

Windows, 32-bit Intel (aka 386)

Installation

GitHub releases or script from README

Setup

On one machine

AdGuard Home version

Latest version

Action

I only restarted the computer

Expected result

Resolve the issue of automatically changing permissions after restarting, resulting in inability to use

Actual result

Automatically change permissions, unable to use

Additional information and/or screenshots

https://github.com/AdguardTeam/AdGuardHome/issues/7439

xianhongtao commented 2 days ago

+1,my internet just crushed

iophobia commented 1 day ago

Same here for me with b59/60 on Win 10 Pro on a 1145G7 NUC. Adjusting the rights doesn't seem to stick wehther it's just the exe or the whole folder. And while AGH might start and take requests, it will not filter anything since it can't access/update filter lists in my case.

Chromos-Def commented 1 day ago

Here are some of my findings, hoping it'll help in some way, shape, form or fashion.

Using: AdGuard Home v0.108.0-b.60

I gave my user account full control and ensured that traverse folder / execute file was also checked. I clicked advanced options and also checked everything in there.

I then clicked enabled inheritance and it automatically populated more user accounts with permissions after I clicked apply.

I then opened up powershell as admin and ran AdGuardHome.exe -s start and voila I didn't get access is denied. But after successfully starting it, AGH reverted all permissions back to Special and I'll attach a screenshot of how it looked after the service started. image

If I recall correctly after I stopped the service and tried restarting it, it simply doesn't work again because it messed up permissions while the service was started.

EugeneOne1 commented 16 hours ago

Closing as a duplicate of #7400, see the most relevant workaround.