Some people will like this but after a quick look-see it's not my cup of tea, with apologies to the dev, who deserves kudos for responding in the GOTD comments. Per the FAQ, the dev is also generous, allowing multiple installations on hardware you personally use. Reading the FAQ, Fileside needs to be run as admin. to access Windows-restricted files/folders. There are a few ways to do that without the hassle of right-clicking the Start Menu shortcut, then more, then run as admin. You can add a shortcut to the desktop, which lets you right-click -> select run as admin; you can right-click the .exe file [Fileside.exe], click Properties, then the compatibility tab, then check the box for run as admin.; you can right-click the Start Menu shortcut, select open file location, then right-click that shortcut in the File Explorer window that opens, click Advanced, and then check the box to run as admin.
Monitoring the installation in a Win11 VM [semi-23H2], once installation *seemed* to finish, 3 Fileside processes continued running with around 20-30% CPU -- after ending those in Task Mgr., that never reoccurred when running the software. The app installs to Users\ [UserName]\ AppData\ Local\ Programs\, with 3 folders added to Users\ [UserName]\ AppData\ Local\, and one to Users\ [UserName]\ AppData\ Roaming\. I recorded 111 new registry entries on installation, 105 from activation, though a majority were cache related. A copy of the setup file [installer.exe] is added to Users\ [UserName]\ AppData\ Local\ fileside-updater\.