Windows 10: GATT Driver Stopped Working after Win10 Optional Update & Like Numerous Online Can Not...

GATT Driver Stopped Working after Win10 Optional Update. Some Microsoft official advisors in past MS threads suggested uninstalling GATT in Device Manager, reboot for auto reinstall. It was never reinstalled. There are many online stating they followed this foolish advice as MS advisors often instruct, and the situation was made even worse. I was reluctant to post here as MS support forums are the worst online since early 90's BBS days. MS advisors seem to post some generic copy & paste from some basic KB. They rarely reply specifically to the victims. They often make the situation

:)

 

How to stop Win10 updating graphic driver!?

What the hell am I suppose to do to finally shut up god damn retarded Windows 10 driver updating? This bullshit will drive me insane.

Catalyst 15.7 that comes through Windows Update is BROKEN for AMD E-450 APU. It just doesn't work, it's slow as fuck and makes Youtube unusable even for 480p videos which is unacceptable.

I've disabled the driver updating in System panel, erased all drivers, installed Catalyst 14.12 WHQL for Win8.1 that actually works fine on Win10 even for Youtube, but after few hours, god damn retarded Windows 10 reinstalls the broken Catalyst 15.7 through Windows Update absolutely silently. I just notice everything works like shit and when I check display driver, it's the damn 15.7 again that's installed. Even if I do Driver Rollback, retarded Win10 AGAIN reinstalls it on its own after few hours. WHAT THE HELL!?

This is the EXACT reason why I was against moronic driver updating in Win10 and I fucking have to be the one affected by it. God damn Murphy's Law.

What else can I do for Windows 10 to stop updating the god damn driver!? This is insane.

 

How to stop Win10 updating graphic driver!?

Also on Win10 home and no auto-driver update.

 

How to stop Win10 updating graphic driver!?

Since when does this method work?.. We had a thread about this issue, right before July 29, and everybody confirmed that it does nothing on RTM build. Hence why Microsoft had to release a standalone troubleshooting module that would allow users to block certain drivers offered through WU.