Please edit your Original Post (“OP”) above - or - Repost your issue, in order to reflect the template and guidelines, and Brave Support may be more than happy to assist you.
Guidelines - Before posting, please:
Search the forum to see if anyone else has already posted or resolved the same issue you’re having.
Ensure that you’re posting in the appropriatecategory — please use the appropriate category when posting to ensure that whoever assist you has a clear idea of what product or platform you are using.
Fill out the template that appears in your editor when posting as it contains all the boiler-plate information surrounding your issue. It will help the Support team members and other Community members to efficiently assess and resolve your issue. NOTE: “Uncategorized” posts do not have a template, so please ensure you’re posting to the right category as mentioned above.
Tag your post appropriately – use tags to help track and organize threads on this forum.
Brave uses the OMAHA updater, which is open source alternative to what Chrome uses, and probably what Edge uses as well.
OMAHA update can only update in two locations, Program files when you install with admin rights and %localuserdata% when you install without admin rights, but the User Data never changes, it always goes to where it goes.
Brave by not having a custom installer, they have the way to use Policies and all that which is good for enterprise, unlike other Browsers.
So, in that case, what you have to move is the User Data.
Brave in their Github page already offers a zipped version of the Browser which doesn’t have the updater, which means you can place it anywhere you want, and then you can create a BAT file [batch file?] or Shortcut and use whatever directory you want for the User Data.
You can use --user-data-dir="User Data" and the folder will be placed wherever the Brave.exe you are starting is.
If you want to keep the ‘updater’ but move the files, then you should use Junctions or Symbolic Links, which is exactly what Windows users all over Windows, so using them will not cause issues.
The best way to use it is by installing Brave without admin rights, so everything Application, Updater and User Data will be placed in the same folder, in %localappdata%\BraveSoftware
Then you use move it somewhere else and create the junction or symbolic link to it in the same place so Updater and everything works as expected.
It is the way Chromium works, this has to be something Chromium offers easier without using the --user-data-dir=.
One test, is, without Brave Browser (“BB”) running, set aside (for example, move to the Desktop:) the “User Data” folder:
C:\Users[UserName]\AppData\Local\BraveSoftware\Brave-Browser\User Data
Start up Brave Browser. A new, fresh “User Data” folder (including contents, sub-folders, a new default user Profile) will be created.
But the test question, is, Will BB then launch?
If BB will launch, then the problem is somewhere in the old “User Data” folder.
If BB will not launch, then the problem is the original installation.
If BB Beta will launch, then the problem is the original installation.