Hi Alberto,

Thanks for sharing this issue.

The uninstaller should remove the NCrunch install files from VS. There are two other things to clear if you want a full reset:

- Ensure that you remove the configuration file at C:\Users\USER\AppData\Roaming\NCrunch
- Remove the _NCrunch_* directory present inside the solution(s) you're working in. This will reset any NCrunch cached data which may be contributing to the failed state

If you're able to send through a bug report or share more specific details about the problem you've been hit with, I may be able to provide better guidance on how to resolve it.

The cleaning of grid nodes is slightly different to clients. You'll probably want to clear out the snapshot storage directory on the node (this is a configurable path, but will default to the logged in user local data directory). Cleaning out the workspace base path is probably also an option in case something was left behind in there (though the node should purge this on startup anyway).

Synchronising the Nuget packages on the grid node with one of your clients might also not be a bad idea. We have noticed binary differences between the same versions of the same Nuget packages (how this happens I do not know), which has been known to cause desync between node results. The node will copy nuget packages automatically but when they differ between clients there are edge cases we haven't been able to track down.