Please see here for latest: Re: MacBook Pro Retina Bootcamp USB set address failed
Submitted the bug.
*I thought I'd focus on the latest manifestation of the problems which is in this ticket here with Anniversary Edition
*I made the point that a lot of us have the bug, therefore seeing all these forum posts is more important than my particular hardware spec
* See the bug ID and the text of my bug entry below. I will post updates here and also on the microsoft forum mentioned below
*I haven't replied to MS yet, perhaps I should raise a bug formally with them also? Please do give me suggestions what to reply to them with
If anyone else would care to join me in submitting or resubmitting a bug request, that would help.
Bug ID: 29809345
New Mac Problem
Classification: Serious Bug
Reproducibility: Always
Title: MacBook Pro Retina Bootcamp USB set address failed
Description:
For over three years now (see date of first post on first link below), a wide range of Macbook users have reported severe problems with the bootcamp SD card driver, we think for a particular Broadcom chipset. The issue got progressively worse with the release of Windows 10, and now with the Windows 10 Anniversary Edition (1607 release) the SD Card is inoperable: on boot we receive Set Address Failed (see last link for latest post) and no known workaround exists. Please see the following links for a large variety of users posting detailed reports on this issue:
https://discussions.apple.com/thread/5408471?answerId=30152035022#30152035022
https://discussions.apple.com/thread/7325142?answerId=29396575022#29396575022
https://discussions.apple.com/thread/7352538?answerId=31154740022#31154740022
https://discussions.apple.com/thread/6459962
https://discussions.apple.com/thread/7352538?answerId=31154928022#31154928022&ac_cid=tw123456#31154928
Please see the following link for progression of the issue with Microsoft:
https://answers.microsoft.com/en-us/windows/forum/windows_10-hardware/sd-card-de tection-issue-in-windows-installed-on/7a2a896a-335f-4504-aa88-952ec8ed2eb3?msgI d =ea9662be-39e4-4121-8706-ab0d49d27d27
Please see the following links for a random selection of non-Apple and non-MS forum posts of users suffering from the issue
http://superuser.com/questions/1129612/unknown-usb-device-set-address-failed-for -apple-sd-card-reader/1159547
https://www.reddit.com/r/techsupport/comments/4t6aa8/bootcamp_windows_10_doesnt_ recognize_sd_card/
https://www.reddit.com/r/applehelp/comments/3s0g2c/boot_camp_windows_8110_detect ing_sdcard_reader_as/
Steps to reproduce:
Boot into bootcamp on a Macbook pro Retina (other users have found the problem in Macbook Airs also - see posts) which uses the affected broadcom chipset, running Windows 10 Anniversary Edition. Try to access content stored on an SD Card using the inbuilt SD Card reader.
Expected Results:
Device Manager (and an OS-desktop popup) will show "USB Set Address failed" as detailed in https://discussions.apple.com/thread/7352538?answerId=31154740022#31154740022 and included in the attached files
On a previous version of Windows you may instead suffer the SD card not resuming from sleep or some lesser issue
Actual Results:
Device manager shows "USB Set Address Failed" and no known workaround is applicable. On older versions of windows you may experience a lesser issue that still renders your SD card unreadable.
Configuration:
See the below configuration of my mac, see also all included forum links for many other hardware configurations where this occurs and the general conclusion that this affects the Broadcom SD-card driver chipset
Hardware Make and Model & OS X Version/Build
Model Name: MacBook Pro
Model Identifier: MacBookPro12,1
Card reader:
Product ID: 0x8406
Vendor ID: 0x05ac (Apple Inc.)
Version: 8.20
Serial Number: 000000000820
OS: El Capitan 10.11.6 and Windows 10 Anniversary
Additional notes:
See all the links mentioned. Note the number of users affected, the diversity of their hardware, the amount of time that has expired since reports came in and the perceived lack of faith from users in a resolution due to Apple and Microsoft (for whom users are both paid customers) not seeking to resolve the issue. Hence I would suggest this is very urgent.