Every download is marked as "This type of file can harm your computer".

[rodrigodzilla]

Downloading any type of file displays the "This type of file can harm your computer" message every time. It's still possible to download the file but with many files it's bothersome.

[dennyamarojr]

Probably a flag is enforced that cause this message, don't know which flag it is

[ahtaarra]

I don't see this type of warning dialogue on ungoogled-chromium v87.0.4280.88-3 which I built from AUR without any own modifications (but changed a bunch of settings after installing).

Try enabling and disabling the option for asking for file location on each download and see whether that makes any difference. Also, why not include the version number?

[chiragwad]

facing the same issue on UC Version 87.0.4280.141

[chiragwad]

I don't see this type of warning dialogue on ungoogled-chromium v87.0.4280.88-3 which I built from AUR without any own modifications (but changed a bunch of settings after installing).

Try enabling and disabling the option for asking for file location on each download and see whether that makes any difference. Also, why not include the version number?

tried both but message still shows on UC Version 87.0.4280.141

[xNaCly]

Version 87.0.4280.141 (Developer Build) (64-bit)
Same issue here:

[rodrigodzilla]

Try enabling and disabling the option for asking for file location on each download and see whether that makes any difference.

Same issue. After selecting the destination it's still appearing on the downloads bar.

Also, why not include the version number?

My apologies, I'm using 87.0.4280.141-1 (64-bit)

[ahtaarra]

I have used nix package manager (on my Arch Linux install on which I had previously built and installed v87.0.4280.88-3 from AUR) to install ungoogled-chromium v87.0.4280.141 but I'm unable to reproduce this warning with the same 'profile' (or 'person').

