niks nut

Sure, do you need any further details, such as the current license key (ends with: 5C4B6J, valid through 17. Aug. 2022, via Cleverbridge email of 17. Aug. 2021)? But I don´t think I need that. My solution seems to work for now, it is just odd. Thx, Niks

CCleaner, at least I assume it is, has just reset the permissions of the .lic file again back to original, while I was using it as user. I have now changed it to the following which worked before. Now lets see how long this holds. Niks Privileges9.tif

I downloaded CCleaner always from Piriform directly. I don´t use the windows store for anything. I also went through the registry but could not find any hint to the .lic file, or the .dat file for that matter. Anyway, I applied my workaround again and changed the privileges of the .lic file. Attached are the privileges of the .lic file as they are after installation (3) and after I changed them (6). Regards, hope you find a solution. Niks Privileges3.tif privileges6.tif

MeganCCLeaner, I did as you requested. De-installed, made sure that the whole directory was deleted and freshly re-installed CCleaner. All with the same effect. I again have a .lic file with access privileges that prevent a user access to the Pro functionality. I do not have a .dat file. What is interesting to note is that upon activation, CCleaner presented me an old, now invalid, License number, not the latest that I have been using for some months. Apparently some license history was still stored somewhere. CCleanerNewInstall.tif

"Are you saying that if you log into your machine with an admin account then it runs CCleaner Pro, but if you log into the same machine with a non-admin account then it runs CCleaner Free? " Exactly that is what I am saying. I also did not have this problem in the past it is new (very recent). After I noticed the problem I started to investigate and found that the culprit was the access privileges to the .lic file for the user. In addition, as I stated in my 1st Email it turns out that , when you change them as Admin to provide users with read access, the CCleaner program apparently resets these privileges wrongly again. Hence the solution to prevent the program from resetting the access privileges to the .lic file, after having given read access to users. My system is Win10Pro-64bit (completely updated latest version (19041.1415)), CCleaner Pro (5.88.9346 (64-bit)). CCleaner.tif

Incredible did you drink to much beer or whisky today already? I stated: "However CCleaner then sets the access privileges to the license file such that normal users cannot read the file. The result of which is that normal users do not have the access to the registered Pro-version, whereas the Admin´s do." When a user does not have ANY access to the license file, then the user´s version will always run in the "free" form, whereas he has paid for the functionality of the "pro" version. This implies that certain functionality that only comes with the pro-version is not available to the user, when he does not have access to the license file. Only when the user has at least "read access" to the license file does he have the functionality of the "pro" version available. There is thus a bug in the program that wrongly sets the read privileges of the license file for users.

Recently I noticed that when I was using CCleaner as a user that it would not clean up after I closed firefox. I then noticed that I as user, was not a registered user, although as an administrator I was. CCleaner generates a license file (.lic) after registration. This must be done by the Administrator of the system. However CCleaner then sets the access privileges to the license file such that normal users cannot read the file. The result of which is that normal users do not have the access to the registered Pro-version, whereas the Admin´s do. I can reset the privileges of this file as an administrator, but apparently the program resets these privileges again such that normal users are excluded. I found a solution to this, basically excluding access to the file by the program, but obviously this is not as it should be. Hope that the next version has this resolved. Niks