The Seeker
-
Posts
17 -
Joined
-
Last visited
Posts posted by The Seeker
-
-
Users of Google Chrome beta usually stay on that channel, such as myself. As previously mentioned, this has only become an issue with the latest version.
-
I have been using Chrome Beta for at least the last two years - this is the first time it has failed to appear in CCleaner's 'Applications' menu. Will this be resolved?
-
Don't feel too bad it doesn't properly clean on older versions of Chrome/Chromium based browsers either which I I use Chrome's (SRWare Iron to be exact) built-in cleaners to do it, then you won't be waiting for them to update/fix CCleaner to do it.
You can even create a shortcut/link in Chrome in the Bookmarks Bar to make it more quickly accessible with this in it as the URL (well at least it works in SRWare Iron that I'm using):
Bookmark Name: Clear Browser Data
Bookmark URL: chrome://settings/clearBrowserData
Screenshot:
Yes, I've been using Chrome's inbuilt cleaner to remove the history, via Ctrl+Shift+Delete. Sometimes I'll do it with BleachBit too as that seems to work.
-
Lastest CCleaner (5.30.6063 64-bit) on Windows 10 Pro (15063.296) still does not remove Chrome's browsing history (59.0.3071.47 beta 64-bit).
-
your problem in identifying a cause is made harder by all three things being quite new; Creators Update, beta Chrome and CC v5.29.
the easiest to test would be take Chrome and/or CC back a version and try that theory.
True.
As it's not a massive issue I'll see whether the next release of CCleaner rectifies it. If not, I'll do as you suggested. Thanks for taking the time with your input
-
Ah, beta, you may be onto something there then.
Beta's by their nature are funny beasts.
But... it could still be some other Google task running.
Do you use Google Drive, or basically, any software that may inhibit CC for being able to access Chrome History?
No other Google services running. I do think it's the browser as this is the first time it has ever happened.
-
what have you done so far to try to fix your issue?
anything here help? https://forum.piriform.com/index.php?showtopic=40285
also check Task Manager to see how many chrome.exe processes are running?
Thanks for the possible solutions.
Regarding the first step, I know that my Chrome sync is only set for Bookmarks, Extensions and Settings. I double-checked just now and as I thought, History is definitely not selected.
"Continue running background apps when Google Chrome is closed" was selected, so I disabled it, closed Chrome and ran CCleaner again. History remains. I did also check that no chrome.exe instances were running under Process Explorer, and there were none.
I'm thinking something has changed in the latest Chrome Beta as this has only arisen since the latest update.
-
CCleaner 5.29.6033 on Windows 10 Pro 64-bit Version 1703 (15063.250) does not remove Chrome's browsing history (Version 59.0.3071.29 Beta 64-bit).
-
I see that free space defrag has been added to the command-line app. Thanks for this
-
Last bump, then onto another program.
-
Bumping in the hope that someone in a position to answer may actually do so.
-
It doesn't exist as a specific command line paramater, no. But I guess where the OP is coming from is questioning whether freespace defrag is the default behaviour in a command line defrag - and the documentation doesn't answer that question.
Exactly.
-
Does the command line version defragment freespace during a defrag?
Devs? Mods? Anyone?
-
Does the command line version defragment freespace during a defrag?
-
Actually it fixed an option where all personal settings got removed.
Ah ok, thanks very much.
-
I've noticed that CCleaner has added cleaning for MSN Messenger in the latest version.
I was wondering if anyone knew what exactly it cleans? Chat logs, received files? I wasn't able to find any information on the CCleaner site or with a search on this forum.
Thanks in advance
Chrome Beta
in CCleaner Bug Reporting
Posted
I noticed today that Google Chrome beta now resides in Program Files (x86) folder, whereas previously it could be found in the %AppData% directory. I wonder whether this is the reason for the odd behaviour?