Jump to content
CCleaner Community Forums

ArchAngle

Experienced Members
  • Content Count

    42
  • Joined

  • Last visited

Community Reputation

0 Neutral

About ArchAngle

  • Rank
    Member

Recent Profile Visitors

364 profile views
  1. I had not checked Defraggler on my most recent PC build until today as it is so recent I still have very little on either of the two HDDs; primary drive is a SSD. But doing some new year maintenance and I thought I might as well use it. Same problem as reported by others here, both the HDDs reported as SSDs. Version 2.22.33.995 is indeed the culprit. So much for the 'vital' importance of keeping your software up to date; I installed all up to date software when I finished the build and it is not the only program I've had to remove/roll back because of similar issues. I know the version of Defraggler on one of my other PCs does not have this problem so I'm going to uninstall the v2.22.33.995 and reinstall Defraggler using one of the old installers I've archived for problems like this. If anyone else here has had the same HDD/SSD misreporting and wishes to revert to an older version too it is likely you can find an old Defraggler installer at FileHippo but make sure it is that older version selected because sometimes the old version links at those archive sites download the latest one instead. EDIT 1 Interesting. When I actually checked my Defraggler version on the other PC which is practically the same: identical SSD primary drive and two similarly matched storage HDDs ie. same make and size as those on the first PC. Those are the HDDs which Defraggler v2.22.33.995 are reporting as SSDs on that PC but are reporting correctly as HDDs on this one with.............................what turns out to be exactly the same Defraggler version! I had to think about this and I'm going to test this theory later and report back the result. The only difference I can think of is that on the first PC v2.22.33.995 was a completely fresh install on a virgin PC build. On the other machine that version was installed as an update to the previous version, likely v2.21.0.993, and that similarly installed as an update and so on back to when the PC was first used in 2016. So my theory is that something is wrong with v2.22.33.993 but when the previous version was updated there was something already there that was not updated because it does not normally need to be. I'm going to try thoroughly uninstalling v2.22.33.995 on the first PC, re-installing Defraggler from the older version installer I have, v2.21.0.993, and then updating that to v2.22.33.995. EDIT 2 Tried that but no joy. I did every combination of old and v2.22.33.995 install I could think of on the newer PC using both v2.21.0.993 and an even earlier v2.20. I tried updating by fresh downloads of v2.22.33.995 from 'Piriform' and third party sites and the older versions all freshly downloaded too. I used the same older installers to incrementally update the installation too ie. from v2.20 > v2.21>v2.22 rebooting the whole PC between installs. Same problem recurred when v2.22 was installed. I also created a portable version of v2.22.33.995 and ran that but it produced the same HDDs misreported as SSDs issue as does the installed version. So what the hell is causing that and why can my other PC (see attachment) use v2.22.33.995 without any similar trouble? Speccy too misreports the same two HDDs as SSDs on this PC but on the other absolutely correct. As said earlier they're very similar set ups, Win 7 Pro 64bit OS, both Gigabyte MBs, 3rd gen Intel CPU on this PC, 4th gen Intel CPU on the other. The actual SDDs and two HDDs in each are identical makes and sizes the only difference is the partitioning of one of the HDDs. I can not think why there would be this difference in reporting. If anything you'd think it would be the other way round as it is the one with the 3rd generation CPU and slightly older MB that is misreporting the HDDs as SSDs. Mysterious - I hope somebody can come up with an explanation. However as it is apparently the only solution for anyone having this problem is, as others have said here, to install Defraggler v2.21.0.993 instead. Remember to go into the settings and untick the Settings > Options: update check too. BTW if you're playing around with either older or newer Defraggler or other Piriform installers be very careful. Some come with a Chrome browser install pre-checked and the latest one similarly 'offers' the latest version of CCleaner in a pop-up. Also with the v2.22.33.995 installer only use the "Custom" install option or you will likely get it replacing Windows defragmenter too.
  2. Don't we all? A new serious security flaw has been found in Win10 only this week. Updating your OS to Win10 for better security and performance is very important (irony intended if that was not clear). WinXP and Win7 FTW.
  3. I'd uninstall it using Revo (Advanced option scan to get all left-overs). Then reinstall a fresh copy from the download links at the top here. It should not take a long time to open or display in the normal way. With Windows 7 64bit you get the familiar UAC admin consent dialogue box when you launch Recuva which I believe Windows 10 should also do too. I would have suggested you try the portable version of Recuva instead but unfortunately Piriform have surreptitiously ceased providing that version - the links from the build page lead to a page with a portable download link but the actual file downloaded is their standard installer .exe. You can still create a portable installation from either of the installed 32/64bit recuva .exe files fairly easily but doing that rather defeats the point of testing a system with portable version of the same program in this particular case.
  4. Possible your anti-virus is the culprit? Look for it in your AV's quarantined folder or sandbox. If you have it set to quarantine or even delete suspicious files or it does that by itself without asking then that may be an explanation. Suspicious file can just be ones with suspicious behaviour and a recovered deleted file reappearing again might be enough to trigger a paranoid AV. I'd try recovering another a test file and see if that happens again.
  5. You have to click on the SCAN button to get it to search for deleted files in the location specified. By default that is just C:\ ie. your primary drive but all other locations are available from the drop down menu. In the file search options box the default is every file type but you can change that to narrow down the search to a particular custom folder path or for more general Picture, Music, Documents, Video, Compressed or Email files using its drop down menu.
  6. It is indeed that just as I suggested earlier too. This thread:- https://forum.piriform.com/topic/51922-defraggler-222-detecting-my-hdds-as-ssds/?do=findComment&comment=313762 indicates that the same applies to Defraggler and Recuva too. I speculated on the reason why in that thread but it would be interesting and helpful to have things confirmed by somebody in a position to do so, if anything is going to be done about it and explain why the "Pro" versions are still being offered when they are now significantly flawed for the same reason.
  7. Lots of people are now reporting this and similar problems with Speccy too. Me as well. See my post here about that and likely explanation:- https://forum.piriform.com/topic/42888-the-wrong-temperature-thread/page/5/?tab=comments#comment-313660 Put simply Piriform products were once updated regularly and highly reliable but, as many faithful users predicted, since AVAST bought it in 2017 things have slipped with all the effort going into CCleaner, about which I could say more but I will not. Speccy has effectively not been updated since then, Recuva likewise. Defraggler was last given an update in May 2018 the only one since 2016 and the only one since AVAST took over. How they can get away with trying to sell "Pro" versions of what are apparently the same outdated software without making it clear to new users that these types of problems are only going to increase is a very good question. If you use older OS, software and hardware circa 2017 then they are all still great products well worth using but otherwise unless AVAST/Piriform get there fingers out and do something they will become increasingly irrelevant to users of new software and hardware. Updating Speccy seems like it might be a fairly simple thing as the GUI is already excellent and really does not need any work. The only update necessary would be to replace what appears to be the outdated cpuid.com (cpuz143) driver. That has been updated regularly, currently v1.91 (cpuz149), so perhaps AVAST just do not want to pay CPUID EURL a French based company, further developers' fees.
  8. Suggesting the OP tries a slim reinstall on top of a possibly corrupt one might cause more problems. You need to find out exactly where the existing installation was installed first. Type "CCleaner" in the "search program and files" box and then hover the mouse over the result and it should show you the path. I think it is slightly different with Win10 but there should be (I certainly hope there is) a similar search option available. Then I'd be looking to try uninstalling it using Revo or BCUninstaller. Although Revo will do this too I'd suggest putting in your own restore point. If it finds wherever CCleaner is installed either of those programs should be able to uninstall and get rid of the leftovers which might cause problems with any reinstall. Where did the CCleaner installer originally used come from? These are the MD5 and SHA-256 file hashes you should use for verification purposes:- ccsetup563.exe - CCleaner Free Installer MD5: 037c93d6e729c43fab88e9180ca8c2d7 SHA256: f2aba7dc1d4ab617d7b09b19e7a5b4f6b6e3f790981050d163f395002646b890 Personally I'd recommend you use the portable version instead also linked to on the same page as the Slim version. Less hassle and you may avoid the forced updates CCleaner now does whether you like it or not. With a portable installation you'll have to create your own desktop shortcut and same applies if you want it in the Start Menu too.
  9. ^ Yes, agreed. However, that does mean there must be something wrong if Defraggler is trying to defrag it. My concern was/is either that it is corrupted or that the HDD may have a bad sector and it needs to be moved and the sector identified so it is not written to again. CHKDSK should do that.
  10. Are not these sort of reports about incorrect system information just more indications that Speccy badly needs updating? In reply to another thread last week about similar matters my research suggested Speccy may use CPUID's CPU-Z driver and in particular CPUZ143 a version which is over two years old. That is how Speccy is reported by Process Hacker 2 ie. in Services as CPUZ143: Driver. I can't remember the last time Speccy was updated but my installation of v1.32.740 shows that as dated 2018 so it might not have been updated since then. Is it any wonder it can not report accurately/correctly information about and for some new hardware. EDIT 1 Just been checking CPU-Z and it comes with a ReadMe including a changelog history. That details all the support changes made since May 2017 which was when the CPUZ143 driver was first used. There were actually a number of version of CPU-Z after that which updated the driver support but not the driver itself. If I'm right about all this and Speccy is using the CPUZ143 driver dating from May 2017 (CPU-Z v1.79.1) it explains pretty much all the problems described here and in other threads. CPU-Z History.txt EDIT 2 I had not thought to check Speccy thoroughly until this weekend (19.01.20) when I found Defraggler was incorrectly reporting two HDDs as SSDs on one PC. On one of my PCs Speccy v1.32.740 is also showing the same HDDs as SSDs too. Not checked any other yet. I'm going to try reverting to the previous version which I think is v1.28 something.
  11. Put in a system restore point first as a safety net. Then I'd run System File Checker (SFC): Run > cmd > "sfc /scannow" No quotation marks of course. Hopefully no system file problems will be found but if it does it may repair them. Next I'd run CHKDSK without repair options* (as it is your primary drive) and see if it reports anything about the USN Journal (Update Sequence Number Journal). That is what that file appears to be. If it does find a problem then try scheduling CHKDSK to run on next boot with repair options. *Computer > C drive > Right Click > Properties > Tools tab > Check now, untick the repair options and click Start. For boot time do the same thing but tick the repair boxes, When you click Start it will give you the option to schedule the scan at next boot.
  12. I've read about something called a "symbolic link" (symlink) say between a user's documents folder and a folder of the same name on another drive. There is also something similar to do with "shell objects" or "shell folders": So since at least Windows XP the a user has been able to move the location of the Documents folder almost anywhere to free up space on the C:\ drive. But you still access the content using the same C:\ drive system links ie. like a shortcut but you're not redirected to the actual files' new location. It sounds as if maybe something along one of these lines has happened here accidentally and what you're doing, because of this folder linking, is actually renaming or trying to delete the actual 'parent' folder. But which is which now, how it came about and how to fix it is beyond my knowledge. If you can identify with certainty where the real My Documents folder content is located it would probably be useful. This article may be relevant:- https://www.techsupportalert.com/content/how-move-windows-7-personal-folders-my-documents-another-drive.htm using the "Find Target" option would seem to be the obvious first step. But after that I am not qualified to advise.
  13. Concur ^. Never use the Windows default uninstaller or the program's own uninstaller directly (often shown in the Start Menu). Always use a dedicated uninstaller like the ever reliable Revo. After putting in a restore point it will run the program's own uninstaller or, when one is not provided, Windows default uninstaller. If you've used the Advanced settings ie. thorough uninstall, it will then scan and display all related links and leftovers it has found for the uninstalled program. That includes the usually hidden Program Data, AppData > Roaming/LocalLow/Local and registry entries often left behind. These are really what this thread is all about. Once the program's own uninstaller has been used those leftovers are much more difficult to find and remove. So use a purpose designed uninstaller right from the start. But do be careful with the Revo Advanced options and check what is being removed before clicking the delete button.
  14. That does bring up an issue that whilst it is secure deleting the files making them unrecoverable a record of the name of the file can still be present and reported by Recuva. That in itself is evidence the file was on your PC and possibly even useful information to anyone unauthorised who might gain access to your PC. Using CCleaner to wipe free space on a volume will multiple overwrite it with ZZZZZZZZZZZ file names, I think including the MFT. However if before that was done the deleted file space was over-written by another file still in use the 'underlying' file name may still be read by Recuva.
  15. Anyone have the "Pro" version of Speccy to check this too. If that is showing the same inaccurate information then that is pretty bad form. Speccy 'Free' v1.32.740 has not been updated in months, possibly not since May 2018, whereas CPU-Z has been updated at least twice recently, currently on v1.91. Process Hacker 2 reports that the most recent Speccy version when launched as being CPUZ143 so if that means it is using that CPUZ 'engine' I'd bet that if users of more recent Intel CPUs used that it will report the same thing. However it is difficult to test because CPUZ uses a different ID to the version numbers. For instance the current version v1.91 reports as CPUZ149. So what version or versions CPUZ143 was used for and how old that is ..........................................................just found it. Luckily CPU-Z have archives of old versions with details of what was updated and whilst I can not be bothered to check back* when it was introduced CPUZ143 was last used by CPUZ v1.81 dated 27th September 2017. So the 'engine' Speccy apparently uses is over two years old and it is therefore not surprising it can not identify more recent Intel CPU versions. https://www.cpuid.com/softwares/cpu-z.html Still it should have been updated by now to be able to identify those CPUs and if 'Pro' Speccy is the same then you have to ask what are people paying for? *by fluke I downloaded what I'm fairly sure is the first archived version they had of CPUZ143 which is CPUZ v1.79 dated April 2017.
×
×
  • Create New...