Jump to content
CCleaner Community Forums
APMichael

CC 3.19.1721 /EXPORT doesn't work

Recommended Posts

Hello,

 

with the new version 3.19.1721 (Portable) the command line parameter /EXPORT doesn't work anymore. After the UAC nothing happens (Windows 7 x64).

Any idea?

 

Thanks and kind regards,

Michael

Share this post


Link to post
Share on other sites

Yes - I have an idea. Do you want to know more ? :)

 

The very first item on the announcement of this new release was

Added option to skip User Account Control (UAC) warning.

 

I immediately wondered about the impact on my Trim_*.bat which was modified to detect and accommodate UAC aggravation.

 

I think that if Trim_*.bat detects that UAC is active it might be appropriate to simply ignore the suggestion to run with elevated privileges.

It is always possible that version 3.19 does NOT run with elevated privilege BUT TOGGLES the privilege,

in which case if it is launched with standard privilege then it executes as privileged,

but when launched with elevated privilege it might execute at diminished privilege.

 

I regret that this is not a good time for me to do any more than give suggestions.

I am currently occupied with configuring my system to minimize extravagant waste of the life of my new SSD.

 

Regards

Alan

Share this post


Link to post
Share on other sites

Thanks for your reply. It seems that the new version of CC ignores the UAC now. It doesn't make a difference if you select yes or no - CC starts with standard privileges only.

 

But if you start the command prompt with the windows option "run as administrator" and then execute the parameter /EXPORT everything works fine again. So we have to use "run as administrator" always now?

Share this post


Link to post
Share on other sites

Welcome to the world of BETA TESTERS :D

 

Piriform have done a good job getting the main functionality of CCleaner to avoid the fatal embrace of UAC.

I am hopeful that the /EXPORT feature was overlooked and will be easily corrected.

Share this post


Link to post
Share on other sites

I reported the same issue in the staff forum, thank you for also doing so here in the public one :)

Share this post


Link to post
Share on other sites

I have just recreated this problem using my testing environment.

 

This issue was described in details and passed to dev team. It should be fixed in next version.

 

Thank you all for your help J

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×