Jump to content
LaunchBox Community Forums

LaunchBox not that portable after all?

Recommended Posts


Installed LaunchBox on a local drive, ran fine, copied the LaunchBox folder to a networked drive location (I have lots of PCs spread around the house). Ran it, using the same PC(So dependencies are fine) but from a remote folder instead and got the following error...


An attempt was made to load an assembly from a network location which would have caused the assembly to be sandboxed in previous versions of the .NET Framework. This release of the .NET Framework does not enable CAS policy by default, so this load may be dangerous. If this load is not intended to sandbox the assembly, please enable the loadFromRemoteSources switch. See http://go.microsoft.com/fwlink/?LinkId=155569 for more information.

App:     LaunchBox
Version: 8.3
Type:    System.NotSupportedException
Site:    System.Reflection.RuntimeAssembly nLoadFile(System.String, System.Security.Policy.Evidence)
Source:  mscorlib

   at System.Reflection.RuntimeAssembly.nLoadFile(String path, Evidence evidence)
   at System.Reflection.Assembly.LoadFile(String path)
   at (Object , ResolveEventArgs )
   at Unbroken.LaunchBox.Desktop.Program.CurrentDomainAssemblyResolve(Object sender, ResolveEventArgs args)
   at System.AppDomain.OnAssemblyResolveEvent(RuntimeAssembly assembly, String assemblyFullName)

Recent Log:

   16:41:17 Exception

Seems to have a problem with the .Net loadFromRemoteSources compile switch?

Share this post

Link to post
Share on other sites

I found a solution to this problem. 

.NET framework does not allow assemblies to be loaded from a network location.

You can modify this behaviour by doing the following:

Edit Launchbox.exe.config

place the following line below <runtime>

<loadFromRemoteSources enabled="true"/>

You can also do this for bigbox.exe.config

  • Like 2

Share this post

Link to post
Share on other sites

Sorry for the late reply Arsim2222, I actually gave up on LaunchBox because of this problem.


Thank you! I can now get back into using LaunchBox because of your fix! :x


Share this post

Link to post
Share on other sites

I have come here to specifically reply to this, as a thanks, for helping me resolve my issue. For some reason, (Windows 10 update?) LaunchBox would crash during the "initializing" phase of booting up (after clicking the .exe). I enabled logs, checked them and confirmed what was written above. I used the above fix and it worked. Thanks @arsim2222.


Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...