can I add check for update rights?

Why do you need to know this? wyUpdate tells the user if they need to elevate -- there's no way to bypass UAC.

Can you tell me why you want this?

HiI need to check if my user have the rights to update.because updating is not allowed for all users(customers)the update is not free for all users this is why I want to check it before updating.I want to check if there is an update and after that I check if the customer have the right to update.if yes continue else show an error message for update.you have understand me???

Oh, I see. You want to limit updates based on whether they have an up-to-date service license. Sure this is possible.

We have an example using LimeLM licensing to limit updates on the server side. Read the SaaS and time-limited licensing article to learn more about it.

But the basics of it are this:

1. Use %urlarg% to pass your product key to your webserver.2. Validate the licenses is up-to-date on your server.3. Either reject the user or send the file to the user.

If you already have a LimeLM account you can download the full source code example that implements all this. Get it on your API page.

Tell me if this helps.

Is it possible to disable AutomaticUpdater on the client side without having to interact with the server? For example, the client licence is out of date so I disable the update from even starting.

Hey Paul,

Yes, this is possible. But we recommend you block both at the client side and the server side. To stop checking on the client side, just set the "UpdateType" property of the AutomaticUpdater to "DoNothing".

The reason you should block on the server side as well is if your users are technically inclined they can get around these client-side blocks. However if you block on your server side as well, then there's no way to cheat the system -- you're in full control.

LimeLM & TurboActivate supports both server side and client side blocking based on license feature values like "update_expires".

Use the client-side blocking to present a friendly message to purchase more time on their update contract (or however you sell your product), and use the server-side blocking to actually prevent malicious users from using workarounds to try to get the update.

Does this make sense?

Thanks Sam,

It makes sense. The server side checking is better. It's just good to know that I have the client side option.