Moreover, I also tried creating a new 'person' using the latter build (and tried it once again after pressing the 'clear all' button at the chrome://flags page on another fresh 'person' even though no flags were seemingly modified) and after that file-picker was opened and I selected the destination and the filename, there was no such warning.

[Ahrotahn]

I don't encounter this on arch.

@rodrigodzilla, @blackbeardth, @xNaCly: What platform are you on? Whose build are you using? Does the same thing happen with a new chromium profile?

I'm pretty sure that this is part of the safebrowsing stuff that is removed, so something seems to have gone wrong with the build you're using.

[xNaCly]

@Ahrotahn Im on newest windows, using the newest ugc build and its happening with every download.

[dennyamarojr]

This is related to Safe browsing, I'm make some research and it seems the fix is apply regedit tweak to Safe Browsing, to Chromium (that applies to ungoogle chromium too, that could fix the issue)

[rodrigodzilla]

The issue is happening on Windows 10. I'll soon try to get the latest ungoogled-chromium release on my other laptop using Manjaro Fedora 33 and report if the issue still happens.

EDIT: Since the AUR compilation took many hours with no progress (and pointless because @dennyamarojr already did let us know the issue's not happening on Arch), so instead I decided to change the distribution to Fedora.

[rodrigodzilla]

Fedora 33, no warning appeared. Seems likely a Windows only issue.

[dennyamarojr]

For Windows users, open CMD as admin and them paste this command:
reg add "HKLM\SOFTWARE\Policies\Chromium" /v "SafeBrowsingProtectionLevel" /t REG_DWORD /d 0 /f

After that, open ungoogled chromium, and in the address bar type chrome://policy and check if the SafeBrowsingProtectionLevel looks like this screenshot

[J4gQBqqR]

For Windows users, open CMD as admin and them paste this command:
reg add "HKLM\SOFTWARE\Policies\Chromium" /v "SafeBrowsingProtectionLevel" /t REG_DWORD /d 0 /f

After that, open ungoogled chromium, and in the address bar type chrome://policy and check if the SafeBrowsingProtectionLevel looks like this screenshot

Tried on Windows 10 installation, does not work.

This is prompt for download really annoying.

[notwa]

Same problem here. I'm using this release (87.0.4280.141-1) on Windows 10.0.18363. I tried the cmd to add the "SafeBrowsingProtectionLevel" registry key, and while it did appear in chrome://policy, it did not affect the issue. I also tried backing up %LOCALAPPDATA%\Chromium and reinstalling, but the issue persists.

[dennyamarojr]

For Windows users, open CMD as admin and them paste this command:
reg add "HKLM\SOFTWARE\Policies\Chromium" /v "SafeBrowsingProtectionLevel" /t REG_DWORD /d 0 /f
After that, open ungoogled chromium, and in the address bar type chrome://policy and check if the SafeBrowsingProtectionLevel looks like this screenshot

Tried on Windows 10 installation, does not work.

This is prompt for download really annoying.

I'm using Windows 10 and works, did you try to use the code with CMD as admin?

[dennyamarojr]

Here's some screenshots

Using the code:

After press enter:

My Windows 10 version and build:

The command:

reg add "HKLM\SOFTWARE\Policies\Chromium" /v "SafeBrowsingProtectionLevel" /t REG_DWORD /d 0 /f

[dennyamarojr]

And here's the screenshot from the browser:

[J4gQBqqR]

Here's some screenshots

Using the code:

After press enter:

My Windows 10 version and build:

The command:

reg add "HKLM\SOFTWARE\Policies\Chromium" /v "SafeBrowsingProtectionLevel" /t REG_DWORD /d 0 /f

Hi, I am doing exactly the same thing, and after doing so, I can see the policy value is 0 inside of my browser. But I still see those download alerts.

[dennyamarojr]

Here's some screenshots
Using the code:

After press enter:

My Windows 10 version and build:

The command:
reg add "HKLM\SOFTWARE\Policies\Chromium" /v "SafeBrowsingProtectionLevel" /t REG_DWORD /d 0 /f

Hi, I am doing exactly the same thing, and after doing so, I can see the policy value is 0 inside of my browser. But I still see those download alerts.

Did you go to chrome://policy and them click reload policies?

[dennyamarojr]

Because here is working and no messaging, The only that I add later was specified a Secure DNS, nothing more

here's the screenshot:

[J4gQBqqR]

No, I didn't, I restarted my browser. Would that be enough?

[dennyamarojr]

No, I didn't, I restarted my browser. Would that be enough?

I test here and it seems, need to reload the policies manually, I remove all the policies and add the command, the message still. (need update chrome://policy manually)

[dennyamarojr]

Here's the screenshot:

[J4gQBqqR]

I see, I'll reload manually this morning and feedback. Thanks!

[dennyamarojr]

Ok, check here and it seems another thing is interfering, will try add the secure dns to see if fix the issue

[dennyamarojr]

Ok, check here and it seems another thing is interfering, will try add the secure dns to see if fix the issue

After use secure dns still appearing , I will try the other settings for Safe browsing here to see if the message goes away.

[dennyamarojr]

But probably is because missing a file download_file_types.pb in C:\Users%USERPROFILE%\AppData\Local\Chromium\User Data\FileTypePolicies

Not sure, if the file really need, but all the topics I search show for this location too.

[Ph0rk0z]

I have the same issue with the latest x64 windows build and adding the policy does nothing. Furthermore I can't seem to choose download location whether the setting is on or off.

[sharpden]

As temporary workaround one can replace in file ungoogled-chromium-windows\build\src\components\download\internal\common\download_item_impl.cc string danger_type_ = danger_type; in function DownloadItemImpl::SetDangerType to danger_type_ = DOWNLOAD_DANGER_TYPE_NOT_DANGEROUS; and then re-run build

[J4gQBqqR]

This currently cannot be resolved by end user. Not every user has the capability to build from source. I am switching back to the older version. Will wait and see if this got improved in the future.

I guess issues like this are one of the downsides that we have to bear when using third party chromium based browser. Lack of settings/preference syncing is another downside though...

[icy0007]

Hi Guys
Microsoft is making contracts with sofware companies to render pirate or copied software useless.
they sell a sever with software for direct contact between both , microsoft & the software company.
software to render the software of that software company is directly incorporated into Windows 10,
starting with version 20H2 , see size of the windows isos
Win10_2004_English_x64.iso 5,268,953,088 07/25/2020 13:13 -a--
Win10_20H2_English_x64.iso 6,155,782,144 10/21/2020 20:45 -a--
Win10_20H2_v2_English_x64.iso 6,221,846,528 01/30/2021 18:58 -a--
I am now going to use Windows 7, remove all remote,firewall & defender.
Look at all the updates,most of them are there to assure connection with remote
Have a look at this :
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\mpssvc\Parameters\AppCs\AppCs firewall
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\Defaults\FirewallPolicy\FirewallRules
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\FirewallRules
There are more than 2000 rules in a full windows 10, this is not normal
this is to assure there is always connection to Windows servers
Windows 10 is an enormous spy machine,
Everything what is used onto your computer is traced
Now they are going to play policeman
So try Windows 7 or 8 to see if this is also the case
icy

[CodeSlinger69]

This appears to still be an issue in the 88.0.4324.150 builds. Sticking with build 87.0.4280.67 for the time being, which works correctly.

[J4gQBqqR]

@Eloston Could you help us check if this is a valid fix to be done in the source code?

As temporary workaround one can replace in file ungoogled-chromium-windows\build\src\components\download\internal\common\download_item_impl.cc string danger_type_ = danger_type; in function DownloadItemImpl::SetDangerType to danger_type_ = DOWNLOAD_DANGER_TYPE_NOT_DANGEROUS; and then re-run build

Windows build is having this issue for a month now.

[icy0007]

Hi Eleston it is still happening on windows 7 & 8.1 icy

…

On Wed, Feb 17, 2021 at 3:19 AM J4gQBqqR ***@***.***> wrote: @Eloston <https://github.com/Eloston> Could you help us check if this is a valid fix to be done in the source code? As temporary workaround one can replace in file ungoogled-chromium-windows\build\src\components\download\internal\common\download_item_impl.cc string danger_type_ = danger_type; in function DownloadItemImpl::SetDangerType to danger_type_ = DOWNLOAD_DANGER_TYPE_NOT_DANGEROUS; and then re-run build Windows build is having this issue for a month now. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1337 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AI6HARPTS67UNBIQ5H25BJTS7MKSNANCNFSM4WFZRORA> .

[Yasand123]

Still not fixed.

v88.0.4324.150 on Windows 10.

[TontyTon]

same here not fixed in v88.0.4324.150 on Windows 10.

Also, there is no safe browsing toggle in settings, maybe in chromium they made the rules like - 'dangerous unless stated otherwise'.

[CodeSlinger69]

Build 88.0.4324.182 continues to exhibit this same problem.

87.0.4280.67 is still the latest build that works correctly.

[J4gQBqqR]

This issue has been plaguing Windows build for months, will it even get noticed by the developer?
Is this repository/project still actively maintained?

[Nathan-Kr]

I also have the issue, 88.0.4324.182 windows 10. The registery thing doesnt do anything unfortunatly. I searched in chrome flags but didnt find anything related to download or safe browsing. The antivirus seems to be deeply implemented in chrome, tho i know nothing about chromium, just adding for notification.

[mooms06]

.

[achesnok]

Have the same issue. windows 7, Version 88.0.4324.182 (Developer Build, ungoogled-chromium) (64-bit).

[Ph0rk0z]

I tried to add SafeBrowsingEnabled to false. Chrome says "This policy is blocked". BTW on windows 8 and probably 7 the policies moved to Wow6432Node in the registry. At least the password saving works again.

[CodeSlinger69]

This appears to be fixed in 89.0.4389.90. Thanks developers!

[mooms06]

Yes, I confirm.

[rodrigodzilla]

Can confirm that the issue has been fixed, thanks for all the hard work! Closing.