DCS Loader 5.0 "Critical Error - Unable to Continue" - "Configuration system failed to initialize"

I still use XP (SP3) and have had no problems.  I connect with a serial cable since the USB to serial cables are slow and prone to errors.

Rebooting is odd.  Now would be a good time to run Malwarebytes and Superantispyware, both are free.  Maybe some adware, or worse, is interfering with the DCS loader.

Could be bad RAM memory.

Run a RAM test if you have one.

says a retired computer tech....

I thought I saw that when I upgraded to new Windows 10 or whatever it is called?

I had a loader that failed after upgrading to a newer loader and then trying to reuse the older version. That may have been when I saw that message.

I think something got changed and lost a line that the old loader needed to run

OK, I can answer my own question for those that search in the future.

It appears that a DCS Loader configuration file was corrupted. This is how I fixed it on my XP computer:

Look for the MTH folder in your "Documents and Settings" folder, something like:

C:\Documents and Settings\Owner\Local Settings\Application Data\MTH

In that folder, there will be folders named something like:

MTH_DCS_Conumer_Loader_V5_Url_lhakjlhvmlaigb1x1bcjrp2rjs0efzqy

Delete all of these folders (yes the folder name is misspelled 'Conumer'). That solved it for me. Thanks for all of the comments.

HI  GLAD YOU FIGURED IT OUT BUT BY THE WAY anytime you have computer issues out of the norm usually it will be a corrupted file or files in your system, a total reload or reset can usually fix your problems but not always!

I have found out usually uninstall suspected file or program or even netframe 3.5 being corrupted as mth loader needs the program to run the loader!!!uninstalling said suspected program and reinstalling your program will usually fix your problem. I sell  computers and run into these situations all the time!

sincerely hope this helps anyone in the future!

be glad to help anyone with computer issues

happy new year

Alan

p.s. even a corrupted serial usb to 9 pin tiu can cause many issues!

In my trouble shooting, I had removed .NET 3.5 and, of course, the DCS Loader itself. Reinstalling (and running Windows update to get the .NET patches) did not solve the problem.  I could install the older version of the Loader, v2.3.4, and it would run. Removing the DCS Loader didn't get rid of those folders in "Documents and Settings". I got the hint from some web page to look for "*.config" files and that's how I found them.