Cannot connect to cortexes

Hey guys, I know this is a constant problem, but I can’t get the vex cortex to update firm ware.
• “No Communication link available”
• “At least 3 cortexes will not connect to communication mode.”
• “2 Currently do not register as Vex Robotic Comm Ports, instead they show up as IFI MCP2458 HID.”
• Before they stopped registering as Comm Ports those 2 registered as having communication, and I tried to download the firm ware. Then, they gave an error “Failed to initiate Master CPU downloading Mode”

• Another cortex accepted a blank program - then crashed robot C. When I re-opened RobotC, and tried to load the blank program I got the firmware-52 error(see attached image) and robot controller failed to respond (see other image). Then I tried to update the firmware, and got a loading bar"wait for 15 seconds…" and then the error “Failed to initiate master CPU downloading mode” (see attached). The vexnet upgrade utility recognized and updated that cortex. After that it still shows up as a Comm port, but robot C still won’t load code into the bot, and still cannot update the firm ware.

Things I have tried:
• Vexnet upgrade utility. When the cortexes are recognized as Comm ports it works - but they still wont accept firmware upgrades.
• Uninstalling and re-installing the VEX USB Driver
• Power cycling - every which way.
• Changing batteries and checking the voltage on the batteries
• Different USB Cables
• Different USB Ports
• Running RobotC as an administrator

It was working fine up until recently, I was able to update the firmware when there were problems connecting to the student PCs.

PC features:
Windows 10
RobotC is up to date
We do a lot of virtual worlds

Please help - my class is going to grind to a halt if I can’t get these working.
Firmware 10-52.PNG
controller failed to respond.PNG
Failed to enter master cpu mode.PNG


Thank you for the detailed information.
First thing I would like to check is that the correct drivers are in place. Can you please email me a screenshot of your Windows Device Manager under the “Ports” section?

It should look like the example attached.
This will help us isolate the problem.
VEX Robotics Comm Port (While Connected).png