MobileRead Forums - View Single Post - Windows 10 signed RNDIS driver for USBNetwork

Marco77 · 11-24-2016, 04:07 PM

Hi,
Apologies for the late reply. Indeed, I can confirm upgrading to Windows 10 Anniversary (1607) temporarily breaks the package signature (a bit).

In complement to @tshering's instructions, it is possible that in the device's "driver tab", the digital signer is an "unsigned publisher".

If that bothers you, right-click on the "Kindle USB RNDIS Device (USBNetwork enabled)" device, select "Uninstall" and then tick the "Delete the driver software for this device".

Then, unplug the USB cable and plug it back again. The Kindle should now reappear as a COM port, possibly with a slightly different name, such as "COM4" instead of "COM3". Then, start over with instructions from the first post.

The digital signer should be back to "MobileRead-CodeSigning-CA" again to reflect this change.

11-24-2016, 04:07 PM	#18
Marco77 Connoisseur Posts: 55 Karma: 8430 Join Date: Mar 2016 Device: PW3, Clara HD, PB740	Hi, Apologies for the late reply. Indeed, I can confirm upgrading to Windows 10 Anniversary (1607) temporarily breaks the package signature (a bit). In complement to @tshering's instructions, it is possible that in the device's "driver tab", the digital signer is an "unsigned publisher". If that bothers you, right-click on the "Kindle USB RNDIS Device (USBNetwork enabled)" device, select "Uninstall" and then tick the "Delete the driver software for this device". Then, unplug the USB cable and plug it back again. The Kindle should now reappear as a COM port, possibly with a slightly different name, such as "COM4" instead of "COM3". Then, start over with instructions from the first post. The digital signer should be back to "MobileRead-CodeSigning-CA" again to reflect this change.