Quaros

Sorry for the confusion but I am reacting in this thread because LaunchBox is behaving exactly the same when installing themes via BigBox. So I am not adding any custom theme via adding folders and unzipping files. I am just using the inbuild user interface to download themes that are presented up there. I download those, apply as main theme and only the menu's are changing not the actual themed user interface. The default theme graphical user interface part is still loading with the newly installed themes menu. I hope this make anything clear? Maybe the themes unzipped via the BigBox menu also have the same issue with DLL's? I am not sure but I am sure non of the BigBox provided themes are working except the default one

I have tried several themes, none of them are working. I have used Launchbox for a long time now, but I have never seen this before. This problem happens on a new installation of Launchbox (13.17) on Windows 10 Enterprise IoT. I am able to download the theme and after I hit apply as main theme only the menu of the theme has changed but still the default theme is loaded as the graphical interface. It's really a weird issue. Launchbox is running on it's own SSD which is seperate from the OS NVME. I never had this issue in Windows 11 before.

Also the themes that can be downloaded via BigBox don't work for me. I download them, apply them as main theme but only the menu theme changes not the actual graphical part of the theme. It still keeps the default theme. Any help would be appreciated. Is it a bug?

Not original but this feature is also one I would like to see in the near future. There are some platforms which are for instance not supported by a BigBox theme.

I understand that it is maybe outside of the intended use case, but it's for me the only way to manage/control my 22TB Launchbox installation. Besides the problems I had that were mentioned above it is running perfectly fine now. Especially since I have added SSD caching to my NAS and upgraded to a 10Gbit network backbone.

Thank you! That fixed my installation again. This information should be in the FAQ of LaunchBox.

So purely out of curiosity how did you do that and what apps did you use for it?

And another one here. Would love to have an import function.

It's already a very old topic, but I am facing the same problem. I have no problems running LaunchBox from my local SSD, but when I try to start it from my mapped network share it hangs with the same error. So I was wondering where did you change these settings? I am running a Synology NAS with a Shared Folder on which I have set the permission Read and Write to Everyone and I did the same for the 'NTFS' permissions for the LaunchBox folder on the share. Still no luck starting LaunchBox though. What did I do wrong?