Hi All,
My apologies if this has already been addressed elsewhere, but when I try to run CCleaner (version 3.10) to remove Hotfixes on a machine running Windows 2003 Server (SP2), it does not work. I have been able to use CCleaner on other Server 2003 installations without any issue.
The only difference I see is that Windows' installation is on the M drive letter, rather than C. Could this be the cause? Any known workaround?
Any help would be greatly appreciated.
Thank you!
Hello again!
Anyone able to help me with answering this question or better yet, was it already addressed in more recent builds?
Thank you!
6 months later and no response.. amazing...
Does anyone want to respond to this? I would really appreciate it and have been more than patient.
Devs?
Hi! I'm not a dev, but have you tried the latest version (v3.16.1666)?
If that doesn't work, there might be some program or services blocking the cleaning process.
I noticed that certain CCleaner commands may appear to run under a limited account, but not do anything due not having Admin rights.
Are you running with limited, or admin rights on this machine?
I'm pretty sure (well, mostly pretty sure), that CCleaner is hard wired to look for default locations on the C: drive.
However, if CCleaner is installed on that M: drive, I couldn't say how it would react, as a System Drive not carrying the C: drive letter is very unusual.
I don't even think any of the other guys on here would have any personal experience with that configuration. I think the devs are needed to confirm that one way of the other, but I do think it wouldn't function without it's built in default locations to find.
If any of the guys has experience of that, and a more definitive answer, I'm sure they'll contribute.
I have been able to use CCleaner on other Server 2003 installations without any issue.
The only difference I see is that Windows' installation is on the M drive letter, rather than C. Could this be the cause? Any known workaround?
This implies CCleaner is perfect even on "standard" Server 2003 installations, but has a problem with an abnormal Windows System M:\
It is unlikely that typical home users would have experience or be able to advise.
If you are running several Server 2003 installations it would be reasonable to consider payintg for developer support/advise,
which appears to be quite readonably priced.