Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AdGuardHome Windows edge version [Unknown error: Access is denied. (0x80070005)] #7400

Closed
4 tasks done
pekkle-hksar opened this issue Nov 3, 2024 · 62 comments
Closed
4 tasks done
Assignees
Milestone

Comments

@pekkle-hksar
Copy link

pekkle-hksar commented Nov 3, 2024

NOTE: For most relevant workaround see the comment.

Prerequisites

Platform (OS and CPU architecture)

Windows, AMD64 (aka x86_64)

Installation

GitHub releases or script from README

Setup

On one machine

AdGuard Home version

v0.108.0-a.977+1d2026bf

Action

run "AdGuardHome.exe" in command prompt with admin right

Expected result

start AdGuardHome properly

Actual result

Error message shown "Unknown error: Access is denied. (0x80070005)"

Additional information and/or screenshots

seems latest edge release in Windows is having problem
I fallback the previous version by remove the whole folder, and unzip the previous edge version (Version:
v0.108.0-a.975+e529d29e), AdGuardHome could start properly

@bestpika
Copy link

bestpika commented Nov 3, 2024

I discovered that the latest edge version modifies the access rights of the entire folder, which is the main cause of this issue.

This is the permission for a regular folder.
image

These are the folder permissions after the update is complete.
image

@pekkle-hksar
Copy link
Author

pekkle-hksar commented Nov 3, 2024 via email

@bestpika
Copy link

bestpika commented Nov 3, 2024

I found that this issue is significantly related to #7314. Moreover, based on the current folder permissions, the service should not be able to start normally after rebooting because the SYSTEM permissions have been removed.

@simpleandstupid
Copy link

It happened on my device as well.

@EugeneOne1
Copy link
Member

@pekkle-hksar, hello and apologies for the delayed response. It's definitely related to the issue @bestpika mentioned, and we've already pushed the new edge release, that should avoid this behavior. Could you please try updating to it? Note that it indeed changes the permissions of the files in the working directory due to security concerns. I strongly recommend that you to backup the directory before updating AdGuard Home.

AFAIK, the problem only appears after an update, so I believe it could be fixed by giving full access rights to AdGuardHome.exe to the Administrators group (the owner). In fact, AdGuard Home expects to be run by an administrator user with its rights, so any other scenario is now considered unsafe.

@bestpika
Copy link

bestpika commented Nov 7, 2024

@EugeneOne1 The problem still exists, and there is an issue with the permission design.

  1. The SYSTEM should have full permissions.
  2. You should not assign permissions to a specific user, but rather to the Administrators group.

@StoneOfStones
Copy link

When starting service it now says access denied.
Windows 11

@EugeneOne1
Copy link
Member

@bestpika, how do you install the AdGuard Home service? Are you using PowerShell running with Administrator privileges? If so, could you please show the result of the following command:

([Security.Principal.WindowsPrincipal]
    [Security.Principal.WindowsIdentity]::GetCurrent()
).IsInRole([Security.Principal.WindowsBuiltInRole]::Administrator)

If not, could you please provide a detailed description of the process? Also, which security identifier corresponds to the "SYSTEM"? If it is listed in this resource?

@StoneOfStones, what permissions are assigned to the file AdGuardHome.exe?

@Eyeborgs
Copy link

Eyeborgs commented Nov 8, 2024

После обновления на v0.107.54 у меня была тоже ошибка с доступом и служба не могла работать и мне пришлось самому по стандарту все учетные записи добавлять и в каждом убирать эти галочки которые на фото.

After the update to v0.107.54, I also encountered an access error, and the service could not function. I had to manually add all the accounts according to the standard and uncheck those boxes in each one, as shown in the photo.

image

@StoneOfStones
Copy link

@StoneOfStones, what permissions are assigned to the file AdGuardHome.exe?

@EugeneOne1 don't know.

I fix it with:

  1. Renamed the folder to AdGuardHomeOld.
  2. Create new folder and named it AdGuardHome, it creates folder with default permissions.
  3. Copied contents of the AdGuardHomeOld to AdGuardHome.
  4. Downloaded version v0.107.53 and extracted exe to AdGuardHome.
  5. Changed permissions to files/folders of AdGuardHome with this instruction except step 6, if option 7 is not present click Change permissions.
  6. Started service as usual and it is now fixed.

