Jump to content
Piriform Community Forums

All Activity

This stream auto-updates     

  1. Past hour
  2. Disk Analyzer

    g'day Mike and welcome to the forums. when you hit 'execute', what do you mean? as Disk Analyser only has the Analyse button and lists all your files into categories. and do you remember the error message? did you do other tasks in CCleaner, like reg cleaning and Run CCleaner?
  3. Today
  4. Disk Analyzer

    Greetings all, Went to use Disk Analyzer of CCleaner today. Win 10 - latest updates. CCleaner latest update. When executed, CCleaner croaked with an error message; which I chose to send to Piriform. I now seemingly have no good hard drive driver. I cannot shut down Win 10. Task Manager's ability to 'see' the hard drive is gone. Launched Windows' Disk and Partition program, and it simply hangs there waiting for the Virtual Disk service. I'm afraid to try anything with CCleaner. I've tried to roll back to the last, and only, Windows Restore Point. After about 15 minutes, restore point fails. Then I tried to 'Reset PC'; that too failed. The machine starts up just fine and I can apparently do most of what I need to do; but cannot shut down. Any ideas? Piriform, CCleaner indicated it was successful in sending the error report to you. thanks, mike
  5. Yesterday
  6. Tracking files not cleared?

    If this is causing so much confusion and these files are not "Tracking Files" then Piriform should remove the labelling of files as such. I think this is unethical and misleading; people have probably wasted much time trying to sort out this issue that Piriform/Avast is responsible for. Piriform run the program themselves and must be aware of this issue. What did the Piriform developers think people would understand when they see thousands of "Tracking Files" have been removed from their computers? I am sure there are Piriform people reading these posts, why have they not given a complete and precise explanation of what is actually happening? As for the image of the man in dark glasses, they are obviously trying to imply these, "Tracking Files" are something sinister. Disgusted!
  7. Yeah, it’;s been a bit a bit of a classic muck up really, fixed one error only to have it the other way around now.
  8. pasword required

    Very frustrating that this has not been fixed. Pls. put higher on the priority list.
  9. Funny, I have this the other way around, after I updated to v2.22.995 from v2.21.993, all my external HDD's are showing up as SSD? Whats going on with that? Guess I'll have to revert to previous version again.
  10. Hi, after using CCleaner my windows slideshow doesn't work anymore. When I go to "settings" it always shows "single picture". I can switch it to "slideshow", but after restart it is "single picture" again. Microsoft support told me that the reason should be "CCleaner". Can somebody help me? What can I do?
  11. The HDD I refer to in my original post has a highly fragmented C: drive (42%), and needs the robust defrag accorded to HDDs. ADDITIONAL INFO: Defraggler incorrectly reports all 3 NTFS partitions on this HDD as SSD - "HOWEVER", it correctly reports the FAT32 OEM Tools partition as HDD. (That's right, 1 drive with 4 partitions, with 3 being reported incorrectly as SSD, and 1 partition - the FAT32 one - reported correctly as HDD). - Maybe this info may help Piriform devs get some insight into the bug. With 42% fragmentation, I need the robust defrag accorded to HDDs. But I don't trust Defraggler to do the job right after misidentifying the drive as SSD. Why dismiss a Warning about SSD defragging, take the time to defrag/optimize/whatever, and NOT get a proper HDD defrag? I (and other users) can't trust Defraggler due to this this bug. Please, Piriform, reply with accurately researched answers to these questions (not mere suppositions): Can I use Defraggler v2.22 to robustly defrag an improperly ID'd "SSD"? Is there some Registry hack, Defraggler .ini file, or other way to change the incorrect SSD flag to HDD? If not, is there an older version of Defraggler that omits the HDD/SSD detection (i.e. no offer of Optimize vs Defrag)? I cannot be the only user of Defraggler who wants answers to these questions. My suggestion - as an engineer - is this: If the bug cannot be banished to the point that Defraggler can, with a VERY high degree of precision and consistency, differentiate between HDDs and SSDs, automatic drive detection determination of defrag algorithms MUST be removed. Present the user with a prominent WARNING regarding SSD defragging; give the user info as to how to determine how to ID their drive type; and make the user MANUALLY select "Optimize SSD" or "Defrag HDD" before proceeding - with a restatement of the danger of defragging an SSD. Do NOT take away user choice when your software relies on faulty drive detection algorithms. I'll have to use another Defrag program if this issue isn't responded to - in fact I'm looking at others RIGHT NOW, because I have a 42% fragmentation C: drive that needs attention. I loved Defraggler for years (I particularly appreciate the SETTINGS -> OPTIONS -> ADVANCED checkbox to "Stop VSS when defragmenting NTFS volume"). That "Turn Off VSS" made your product superior to 2 other defraggers I used that caused MASSIVE numbers of Restore Point creations during defrag (once exceeding 30GB), that actually made the drive highly fragmented with the new Restore Points being written as the drive was being defragged. I came for the "Turn Off VSS", and stayed for the excellent performance of Defraggler otherwise - but I may now be forced to leave. What a pity, if Piriform can't fix this. My drive's health is more important than my love of Piriform software. (And remember, Speccy is ALSO misidentifying this HDD as an SSD). Sorry if this is considered a TL;DR rant. I'm not Ranting - I'm Pleading: Piriform, please fix this Really Bad bug.
  12. no need to double post, others (especially Admins) will see your other post over at https://forum.piriform.com/topic/52083-both-speccy-v132-and-defraggler-v222-incorrectly-report-hdd-as-an-ssd/?tab=comments#comment-296854
  13. +1 all I can add is the Admin and Dev Teams know about it (obviously after all this time). the closest thing I have seen to an official response is a suggestion they may be thinking about a 'manual override switch' but that never eventuated with the latest releases - so who knows.
  14. BOTH Speccy v1.32.740 AND Defraggler v2.22.995 are misidentifying a WD Black 750GB HDD an an SSD. The drive is Western Digital WDC WD7500BPKX-22HPJT0. It was manufactured Aug 2014, so is nothing new to the tech world - it is a multiplatter rotatating disk HDD. WHY are both Speccy and Defraggler misidentifying it as an SSD? Defraggler has had this bug since v2.07 back in 2011, if not earlier. WHY hasn't this bug been fixed? By the way, I've used Speccy, Defraggler, CCleaner, and Recuva for MANY years, and have been a Piriform evangelist also for several years (and I install your products on computers I work on for others). But this long-running bug (misidentifying both SSDs as HDDs "AND" HDDs as SSDs) - as reported in your Community Forum by users - should have been fixed LONG AGO. When are you going to fix this bug? It is very frustrating to your users.
  15. BOTH Speccy v1.32.740 AND Defraggler v2.22.995 are misidentifying a WD Black 750GB HDD an an SSD. The drive is Western Digital WDC WD7500BPKX-22HPJT0. It was manufactured Aug 2014, so is nothing new to the tech world - it is a multiplatter rotatating disk HDD. WHY are both Speccy and Defraggler misidentifying it as an SSD? Defraggler has had this bug since v2.07 back in 2011, if not earlier. WHY hasn't this bug been fixed? By the way, I've used Speccy, Defraggler, CCleaner, and Recuva for MANY years, and have been a Piriform evangelist also for several years (and I install your products on computers I work on for others). But this long-running bug (misidentifying both SSDs as HDDs "AND" HDDs as SSDs) - as reported in your Community Forum by users - should have been fixed LONG AGO. When are you going to fix this bug? It is very frustrating to your users.
  16. Last week
  17. Why the constant updating of the Program?

    other than hotfixes to repair system killing bugs, ccleaner is released once a month, not two weeks. These monthly releases add programs to be detected and fixes for bugs.
  18. It does. But the terms you use there (analyze & clean) are in the standard file cleaning section not the registry cleaner, the standard file cleaner does not touch the registry. In the registry cleaner use 'Scan for Issues' which will find any potential issues in the registry. When the results show use the scrollbar at the bottom to scroll across to the right to see the registry keys found. (Or drag the separators at the top of the colums to change the column widths). The usual caveat about using the registry cleaner- Don't use it unless you know what you are doing and are using it for a specific 'advanced' purpose. It should not be used as a general routine. Microsoft recommend that you never use any registry cleaner, especially with Windows 10.
  19. Well changing "Settings stored in INI file" seems to have stopped it; though I'd call it a Work Around rather than a Fix. Also, using Avast security package, and it made no difference to the issue whether On, Off, or un-installed before the Work Around. Thanks for all suggestions, looking forward to next Update, I think.
  20. Winapp2.ini additions

    Thank you for the info. I found out that it depends on the installation type. On the first setup screen you can click on "Advanced" and choose the "Installation type": "Install per user" (default setting) uses "%LocalAppData%\Vivaldi\Application" and "Install for all users" uses "%ProgramFiles%\Vivaldi\Application". Winapp2.ini update: https://github.com/MoscaDotTo/Winapp2/commit/f26f273c079d3273935f80d8a0deed18a39cb3e1
  21. This is the only program I have ever owned that wants me to update it almost every two weeks. I am used to security programs updating their definitions all the time, but updating the program itself, so often, seems either over-professional or non-professional. It is almost as though the engineers are never satisfied with their code. Does anyone know why this is the only program I have that wants to update itself constantly? Or more direct; Why is Piriform updating the "program" so often?
  22. Today I ran into this problem: When selecting Run Cleaner > Continue, the app automatically closed without running the cleaner. Other functions of the Cleaner worked; however, not that one. I tried the solution posted above on May 22 by siliconman01, i.e., I changed the Cleaner Results option to a file list (from summary). That worked. Thanks siliconman01. Details: ccleaner v5.43.6522 - Windows 8.1 - Kaspersky Total Security 18.0.0.405
  23. Useless new Privacy 'menu'?

    so how do users know that when you say CCleaner you are referring to the company or the program? "For a description of the data CCleaner collects and how CCleaner uses it..." so if a user sees that in CCleaner (yep, I'm talking about the program), the first reference is to a Company and the second to a Program - or is it??? that's confusing and ridiculous. that's on par to every tool on a mechanics bench being called a 'spanner'...
  24. HDD seen as SSD

    if DF thinks the drive is a SSD, right clicking it will so Optimise Drive as well as a Defrag Drive option (no idea why - I guess old habits die hard and some users simply still defrag a SSD). for HDD, only the Defrag Drive option is shown (obviously). glad you got it sorted.
  25. I have been using CCleaner for years but I always asked myself, why this program doesn't show registry keys which are found for deletion if analyze is used first, or what is already deleted if clean is used. It's so annoying, I am unable to see what is cleaned in registry or what will be. Please fix this.
  26. HDD seen as SSD

    I've deleted the files & nothing bad has happened. I found that if you right-click the drive you still get a "defrag" option, and it has in fact cleaned up better than it has for years! Nita - I'm running the "Home" edition of Win10, and I think that VSS is turned off by default, so hopefully I won't have any shadowing issues (assuming that is what you meant? Thanks again.
  27. Winapp2.ini additions

    I'm suggesting to add FileKey21 to [Installer *] for the same reason as above: [Installer *] LangSecRef=3029 Detect1=HKCU\Software\7Star\7Star Detect2=HKCU\Software\360Browser\Browser Detect3=HKCU\Software\Amigo Detect4=HKCU\Software\CentBrowser Detect5=HKCU\Software\ChromePlus Detect6=HKCU\Software\Chromium\PreferenceMACs Detect7=HKCU\Software\CocCoc\Browser Detect8=HKCU\Software\Comodo\Dragon Detect9=HKCU\Software\Coowon\Coowon Detect10=HKCU\Software\Epic Privacy Browser Detect11=HKCU\Software\Flock Detect12=HKCU\Software\RockMelt Detect13=HKCU\Software\Slimjet Detect14=HKCU\Software\Torch Detect15=HKCU\Software\Vivaldi Detect16=HKCU\Software\Yandex\YandexBrowser DetectFile1=%AppData%\brave DetectFile2=%LocalAppData%\Google\Chrome* Default=False FileKey1=%LocalAppData%\7Star\7Star\Application\*\Installer|*.7z FileKey2=%LocalAppData%\360Browser\Browser\Application\*\Installer|*.7z FileKey3=%LocalAppData%\Amigo\Application\*\Installer|*.7z FileKey4=%LocalAppData%\Brave\*\Installer|*.7z FileKey5=%LocalAppData%\CentBrowser\Application\*\Installer|*.7z FileKey6=%LocalAppData%\CocCoc\Browser\Application\*\Installer|*.7z FileKey7=%LocalAppData%\Coowon\Coowon\Application\*\Installer|*.7z FileKey8=%LocalAppData%\Epic Privacy Browser\Application\*\Installer|*.7z FileKey9=%LocalAppData%\Flock\Application\*\Installer|*.7z FileKey10=%LocalAppData%\Google\Chrome*\Application\*\Installer|*.7z FileKey11=%LocalAppData%\MapleStudio\ChromePlus\Application\*\Installer|*.7z FileKey12=%LocalAppData%\RockMelt\Application\*\Installer|*.7z FileKey13=%LocalAppData%\Torch\Application\*\Installer|*.7z FileKey14=%LocalAppData%\Vivaldi\Application\*\Installer|*.7z FileKey15=%LocalAppData%\Yandex\YandexBrowser\Application\*\Installer|*.7z FileKey16=%ProgramFiles%\Comodo\Dragon\*\Installer|*.7z FileKey17=%ProgramFiles%\Google\Chrome*\Application\*\Installer|*.7z FileKey18=%ProgramFiles%\Slimjet\*\Installer|*.7z FileKey19=%ProgramFiles%\SRWare Iron\*\Installer|*.7z FileKey20=%ProgramFiles%\SuperBird\*\Installer|*.7z FileKey21=%ProgramFiles%\Vivaldi\Application\*\Installer|*.7z
  1. Load more activity
  • Who's Online   1 Member, 0 Anonymous, 26 Guests (See full list)

  • New starters

  • recent activity

  • Announcements

    • TwistedMetal

      Forum Rules

      Welcome to the Piriform Forums!     In order to keep the forums running well and to prevent problems, please follow these simple rules for the forums. If you have any questions or problems, please feel free to contact one of The Moderating Team.     1: Be respectful to all members when posting.   No flaming, personal attacks such as flaming, instigating "flame bait", verbal abuse or mocking of members in forum posts are not tolerated at the Piriform Forums. Such posts will be deleted on sight and moderated accordingly. If you are a long standing member, act like one.   Lead by example and assist other newer members rather then attacking them. Members that reply to posts simply to instigate argument will be warned. Should you ignore this warning you will be banned.     2: No Warez (links) & Cracks.   Help, requests or posts that discuss circumvention. This includes linking to illegally obtained software, movies & music files - posting about it, and suggesting to get it.     3: Don't post your question under multiple topics.   Think before posting and choose the right forum for your question or answer. Be sure to check the pinned topics or use the Search feature to see if your question has already been addressed. When posting, have something to say, not just "My first post!"     4: No spamming, ever!   Spamming is characterized by the initiation of threads or posts that contribute nothing to a forum, be it off topic or on topic.   Examples include: empty bodies, bodies with few words that have no relation to the current thread or discussion and those posts that state they are spam, either to annoy, advertise or increase a member's post count. Resurrecting old forum posts is also not appreciated unless it serves a worthy cause to the forum. This determination is made by the forum Moderator or Administrator and is not up for discussion.     5: Unacceptable Forum or News comments.   While some members feel that post count is important, there are some posts that do not contribute to the community in any way whatsoever. Below is a list of unacceptable posts. If you wish to direct a fellow member to something that has already been posted, please do so in a courteous manner.   "Old news" or anything similar.   "(Insert product or brand) sucks" or anything similar.   "I posted this x days ago!!!" or anything similar.     6: Avatars, signatures and custom user titles.   I: Avatars are a luxury for the members to have. Avatars can be a maximum of 90x90 and 50kb in size. Avatars can also be in any of these formats: gif, jpg, jpeg, png.   II: Forum signatures are to be used respectfully, so do not annoy our members by making your signature into some sort of web ad. Signatures can be a maximum of 350x100 and 80kb in size.   III: You may have an image at the maximum of 350x100 in your signature at the standard text size and four lines of text with the image.   IV: You may have a maximum six lines of text in your signature at the standard size. Larger font sizes are allowed so long as they do not break the 350x100 limit.   V: X-Fire signatures are an exception to this rule as they only have two sizes that are preset.   VI: Advertising in your signature is strictly prohibited. Linking to a product that competes against Piriform is strictly prohibited.   VII: Custom user titles are not to be abused. Vulgarity, racism or flaming in member titles will not be tolerated.   VIII: Inappropriate content such as Pornographic, violent or otherwise offensive images, language etc. This may include racist remarks, slander etc...   IX: If the avatar/signature is overly distracting, ie. bright flashing colors, animated signatures (i.e. GIF's/Flash) Audio and Video. These are distracting for our members, so do not have audio or video in your signature.   X: Please do not include signature links of a malicious nature. Examples are those that crash your browser, trigger popup floods or emulate BSOD's.   XI: Do not use your signature to link to pages that contain objectionable material. This includes, warez, cracks, pornography, pyramid schemes, referral ID's, ebay listings and requesting personal donations.   Abusing these privileges will result in them being lost and your account being restricted. Disregarding the above rules will result in the loss of the item in violation without warning.     7: Posts in a particular forum need to stay on topic.   If you want to talk about something that is drastically removed from the topic of a forum, please take it to "The Lounge". The Lounge was set up and designed for members to discuss issues not related to a specific forum section. We welcome most general conversation in The Lounge, but discourage it from other forums.     8: Use a title that describes the content of your post. Don't use all caps or special characters to draw attention.   Please refrain from using CAPITALIZATIONS in the topic title or when participating in threads because they will not attract attention - instead it will annoy many of the Piriform Forum members.   Very often we see meaningless subjects in topic title. They give no clue of what the posts are all about.   For example: Oh no! | I'm mad | Please help.   This should be avoided. Users should enter something more specific in topic title so that it is easier for others to help.   A few good examples:   CCleaner crashes during the analysis | Registry issues keep reappearing after scanning with CCleaner Issues | Computer very slow to startup.     9: No alternate accounts are allowed.   Should you be disciplined with a restriction or ban, you are not allowed to open a new account to obtain freedom to post. Restrictions and bans are given for a reason, and usurping that ability by re-registering is not tolerated.   If another account is opened, that account will be banned immediately, and the original account will be further penalized. Anyone who has warnings on their account are automatically excluded from changing their user name.     10: Giving advice on Malware Removal.   Giving advice on the removal of Malware by any member is to be discouraged. Even though some members may believe they have the knowledge to offer some basic safe advice, it may not be the "best" advice, and could also set a precedent for any member, knowledgeable or otherwise, to do the same.   Advice should only be dispensed by a qualified Malware Removal Expert on a reputable Malware Removal Forum.   This is to prevent "wrong" advice, albeit well meaning, being given by non qualified members, which could have disastrous consequences for the original poster.   If someone asks for help on removing Malware would members please limit themselves to pointing them to one or all of the following Malware Removal Forums ...   1: BleepingComputer   2: Geeks to Go   3: MalwareBytes Malware Removal   4: Malware Removal Forum   5: Cyber Tech Help   6: Avast Malware Removal Forum     11: Inappropriate Content.   No content, or advice or requests for assistance, relating to any activity that the moderators consider to be illegal or offensive will be tolerated.     12: The Piriform Staff requires that members respect the decision of moderators.   Threads and posts questioning the actions or decisions of forum moderations will be deleted on sight, and the appropriate action taken (up to and including forum bans) against the thread starter and/or participants.   Reporting System: Do not abuse the report system, while we appreciate members reporting bad behavior, we don't appreciate rude comments or your opinion on how 'quick' staff are at handling problems around here.   However, as a member you reserve the right to PM any Moderator or Administrator regarding action taken at the Piriform Forums.     13. Closed or removed an unacceptable post or topic:   Once an administrator or moderator has closed or removed an unacceptable post or topic it's then deemed to be a closed matter. If the member starts a new topic or posts with the same or similar unacceptable content it will result into administrative actions being taken against the member.   14. Publishing the content of Private Messages:   Please be aware that the posting of any contents of private messages (PM's) is expressly forbidden on the forum unless both parties have agreed to it.   15. Requesting help with computer issues via the pm (private messaging) system:   The pm (private messaging) system isn't to be used for requests for help with computer issues.   All requests for help must be posted in a topic on the forum where the poster will benefit from the knowledge and expertise of all members, and many others will benefit from the answers and solutions provided.   If any member (which includes moderators) wants to volunteer aid by pm after a topic has first been opened, then that's up to him or her and is perfectly acceptable.   Using the pm system as an alternative to opening a topic where everyone may benefit, isn't the correct or fair way to use that system, and could put members into the uncomfortable position of having to refuse requests for help, or worse still, being unable to refuse.   If any member is in that position, and still doesn't know what to do, then please pm one of the moderators, and they will sort it out quickly, confidentially, and in as friendly a way as possible.     Note:   Any infraction of these guidelines will result in a warning placed against your Piriform Forum account and will be added to your overall warning level.
×