PeeVee
-
Posts
27 -
Joined
-
Last visited
Posts posted by PeeVee
-
-
even when you don't start FF, there must be a reason the process is getting started.
have you checked MSCONFIG to see what process and services are starting that could explain that.
is there an add-on, extension, toolbar that FF has installed that is getting started with the PC?
Not that I'm aware of.
There is NO mention of Mozilla or Firefox shown under System Configuration > Startup, and the Mozilla Maintenance Service is "stopped" under the services tab.
-
You may want to invesitgate whether or not you've installed the Mozilla Maintenance Service, it may be creating rogue firefox.exes
This is the first I have actually heard of "Mozilla Maintenance Service" and I had not intentionally iinstalled this, however it is shown in the Programs (x86) folder.
When I (previously) checked Task Manager it was not shown as a running process, so I don't think it is that causing the issue.
-
Thank you all for your help.
I can now see the problem is (most likely) caused by the Firefox version update v29 as, opposed to the latest Ccleaner update.
I have reported this issue, using the Firefox Feedback, and I have given them my email address so if anyone from Firefox needs to contact me they can. I have screen snippets proving what happens if they need to see evidence.
I have experimented with my own PC and sure enough " firefox.exe*32 " sometimes continues to be shown in "Task Manager", "Processes" (show all users) after closing the browser and sometimes even when the Firefox browser hasn't been used!
In the meantime I shall use Task Manager if necessary to stop the process running in the background.
Cheers one and all.
-
What I've seen since using Firefox v29 is that it doesn't always want to exit most of the time, the firefox.exe process continues running in the background after closing the browser.
This happens with both the install version from Mozilla, and the PortableApps.com portable version. It's made worse with the addon/extension Ghostery installed because firefox.exe would never close with it installed.
If firefox.exe is still running in the background it can be manually closed using Task Manager
Hi Andavari,
Thanks, now you mention it I think I updated to v29 about the same time as I updated Ccleaner to the latest version. That would make perfect sense, thanks.
I'll get on to Mozilla Firefox and let them know. Cheers!
-
Though you've answered the question, just for clarity, a firefox clone (or chrome clone) is another browser built on the source code of firefox (Palemoon, for example) or Chrome (Torch, for example)
Many thanks Winapp2.ini.
I never knew that and had never even heard of Palemoon or Torch (showing my ignorance!). You learn something every day.
-
Although Firefox is not running, check Task Manager for any background Mozilla task.
What is your OS?
What browser do you use?, is it a Firefox clone?
If you run CC from Safe Mode without problem then it is some background, Firefox based, task that CC thinks is still running.
Hi mta,
The Operating System is 64bit, Windows 7 Home Premium, Service Pack 1.
I mainly use Google Chrome as my browser, however I do have Mozilla Firefox and Internet Explorer installed. ALL are fully up to date with the latest versions, updates & patches.
I'm unsure what you mean when you ask "Is it a Firefox clone?". I only install things from the official websites. I am VERY security minded.
My security software is checked every couple of hours (max 4 hours) for the latest virus definitions, malware updates etc;
In Task Manager (show processes from all users) the only thing that obviously relates to Mozilla Firefox is "firefox.exe*32". No other processes mention Firefox, so I cannot speak for those.
I have never run CC from Safe Mode, and I wouldn't know how! I'm not very technical; although I'm "Administrator" for all my PCs it is only because there is nobody else, and you have to have one! I get by as long as things are relatively straightforward.
Hope that answers your questions?
-
Hi,
Following the latest update (v4.13.4693 64bit) when I try to Run Cleaner it starts to work then stops with a message saying that Firefox Mozilla is still open and needs to be closed to continue. Following that it say it is taking too long to close, do I want to force it to close? I select yes and it continues to clean up as normal.
This is all very well, if it were not for the fact that although Mozilla Firefox (v29.0) is installed on my laptop it isn't in use! I only have it as a spare browser.
This has only happened since the last update.
[A registry scan shows up NO problems]
So, I'm reporting this as a new bug.
PeeVee
-
GOOD NEWS!
The latest update to v4.08.4428 seems to have fixed the problem.
-
Firstly, remove it from "Keep" folder.
Step two: you should exit all macromedia products and internet browsers. Try Ctrl+Alt+Delete to see if something is running that should be off.
Now, use CCleaner to clean-up cookies. It should work now.
Otherwise, use Auslogics Browser Care, it's freeware: http://www.auslogics...e/browser-care/
P.S. You can try cleaning in Safe Mode of your OS.
Hi enthusiast_385.
Thanks for your reply.
Re: Your suggestions...
The persistent "macromedia.com" cookie does NOT appear in the "Cookies to Keep" list, and it never has. It only appears in the "Cookies to Delete" list.
When I run Ccleaner it just keeps re-appearing in this list, as it is NOT being deleted.
At the times I run Ccleaner there are NO other things shown in Task Manager.
My original posting shows a couple of screen snippets which are pretty self-explanatory.
Ever since a programme update with a new version of Ccleaner (a couple of versions ago now) this started happening on all my PCs, which use different operating systems. I am not the only person who has noticed this.
I have proved conclusively that the fault lies in some unknown change in the way Ccleaner works, which occured in a programme update.
-
In case there is a remote possibility of anyone at Piriform actually giving a damn... this issue HAS STILL NOT BEEN FIXED.
There have been TWO newer versions released since I reported this problem and neither has addressed the issue or rectified it.
-
Hi once again.
I have just downloaded and installed the latest version of Ccleaner (v4.06.4324 (64bit)) and the problem with the persistent macromedia.com cookie HASN'T been resolved!
See attached screen snippet.
-
I would have to agree with PeeVee on this one I also have this problem. Older builds of ccleaner show all cookies as being removed but the latest version shows the exact same cookie persisting.
Many thanks render. I was beginning to wonder!
Seriously though, I have proved (to you and myself at least) the fault lies with some change in the last update of CCleaner.
I'm not doing anything until Piriform look into this themselves.
-
Sorry for the delay folks, but I can now PROVE that the latest update version is what has caused this issue.
I got an old PC out of mothballs and loaded CCleaner v4.04.4197. All cookies were removed using CCleaner.
I then installed the latest version v4.05.4250 and sure enough the macromedia. com cookie reappeared and was NOT removed by cleaning.
Please see attached screen snippet which shows the relevant details.
I am now 100% certain the fault lies somewhere in the latest version update and the ball is in Piriforms court for a fix.
-
If you read my above post again, I'm sure you'll find that providing information would potentially be very helpful in resolving this issue. As you said, it is likely a ccleaner fault.
Yes, thanks Winapp2.ini I did read your post. I'm still trying to work my way through things on all my PCs to see if I can provide more information.
I am not familiar with the "portable" version you refer to?
I had intended replying to your post in the morning as it is now 01:40 a.m. in UK.
-
I have what may be useful additional information about this problem.
I have EXACTLY the same problem on 3 of my PCs.
One PC is Windows XP, one is Vista and the other is Windows 7.
Using my lay person's logic this indicates the fault does not lie with something I have done (or not done), and would suggest the fault is with CCleaner.
All 3 PCs were working fine before the current latest CCleaner update, and since the update ALL THREE O.S.'s have the same issue:
Macromedia.com cookie is NOT removed after cleaning by CCleaner v4.05.4250.
Based on this, I have put a hold on making ANY changes to any of my PCs in order to attempt a "fix" until Piriform investigate this issue and provide an update to fix this.
-
If you look around the forums there's allot of posts about people having cookie problems for the past few versions of CCleaner. So maybe it's something that will eventually get remedied in a newer version.
Yes thanks Andavari.
It could be, as I suspected as much before I posted my issue.
Normally I find CCleaner pretty trouble free.
At the moment I'm holding off doing anything too radical.
With luck the next routine update might clean up the problem (wishful thinking?).
-
Going by what Winapp2.ini posted in post #4, if you have Google Chrome installed it uses it's own build of Flash, so you may have to go digging through your Google Chrome profile sub-folders to find it and delete it.
Thanks Andavari.
I don't think that will be necessary as I didn't have any problem with Google Chrome or CCleaner previously. It's only since the last CCleaner update that this problem has occurred, but thanks for the suggestion though.
-
Bugger, sorry I'm typing on an iPad mini and my usual typo rate is higher than usual.
That was suppose to say, download previous version AND pow, good to go.
(miss one little character and the whole meaning changes).
OK, thanks. I have the same problem on my laptop!
-
Not always needed but the safest way to go back is to first uninstall the current version.
Download one of the previous ones.
(Personally I would do a reboot at this point, sucks I know, but, to be sure, to be sure)
Then double click the save download previous version at POW, good to go.
All noted thanks. Excuse my ignorance you said "... download previous version at POW". What is POW ?
-
-
You can assume that if something is posted, it gets read.
Mods, Admins, Members and even the Dev Team see all posts.
Also assume that if someone has an idea and replies that they are freely offering their best suggestion, either based on personal experience or a logical guess.
Feel free to try (or not) the offered ideas and post back your outcome - good or bad and if other members can help then rest assured they will.
Do not assume a lack of reply is a lack of concern - it is merely a lack of any helpful suggestion for the time being.
It is also a fair assumption that not all members check into the forum on a regular basis, so the one person who may have your answer just hasn't seen your post yet.
In the meantime, why not go back to the previous version you know did work and worst case if it is a bug, await the next release.
Thank you mta.
I did (immediately) follow BOTH the recommended suggestions that I had - from hazelnut and Winapp2.ini.
As soon as I found they didn't solve the problem I reported back to let them know.
I don't know HOW to go back to the previous version, which you have suggested. When I do I will try that.
Thank you.
-
I think that you have a rather elevated opinion of the moderators' skills. We don't know the answer to everything, and you've already had one helpful post from one moderator, and equally helpful responses from other forum members.
This is a free support forum, and whether you get an answer or not is in the lap of the Gods. We're just human, so we might get rather miffed at being berated.
I don't have this cookie, but I would check the date to see if it's constantly being recreated (you said it returns), or revert to a previous CC version if it's so annoying.
Steady Augeas,
I wasn't having a go at anyone.
I'm new to this particular forum and I assumed Moderators or Piriform Support staff monitored the postings.
When I responded to the 2 replies I had received I was grateful and polite (I thought).
I made my last post (prior to this one) as I thought it was regarded as "Closed", which it isn't, that's all.
No need to get stroppy.
Firstly, I thought Piriform would have wanted to know that the last update had caused this sudden appearance of what I'm calling a "persistent cookie" and that it wasn't being removed successfully.
Secondly, I was hoping to get some assistance getting rid of it.
-
I still have this problem (as per original posting), but have NOT received a reply that fixes this issue.
Can I assume Piriform moderators do not read these postings?
Is it the case that Piriform CCleaner doesn't remove persistent cookies?
Can SOMEONE PLEASE let me know?
-
Looks like it's both a chrome and a flash cookie. Do you have cookies selected under both Google Chrome and Internet Explorer? If not, try that.
Hi Winapp2.ini
Thanks, I have cookies selected under Google Chrome, Internet Explorer and Firefox.
Just in case it is relevant, this only started happening after the last CCleaner update. It removed everything prior to that.
Latest update (v4.13.4693 (64bit) causing problem
in CCleaner Bug Reporting
Posted
Thank you Alan_B.
I have noted both your points.
I had previously checked (when the problem occurred) and Mozilla Maintenance Service was still shown as "stopped", so I think that's not the problem.
As for the default browser question. I don't think there are any conflicts, as whenever I got any issue which would ask me about making it my default browser, I have stuck to having Google Chrome as default. I never get asked these days, so I'm pretty confident if there WAS any conflict in default browsers I'd know about it.
I have 3 browsers that I can choose from on this notebook. Google Chrome, Mozilla Firefox and Internet Explorer 11. The first is currently my default and the other 2 are spares. I use the spares whenever there are any problems encountered with Chrome, or when there is no other option. I can also "test" websites with alternative browsers - which can be useful eliminating the cause of whatever is stopping a website from working.
Thanks for your suggestions though. Much appreciated.
The most annoying thing with this current issue is that it occurrs at random; sometimes when I've not used Firefox for days and not had any problems caused by it. It would be much easier, if it was consistent, to track down the cause.
Currently I favour the Firefox v29 update as the cause of it. As someone else said on here - that update is causing LOTS of different problems since the launch.
Thanks once again.
PeeVee