Don't want to update to a new version just to break it again

@c15412
Copy link

c15412 commented Nov 9, 2024

If not, could you please provide a detailed description of the process? Also, which security identifier corresponds to the "SYSTEM"? If it is listed in this resource?

Services on a windows system run with SYSTEM permissions, so SYSTEM permissions must be kept

@pekkle-hksar
Copy link
Author

@pekkle-hksar, hello and apologies for the delayed response. It's definitely related to the issue @bestpika mentioned, and we've already pushed the new edge release, that should avoid this behavior. Could you please try updating to it? Note that it indeed changes the permissions of the files in the working directory due to security concerns. I strongly recommend that you to backup the directory before updating AdGuard Home.

AFAIK, the problem only appears after an update, so I believe it could be fixed by giving full access rights to AdGuardHome.exe to the Administrators group (the owner). In fact, AdGuard Home expects to be run by an administrator user with its rights, so any other scenario is now considered unsafe.

same as others, it's not working... after updated to the new version, it will be access denied.
it's because of wrong permissions settings of adguardhome.exe and the data folder, too.

@avatartw
Copy link

avatartw commented Nov 9, 2024

which security identifier corresponds to the "SYSTEM"? If it is listed in this resource?

SECURITY_LOCAL_SYSTEM_RID
String value: S-1-5-18

https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/manage/understand-security-identifiers
SID: S-1-5-18
Display name: System (or LocalSystem)
An identity that's used locally by the operating system and by services that are configured to sign in as LocalSystem. System is a hidden member of Administrators. That is, any process running as System has the SID for the built-in Administrators group in its access token. When a process that's running locally as System accesses network resources, it does so by using the computer's domain identity. Its access token on the remote computer includes the SID for the local computer's domain account plus SIDs for security groups that the computer is a member of, such as Domain Computers and Authenticated Users.

WELL_KNOWN_SID_TYPE enumeration
WinLocalSystemSid = 22

@wrt97vedm2bpm5cefa2po4t

I have the same problem. It is really frustrating. 😣

@EugeneOne1
Copy link
Member

Hello again everyone! Unfortunately we can't reproduce the problem on our test machines. I suspect it's due to differences in the behaviour of different versions of Windows. Could you all please provide some common information:

  • Which version of Windows you are using, e.g. Windows 10 Pro version 22H2 19045.5011 (Windows Feature Experience Pack 1000.19060.1000.0); it's usually located under StartSettingsSystemAbout.
  • How exactly was AdGuard Home installed as a service? Did you use a custom API (.\AdGuardHome -s install)?
  • What command-line tool are you using and what privileges does it have?

As a temporary workaround for anyone facing this problem, the @Eyeborgs's comment should prevent any further permission issues. It will generate a security warning in the log on every reboot and update, but that's not critical.

@simpleandstupid
Copy link

Hello again everyone! Unfortunately we can't reproduce the problem on our test machines. I suspect it's due to differences in the behaviour of different versions of Windows. Could you all please provide some common information:大家好再次!不幸的是,我们无法在我们的测试机器上重现这个问题。我怀疑这是由于不同版本Windows的行为差异造成的。请大家提供一些共同信息:

* Which version of Windows you are using, e.g. Windows 10 Pro version 22H2 19045.5011 (Windows Feature Experience Pack 1000.19060.1000.0); it's usually located under _Start_ → _Settings_ → _System_ → _About_.您正在使用哪个版本的Windows,例如Windows 10 Pro版本22 H2 19045.5011(Windows功能体验包1000.19060.1000.0);它通常位于“开始”'''设置'系统'下。

* How exactly was AdGuard Home installed as a service?  Did you use a custom API (`.\AdGuardHome -s install`)?AdGuard Home到底是如何作为服务安装的?您是否使用了自定义API()?

* What command-line tool are you using and what privileges does it have?您正在使用什么命令行工具?它拥有什么特权?

As a temporary workaround for anyone facing this problem, the @Eyeborgs's comment should prevent any further permission issues. It will generate a security warning in the log on every reboot and update, but that's not critical.作为任何面临此问题的人的临时解决方案,的评论应该防止任何进一步的许可问题。每次重新启动和更新时,它都会在日志中生成安全警告,但这并不重要。

