Registry fix to address file type associations from Muon

Description

Setting Brave as a default program for [some] file types produces inconsistent results at best. Opening hyperlinks, for example, generally works, but I’ve had users report that even that wouldn’t always take.

This applies to any way in which file type associations are made:

1. Via reg/command line args
2. Open With... --> Always open... from context menu
3. System Settings --> Choose a default app for each type of file

Steps to Reproduce

1. Use any method to associate a file type/extension (.jpg, .html, .tiff, etc) with Brave.
2. Test the association by opening a file of the appropriate type

Actual result:

Sometimes works, sometimes doesn’t - very inconsistent.

Expected result:

File type opens in Brave as long as it’s capable of doing so.

Reproduces how often:

Inconsistently, but often enough that you should be able to reproduce this after a few tries/file types

Brave version (brave://version info)

Brave Release channel build v0.58.18 Win10 x64

Reproducible on current release:

• Does it reproduce on brave-browser dev/beta builds? Yes

Additional Information

Report from user with additional details and test methods: https://community.brave.com/t/file-extensions-wont-associate-with-brave/39034

[lucazertyui]

Hi, I had the same issue on Windows 7 (64 bits) As explained here, for me the problem was that the value of BraveHTML in Windows Registry (HKEY_CLASSES_ROOT\BraveHTML\shell\open\command) did not match brave.exe location I changed the value and now everything works !

[SpawnMoreOverlords]

@lucazertyui modifying the registry key value at this location has fixed the problem for me too, thanks!

It was pointing at “C:\Users\myuser\AppData\Local\Brave\Brave.exe” – “%1” which must have been the path to the legacy Muon-based Brave installation.

I’ve now modified the path to “C:\Program Files (x86)\BraveSoftware\Brave-Browser\Application\brave.exe” – “%1” and it works.