Skip to main content

Elgato issues a fix for HD60 Pro issues on the Fall Creators Update

Alienware Aurora
Alienware Aurora

Sadly, no major OS update passes without some issues being caused somewhere, and in the case of the Fall Creators Update, Elgato's PCIe capture card, the HD60 Pro, is affected in a pretty major way.

The driver for the card can go into an endless reboot loop rendering it completely useless. So, Elgato has pumped out a quick fix but is emploring its customers to update their card's firmware and drivers before installing the Fall Creators Update.

As some of you may be aware, the Windows 10 Fall Creators Update is out, and as with any major OS update, low-level changes can have effects on hardware. Unfortunately, this time the HD60 Pro is affected.The issue: With the Windows 10 FCU (Fall Creators Update), the HD60 Pro driver will get stuck in a reboot loop and the firmware will be blank.The solution: We have released a new software update, 3.60.108, which includes a new driver that fixes the issue.

If you've already grabbed the Fall Creators Update, Elgato is advising rolling back first, then installing its new drivers and firmware. I have an HD60 Pro and haven't seen these issues myself, but they're clearly widespread enough given the message.

Find out more including full recommended steps on the Elgato Gaming subreddit and grab the latest updates from the company's downloads page.

Richard Devine is an Editor at Windows Central. A former Project Manager and long-term tech addict, he joined Mobile Nations in 2011 and has been found on Android Central and iMore as well as Windows Central. Currently you'll find him covering all manner of PC hardware and gaming, and you can follow him on Twitter and Instagram.

6 Comments
  • the program coudl use some updating too. its so buggy. its hard for a youtuber gamer like me to keep up with the uploads cuz the program keeps freezing.
  • Ouch, rolling back first? I hope they can get a FCU compatible update out pretty quick, have always had issues rolling back so now I just wait several weeks after a major update is released. Even then that update still causes no end of headaches. Goes to show why you shouldn't fire all your dedicated testers....
  • I see some of FCU users having more problems as compared to CU. 😐
  • Yep. As always because developers are too stupid to test against the PUBLICLY AVAILABLE PRE-RELEASE VERSIONS.
  • Maybe you're right. After TH2, I got update problems while downloading CFU via Update settings. But this problem didn't face by all users. That's why I always choose ISO to install major update and mscatalog for Cumulative patches.
  • OEM Guy 1: So as we know there's a new Windows release coming out since we don't live under a boulder, and there are publicly available releases for testing, think we should make sure our products work on the coming version? OEM Guy 2: Naaaaah. It'll be fine. I mean, what? Are they going to change something that introduces some problem with our drivers? OEM Guy 1: Yeah. It happens with alarming regularity and like clockwork we're never ready and our customers end up hosed. OEM Guy 2: Meh. OEM Guy 1: Good point. I'll go back to staring at the wall!