Unable to load NCrunch in VS2017 after crash during test configuration

NCrunch and VS crashed while I was configuring global options in NCrunch

When i start VS i get this erromessage:
“ Microsoft Visual Studio The 'nCrunch.VSIntegration2010.CrunchPackage, ! nCrunch.VSIntegration2017, Version=3. 11.09, Culture-neutral, PublicKey Token=01d101bf6f bff3e0aea' package did not load correctly . The problem may have been caused by a configuration change or by the installation of another extension. You can get more information by examining the file 'C:\Users\werenskjold\AppData\Roaming\Microsoft \VisualStudio\15.0 102b856c\ActivityLogxml Restarting Visual Studio could help resolve this issue. Continue to show this error message? ”

I have tried manual installation, and i have followed these instructions https://www.ncrunch.net/documentation/troubleshooting_installation-and-setup-problems

This is content from the log ActivityLog.xml


<entry>
<record>998</record>
<time>2017/09/22 00:29:46.939</time>
<type>Information</type>
<source>VisualStudio</source>
<description>Begin package load [nCrunch.VSIntegration2010.CrunchPackage, nCrunch.VSIntegration2017, Version=3.11.0.9, Culture=neutral, PublicKeyToken=01d101bf6f3e0aea]</description>
<guid>{14D2CAB3-EE7F-496E-BF5D-C67D2CBDD84D}</guid>
</entry>
<entry>
<record>999</record>
<time>2017/09/22 00:29:47.416</time>
<type>Error</type>
<source>VisualStudio</source>
<description>LegacySitePackage failed for package [nCrunch.VSIntegration2010.CrunchPackage, nCrunch.VSIntegration2017, Version=3.11.0.9, Culture=neutral, PublicKeyToken=01d101bf6f3e0aea]Source: &apos;mscorlib&apos; Description: Input string was not in a correct format.&#x000D;&#x000A;System.FormatException: Input string was not in a correct format.&#x000D;&#x000A; at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer&amp; number, NumberFormatInfo info, Boolean parseDecimal)&#x000D;&#x000A; at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)&#x000D;&#x000A; at nCrunch.Core.Configuration.CPUCoreConfigHelper.&#x0002;.&#x0003;(String &#x0002;)&#x000D;&#x000A; at System.Linq.Enumerable.WhereSelectArrayIterator`2.MoveNext()&#x000D;&#x000A; at nCrunch.Core.Configuration.CPUCoreConfigHelper.GetCoreMaskFromCoreDescriptor(String coreDescriptor)&#x000D;&#x000A; at nCrunch.Client.ClientThreadAffinitiser.ApplyProcessorAffinityToAllThreads()&#x000D;&#x000A; at nCrunch.VSAddIn.VsServiceInitialiser.InitialiseServiceLocator(Boolean isVSRuntimeEnvironment, Nullable`1 vsVersion)&#x000D;&#x000A; at nCrunch.WpfUI.WpfServiceInitialiser.InitialiseServiceLocator(Boolean isRuntimeEnvironment, Nullable`1 vsVersion)&#x000D;&#x000A; at nCrunch.VSIntegration2010.CrunchPackage.Initialize()&#x000D;&#x000A; at Microsoft.VisualStudio.Shell.Package.Microsoft.VisualStudio.Shell.Interop.IVsPackage.SetSite(IServiceProvider sp)</description>
<guid>{14D2CAB3-EE7F-496E-BF5D-C67D2CBDD84D}</guid>
<hr>80131537</hr>
<errorinfo></errorinfo>
</entry>
<entry>
<record>1000</record>
<time>2017/09/22 00:29:47.429</time>
<type>Error</type>
<source>VisualStudio</source>
<description>SetSite failed for package [nCrunch.VSIntegration2010.CrunchPackage, nCrunch.VSIntegration2017, Version=3.11.0.9, Culture=neutral, PublicKeyToken=01d101bf6f3e0aea](null)</description>
<guid>{14D2CAB3-EE7F-496E-BF5D-C67D2CBDD84D}</guid>
<hr>80131537</hr>
<errorinfo></errorinfo>
</entry>
<entry>
<record>1001</record>
<time>2017/09/22 00:29:47.431</time>
<type>Error</type>
<source>VisualStudio</source>
<description>End package load [nCrunch.VSIntegration2010.CrunchPackage, nCrunch.VSIntegration2017, Version=3.11.0.9, Culture=neutral, PublicKeyToken=01d101bf6f3e0aea]</description>
<guid>{14D2CAB3-EE7F-496E-BF5D-C67D2CBDD84D}</guid>
<hr>80131537</hr>
<errorinfo></errorinfo>
</entry>

Thanks for sharing this problem. This is being caused by an invalid core descriptor in your global configuration file at C:\Users\USER\AppData\Roaming\NCrunch.

If you can share the contents of this config file with me, I'll see if I can reproduce the problem on my side.

Removing or renaming the config file will reset the global settings and resolve the problem.