Sebariton Posted January 17, 2020 Share Posted January 17, 2020 Hello, I had an issue with my previous HDD so I had to re-install everything from scratch. But whenever I try to launch Launchbox, it crash without ending the boot sequence with the following log: (Inner Exception) Impossible de charger le fichier ou l'assembly 'System.Reflection, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' ou une de ses dépendances. La définition trouvée du manifeste de l'assembly ne correspond pas à la référence de l'assembly. (Exception de HRESULT : 0x80131040) App: LaunchBox Version: 10.9 Type: System.IO.FileLoadException Site: Void Initialize() Source: Caliburn.Micro.Platform at Caliburn.Micro.BootstrapperBase.Initialize() at Unbroken.LaunchBox.Windows.Desktop.Bootstrapper..ctor() (Outer Exception) 'L'invocation du constructeur sur le type 'Unbroken.LaunchBox.Windows.Desktop.Bootstrapper' qui correspond aux contraintes de liaison spécifiées a levé une exception.' numéro de ligne '10' et position de ligne '22'. App: LaunchBox Version: 10.9 Type: System.Windows.Markup.XamlParseException Site: Void RewrapException(System.Exception, System.Xaml.IXamlLineInfo, System.Uri) Source: PresentationFramework at System.Windows.Markup.XamlReader.RewrapException(Exception e, IXamlLineInfo lineInfo, Uri baseUri) at System.Windows.Markup.WpfXamlLoader.Load(XamlReader xamlReader, IXamlObjectWriterFactory writerFactory, Boolean skipJournaledProperties, Object rootObject, XamlObjectWriterSettings settings, Uri baseUri) at System.Windows.Markup.WpfXamlLoader.LoadBaml(XamlReader xamlReader, Boolean skipJournaledProperties, Object rootObject, XamlAccessLevel accessLevel, Uri baseUri) at System.Windows.Markup.XamlReader.LoadBaml(Stream stream, ParserContext parserContext, Object parent, Boolean closeStream) at (App ) at Unbroken.LaunchBox.Windows.Desktop.App.InitializeComponent() at (String[] ) at Unbroken.LaunchBox.Windows.Desktop.Program.Main(String[] args) Recent Log: 13:28:56 Exception I've checked .NET but everything seems to be OK. Thank you in advance for any help you could provide me with. Quote Link to comment Share on other sites More sharing options...
DOS76 Posted January 17, 2020 Share Posted January 17, 2020 @Jason Carr @C-Beats 1 Quote Link to comment Share on other sites More sharing options...
Jason Carr Posted January 17, 2020 Share Posted January 17, 2020 @Sebariton Sorry to hear about the trouble. This appears to be being caused by a corrupted .NET Framework install. What version of Windows are you using? 1 Quote Link to comment Share on other sites More sharing options...
DOS76 Posted January 17, 2020 Share Posted January 17, 2020 https://www.microsoft.com/en-us/download/details.aspx?id=30135 Try running this and see if it fixes it. Its the official repair tool from MS. 2 Quote Link to comment Share on other sites More sharing options...
Sebariton Posted January 17, 2020 Author Share Posted January 17, 2020 2 hours ago, Jason Carr said: @Sebariton Sorry to hear about the trouble. This appears to be being caused by a corrupted .NET Framework install. What version of Windows are you using? Hello, First of all thenk you for the quick reply. Then I'm running a Windows 10 64bits OS updated freshly by Microsoft patches. I'm seeing to version of.net present on my computer: 1 hour ago, DOS76 said: https://www.microsoft.com/en-us/download/details.aspx?id=30135 Try running this and see if it fixes it. Its the official repair tool from MS. I've run the tool and here is what it says: both action were taken and here is the result: In the end it is still not working. Quote Link to comment Share on other sites More sharing options...
DOS76 Posted January 17, 2020 Share Posted January 17, 2020 Never seen it not be able to fix the issue try opening an admin level command prompt and type in sfc/ scannow and see if the System File Checker Finds and corruption with your Windows install Quote Link to comment Share on other sites More sharing options...
Jason Carr Posted January 17, 2020 Share Posted January 17, 2020 Yeah, that's worth a shot. Otherwise, you can try completely uninstalling/removing .NET 4.8. I have unfortunately seen rare situations where the .NET Framework is corrupt and the repair tool doesn't fix it. Hopefully uninstalling and reinstalling will fix the issue. Quote Link to comment Share on other sites More sharing options...
Sebariton Posted January 19, 2020 Author Share Posted January 19, 2020 Hello, Even admin level wasn't doing anything either, to my own knowledge you can't completely uninstall .net 4 in windows 10 but I might be wrong. But before resigning myself to reinstall the OS I switched to windows insider program to get a newer version of the OS (slow ring) and this time it worked, I'm now fully back in Launchbox. Anyway, thank you very much to the two of you for your help. Regards, 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.