ISboxer suite does not start

I have removed and reinstalled .net 3.5 and I have removed registry keys and deleted InnerSpace folder from Program files to try a fresh start, still get the above error message and numerous other after it when attempting to start ISBoxer Suite

browsing around on forums and i have not found a similar issue... help!?

few more I can post if needed

[lax]

Looks like you've replaced Inner Space's GameConfiguration.XML and InnerSpace.XML files with copies of ISBoxer profiles. This kills the ISBoxer.

1. Close Inner Space
2. Open up the Inner Space folder and delete InnerSpace.XML and GameConfiguration.XML.
3. Launch Inner Space

Both files will be automatically re-generated. If you manually added games to Inner Space using Add Game, you will need to do that again

Removed those files and they were automatically recreated with launching innerspace.exe, but I get the same error message when attempting to start ISBoxer Toolkit.exe

[lax]

Delete ISBoxerToolkitProfile.GlobalSettings.XML as well, to reset ISBoxer to opening ISBoxerToolkitProfile.XML.

These are the only XML files I have in C:\Program Files (x86)\InnerSpace\

I have removed the entire folder and re-installed in hopes that it would get me to a working state, but still having the issue. I am not concerned about my previous configurations, just want to get it back working

any update on this? been playing with multiple windows but I would really like to get isboxer working

Thanks,
Phneak

[lax]

Re-reading the error messages you posted, it says the issue is within Microsoft-provided Regex code while reading XML, and says "Attempted to read or write protected memory. This is often an indication that other memory is corrupt."

That is completely bizarre and unexpected while starting ISBoxer. I would say either you need to explicitly use "Run as Administrator" to launch ISBoxer, or you may need to disable some security software (or some other software that is stopping ISBoxer from reading the files but again we have NOT seen this error before), or you may need to reinstall Microsoft .NET Framework 3.5 with Service Pack 1..... otherwise you have some unknown problem on your PC.