Lately, after upgrading my MacPro 2009 (previously flashed to 5.1) to the latest official 141.0.0 I noticed in BootCamp (Windows 7 64 bit Professional) a very strange issue...
All but one onboard USB ports are not more usable, the only functional is the one on the rear group, the middle of the three.
Looking at Hardware under Control Panel I can see many of USB Controllers not working (see attached image) but If I uninstall the tagged ones and redo an hardware refresh, they are working again and all USB ports are back to fully functional status (no more yellow triangles).
This until the next reboot...
I have already tried the usual ways of PRAM reset, SMC reset, reinstall BootCamp drivers but the issue remains. I am quite (although not absolutely) sure that until firmware 140.0.0 all the USB ports worked well since the first boot and Control Panel never reported problems.
So I have two choices: trying a (risky) downgrade to version 140.0.0 or waiting until the next major firmware upgrade in hope this issue will be resolved. I don't know if this happens also on Windows 8 or 10 but on Seven the issue is real.
This issue is present either after a reboot in Windows or a fresh boot from a previous OSX session.
All but one onboard USB ports are not more usable, the only functional is the one on the rear group, the middle of the three.
Looking at Hardware under Control Panel I can see many of USB Controllers not working (see attached image) but If I uninstall the tagged ones and redo an hardware refresh, they are working again and all USB ports are back to fully functional status (no more yellow triangles).
This until the next reboot...
I have already tried the usual ways of PRAM reset, SMC reset, reinstall BootCamp drivers but the issue remains. I am quite (although not absolutely) sure that until firmware 140.0.0 all the USB ports worked well since the first boot and Control Panel never reported problems.
So I have two choices: trying a (risky) downgrade to version 140.0.0 or waiting until the next major firmware upgrade in hope this issue will be resolved. I don't know if this happens also on Windows 8 or 10 but on Seven the issue is real.
This issue is present either after a reboot in Windows or a fresh boot from a previous OSX session.