版本 Windows 11 家庭中文版
版本号 24H2
安装日期 ‎2024/‎10/‎31
操作系统版本 26100.2161
体验 Windows Feature Experience Pack 1000.26100.32.0

我使用.\AdGuardHome -s install安装服务。命令行工具为Powershell(Windows Terminal),无论是直接启动还是“以管理员身份运行”行为一致(Access is denied.)。

@silenceleaf
Copy link

silenceleaf commented Nov 11, 2024

My OS version is windows server 2025. Even in the latest release, after execute AdGuard Home, the folder permission is reset to "none". I guess, server 2025 has same behavior with Windows 11 24H2

@88keyz
Copy link

88keyz commented Nov 11, 2024

My temp workaround is to start AdGuardHome with the following batch file instead of starting it as a Windows service.

Change both instances of C:\Path\to\AdGuardHome to your AGH install path and then save the batch file to your Start-up folder (%APPDATA%\Microsoft\Windows\Start Menu\Programs\Startup).

It works by adding a short delay after starting the AdGuardHome executable and then resetting the folder permissions to NTFS defaults.

@set @_cmd=1 /*
@echo off
setlocal EnableExtensions
title AdGuardHome

whoami /groups | findstr "S-1-16-12288" >nul && goto :admin
if "%~1"=="RunAsAdmin" goto :error

echo Requesting privileges elevation for managing the AdGuardHome service . . .
cscript /nologo /e:javascript "%~f0" || goto :error
exit /b

:error
echo.
echo Error: Administrator privileges elevation failed,
echo        please manually run this script as administrator.
echo.
goto :end

:admin
pushd "C:\Path\to\AdGuardHome"
AdGuardHome.exe -s start
ping /n 5 /w 10000 localhost >nul
icacls "C:\Path\to\AdGuardHome" /reset /T /C /L
popd
echo.
echo Thank you for using AdGuardHome!

:end
`exit` /b */

// JScript, restart batch script as administrator
var objShell = WScript.CreateObject('Shell.Application');
var ComSpec = WScript.CreateObject('WScript.Shell').ExpandEnvironmentStrings('%ComSpec%');
objShell.ShellExecute(ComSpec, '/c ""' + WScript.ScriptFullName + '" RunAsAdmin"', '', 'runas', 1);

@pekkle-hksar
Copy link
Author

pekkle-hksar commented Nov 11, 2024 via email

@micceo
Copy link

micceo commented Nov 12, 2024

Temporary solution until AdGuard stops mocking around with permissions.
Create a local user account which is not member of the Administrator group, that is a normal user. Uncheck that the user needs to change password, and check Password never exp and Can't change password.
Change the login account for AdGuard service to use this (you get a popup that the account has been granted Login as service)
Change the permission on the folder so the Authenticated Users or Users have Change (not Full).

Edit: This is a nice way of increasing the security too, because AdGuard is no longer running with SYSTEM (lots of permission) instead with normal user permissions.

@THEBOSS619
Copy link

THEBOSS619 commented Nov 12, 2024

Same problems, same issues for both Edge & Beta. I'm back using edge/beta version before all this permissions issues happened. Here's the file if anyone interested before the day of all this permissions issues happened.
AdGuardHome.zip

The version on the zip file are this....
image

@ImmortalD
Copy link

Actually, this is generally not done on Windows. This kind of practice is more suitable for Linux. Therefore, is it possible to disable this permission check on Windows?

@M0n7y5
Copy link

M0n7y5 commented Nov 15, 2024

This issue currently broke internet connections on all windows machines where I installed AGH as service.
Some workaround would be nice.

@Eyeborgs
Copy link

@EugeneOne1
That's certainly good, but I would prefer that permcheck is not applied by default.
For those who want to use permcheck, they can add the option .\AdGuardHome -s install --permcheck.

@okastl
Copy link

okastl commented Nov 22, 2024

@EugeneOne1 That's certainly good, but I would prefer that permcheck is not applied by default. For those who want to use permcheck, they can add the option .\AdGuardHome -s install --permcheck.

100% agree

@1aTa
Copy link

1aTa commented Nov 22, 2024

