Official AMD Uninstallation Utility!

phew luckily i haven't try this yet, because my download of the latest driver haven't finished yet.

but can anyone confirm if this issue also apply for windows 7 ultimate x64 ?

 

Whats wrong with Add/Remove Programs? Works fine for me every time.

 

even if it works, but it doesn't remove everything if we uninstall normally, there are a lot of traces of registry and files scattered.

that's why driver sweeper is useful for it.

 

Worked amazingly fine on Win 7
Amazing tool! I love it.

 

Worked very well on windows 7 x64

 

Yup, its all i do, run the Catalyst Install Manager from there, select remove all (as Intel), then after the restart, install the new, been doing it for eons, works every time, and its even what AMD says to do

 

if even AMD suggested that, then why did they bother making this uninstall utility ?

its because AMD knew that normal uninstall is not working as it should be, otherwise they wont bother spending resources in making this tool.

 

Havn't a clue, but here it is :-

http://support.amd.com/us/kbarticles/Pages/GPU57RemoveOldGraphicsDrivers.aspx

Ive never had any problems at all doing this, as said, its all the driver sweepers, reg cleaners, spinning around on your heads 3 times etc.... thats messing installs up imo.

 

atiman's uninstaller is far superior...i'll pass:banana:

 

@warlord : nah, i've tried atiman, it messed with my system for win7x64, never used it again ever since, so i'm only using driver sweeper, cos driver fusion is only driver sweeper reskinned.

 

Any plans for a Win 8 fix????

 

So they did a Windows 8 driver but their uninstall utility is bugged on that OS.

Ok.

 

It leaves lots of orphaned registry entries and phantom pointers which can cause problems. A run of CCleaner after using Add/Remove will prove the point.

Sorry to here this new utility is broken. I'll stick with Diver Fusion, Safe Mode and CCleaner for now.

 

I made a mistake the first time I used ATIMan... I didn't run it with the Automatic mode after the prompt shows up. So it messed up things... by using quick, it did not do it right.

Then next time, after ATIman did it's thing, I restarted my system again and it created huge problems... like the system not coming into windows... no display etc.

Turns out... you run the automatic mode and YOU CAN NOT restart the system.

Using ATIMan is so simple, it just takes longer than usual cause you have to sit through the reboots. I think most people who say they won't use it, don't know how to use it.

 

Ya, it works for me without crippling a Windows 7 x64 install, but then again lots of files left around in System32/SysWOW64.

Still doesn't remove OpenCL properly and leaves the prior higher version intact...

The Windows defender of driver uninstall utilities, looks like it's doing something, but doesn't catch ****.

Nice try, but back to ATIMan 4 me... oh well.

 

Confirmed working Correctly on Windows 7 X64 Ultimate.

I can also confirm this bug is present in Windows 8 X64 when using the de-installation tool.

It looks like win8 is not currently supported by this application just yet.

 

Managed to use this (somewhat) successfully... to the point where it removed all ATI/AMD stuff but it didn't 100% complete the process so it didn't revert to the default VGA driver, but did seem to fall back to the integrated sandy bridge GPU. Found this out (luckily) because I had LogMeIn installed and could hook into it from my phone (and could see everything perfectly). Removed the 3x ATI GPUs from device manager again (they were "unknown") then rebooted, where it defaulted to the default VGA driver for the ATI cards. Ran the removal program again, where it flashed up that it had done it's thing almost instantly and asked to reboot.

Then installed 13.2 beta

Point of note: I don't think this uninstalled the CAPs, though... so it might be best to uninstall those manually before running this.

 

Monitors go black and don't come back!

After running this or the uninstall utility in 'uninstall programs' menu my monitors go black and don't come back!

 

See my post... it may not fix it, but I'd guess that's what happened.