VS2010 crashes when "Stop Debugging (Shift+F5)" is used

Today I upgraded Isolator from 6.2.5 to 7.0.6. The built in test runner fails for many of my tests due to it not picking up on the app.config in the test project (this bug has already been reported here: https://www.typemock.com/answers/11326/). The tests failed on a NullReferenceException when trying to use a null reference returned by ConfigurationManager.GetSection().

Before I knew about the app.config bug in the runner, I tried to debug that exception. So I placed a breakpoint where the configuration is being accessed (in the class being tested) and clicked the Debug button of the failing test (in the Armadillo UI). The debug session reached that breakpoint and after seeing that it was null and realizing what the issue is, I clicked the Stop Debugging (Shift+F5) button, at which point Visual Studio crashed (and Watson uploaded a crash report).

I tried using the TypeMock test runner to debug other tests and Stop Debugging at other locations but couldn't get VS to crash. But I consistently (100% of the time) can get VS to crash if I Stop Debugging at that breakpoint when using the TypeMock test runner. If I use another runner (MSTest or ReSharper's) and Stop Debugging at the same point, VS doesn't crash.

Also, is there some way of telling the test runner to ignore certain tests or test classes (without causing other test runners to ignore it, i.e. not using [Ignore]) so that I can use it to find tests fail due to an actual bug and not the app.config issue? If not, is there a way to hide the Armadillo UI until the app.config issue is resolved?

Thanks!