The next set of videos that would be downloaded from a camera or camcorder would then reset it and not allow me to delete one or more of the videos when I am through with it. I dd notice that if I completely shut it down and rebooted it, I could then delete the video file(s). Since I frequently go on and off my computer, I usually just hybernate it. It would say that such and such video could not be deleted because is was open in an ffprobe.exe file. I had no problems until recently when I would have problems deleting videos I had made from my video files.
I have had and used realplayer for several years now, but upgraded to cloud when it first came out. Computer specs : DELL Latitude E6520, 64bits, Windows 7 Professional. PS -I am fairly computer literate but no specialist. Many thanks for taking the time to read this and I do hope you may be kind enough to help me find a solution. Can you or your software help in this respect ? The list starts with realsched.exe by RealNetworks and says suspended (logical since I stopped it) but the next three items are three ffprobe.exe's which take up between 20+ and 25% of CPU each.Around 80% in total, just for these three, so that my CPU reads 100% busy all the time.Īre these ffprobe.exe's the ones connected to RealNetworks? Or anything else you know of ?ġ)Is it safe to get rid of them and could your software help to do this ?Ģ)In any case I do want to get rid of RealPlayer and they give no assistance in doing this. Today, looking into a Resources monitoring feature of Windows 7, I found that this ffprobe.exe is occupying about 80% of my CPU!! Recently, my computer, usually fast and efficient, started working v. Being forced to live with it, I just closed it and never open any of their sollicitations, yet it is still there. When updating RealPlayer last year, it forced on me its latest, Cloud version.When I saw how it operated and installed itself as an individual item in the OS, I tried to uninstall it BUT it carries no uninstalling function !! Their site advised to download again but of course this did not solve the problem.
0 kommentar(er)
