mta

I'll tag out at this point and wait for other members more experienced with Recuva to chime in.

so under C:\ drive, you see no windows.old folder? it shouldn't need it, but check your folder options allow you to see hidden & system files. let me guess, you have no backups either?

g'day husky and welcome to the forums. Speccy already has Minimise to tray that still lets it run in the background so you can see your metrics. wouldn't Close to tray just be the same as hitting the close X icon?

I think those with Enterprise would have 'acquired' it through either the company they work for or a 'contact' at another company. or they are using their work computer when reporting these issues.

can I just add a note of caution. reg cleaning hasn't been beneficial for many years - simply no need for it. the only time it has helped me was once, when I had malware living in the registry. but from a space and speed view point, cleaning the registry will give you no perceivable advantages. and if you are on Windows 10, with it's regular updates, it is always a few steps ahead of any company trying to determine what keys in the registry can be cleaned and any side-effects. official word on the matter from MS; https://support.microsoft.com/en-us/help/2563254/microsoft-support-policy-for-the-use-of-registry-cleaning-utilities if you do want to go ahead with using any reg cleaner, as Nergal's sig stats - back it up first, and do it in small chunks.

the re-installation of Windows 7 should have put all your personal files in the Windows.old folder within the Users folder - like they were before the install. so look there. because your programs are still there, it didn't do a fresh install or factory reset install, so you should be good. a bigger question is, WHY did that happen? (that sort of thing doesn't just happen out of the blue)

what I have found Nikki over the years is with each new release of Speccy, CC and DF, what tends to happen (for me at least) is if the current version reports the drive as one way (right or wrong), the next version reverses it. I've even had one product report it correctly and another wrongly - then the two swap their detection with the next release. I've also seen the same version get it right or wrong depending on the brand of SSD - which is why not every person has this issue. there is definitely an issue and other programs get it consistently right (like Microsoft's own OS) so there should be no reason Piriform can't pull their fingers out and fix it. but from reading between the lines when Admins do deem us worthy and throw us some tit-bit details, I have gotten the impression that their coding department is small, like VERY small, like I reckon you could count them on one hand - the same hand that had that industrial accident and lost 3 fingers. that's how many programmers I think they have to play with that support all their products. that may have (should have) changed now Avast is calling the shots, but with their entire focus being blindly pointed at CC, and now with the mess that that is currently in, being forced entirely on CC, don't expect any fixes for the other products any time soon. the SSD <--> HDD issue is at least 2 years old, then there's the Speccy wrong temperature long running bug - it is at a point now where I've stopped using them as you simply can't trust the figures.

and you can also add Defraggler to that sad list.

and if that doesn't help, try doing it with the PC booted into Safe Mode. and start regedit with admin privileges.

thanks Tex. luckily us Mods aren't tied to the company in any way. we are all just volunteers here, freely given up our time to help others, and that part, we (well, I should only really talk for me) enjoy. it's the very reason I started, and have stayed, on the forum. all being a Mod really means is we get extra forum housekeeping duties like banning rule-breakers and moving posts to their correct threads.

that particular bug has now been known about for around 2 years - so you can either read into that 1) it can't be fixed or 2) they don't care. but you wouldn't know since no official word from high has been given. Piriform has recently hired a new, junior Product Manager, so maybe this will be part of his new duties - but again - purely speculation on my part.

that screenshot also shows you are using Windows 10 Enterprise, not Professional.

yep, Speccy bug. it has a habit, for just a few unlucky users, of reporting certain, core things wrongly.

if it was just the one 'mistake', no user would have cared too much. there would have been an initial backlash but things would have settled down. but it was the kind of mistake, the repeated mistakes (in yet another version), the way it was introduced, and the utter lack of any information in weeks apart from that one "we have listened, it will be fixed" that finally broke the camel's back. it is simply that the user base has had enough. fool me once, shame on you - fool me twice (3 times, 4 times.....), shame on me. each of the previous 'mistakes' usually made some users find alternatives, but either the hunt for them was too hard or they simply didn't do what CC did for them and they scurried back to the devil they knew. but when that devil itself became the very issue they had with the alternatives, they have gone "bugger it, I might as well use something else now". and let us be honest here, the sneaky implementation of the heartbeat/monitor issue was no mistake. for me, the nail in the coffin was the company's failure to take control of the narrative. (this forum being a prime example) in fact, that implies they participated in the narrative but were out out voiced whereas they have decided to not even participate.

+1 and you have to give them credit where credit is due - they are spectacularly good at it, which they have demonstrated on more than one occasion.

g'day SeekerK and welcome to the forum. in case it helps, what is your OS?

not when it is built into Windows. in that scenario, CC is the competitor. just in case you aren't aware, cleanmgr can be further improved by using the /sageset switch. type cleanmgr /sageset:1 (where the number can be anything up to 64000) and tick all the categories you want cleaned. to use your selection, type cleanmgr /sagerun:1 (with the number matching the /sageset number you used) so I have a sagerun:1 to clean all categories except windows old installs and a /sagerun:666 that only does windows old file.

luckily the inbuilt MS cleanmgr program, which has gotten better with Windows 10, does just as good a job cleaning Windows as CC did.

no solution I'm afraid, not if DF is wrongly detection the SSD as a HDD. it's a long-standing, known, unresolved issue with DF and CC. I have a batch file of maintenance tasks, to optimise a SSD, I use this; defrag %systemdrive% /L /V

is it just Acrobat Reader that is corrupted, or others? if just the one, uninstall and reinstall the software. if others, it may be a sign of deeper issues (gremlins, hard drive failure) and you should be backing up, scanning your drive, perhaps even a repair reload of Windows. to get you started, start an elevated command prompt and do these; chkdsk c: /r sfc /scannow

if it is, it was completely unintentional. maybe my subconscious knows more than she lets on. but now you mention it - I like that idea and will stick to it, my 40 days of mourning for what was, and will never be again. as to staff in the Who's Online status, yeah, I don't think they have increased any activity on that front. I usually see the odd one lurking around. if they bothered enough to log in and browse, why not spend the few extra seconds and; post an update, say Hi, give us a status report, tell us what's coming down the pipeline, post some feel-good news - ANYTHING, but no, let's stay mouth shout and let the crazy members prattle on with their trivial chatter.

Notepad++ v7.5.8 bug-fixes: 1. Remove annoying "no update" notification. 2. Fix Folder as Workspace not updating regression. 3. Fixed crash issue by checking & unchecking "Disable extension column" option in preferences dialog. 4. Fixed a crash when trying to launch a secondary instance with command line arguments. 5. Fix "Explorer Here" from "Folder as Workspace" problem if folder name contains comma.

the delayed start, like the one you describe, is common when using winapp2.ini due to its size and the sheer time taken to process its contents. but this shouldn't be your issue. as a first try, I would rollback to an earlier version (personally, try v5.40 first) and see if that helps. uninstall your current version first. then go into the Program Files folder for CC and delete its contents (keep the .ini file if you have customised settings) download the latest build from here; https://www.piriform.com/ccleaner/builds (or use FileHippo for previous versions) reboot the PC then install CC from your downloaded file. if you need to convert this Free version to the Pro, go to Options > About and enter your license key.

sadly there has been no response from any 'organisation representative' that I have seen except for that one by @Stephen Piriform where he discussed the mistake and the intent to undo it. and the company's lack of such communication is simply fanning the flames. the vacuum is being filled regardless, by everyone else, except the one's in authority.

so it's v5.44 and it does work but takes 5-10secs until you see any activity? do you use winapp2.ini or any other enhancements? what was the previous version you had that did work OK?