bright, fresh software
Downloads  |  Buy

wyUpdate and UAC

Post a reply


This question is a means of preventing automated form submissions by spambots.
Smilies
:D :) ;) :( :o :shock: :? 8-) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :!: :?: :idea: :arrow: :| :mrgreen: :geek: :ugeek:
BBCode is OFF
Smilies are ON
Topic review
   

Expand view Topic review: wyUpdate and UAC

Re: wyUpdate and UAC

Post by Roman » Today, 8:48 am

So, at some moment some user will have an Access Violation error...
Ok, thank you for fast response.

Re: wyUpdate and UAC

Post by Wyatt » Yesterday, 10:29 pm

Because wyUpdate is not magic. Nor is the UAC. There's no way to magically bypass the UAC. You just need to write data to parts of the computer that the current user has access to.

Sure, you can make it so wyUpdate doesn't prompt for elevation. But then what do you accomplish? Exactly nothing: because now wyUpdate will just show an error when it can't write to folders / registry / etc.

Make sense?

Re: wyUpdate and UAC

Post by Roman » Yesterday, 10:20 pm

Sorry for resurrecting old thread, but could you point me to possible problems of using this kind of solution:
DMaly wrote:
> change the behavior of the wyUpdate to bypass the UAC by changing the source code.

Why this is bad idea?

Re: wyUpdate and UAC

Post by Wyatt » March 27th, 2013, 6:33 pm

Just to update this topic for future readers: this is answered here: Admin elevation is not handed over to updated version

Re: wyUpdate and UAC

Post by Ani » March 27th, 2013, 10:54 am

[quote="Sam"]If you want wyUpdate to not request UAC permissions then you need to install to a predefined location that the user is guaranteed to have access to. For example: the desktop, documents folder, %appdata%, etc.

The "C:\CSI " folder is not one of those predefined folders, and thus UAC access is required.[/quote]

Is there a list available somewhere of all the directories that the user is guaranteed to have access to?

Is this testable beforehand, via C#, so that one can notify the user at program startup that they will not be able to update without uac. And recommend that they move the program if the user feels he want this functionality?

Re: wyUpdate and UAC

Post by Sam » March 14th, 2012, 10:08 am

If you're realsing your own version of wyUpdate then you need to make sure the self-update works. See: How to make a custom version of wyUpdate.

Re: wyUpdate and UAC

Post by DMaly » March 14th, 2012, 6:40 am

We decided to change the behavior of the wyUpdate to bypass the UAC by changing the source code. It satisfied our requirements. But I have another important question - what will happen when you release new version of wyUpdate? Will this your new version overwrite our version?

Thank you.

Re: wyUpdate and UAC

Post by Sam » March 13th, 2012, 2:49 pm

In general it's a bad idead to make a programs directory writeable by all. One alternative is to run a "dummy" service that does the updating in the background. See one of the following articles:

Re: wyUpdate and UAC

Post by DMaly » March 12th, 2012, 11:58 am

Yes , but all these folders are User-Specific. We need to solve following scenario. A teacher (admin) installs the application (it is really only several files, no services, no registry changes). Then students (users) will use the application. When we release a new version and any student will start it, we need the application to download this new build and install it without any cooperation with a teacher.

In case we will use AppData or Desktop folder, then every user must install its own copy of application. How to solve this scenario, please?

Thank you.

Re: wyUpdate and UAC

Post by Sam » March 12th, 2012, 9:07 am

If you want wyUpdate to not request UAC permissions then you need to install to a predefined location that the user is guaranteed to have access to. For example: the desktop, documents folder, %appdata%, etc.

The "C:\CSI " folder is not one of those predefined folders, and thus UAC access is required.

Top