--disable-encryption not working anymore

Hi,

There is currently an issue with the patch to disable encryption to allow portability (Eloston/ungoogled-chromium#591) on Windows. Looks like this regression occurs between Chromium 76.0.3809.132 to Chromium 77.0.3865.75 (see https://github.com/brave/brave-core/pull/3385#issuecomment-545787343 and portapps/brave-portable#33). Do you have any idea about this @tangalbert919 @Eloston? I would like to fix this on Brave and ungoogled-chromium but hard to find something relevant. I have this output when I open ungoogled-chromium (80.0.3987.149) if --disable-encryption is enabled:

[1896:2800:0323/163555.011:ERROR:os_crypt_win.cc(102)] Failed to decrypt: Clé non valide pour l’utilisation dans l’état spécifié. (0x8009000B)

Thanks

[kleuter]

Not true, try running your ‘portable’ app on another machine. https://portapps.io/app/ungoogled-chromium-portable/#known-issues

[jiangzhenjerry]

Just to clarify - I’m not saying the location of the [profile] folder (could be [user-data-dir]\Default, or [user-data-dir]\Profile 1, [user-data-dir]\Profile 2… based on your use case) is changed. I’m saying the Cookies file has moved. For example, prior to 97, it likely resided as [user-data-dir]\Default\Cookies, but after 98 it is [user-data-dir]\Default\Network\Cookies. If there is a script that deletes the Network folder as a whole, then the Cookies file inside it is deleted as a result. I do write my own (super aggressive) script to clean the junks of Chrome, so such minor internal file shifting sometimes causes me trouble.

And yes please try a new profile. That’s a good first-step for trouble-shooting.