> In an effort to resolve this I remove RD (Apps & Programs); Shut down and then restarted. Then downloaded the latest pre-release (2.5.0.5296) and installed it. The issue remains and Vogel612's culprit seems to be the one as it is the last entry in the trace.
> The problem here seems to have been a stale reference to the RD unit testing library in the project itself. When we tried to [add the reference](https://github.com/rubberduck-vba/Rubberduck/blob/5d7369a3c8ed8df1848bd3583c0fb6a0e97887b7/Rubberduck.UnitTesting/UnitTesting/VBEInteraction.cs#L109), it failed because a reference with the same project name was already present.
We usually remove the reference, if it already exists [here](https://github.com/rubberduck-vba/Rubberduck/blob/5d7369a3c8
> The problem here seems to have been a stale reference to the RD unit testing library in the project itself. When we tried to [add the reference](https://github.com/rubberduck-vba/Rubberduck/blob/5d7369a3c8ed8df1848bd3583c0fb6a0e97887b7/Rubberduck.UnitTesting/UnitTesting/VBEInteraction.cs#L109), it failed because a reference with the same project name was already present.
We usually remove the reference, if it already exists [here](https://github.com/rubberduck-vba/Rubberduck/blob/5d7369a3c8
> I did some testing with a debugger attached. The problem is the following.
- In the name we get from the registry is `Rubberduck AddIn` as displayed in the VBE's references toolwindow. - The name on the reference in the project`s references collection is `Rubberduck`.
Accoringly, `FindReferenceByName` never finds the reference and, thus, never removes it. It works if the reference is up to date because we have another check that verifies that a reference with the same path does not ex
VBA Rubberducking
VBA Rubberducking