Is it just me or did W10 Anniversary screw up Mayflash gear?

Sannakji · (This post was last modified: 09-17-2016, 02:29 PM by Sannakji.)

Syncing my Wiimote up takes a lot longer now, the nunchuck will be plugged in but it won't be read, most obvious in games like Skyward Sword.

And my GC controller adaptor hasn't worked for weeks now. It works fine on my WiiU, so it hasn't died, but I can't get Dolphin to detect it for love nor money. Anyone else having these problems lately?

**JosJuice** · 09-17-2016, 05:04 PM #2

I've heard about GC controller adapters stopping working after the update. Does it work if you re-run Zadig and all that?

Sannakji · 09-17-2016, 07:54 PM #3

So this is a known issue? I wonder why mayflash hasn't come out with a fix. Damn MS. This release has been pretty bad. Constant web browser freezes etc. How can I remove and reinstall firmware on a Mayflash device? Maybe the Dolphin team could come up with a fix from their end?

**leolam** · 09-18-2016, 01:58 AM #4

Quote:Syncing my Wiimote up takes a lot longer now, the nunchuck will be plugged in but it won't be read, most obvious in games like Skyward Sword.

It's probably not Windows 10's fault, since plenty of other users are on Windows 10 and it works fine for them.

**mbc07** · 09-18-2016, 10:19 AM #5

The Anniversary Update now enforces a more strong driver signature. Zadig uses libwdi, which generates cross-signed drivers, that kind of signature is refused too in Anniversary Update unless you enable test mode. In other words, try running "bcdedit -set TESTSIGNING ON" with elevated privileges and then try running Zadig again. For the annoying watermark which is shown while in test mode, you can use "Universal Watermark Disabler" from WinAero (Google it) to get rid of it...

**ExtremeDude2** · 09-18-2016, 10:28 AM #6

I was able to reinstall my adapter after I installed the anniversary update without test mode.

**mbc07** · 09-18-2016, 10:57 AM #7

It's only enforced on fresh installs AFAIK, but I had problems even when doing an update from the previous 1511 version, it's worth trying test mode if everything else fails...

Sannakji · (This post was last modified: 09-19-2016, 05:22 PM by Sannakji.)

(09-18-2016, 01:58 AM)leolam Wrote: It's probably not Windows 10's fault, since plenty of other users are on Windows 10 and it works fine for them.

I didn't say W10, W10 was working fine for me, I specified W10 anniversary.

Guys, how do I go about removing and reinstalling the drivers?