Some Kindle users reporting Windows 10 Anniversary compatibility issues

Microsoft officials say they're working on a fix to alleviate compatibility problems involving Windows 10 Anniversary Update and Kindle Voyager and Paperwhite e-readers.
Written by Mary Jo Foley, Senior Contributing Editor

On the heels of reports of Windows 10 Anniversary Update compatibility issues involving webcams and PowerShell, there's yet another gotcha affecting some users.


Some users attempting to plug in Kindle Voyager and Paperwhite e-readers to their computers running Windows 10 Anniversary Update to charge those devices or transfer e-books are experiencing device lock-ups and blue screens, as The Register reported on August 25.

Microsoft's statement on the matter:

"We are aware of an issue with a small number of Kindle Voyager and Paperwhite e-Readers causing an unexpected behavior when plugged into Windows 10 devices after installing the Anniversary Update. We are currently working on an update to address this issue."

The spokesperson who provided the statement above said Microsoft would not comment on when the Kindle issue may be resolved or provide details as to the number of users affected.

I've seen more than a few Windows users wondering aloud why these compatibility issues weren't reported by Insiders testing the Anniversary Update. I'm not blaming Insiders, but I am curious. In the PowerShell case, the compatibility problem seems like it may have been introduced by the most recent Cumulative Update of fixes to the Anniversary Update, rather than the RTM version of the Anniversary Update itself.

While on the topic of Cumulative Updates, Microsoft released on August 25 yet another Windows 10 Anniversary Cumulative Update -- but only to those in the Slow and Release Preview Rings.

That build, 14393.103, includes a number of fixes, reliability improvements, and updates for PC and Mobile users in the areas of Windows Ink Workspace, Edge, the Shell, and more. Maybe this will be the build Microsoft intends to provide to non-Insiders next week to fix the aforementioned PowerShell Desired State Configuration (DSC) problems.

Editorial standards