Configuration system failed to initialize
A simple application launcher.
Brought to you by:
madproton
Menu
▾
▴
#19 Configuration system failed to initialize
I have used MadAppLauncher for serveral years with no problem. This morning when I tried to start it, MadAppLauncher failed with the message "Configuration system failed to initialize".
The only recent change I made to the system was installing the Sugarsync cloud storage driver yesterday.
I have uninstalled Sugarsync and re-installed MadAppLauncher, but the problem persists.
Other software that uses .net, like Keepass, seems to be working fine.
Any ideas as to how to fix this?
Try renaming the file "C:\Users\<your user="" name="">\AppData\Local\MadAppLauncher\MadAppLauncher.exe_<some alphanumeric="" characters="">\1.10.0.0\user.config" to user.config.old</some></your>
Start MadAppLauncher
Note: This file contains the settings you modified using the menu. It will be recreated when you start MadAppLauncher but you will lose your current settings. If MadAppLauncher starts, then the problem is fixed.
*** To restore your old settings ...
1. Exit MadAppLaunhcer
2. Open user.config.old in Notepad.
3. From user.config.old, copy from the line <usersettings> to </usersettings>
4. Open user.config in Notepad.
5. From user.config, select/highlight from the line <usersettings> to </usersettings> and paste text from step 4.
If you are familiar with XML, you just need to replace the new <usersettings> section with the old one in user.config.old.</usersettings>
Start MadAppLauncher and see if it works.
BTW, I also started writing a slightly different/improved version called MaxLauncher. You might want to try that out. http://maxlauncher.sourceforge.net/
Cheers!
Thanks for the explanation. Actually, after I posted the question, I tried another re-installation, but I did it more thoroughly. I did the software un-installation from Control Panel, and then went through and deleted all the left-behind folders with MadAppLauncher in the name, wherever I found them. Then I did the re-installation. After that MadAppLauncher started OK. All I had to do was point it at my original .mal file.