Jump to content

nukecad

Moderators
  • Posts

    7,732
  • Joined

  • Last visited

Everything posted by nukecad

  1. That does make sense, and isn't a screw up as such, Windows is doing it like that for a reason. The reg entry for Local_Machine is showing 3.3.3, because that will be the first/last version that you installed on the machine from scratch and you've been updating since. The reg entry for Current_User is showing 3.4.2 because it knows you have updated as that user. Although I've never had reason to do it, is possible for different user accounts to have the same software installed, each one a seperate full install for that user with their own settings/customisations. So it's possible for different users to have different versions of the same software installed. Which explains why the registry shows it like that, it could be a different version for each 'Current_User'. It also explains how uninstalling/reinstalling would/should do the trick, the reg entry for Local_Machine would/should then show the version of the new 'install from scratch'. ie. The uninstall would remove those reg entries, the reinstall would make new ones with the newly installed version. (Any user who did have their own seperate version installed in their own account should retain that version, it wouldn't have been uninstalled). So it seems that the CCleaner uninstall tool is reading what Windows says is/was installed on the machine, and not what is installed for a particular user. I've not thought through the pros/cons of that, but presumably it's done that way for a reason?
  2. Ha, sorry I thought this was a current problem. It's just a bit unusual for someone to be posting about an issue that they were having 2 years ago but not now.
  3. Just jumping in to check something. You're not unticking the Steam option and then running Health Check are you? The ticks/unticks only apply to Custom Clean. Health Check ignores any ticks/unticks. As Dave also hints, stop using the registry cleaner and see if your problem stops then.
  4. The DNS_PROBE_FINISHED_NXDOMAIN error that you are getting is apparently a common Chrome error. See here for a step by step of how to fix it: https://nestify.io/blog/the-easy-guide-to-fix-dns_probe_finished_nxdomain-error/
  5. It's possibly because they have released 3 version updates in the last 5 days - 3.4, 3.4.1, & 3.4.2 When they are popping out new versions almost daily it can be difficult for everyone else to keep up with the changes. https://www.sumatrapdfreader.org/docs/Version-history CCleaner will be reading the Sumatra version number from Windows, so presumably Windows hasn't updated that information yet. I wouldn't worry, if you use the Uninstall tool it will call whatever 'uninstal.exe' Sumatra have put in their own programme folder.
  6. Your first change should have done the job for the specific "other MRU's" message so that it now shows again when needed. The second one you changed (ShowCleanWarning) is for the message that pops up each and every time you do a Custom Clean.
  7. I don't know how I can explain it any more clearly than I did above. All 4 conditions must be met for the message to pop up, if any single one of them isn't met then it won't show. And v6.00.9727 on my machines are clean installs not updates, I never update I always do a new install. (Unless for some reason I'm testing the update function itself). In fact I do more clean installs than most users as I'm regularly changing settings, etc. and often installing/uninstalling different versions to check out things that are brought up on this forum. Once I've finished testing I'll do a clean install of the current version and apply my regular settings. Cleaning of 'Other Explorer MRUs' is behaving exactly as I described above on both of my laptops, how do you think I got that screenshot?
  8. The warning message that the OP got about Explorer MRUs was the one I screen-shotted in my last post. Nothing was mentioned about a 'Restart' message until you mentioned it yourself. You will only see that message if you have some other MRUs to be cleaned, and if have Custom Clean set to clean them, and if Explorer needs to be closed to clean them, and if you haven't previously told Custom Clean not to show the message again. It takes all 4 of those conditions to be met before you will see that message. Incidentally, that screenshot above was taken from this laptop on Monday minutes before I posted it, so yes the warning is working as it should if all 4 conditions are met.
  9. It isn't CCleaner/Piriform - It's the 'Invision Community' software that the forum runs on. We are getting exactly the same login error on the Malwarebytes forum, which also runs on the latest version of 'Invision Community' software. So it's Invision who have to fix it, and they seem to be taking their time about it. PS. if you have your logins/passwords saved in your browser then it's just a matter of clicking the buttons rather than typing them again.
  10. It's just human nature with anything new/changed and has always gone on, how far back do you want to go? "I don't care for these new steam ships, they only make them so that you have to keep buying coal, I'll stick with my old windjammer thanks that's paid for". "These new iron axes don't last as long as the old stone axes we use to get".
  11. To put it another way: Most criminals use cars to get to their 'work', that doesn't mean that everyone who uses a car is automatically a criminal. Some criminals will use CCleaner to delete their computer files, that doesn't mean that everyone who uses CCleaner to securely delete files is automatically a criminal.
  12. Why would I do that? (I don't let File Explorer keep recently used lists anyway, so I'd have to enable that as well). I'll take your word that you got such a restart message in the past. I can't remember if CCleaner used to do that? but it may have done because sometimes to change things in File Explorer then you have to stop and restart it, they can't be changed while it's still running. An easy way of doing that is by restarting your computer, but there are other ways and obviously CCleaner is now using one of those. In any case the OP here doesn't mention such a such a restart message. I believe that it was this one: The 'issue' here is simply that after clicking not to show the message again it will do exactly that and not show the message again. Without a message you can't say Yes or No, and so CCleaner just skips cleaning it.
  13. And to add that the same has been reported over at Malwarebytes, it appears that CFA is blocking Malwarebytes from accessing it's own folders and throwing up the same notification flag. So it does look as if changes in CFA are the cause of this issue. https://forums.malwarebytes.com/topic/286706-controlled-folder-access-blocked-mbamserviceexe/ The advice at Malwarebytes is the same as in that link I gave above, ie. if you want to leave CFA on then make the programme and it's folders an exception in CFA. https://support.microsoft.com/en-us/windows/allow-an-app-to-access-controlled-folders-b5b6627a-b008-2ca2-7931-7e51e912b034
  14. “Do not show me this message again.” and a tickbox is only the last part of the message, it's shown on various pop-ups. Was it saying that MRS's were still in use and asking you if you wanted to close them? or was it saying something else? When you tell CCleaner to ignore future pop-ups about something then in future if it can't clean whatever it is (usually because it's in use) it will just skip whatever it is without asking you again. Try looking in your ini for a section like this: and if there is a 'Show###Warning=False' for Explorer MRU's (sorry I'm not sure what it would be called if there is one there) then change it to True to get the warning back. For example, the one I have there for Firefox is because I told CCleaner not to show a pop-up again if Firefox is still open, so now if Firefox is open it just skips it without asking me.
  15. Good to hear that it's solved for you, even though we may never know what it was being caused by. As you say that you ran sfc and it found and repaired some filesystem errors that was probably causing the problem.
  16. That message when logging into this forum is common, it's a glitch in the underlying forum software. All forums running on the 'Invision Community' sofware are currently seeing it. I get it everyday both here and at the Malwarebytes forum which runs on the same software. So it's not your machine or CCleaner, it's something that Invision need to patch. To get back to the 'need to close the browser' message. You did say that CCleaner "CCleaner doesn't usually perform like this", so was this just a one-off or has it started happening regularly? One though I had if it was a one-off, was there a Firefox update pending? ie. downloaded but waiting for Firefox to be launched again before it installs. You can check if you are signed in to a Firefox account (and syncing) by clicking the hamburger icon, you can see here that I'm not signed into one: HTTPS everywhere shouldn't keep running once Firefox is closed. BTW that extension is no longer needed, the function is now built into Firefox. Go to Settings>Privacy & Security and scroll to the bottom of the page. I don't use Privacy Badger but wouldn't have though that would continue running after Firefox is closed. If you keep getting that message from CCleaner then you could try temporarily disabling PB to see if it makes a difference. If this is a recurring message that you are getting from CCleaner then there are a couple of things you can try in Firefox, such as running it in Safe/Troubleshoot Mode to rule out any interference from add-ons or Firefox/Windows settings. If running FFx in Safe Mode stops the problem then you know that it's an add-on or setting that is causing it. https://support.mozilla.org/en-US/kb/troubleshoot-extensions-themes-to-fix-problems I don't think that your FB oddity with the 2FA is related, reading around it seems that FB's 2FA does throw up issues like that from time to time.
  17. I also use Firefox. Sometimes if you have only just closed Firefox (especially after a long session) it hasn't had time to full close before you run CCleaner. (I have written my own, very fast, cleaner for Firefox and I often have to run it twice because the first time Firefox hasn't had time to fully close yet). Sometimes it may just be a one-off that Firefox hasn't closed properly on that occasion for some reason. (The spinning circle/arrow does indicate that something is 'stuck' and preventing CCleaner from closing Firefox). A 'Restart' (not Shutdown) of your computer would fix that by terminating Firefox altogether. (A Restart will terminate all running processes). if it's happening frequently though then a couple of questions: Did you get your Firefox from mozilla, or from the Microsoft Store? Are you using your Firefox with an account? maybe synced to that account? Do you have a lot of add ons or extensions? Next time you get that message from CCleaner, if you do, then try the following: Close CCleaner without doing anything else. (just 'x' out of it top right). Try to open Firefox. Do you get a message saying that 'Firefox is already running but not responding'? If you do then the profile may have become locked, see this: https://support.mozilla.org/en-US/kb/firefox-already-running-not-responding
  18. Which browser are we talking about? Some browsers do pre-load Some browsers do leave extensions, addons, and associated apps, running when you close the browser. Some do both of those things. Chrome and Edge Chromium are prone to it, but other browsers can do it as well. If we know what browser it is we can (usually) point out how to stop it doing that. This is about Chrome still running in the background: https://support.piriform.com/hc/en-us/articles/204210674-Why-is-Chrome-cleaning-being-skipped-#why-does-chrome-get-skipped-if-you-don-t-have-it-open--0-1 If it's Edge then turn off both 'Startup Boost' and then 'Continue running ...' see this:
  19. A bit late with this follow up: The testing that I've done myself seems to indicate that CFA is objecting to CCleaner updating one of it's own files when you launch CCleaner. The file is CCleaners own file, in CCleaners own 'setup' folder, so just why CFA is objecting to CCleaner changing it's own file is a puzzle? I've made the staff aware of my testing and findings.
  20. I think Dave was trying to track down where the problem lies. If you are still having problems then download the 'Slim' installer, 3rd one down here: https://www.piriform.com/ccleaner/builds Once downloaded double-click it to install CCleaner, you'll get v6.00 now. Don't uninstall first, that way the new install will pick up your existing Pro Licence. If you do uninstall first then you will have to use your registered name/key again to re-register the new install (so make a note of them before uninstalling). The Slim installer usually works when the Standard installer (or updating from within CCleaner) has problems.
  21. Yes, the install is complete. The correct files are all installed, it's just that one ot them was trying to be installed twice at the same time.
  22. I've already questioned this and apparently there are a few issues doing a portable of CCleaner v6.00 because of programming changes. So if you download the portable you will still get v5.92. I'm told that the issues can be resolved and there should be a v6.01 portable next month.
  23. It has been noticed that if you update in a certain way (clicking on 'Check for Updates') then CCleaner will update/install itself twice at the same time. That isn't what should happen, but it's not normally a problem and one just immediately overwrites the other. However a write error can sometimes happen if both installs try to write the same file at the same time. (The first already has the file open for writing, so the second can't write it again). It doesn't happen if you use 'Automatic Updates' or if you just download/reinstall the new version yourself. (There's no need to uninstall the old one first). You can always download the latest installer from here: https://www.piriform.com/ccleaner/builds Once downloaded just double click on it to install. The developers are aware of it, and are looking into why the double install is happening when you use 'Check for Updates'.
  24. Please update to CCleaner v6.00 which has just been released (an hour ago). The blank screen in Performance Optimiser preview that some users were getting has been fixed in CCleaner v6.00.
  25. I have seen that announcement, but haven't seen any details of how to go about it. If you are in Ukraine I suggest that you send an email to the Support team with your request. support@ccleaner.com
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.