I have installed several RC versions of Adobe Flash 10, starting in, say february of this year. But these are Release Candidates and I wanted to un-install those versions but the un-install programs seem to do a lousy job. I used the -force option and that supposedly would get rid of all that Flash software. When I try to install a previous version of Flash the installation program simply refuses to install that older software. The install program tells me that I should go to the website and download and use the latest version. And that's precisely what I don't want. The problem is that those versions 10 seem to take CPU usage to (very) high levels.
It seems somewhere in the registry there's an entry that records which Flash version was previously installed. But I haven't found those entries (yet).
Does anyone have a solution ? Does anyone know what to wipe in the registry ?
Yes, that folder still contains a number of files after un-installing Flash. Should I delete those files ? Some seem to be in use by Explorer (?) and refuse to be deleted.
Unregistering those Adobe Flash files allowed me to delete those files and to perform a new ""clean"" installation of Flash 10.1. Even a re-installation of the latest Flash RC 10.1.53,64 version went well. This ""clean"" installation also solved the problem of CPU usage going up to 100% and staying there, in Windows Explorer. CPU usage now also sometimes can go up significantly but not to the extreme levels as seen before.
I think there were some remnants of older versions of Flash and that caused - IMO - the problem to occur. So, it's VERY important to get rid of the old Flash version(s) before installing a new version.
The lastest version Adobe Flash (10.1.82.76) can be considered to be an dramatic improvement over all the previous 10.1 versions. Up to now, on my PC, it didn't push CPU usage up to 100% like the previous versions did.
I always uninstall Flash with Revo Uninstaller Free, then run Adobe's Flash Player Uninstaller which is a separate download, and then reboot. After all that it's safe to install a new Flash Player version.
I think I need to elaborate. Up to version 10.1 (not including v10.1) I never had any problem installing a new version of Adobe Flash without un-installing the previous version. I just installed the new version and that always worked. But with v10.1 the problems started (I never could go back to a previous version and CPU usage would (sooner or later) go up to 100%). But that seems to be fixed in the latest version.
I recently found out that the combination of Apple's Quicktime and Flash 10.1 was the cause for pushing up CPU usage up to 100% when I opened certain folders with Windows Explorer.
I recently found out that the combination of Apple's Quicktime and Flash 10.1 was the cause for pushing up CPU usage up to 100% when I opened certain folders with Windows Explorer.
That's quite an interesting thing to have come across Willy. What have you done now you've found that out? Uninstalled Quicktime, or just accept the problem as you know what it causing it?
I recently found out that the combination of Apple's Quicktime and Flash 10.1 was the cause for pushing up CPU usage up to 100% when I opened certain folders with Windows Explorer.
Does this still happen with the latest QuickTime version 7.6.7?
I didn't like Apple's Quicktime (including v7.67) performance anyway in the last, say 12 months. When I played a video, the video part of a *.MP4 file could freeze up (especially with large video sizes), in combination with high CPU usage. And then QT barely responded anymore. So, recently I ditched QT and started using an other mediaplayer to play *.MP4 files.
That's when I found out that CPU usage wouldn't go up to 100% anymore when I opened certain folders with Windows Explorer. To confirm it, I re-installed QT and yes, the CPU usage problem reared it's ugly head again. So, no more Quicktime for me.
It seems that the folks at Adobe have improved the Flash software. I recently needed Quicktime because I downloaded a *.MOV video and therefore I needed to re-install Quicktime. Now the ugly combination of *.flv files and Quicktime doesn't push CPU usage up to 100% anymore (/less often (???)).
Thanks to Defraggler I am able to open the temporary internet folders and move *.flv files from there to another folder. Windows simply doesn't allow the user to open those special folders.
But after using Quicktime I nearly always remove QT again. The program simply sucks (as explained above).