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

AdGuard failed to run by {error : Can't get general settings} if FIPS policy enabled #5364

Open
4 tasks done
SaeGon-Heo opened this issue Feb 25, 2025 · 0 comments
Open
4 tasks done
Assignees

Comments

@SaeGon-Heo
Copy link

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

Browser version

Chrome 133

OS version

Windows 10 22H2 19045.5487

Traffic filtering

  • 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?

AdGuard DNS Non-filtering

DNS protocol

None

Custom DNS

No response

What Stealth Mode options do you have enabled?

No response

Support ticket ID

No response

Issue Details

Steps to reproduce:

  1. update from 7.19 to 7.20
  2. run AdGuard Windows or open Services.msc and start Adguard Service.

Expected Behavior

I expected run AdGuard normally like 7.19 with fips policy enabled.

Actual Behavior

Nothing happened. AdGuard is not running.
If start Adguard Service manually it failed to start Adguard Service with error code 1053

Screenshots

Error code when run Adguard Service manually

Image

SettingsDump - C:\ProgramData\Adguard\Crashes\SettingsDump\settings_26-02-2025-03_48_30.439.dat

{error : Can't get general settings}

Log - C:\ProgramData\Adguard\Logs\service\service_2025-02-26-03_48_58.021.log

VERBOSE, AdguardSvc.exe, Logger, 1, 26.02.2025 3:48:58.287, Getting OS architecture from IsWow64Process2
INFO, AdguardSvc.exe, Logger, 1, 26.02.2025 3:48:58.287, GetOsArchitecture: X64
VERBOSE, AdguardSvc.exe, Logger, 1, 26.02.2025 3:48:58.287, Getting OS architecture from IsWow64Process2
INFO, AdguardSvc.exe, Logger, 1, 26.02.2025 3:48:58.287, GetOsArchitecture: X64
VERBOSE, AdguardSvc.exe, Logger, 1, 26.02.2025 3:48:58.303, Getting OS architecture from IsWow64Process2
INFO, AdguardSvc.exe, Logger, 1, 26.02.2025 3:48:58.303, GetOsArchitecture: X64
INFO, AdguardSvc.exe, Logger, 1, 26.02.2025 3:48:58.303, Setting CurrentDir from C:\Windows\system32 to C:\Program Files\AdGuard\
VERBOSE, AdguardSvc.exe, Logger, 1, 26.02.2025 3:48:58.334, Cannot parse dev config because file is empty
VERBOSE, AdguardSvc.exe, Logger, 1, 26.02.2025 3:48:58.334, Cannot parse dev config because file is empty
ERROR, AdguardSvc.exe, Logger, 1, 26.02.2025 3:48:58.334, Unhandled exception event raised. Sender=이름:AdguardSvc.exe
컨텍스트 정책이 없습니다.
Exception=System.InvalidOperationException: 이 구현은 Windows Platform FIPS 유효성을 검사한 암호화 알고리즘의 일부가 아닙니다.
Source: mscorlib
Stack trace: 위치: System.Security.Cryptography.SHA1Managed..ctor()
위치: AdGuard.Utils.Common.CheckSumUtils.GetFileCheckSum(String filePath)
위치: AdGuard.Utils.Files.FileMetadata.MUbGVFHIBtqbe4B7Xaxg(Object )
위치: AdGuard.Utils.Files.FileMetadata..ctor(String filePath)
위치: Adguard.Commons.Application.ApplicationUtils.LqBlqpt4ufm()
위치: Adguard.Commons.Application.ApplicationUtils.q5huftl10jUgZL6SDOvB()
위치: Adguard.Commons.Application.ApplicationUtils.GetFullInfoAboutSubModules()
위치: E446KJqGN763EaIJL9g.FZKGo2javc(E446KJqGN763EaIJL9g )
위치: tdsqBsggTG7pbsZA94.k2WHWae2eJOfPW1VG8.eFTxKWnZ4(String[] )

INFO, AdguardSvc.exe, Logger, 1, 26.02.2025 3:48:59.912, Elapsed on 'Base init: 1' action: 0 ms.

Log - C:\ProgramData\Adguard\Logs\host\host_2025-02-26-03_32_00.053.log

INFO, Adguard.BrowserExtensionHost.exe, Logger, 1, 26.02.2025 3:32:00.061, Call arguments /unregister
INFO, Adguard.BrowserExtensionHost.exe, Logger, 1, 26.02.2025 3:32:00.070, Browser process is rundll32
INFO, Adguard.BrowserExtensionHost.exe, Logger, 1, 26.02.2025 3:32:00.070, Start NativeBrowserAssistantHost application, called by rundll32.exe (PID - 5572)
VERBOSE, Adguard.BrowserExtensionHost.exe, Logger, 1, 26.02.2025 3:32:00.500, Cannot parse dev config because file is empty
VERBOSE, Adguard.BrowserExtensionHost.exe, Logger, 1, 26.02.2025 3:32:00.500, Cannot parse dev config because file is empty
ERROR, Adguard.BrowserExtensionHost.exe, Logger, 1, 26.02.2025 3:32:00.510, Unhandled exception event raised. Sender=이름:Adguard.BrowserExtensionHost.exe
컨텍스트 정책이 없습니다.
Exception=System.InvalidOperationException: 이 구현은 Windows Platform FIPS 유효성을 검사한 암호화 알고리즘의 일부가 아닙니다.
Source: mscorlib
Stack trace: 위치: System.Security.Cryptography.SHA1Managed..ctor()
위치: AdGuard.Utils.Common.CheckSumUtils.GetFileCheckSum(String filePath)
위치: AdGuard.Utils.Files.FileMetadata.MUbGVFHIBtqbe4B7Xaxg(Object )
위치: AdGuard.Utils.Files.FileMetadata..ctor(String filePath)
위치: Adguard.Commons.Application.ApplicationUtils.LqBlqpt4ufm()
위치: Adguard.Commons.Application.ApplicationUtils.q5huftl10jUgZL6SDOvB()
위치: Adguard.Commons.Application.ApplicationUtils.GetFullInfoAboutSubModules()
위치: kNcqAJG3nlfoHdEQtTHX.EtXGy5GlvNT(kNcqAJG3nlfoHdEQtTHX )
위치: iXxlPYvaMHRvJGkle5II.Ie5COevahPsNiE3noAsa.RWiva8RCWEJ(String[] )

Additional Information

First of all, I'm korean. So log and screenshot text are written in korean.
Sorry if you have any inconvenience to see them.

At "gpedit.msc", navigate to "Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options" and enable "System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing" will produce same issue I guess.

It seems use SHA1 for check config file integrity but maybe its too old algorithm.
And I checked 7.20 run normally if disable fips policy, too. (with some filters are disabled idk why :))

One more, I saw #1033 issue and I know enable fips policy may seems odd.
But, as AdGuard worked with it at previous version, I think latest version should work, too.

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

3 participants