<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Development Board Driver Issue</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/34887/development-board-driver-issue</link><description>I use PCA10040 development board. COM port suddenly stopped working. The issue is visible also in Device Manager: 
 
 Google suggests that this issue is caused by Windows Update: https://answers.microsoft.com/en-us/windows/forum/windows_10-hardware/not</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 04 Jul 2018 16:18:32 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/34887/development-board-driver-issue" /><item><title>RE: Development Board Driver Issue</title><link>https://devzone.nordicsemi.com/thread/139015?ContentTypeID=1</link><pubDate>Wed, 04 Jul 2018 16:18:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3b35cf0a-68b9-4145-bb10-2b454463cf28</guid><dc:creator>Igor</dc:creator><description>&lt;p&gt;I *finally* fixed the &amp;quot;error code 39&amp;quot; problem by editing Windows Registry.&lt;br /&gt;Solution:&amp;nbsp;&lt;a href="https://www.lifewire.com/how-to-delete-the-upperfilters-and-lowerfilters-registry-values-2619222"&gt;www.lifewire.com/how-to-delete-the-upperfilters-and-lowerfilters-registry-values-2619222&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Development Board Driver Issue</title><link>https://devzone.nordicsemi.com/thread/138743?ContentTypeID=1</link><pubDate>Tue, 03 Jul 2018 11:00:18 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:38853d23-5fbe-46c3-a08f-431c5d57278d</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;I&amp;#39;m sorry. I agree. It seems like a windows driver issue, then. Have you tried this one?&lt;/p&gt;
&lt;p&gt;&lt;a href="https://www.drivereasy.com/knowledge/device-not-migrated-error-on-windows-10-solved/"&gt;https://www.drivereasy.com/knowledge/device-not-migrated-error-on-windows-10-solved/&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Edvin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Development Board Driver Issue</title><link>https://devzone.nordicsemi.com/thread/138711?ContentTypeID=1</link><pubDate>Tue, 03 Jul 2018 09:24:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e626c82d-b909-4ebd-b3a0-9dae962968a0</guid><dc:creator>Igor</dc:creator><description>&lt;p&gt;yes&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Development Board Driver Issue</title><link>https://devzone.nordicsemi.com/thread/138707?ContentTypeID=1</link><pubDate>Tue, 03 Jul 2018 09:00:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:57ba2ea3-38df-4710-b023-ef9d50d5909c</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;does the board still work on other computers?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Development Board Driver Issue</title><link>https://devzone.nordicsemi.com/thread/138678?ContentTypeID=1</link><pubDate>Tue, 03 Jul 2018 07:47:05 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ccd0b4ce-664f-43c5-89f6-0dca8c32937b</guid><dc:creator>Igor</dc:creator><description>&lt;p&gt;I tried with a regular USB to COM port adapter from a different manufacturer and got the same result as on the picture above. So&amp;nbsp;this is obviously a Windows related issue.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Development Board Driver Issue</title><link>https://devzone.nordicsemi.com/thread/138671?ContentTypeID=1</link><pubDate>Tue, 03 Jul 2018 07:06:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:dd0d8b02-ee57-46af-b5d7-3851a0922d8a</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;Also, did you try the rollback solution advised in the link that you posted in your initial post?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Development Board Driver Issue</title><link>https://devzone.nordicsemi.com/thread/138666?ContentTypeID=1</link><pubDate>Tue, 03 Jul 2018 07:00:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6df16f59-121d-448d-a22b-0548a7d24ce6</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;Could you describe what happened when you tried? Did it show up as &amp;quot;BOOTLOADER&amp;quot; in your devices?&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;BR,&lt;br /&gt;Edvin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Development Board Driver Issue</title><link>https://devzone.nordicsemi.com/thread/138546?ContentTypeID=1</link><pubDate>Mon, 02 Jul 2018 14:06:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fee966ec-fcc5-4c9e-b542-43068efa9763</guid><dc:creator>Igor</dc:creator><description>&lt;p&gt;This does not solve the problem.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Development Board Driver Issue</title><link>https://devzone.nordicsemi.com/thread/133992?ContentTypeID=1</link><pubDate>Wed, 30 May 2018 09:40:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:35132d50-7141-4da2-8646-779e27617966</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;Can you please try to hold the IF BOOT/RESET button while you power cycle the PCA10040 board, and see if it shows up as BOOTLOADER in your windows explorer?&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;If it does, try to download the latest file from &lt;a href="https://www.nordicsemi.com/eng/nordic/Products/nRF52840-Preview-DK/nRF5x-OB-JLink-IF/60180"&gt;here&lt;/a&gt;. (currently version 170724). Then drag&amp;#39;n&amp;#39;drop this file into the BOOTLOADER device. Wait for the copy to finish, and you should see LED5 blinking rapidly. Now power cycle the device without holding IF BOOT/RESET, and see if it shows up as a JLINK device, and if it works as normal.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Edvin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>