Michael Klement

@iSazonov, I agree with @rhubarb-geek-nz that there's no good reason to saddle user on Unix-like platform not only with unnecessary _runtime_ overhead, but - as noted - in the case...

@iSazonov: * The memory usage problem and the - much worse - runtime penalty discussed in #21473 is in the context of _Windows_, where actual AMSI API calls are currently...

@iSazonov, in light of the above: * The `Resolution-Answered` label is inappropriate. * While it is appropriate to make the security WG review this, let me summarize what I think...

It's unclear to me what problem you're facing, but I have two observations: * You should no longer install the now obsolete [WindowsCompatibility](https://github.com/PowerShell/WindowsCompatibility) module in PowerShell 7, because its functionality...

* My previous comment implies that it is ill-advised to try to load _all_ modules via the Windows PowerShell Compatibility feature. * That things change between PowerShell versions (possibly in...

I understand that you _think_ you've provided all the necessary information. My comments were meant to point out that you didn't. What your screenshot shows is: * An ill-advised attempt...

P.S., @Simon79-626: While GitHub seemingly doesn't prevent promoting one's _own_ posts via emoji, I encourage you to abstain from doing so.

> TBH I'm tired of your comments. Unless you have _counterarguments_, please abstain from such gratuitous comments. If you do have counterarguments (and I know you think you do, but...

@rhubarb-geek-nz: Since this issue lacks a clear problem definition, discussing Windows 10 vs. Windows 11 may be premature. What _is_ clear, however, is that the issue exhibits misconceptions and ill-advised...

* Your screenshot shows only expected behaviors (while doing ill-advised things / using broken commands, as noted). * As noted, your issue lacks a clear problem description and the screenshot...