Solved garlin's PowerShell scripts for updating Secure Boot CA 2023

gunrunnerjohn said:

Well, that makes sense! If all that is done, you're finished, right?

Click to expand...

But it doesn't allow someone to use the update script on untouched PC if they really, really, really wanted to try. It would require an override option from the command-line.

I don't own the Confidence data nor do I understand why MS moved a PC into the "bad" buckets. There could be a false positive. If you're running the check script, the worse thing is you get nagged for something that isn't actually wrong. But for the update process, that's a different matter.

garlin said:

But it doesn't allow someone to use the update script on untouched PC if they really, really, really wanted to try. It would require an override option from the command-line.

I don't own the Confidence data nor do I understand why MS moved a PC into the "bad" buckets. There could be a false positive. If you're running the check script, the worse thing is you get nagged for something that isn't actually wrong. But for the update process, that's a different matter.

Click to expand...

Suggestion, instead of adding a new command line flag, how about requiring the user to uncomment a line in your code that would allow update script to run even on troublesome computers. Like a boolean that must be true, but the only way it can be true is for the user to uncomment a line. And you could write some text to explain the risk in the script.

That way, they have to make explicit changes inside the script in order to allow the update script to excute against their computer.
I would say this is safe enough and no end user could use command line argument not truly understanding what it means and brick their computer.

And add text to post #1 explaining how a user can decide to use the update at his/her own risk, so warned twice, post #1 and in the script...

Added bonus, if they get a new version, line is in comment again !