https://devzone.nordicsemi.com/f/nordic-q-a/50432/the-nrf51-dongle-on-our-test-development-rack-stopped-working-recently-windows-7-update-affectEventually we got it working with the Master Control Panel again, but it will not work with our test software. I suspect a Window update change that affected links. Window7 Professional SP1 64 bit.en-USTelligent Community 13Tue, 30 Jul 2019 23:17:18 GMThttps://devzone.nordicsemi.com/thread/201375?ContentTypeID=1Tue, 30 Jul 2019 23:17:18 GMT137ad170-7792-4731-bb38-c0d22fbe4515:fc250ab7-0c11-4cdc-951a-2b1fd9810f9fMark Loy<p>Originally it stopped working with the Master Control Panel interface, which is are default utility and HW troubleshooting tool.&nbsp; After several days and many different methods on multiple computers with different revisions of SW, the dongle started working again with the MCP program.&nbsp; At that point our test software could detect the dongle, but connecting to our UUT will not work.&nbsp; This includes LabVIEW source code software and a custom contractor build EXE interface program.&nbsp; So, now that the MCP works again, it rules out the hardware and the Nordic/JLink drivers to our thinking.&nbsp; So the Windows registry either was never part of the problem, or &quot;fixing&quot; the working JLink path fixed part of&nbsp;the problem.&nbsp; Now we are wondering if some Widnows 7 update may be causing issues and if new MCP (we use 3.9.0, the only&nbsp;version we got it to work as we needed) might be a fix.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/201370?ContentTypeID=1Tue, 30 Jul 2019 21:36:19 GMT137ad170-7792-4731-bb38-c0d22fbe4515:fa051901-5ee6-4341-b6fe-768d075994f6awneil<p>Need more details!</p> <p>What, exactly, are the symptoms of &quot;not working&quot; ?</p> <p>Is the dongle correctly showing up in Device Manager?</p><div style="clear:both;"></div>