||SecretSoftware wrote: So let me ask for this:
Why not design a way so that no- code would execute without my consent, even if its non-admin? I mean no code aside from code run by services that MS designs in the system.
Basically what I am asking is how to prevent this scenario from happening again in the future with another file type? Does this mean maybe UAC should be updated to mitigate scenarios of this type?
1. This would drive every user nuts. Just look at the complaints about UAC as it is, where in normal usage you never see a prompt. I mean, really, for this reason alone I can't believe you're asking this.
Especially if you consider this thread, in which he complains that UAC pops up confirm prompts way too often. And now every process should get confirmed? Baffling.
If you reviewed that thread you will see a proposal to have both. Its called Rules.
With rules life will be good. You set them once. You forget them for ever. And you live your life knowing your secure.
review that thread, you will see that many, many concerns were raised for your idea of Rules, and that many people demonstrated how it would make your system less secure.
But you chose to ignore all those comments, too.