Health Checker -ScriptUpdateOnly asking for prompt to confirm

[docbitter]

Provide Version Number
Health Checker version 22.11.02.1803

Describe the issue
.\HealthChecker.ps1 -ScriptUpdateOnly
Checks for update but asks user for confirmation to acutally do the update

Expected behavior
.\HealthChecker.ps1 -ScriptUpdateOnly should do a silent update without user interaction

Script Output
.\HealthChecker.ps1 -ScriptUpdateOnly

Bestätigung
Möchten Sie diese Aktion wirklich ausführen?
Ausführen des Vorgangs "Update script to latest version" für das Ziel "HealthChecker.ps1".
[J] Ja [A] Ja, alle [N] Nein [K] Nein, keine [H] Anhalten [?] Hilfe (Standard ist "J"):
File signed by CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US
AutoUpdate: Signature validated.
AutoUpdate: Succeeded.
Script was updated. Please rerun the command.

Additional context
We use the script to generate a daily health report of our exchange environment and mail this to a team. Whenever the script gets updated the Task is stuck at a hidden confirmation. We are looking for a way to do a silent update.

[dpaulson45]

@docbitter I believe this must be something on your system. I just went ahead and downloaded an older version and did .\HealthChecker.ps1 -ScriptUpdateOnly and it downloaded the latest update and didn't prompt me. Proceed to do the same for the latest version, no prompt.

What version of the script did you have when you were using that switch. There was an issue a while back regarding this, but it shouldn't be present any longer.

The old issue #1098

[docbitter]

Thanks David! When i add the line
Set-ExecutionPolicy RemoteSigned to my script the prompt is gone

[bill-long]

@docbitter Are you sure you're not confusing the execution prompt and the update prompt?

There are two possible prompts as shown in this screenshot:

Adding -ScriptUpdateOnly stops the update prompt because we pass -Confirm:$false in that case:

Note how -ScriptUpdateOnly stops the update prompt, but not the execution prompt:

You can also disable the update prompt without -ScriptUpdateOnly by adding -Confirm:$false. Note how in the following screenshot, I still receive the execution prompt, but not the update prompt:

Execution policy shouldn't have any effect on the update prompt, but it might affect the execution prompt. Typically you can stop the execution prompt by unblocking the file:

In fact, editing the script as you described should make it fail to run under a RemoteSigned policy unless the script is unblocked:

[dpaulson45]

@bill-long I believe it is still the update prompt for the customer. The original post was the following, which contains "Update Script to latest version".

[bill-long]

@dpaulson45 Yeah, but execution policy would not affect that. His last post was:

Thanks David! When i add the line
Set-ExecutionPolicy RemoteSigned to my script the prompt is gone

That does not make any sense in context of the original post.

[docbitter]

Hi David, Hi Bill,

you are both right. I confused the execution prompt and the update prompt. The execution prompt is gone since i added the Execution Policy to the script.

BUT now i cannot reproduce the issue. The script updates itself now right away.

a) I got an "Update Script to the latest version?"-Prompt when I executed the script without any switches.
b) I got an "Update Script to the latest version?"-Prompt when I executed the script with the "-ScriptUpdateOnly" switch
-> b) is the reason i started this question.

Now i don´t get any prompt whatever switch i use.

[dpaulson45]

@docbitter I wonder if you were on an older build of Health Checker where this was still a problem and was resolved within that old issue I provided above.

Since you are no longer seeing the issue with the update piece, then I think it is safe to say that we can close out this issue.

[docbitter]

Thanks David, yes: we close out this.