Jump to content

Kimbo No1

Experienced Members
  • Posts

  • Joined

  • Last visited


0 Neutral
  1. Following on from the advice provided by Andavari concerning the availability of a slim version of CCleaner and the URL http://www.piriform....ccleaner/builds provided in his post - I have gone back to the URL provided but I notice that the 'slim' version of Cleaner is no longer available - at least the name of the files and the builds webpage no longer include the name of 'slim' within the filename. Has the 'slim' version been removed permanently? At the time of reading Andavari's response to my query I visited the rebuilds webpage and the 'slim' version file name was available for download, but I decided to leave it for the time being expecting to download the 'slim' version when time permitted. How would I now obtain a version of CCleaner that does not contain 3rd party software which causes by security software to constantly requests cleaning CCleaner downloaded file? Any help would be appreciated. Thank you
  2. I refer to Andavari's response of 12 Feb 2017. Many thanks for your very prompt response. I thought that the standard version of CCleaner carries 3rd party software - although I must admit I have not noticed reference during the installations of options being available to accept 3rd party or otherwise to not accept the 3rd party apps. I have visited CCleaner's website many many times but have never seen the the opportunity to download either the portable version or the slim version. That is perhaps due to the fact that the two extra versions are not on my screen when preparing to download the latest version of CCleaner. I very grateful to you in providing a quick response, Andavari. Regards
  3. HI to forum members I am very hopeful that I have selected the correct forum topic to outline the issues being experienced with CCleaner. Having allowed ESET Smart Security to complete a smart scan of my files I now find that ESET has reported a scanned log entry stating the following message:- Quote ESET states CCleaner 5.26.5937 PF-Toolbar-2016.exe - Win32/Bundled.Toolbar.Google.D potentially unsafe application Unquote Within the report it identified that ESET recommended a ;Clean' which I presume is the cleansing of the alleged Toolbar issue. At this time it would seem that the installed version of CCleaner has not been affected as it opens up without a hitch. Seeing the report makes reference to 'Win32/Bundled.Toolbar.Google.D.' I see that ESET has challenged the downloaded version of CCleaner 5.26.5937 as well as the installed version of CCl. Is ESET misbehaving after all it seems to be doing a double whammy with a downloaded file and the same with the installed version of CCleaner. Do I have a problem either with ESET Smart Security or with CCleaner carrying a 'PUP' or even a 'PSA'? baggage? Is anyone able to shed some light on this issue please
  4. You would be correct MTA - the issue comes to be an issue when the CCleaner filename is changed to include the word 'ccleaner' I also have the Windows 10 version you mention - didn't realise that it had been one of the patch downloads on Wednesday. I change the filename of any file that has an abbreviated name such as 'ccsetup' - so that I can keep tabs on what is installed so I no need to enter the Control Panel to check the version installed, I keep track of installed versions via the Menu shortcuts - I use Classic Menu in preference to Windows 10 menu structure. Regards
  5. I refer to the observation and report submitted by APMichael yesterday at 11.40pm (Message #14) I offer my congratulations to APMichael for providing the solution and the reasoning why the latest version of CCleaner (5.25.5902) cannot be installed when using a different file name than that of the downloadable file (e.g. "ccsetup525.exe" works, but "CCleaner_5.25.exe" doesn't work). I reported that I had resolved the installation issue - which I had (by using the downloadable filename) however I have another computer that I need to upgrade with the latest CCleaner version, but as I rename my files (say from (ccsetup525.exe" to "CCleaner 5.25.5902.exe" I returned the installation error I outlined in an earlier Forum message. Seeing that I had the installation error and asked by MTA (Moderator) to provide the error message I can now provide the error prompt I have been told off... I am unable to include the snip tool image of the error - so it will be attached as a file to this message (hopefully). The error prompt appears above the Task Bar alongside the 'notification area' of Windows 10. Thank you again MPMichael for the wonderful investigative work - it is amazing just how you established what caused the inability to install version 5.25.5902. From a Piriform perspective will you be making any future changes to the naming of CCleaner so as the issue we have been experiencing will no longer be an issue... and what of the issue reported within this Forum where Windows 10 Updates (which one I am not sure) of this months Patches that were supplied removed the installed version of CCleaner.? Your response will be interesting to read. Kind regards and have a wonderful Christmas and New Year...\
  6. I refer to the response from MTA of today at 5.22pm Thank you for the URL enabling the download of CCleaner 5.25.5902. This particular version installed without any issue. I am sorry but I did not keep the error message that I received when attempting to install the earlier version of CCleaner 5.25.5902 and the re-installation of CCleaner 5.24.5841. I thank you for the URL and again I am sorry for not keeping a record of the error message,
  7. Greetings and compliments of the season to forum members.... Reporting... I too have attempted to install CCleaner 5.25.5902 following the latest series of Patch Tuesday Windows Updates (received 14-12-2016) but installation of the new version of CCleaner was not accepted by Windows 10... and not even after the removal of version CCleaner 5.24.5841. I use the free version of CCleaner. Between now and when the new version is repaired I shall revert back to version 5.24.5841. Edit:- (see note above) Now experienced that the uninstalled version 5.24.5841 will not now reinstall. A cure is now required please.
  8. I may well not receive advise form this forum but I am not sure just where to seek assistance and hopefully some guidance concerning Registry Key names having ##?# can be provided here. I am posting this query in this Forum as I have been a user of CCleaner for many many years and I am sure a solution can be forthcoming. Besides there doesn't seem to be too many web forums that carry this type of query that I am about to explain... It seemed that the appearance within the registry of keys prefixed with ##?# coincided with the installation of Windows 10 ver 1511. I have a small network consisting of three former Windows 8.1 computers and all three have the same issue. The automatic conversion of key names came to my notice when I tried to perform a 'Find' search within Regedit.exe but the search never finished - it seemed to be in a continual loop. After waiting for quite some time with nothing seeming to be happening I cancelled the search but a prompt appeared indicating that Regedit.exe had stopped and was being restarted. Other forums complain that Microsoft are responsible for the issue of Regedit.exe stopping and restarting but no one seems to acknowledge that registry key names have been modified. The registry keys affected can be found under HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\DeviceClasses. There would be 50 or more keys under DeviceClasses affected. There may well be other HKEY hives that have similar ##?# appendages. With the prefix mentioned having been added to registry keys - is this an indication that the key is now obsolete or that it is corrupt? if the identified keys are obsolete is there a setting within CCleaner that could be made in order for CCleaner to remove the obsolete key entries during a system scan?. If the keys have become corrupt (somehow) is it possible to repair the entries by removing all #'s and ?'s.so that the entries return to become useful once more.are corrupt. Is there a worthy application that will associate the corrupt keys with internal components by returning the affected keys so that they too become useful. I am sure that a forum member or even Piriform support have experienced the auto appending of ##?# to key names and have resolved the issue in some way. Here's hoping that their experiences regarding the resolutions achieved will come flooding in response to this posting. Kind regards Kimbo
  9. Thank you Marmite for your confirmation. Perhaps Piriform will provide a new build correcting this small but significant bug.
  10. The 'Target' properties is pointing to the folder where I installed (Incorrectly) Recuva. The 'Start In' properties state the same destination but without uninst.exe here is no mention anywhere of C:\Program Files\Recuva... The only time the path C:\Program Files\Recuva is ever displayed is when offering that path during the install (this is editable as the installation provides the opportunity to customise the install path) and of course when it is displayed during the un-install process but the path is not editable. Regards Kim
  11. Greetings Hazelnut I appreciate your very quick response. I have just tried safe mode but there is no difference - unable to change the 'default' path of C:\Program Files\Recuva. The reason why I want to remove this install is that I have a dedicated folder for various utilities - this is one of them I wanted - but failed to complete the install path correctly and installed it to c:\Program files\Utilities\File Transfer whereas I really wanted/intended to install it to C:\Program files\utilities\File Recovery. I only noticed what the uninstall did when I uninstalled (to the default path of C:\Program Files\recuva) to find that the folder recuva contained a Lang folder with 34 files and Recuva.exe and uninst.exe still sitting in the Recuva folder. I then checked Programs and Features (equivalent to WinXP's Add/Remove) and saw that the Recuva entry was no longer displayed. Hope Hazelnut this is helpful info to my issue. Hope you can respond as quick as your first reply. Kind regards Kim
  12. I am using Vista Home Premium (More's the pity!!!) Having just installed Recuva 1.31.437 - I realised that I had installed the utility to an incorrect folder. I have attempted to uninstall intending to then re-install Recuva but to place it within a correct Folder. During the uninstall process I am advised by Recuva that the uninstallation path is C:\Program Files\Recuva (which is wrong - I have it installed elsewhere) and there is no way of editing the path displayed to the actual folder I installed it to. If this is not a bug then the opportunity to install to a custom location should not be provided/allowed. How do I now handle this uninstallation - delete the folder Recuva is located in and then use CCLeaner to fix things up? I would appreciate some advice and an acknowledgement that the uneditable uninstall path is not intended to be uneditable. Thank you Regards
  • Create New...

Important Information

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