Also agree with this.

@pekkle-hksar
Copy link
Author

pekkle-hksar commented Nov 22, 2024 via email

@xiao-mantou
Copy link

Hello again everyone! We apologise for not releasing a fix for this issue for a long time and are currently working on it. As far as we can see, the most common problem is the "access denied" error due to insufficient permissions. The main workaround at the moment is to manually reset the permissions via the file properties. For each file in the working directory, do the following:

  • Go to "Properties""Security""Advanced".
  • If the file is owned by the "Administrator" account, give this account "Full Access". If the file is owned by another account, e.g. "SYSTEM", give it "Full access".
    Note that AdGuard Home uses the permissions of the configuration file to determine whether they should be changed, so if the permissions have changed after startup, it's possible that this particular version of Windows (the Services subsystem) expects a different owner for the file, which should also be changed.

We'd really appreciate any detailed feedback on this workaround. If it works or if the error has changed.

Is this mean, until further fix been issued, it is not recommended to run AdGuard Home as a "Windows Service"?

Wow, in stable release, it's happening even when it's not running as service. I just tried the edge biuld, seems fine with --no-permcheck.

@sausje
Copy link

sausje commented Nov 26, 2024

How does one download the edge build? I only see the beta and normal in release/tags?

@xiao-mantou
Copy link

How does one download the edge build? I only see the beta and normal in release/tags?

Here

@Arthur-Kenichi-Condino
Copy link

Arthur-Kenichi-Condino commented Nov 28, 2024

So issues #7439 and #7454 are duplicates of this Issue; I had to fall back to version v0.107.53 from v0.107.54. AdGuard Home is already installed as a service, and updating it manually by replacing the executable and then running the service resulted in AdGuard blocking itself from running because it set only Write permissions to a non-privileged unknown user to its folders (not even myself, as an Admin User, could open the folders because it had permissions which made no actual sense: the yaml file and the data folder had only Write permission, not even Read or Traverse files and folders); I can't update to another stable version until this is fixed because whenever I do that, I have to set AdGuard from scratch.

Setting permissions of full control may allow AdGuard to run once, because it'll set its permissions wrong again in the next run. Also, setting all permissions to the right ones (suggested here in this Issue), but leaving the folders "data" and the yaml file with the Write only permissions AdGuard set automatically when it runs (not even read or traverse files and folders), will allow AdGuard to run on startup normally but I believe it'll not be able to read its settings consistently, so that may be the cause of the DNS filtering not working in my other post on Issue #7439. If the folder has all the permissions with Full Control (even data and yamls file), AdGuard will run normally once and then break again.

Even the Owner of the folder in the security permissions is Unknown and not Administrator or an Admin User (me). So AdGuard won't be able to be run with PowerShell or cmd.

By the way, how would I update to a newer version (but not again v0.107.54) and then not let AdGuard change its permissions? What I understood is that if you install it from scratch as a service, you can do -s install --no-permcheck, but what should I do as an end user, to update it, if it's already installed as a service: after I just replace the executable file? Because I don't need to change permissions: I know it's safer to restrict permissions in important folders, but I'm already an Admin User in my computer, so maybe this changes nothing in the question of security, because I think it's redundant, in Windows: suppose a bad actor invades my computer: it'll be able to do anything it wants, even to AdGuard, because I'm also an Admin User; I know it's safer to create an account without Admin Privileges and leave the Administrator account with its privileges only, but here where I live we don't have so much software security and safety education, so many stores already sell the computer with a new user with administrative privileges (access to root) and with some bloatware sometimes.

I want to restrict my current user and enable Windows's built-in Administrator account with UAC messages with password required to make system changes, but I'm a little bit buzy/lazy to do that right now, it's too much to change.

So for most Windows end users, like myself, who bought a computer and started using it the way it came from the store, changing permissions may be also redundant. Because if I'm infected with malware, the malware will grant itself privileges and access AdGuard with my own credentials (as I'd do manually).

P.S.: I'm not a professional IT, a security technician or anything, I'm just explaining my suppositions and the experience I had installing the new AdGuard stable version as an end user, so please correct me when I said something wrong.

Also, I'm using Windows 11 Pro 22631.4391 Windows Feature Experience Pack 1000.22700.1047.0 and avast!

