Issues with parameter "-crTask" about chrupd HOT 2 CLOSED

There is no "install" as such, arguments are optional and use defaults if missing (they can also be set inside script).
In whichever way the options are given -- crTask will use them to create the task, using the path where the script is.

from chrupd.

There is no "install" as such

Okay. It's a a download followed by an extraction step. Doesn't address the questions I had.

arguments are optional and use defaults if missing (they can also be set inside script).

This still leaves open all questions I had: what if the defaults (or values set in the script) contradict an existing "installation"?

In whichever way the options are given -crTask will use them to create the task, using the path where the script is.

I assume this is the answer? Any previous call to chrupd (and any "installation" performed by it) and its parameters get ignored by the task which runs the next day (with possibly deviating settings)? So I might end up with two different browsers if I or other users inadvertently use different parameters (or forget to set them on the additional script execution for the task creation), right?

I think this behavior should be stated more clearly in the readme.

from chrupd.