Pit99

I made a further test: Seems that the workaround is necessary only when a 6.x version is installed for the first time, after using 5.9x before. When I later installed 6.05 over 6.04, everything ran fine (no uninstalling of the old version, no start from installer necessary).

When CC is started from the installer, admin permissions are inherited to CC; CC starts "as admin", in the bottom left corner of CC is shown "(Admin)". Meanwhile the workaround survived several shutdowns and logons.

I followed your workaround, and now CC runs for me, too, great! It was essential to remove 5.91 first; when installed over the old version it doesn't work. I am also out of ideas what's going on; I hope, the programmers will find out. Maybe I'll also do some tests using ProcMon or else. If I find something of interest I'll come back again and let you know. Once again, many thanks for your friendly help, Kind regards, Pit

Sorry, forgot to mention: no 3rd party AV, only built-in defender. Thanks for now, enjoy your weekend (and your beer) :) Pit

Meanwhile I tried: - logged in as admin, installed ccsetup605_slim.exe over 5.91, 6.05 runs; logged in as non-admin, 6.05 doesn't start, re-installed 5.91 - installed ccsetup605_slim.exe on another notebook with 21H2 (on non-admin account), 6.05 doesn't start, re-installed 5.91

Thank you for your reply. To answer your questions: - I installed CC on non-admin account (as usual over years); then, of course, granted admin rights when UAC pops up. - With 6.04 the OS was on rev 21H2, with 6.05 now on 22H2, same result. - It is the free version, so I can't try "all users". What I see is, that on start on admin account (and also on start of the portable version) a file gc_...dll is created in the program's folder, which disappears after a second or so. On non-admin account there is no write access to that folder, so that may cancel the start. For testing, I gave the folder full access on non-admin account (which can't be a final solution), and CC 6.x runs.

OS: Win 10 Pro 22H2 AV: built in (Defender) Installer (free version): ccsetup604_slim.exe, downloaded 11 Oct 2022 ccsetup605_slim.exe, downloaded 28 Oct 2022 CC does not start on standard account, starts on admin account only 1st attempt: installed over old version (as usual) 2nd attempt: removed old version, then fresh install Same result in both cases. Does not start in debug mode on standard account, no log file created. CC appears for less than a second in task manager. The reason seems to be that there is no write access to C:\Program Files\CCleaner on standard account (for file gc_...dll?). Switched back to 5.9x for now. Thank you. Pit

Thank you for your reply. I read the line FileKey1=... several times, but finally used a backslash instead of a pipe symbol. It seems, the space in My Name doesn't matter at all. So, if it is of interest for other users (XnView is a free picture viewer & converter): [*XnView] LangSecRef=3024 Detect=HKCR\Applications\xnview.exe Default=True FileKey1=%appdata%\XnView|xnview.db Thank you for your help, Peter

Hello, I want to delete the database file xnview.db which is in C:\Users\My Name\AppData\Roaming\XnView when running CCleaner. First I tried FileKey1=%appdata%\XnView\xnview.db which showed "0 byte to delete", and I found out, it's because there is a space in My Name. Then I tried FileKey1="%appdata%\XnView" (with quotes) which showed "*XnView 135kB 3Files", ok so far, but I only want to delete one of these files. When I try FileKey1="%appdata%\XnView"|XnView.db or FileKey1="%appdata%\XnView"|*.db or FileKey1="%appdata%\XnView"|*.* it always shows "0 byte to delete", and I can't find the reason. Thanks in advance for help, Regards, Peter