I installed AdGuard with PowerShell as service with .\AdGuardHome -s install

Edit: this is not a rant in any way. I'm just trying to learn more. I love AdGuard and AdGuard Home because they give me control to my privacy and even more security when browsing. I apologize if any part of my writing had any sign of flame or anger. English is not my native language.

@EugeneOne1
Copy link
Member

Hello, @Arthur-Kenichi-Condino, thank you for a very thorough response! The issues mentioned are really duplicates of this one and all have the same origin, which is the inability to access the files with invalid permissions. We’re already testing the new beta, which should be much more accurate in terms of access rights on Windows.

Even the Owner of the folder in the security permissions is Unknown and not Administrator or an Admin User (me). So AdGuard won’t be able to be run with PowerShell or cmd.

Who owns AdGuard Home’s working directory and its parent directory? The latest release shouldn’t affect the owners of files and directories, it just sets the permissions for them, assuming that the working directory was originally owned by the Administrators account.

What I understood is that if you install it from scratch as a service, you can do -s install --no-permcheck, but what should I do as an end user, to update it, if it’s already installed as a service: after I just replace the executable file?

The service uninstall command shouldn’t affect permissions, so it can be run either before or after the executable is replaced. Could you please try the following:

  • Change the permissions of the working directory to give the “Full control” to the Administrators account and make the Administrators own it. Do that for each file within the working directory.
  • Stop the service, if not already done:
    .\AdGuardHome.exe -s stop
  • Uninstall the service:
    .\AdGuardHome.exe -s uninstall
  • Replace the executable with the latest edge, since the option is currently only available on the edge channel.
  • Install the service again with --no-permcheck:
    .\AdGuardHome.exe -s install --no-permcheck

This should fix skip the unwanted permissions manipulations.

I’m just explaining my suppositions and the experience I had installing the new AdGuard stable version as an end user, so please correct me when I said something wrong.

You’re always welcome to share your experiences with us to help us develop AdGuard Home and other products. However, as a security-aware, server-based software, AdGuard Home strives to avoid all possible vulnerabilities, one of which is insecure access rights (#7314).

@sausje
Copy link

sausje commented Nov 30, 2024

So I followed the instructions given in this topic to update and get it working again, but somehow my filterlists have 0 entries? Even after forcing an update to them. I can see the files in explorer and they have the right data in them. So I guess this way of "forcing" adguard to run renders it unable to read the filter files??

@simpleandstupid
Copy link

simpleandstupid commented Nov 30, 2024

So I followed the instructions given in this topic to update and get it working again, but somehow my filterlists have 0 entries? Even after forcing an update to them. I can see the files in explorer and they have the right data in them. So I guess this way of "forcing" adguard to run renders it unable to read the filter files??

The filter file was incorrectly set with permissions in previous versions, which requires you to restore it manually.
(If a new version of edge is released, don't click on the Dashboard to complete the update, it will break directory file permissions again.)

@M0n7y5
Copy link

M0n7y5 commented Dec 3, 2024

So I followed the instructions given in this topic to update and get it working again, but somehow my filterlists have 0 entries? Even after forcing an update to them. I can see the files in explorer and they have the right data in them. So I guess this way of "forcing" adguard to run renders it unable to read the filter files??

I suggest you to nuke your current adg installation and reinstall it from scratch.

@sausje
Copy link

sausje commented Dec 3, 2024

So I followed the instructions given in this topic to update and get it working again, but somehow my filterlists have 0 entries? Even after forcing an update to them. I can see the files in explorer and they have the right data in them. So I guess this way of "forcing" adguard to run renders it unable to read the filter files??

I suggest you to nuke your current adg installation and reinstall it from scratch.

No need, last update fixed this.

@canronglan
Copy link

这个权限控制完全没必要,都已经是home了,还要担心什么权限问题?多此一举!

adguard pushed a commit that referenced this issue Dec 3, 2024
Updates #7400.

Squashed commit of the following:

commit f50d7c2
Merge: 47040a1 37b16bc
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Tue Dec 3 18:09:23 2024 +0300

    Merge branch 'master' into 7400-chown-permcheck

commit 47040a1
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Tue Dec 3 14:26:43 2024 +0300

    permcheck: fix nil entries

commit e1d21c5
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Mon Dec 2 15:37:58 2024 +0300

    permcheck: fix nil owner

commit b1fc67c
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Fri Nov 29 18:07:15 2024 +0300

    permcheck: imp doc

commit 0b6a713
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Fri Nov 29 17:16:24 2024 +0300

    permcheck: imp code

commit 7dfbeda
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Fri Nov 29 14:28:17 2024 +0300

    permcheck: imp code

commit 3a5b6ac
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Thu Nov 28 19:21:03 2024 +0300

    all: imp code, docs

commit c076c93
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Thu Nov 28 15:14:06 2024 +0300

    permcheck: imp code, docs

commit 09e4ae1
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Wed Nov 27 19:19:11 2024 +0300

    all: implement windows permcheck

commit b75ed7d
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Mon Nov 25 18:01:47 2024 +0300

    all: revert permissions
@EugeneOne1
Copy link
Member

EugeneOne1 commented Dec 4, 2024

Hello everyone! We've pushed the edge build that contains a more proper implementation of the access rights handling. For now, AdGuard Home will only check the working directory permissions and migrate them if necessary. The expected permissions (which won't be migrated) for now are the following:

  • "Full Control" for the Administrators account;
  • any deny access rights for any account;
  • no access rights for any other account;

Note that any file within the working directory is expected to inherit its permissions and therefore be considered protected.

It works fine on our test machines, but we'd really appreciate it if someone would check it before we release a beta and eventually a stable version. If you want to help us test this feature, and you previously installed the service with the --no-permcheck option, it will still take effect, so you'll need to reinstall the service without it. Please make a full backup of the working directory before upgrading.

For those who don't want to use this feature, the --no-permcheck option will also be released in stable and beta.

@1aTa
Copy link

1aTa commented Dec 4, 2024

Hello everyone! We've pushed the edge build that contains a more proper implementation of the access rights handling. For now, AdGuard Home will only check the working directory permissions and migrate them if necessary. The expected permissions (which won't be migrated) for now are the following:

