yamyoume Posted December 21, 2019 Share Posted December 21, 2019 (edited) Hey guys, I know that the commander pro is not supported in the iCUE software for MacOS, but does it really have to show up as a up? because now I'm getting this warning every time I log into macOS https://cdn.discordapp.com/attachments/263798638373896203/657749984375996436/IMG_20191220_170327.jpg https://media.discordapp.net/attachments/263798638373896203/657749394472566784/unknown.png?width=662&height=470 Edited December 21, 2019 by Technobeard changed to links Link to comment Share on other sites More sharing options...
DevBiker Posted December 21, 2019 Share Posted December 21, 2019 Discussed here: https://forum.corsair.com/v3/showthread.php?t=192465. Essentially, that's MacOS misidentifying the Commander PRO because it's apparently using the Bus Description rather than the VID and PID (as Windows correctly does). That's poor form for Apple to be doing, tbh, and reason number 45,928 that my home is an Apple-Free Zone. Link to comment Share on other sites More sharing options...
yamyoume Posted December 21, 2019 Author Share Posted December 21, 2019 hmm I was just gonna live with it, but, now "Time Machine" won't do automatic backups because it thinks we're running on batteries, is there by any chance you guys can firmware update the Commander Pro and change the Bus Description? Link to comment Share on other sites More sharing options...
DevBiker Posted December 22, 2019 Share Posted December 22, 2019 A) I don't work for Corsair. B) Why should Corsair do this and possibly cause issues with the users on Windows (where it is supported) when it's Apple that is misidentifying the device and using the exact wrong methodology to identify the device? Maybe you should go ask Apple if they're going to fix their busted non-spec USB identification scheme. Link to comment Share on other sites More sharing options...
Recommended Posts