![\"\"](\"https:\/\/www.zdziarski.com\/blog\/wp-content\/uploads\/2025\/11\/Screenshot-2025-11-27-at-2.37.49-PM-scaled.png\")
<\/a><\/p>\n<\/p>\n
My Configuration: Xgpro_T76 v13.03, Windows 11 Pro for ARM, Parallels Desktop 26, macOS Tahoe, Apple M4 Max.<\/p>\n
- \n
- Install the XGecu T76 software<\/a>. Go through the driver installation flow, which will install a nonworking<\/em> driver that is not<\/em> compatible with ARM.<\/li>\n
- Open Device Manager. You should see the “XGecu T76” listed in a trouble state. Right click, select “Update Driver”. \u00a0Choose “Browse my computer for drivers”. Near the bottom, click “Let me pick from a list of available drivers on my computer”. \u00a0Scroll down to “Universal Serial Bus devices” and click Next. Select “WinUsb Device” from the pane on the left, and select “WinUsb Device” for the model on the right. Click Next. Confirm the installation.<\/li>\n
- After updating the driver, it will now show up as a functioning USB device. You can close Device Manager.<\/li>\n
- Install\u00a0this registry file<\/a> by importing it into RegEdit (extract, then double-click). This updates important driver properties, including a crucial DeviceInterfaceGUIDs used for driver matching.<\/li>\n
- Reboot your VM. Ensure the XGecu is connected both physically and also attached in the USB menu in Parallels. When you start the programmer software, your device will be recognized.<\/li>\n<\/ol>\n
That’s it. There’s no need to disable driver signing or download Zadig. WinUSB works natively, and is signed by Microsoft. The only tricky part was getting the driver matching correct. This information can be found in the .inf file and applied to other XGecu programmers.<\/p>\n
If the registry file doesn’t work, the important thing is to take note of the DeviceInterfaceGUIDs<\/strong> in the driver registry entry’s DeviceProperties, and make sure to copy that registry key\/value pair back after updating the driver to WinUSB. In the case of 13.11, I had to do it both before\u00a0and\u00a0<\/em>after reflashing the firmware, as the reflash caused the driver identifier to change, and created a new device in the registry. Same with 13.17. I also sometimes need to power cycle and\/or restart the app after re-flash. So the order of actions for an update seem to be:<\/p>\n
- \n
- Install software<\/li>\n
- Convert driver to WinUSB<\/li>\n
- Copy over DeviceInterfaceGUIDs from old instance of driver in registry<\/li>\n
- If prompted to re-flash, proceed with re-flash. After re-flash, it will fail to reconnect.<\/li>\n
- Repeat steps 2 and 3<\/li>\n
- Power cycle unit and restart application<\/li>\n
- Should now connect<\/li>\n<\/ol>\n
What a time to be alive.<\/p>\n","protected":false},"excerpt":{"rendered":"
Running the XGecu T76 chip programmer with x86 emulation has been miserably slow, even on my M4 MacBook Pro, and so I finally took some time to figure out how to get it working on Windows 11 ARM in Parallels on Apple Silicon. There wasn’t any information online about this, except for one person who had some luck with Zadig, but had no idea what they actually did. I’ve documented the entire process below, which works with or without Zadig; the key is not only changing the driver to a native WinUSB driver, but also correcting some crucial GUIDs in the registry to ensure driver matching works in the software. For this, I’ve created a simple registry file that can be easily imported.<\/p>\n