This seems to be working well from my testing so far. Permissions are set correctly, Windows states that I don't have access to the working directly but I can click continue to get access as an admin, configuration is editable from the webUI, no issues on restart of the service.

@simpleandstupid
Copy link

Hello everyone! We've pushed the edge build that contains a more proper implementation of the access rights handling. For now, AdGuard Home will only check the working directory permissions and migrate them if necessary. The expected permissions (which won't be migrated) for now are the following:

* _"Full Control"_ for the _Administrators_ account;

* any deny access rights for any account;

* no access rights for any other account;

Note that any file within the working directory is expected to inherit its permissions and therefore be considered protected.

It works fine on our test machines, but we'd really appreciate it if someone would check it before we release a beta and eventually a stable version. If you want to help us test this feature, and you previously installed the service with the --no-permcheck option, it will still take effect, so you'll need to reinstall the service without it. Please make a full backup of the working directory before upgrading.

For those who don't want to use this feature, the --no-permcheck option will also be released in stable and beta.

It works well on my machine.

@EugeneOne1 EugeneOne1 added this to the v0.107.55 milestone Dec 4, 2024
@EugeneOne1
Copy link
Member

For anyone interested, the fix is available on the beta channel.

@EugeneOne1
Copy link
Member

We're closing this issue for now and preparing a stable release, thanks again to everyone who tested the fix.

@EugeneOne1 EugeneOne1 modified the milestones: v0.107.56, v0.107.55 Dec 5, 2024
@bestpika
Copy link

bestpika commented Dec 7, 2024

@EugeneOne1 Can I continue to use the --no-permcheck option when installing services in the new Edge version?

@EugeneOne1
Copy link
Member

@bestpika, sure. It's also available in the latest beta.

@Zerorigin
Copy link

После обновления на v0.107.54 у меня была тоже ошибка с доступом и служба не могла работать и мне пришлось самому по стандарту все учетные записи добавлять и в каждом убирать эти галочки которые на фото.

After the update to v0.107.54, I also encountered an access error, and the service could not function. I had to manually add all the accounts according to the standard and uncheck those boxes in each one, as shown in the photo.

image

It works for me.
3Q~ (Thank you).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests