SAPIEN Technologies

A quick Google search indicates that your group policy only allows signed executable files to run elevated.
Disable that policy or use a certificate to sign your executable.

Here is an example I found on twitter recently that illustrates this: #PowerShell tip: if you're using `Get-Content` to simply read a file, it's much faster to use [http://System.IO.File]::ReadAllBytes() or [http://System.IO.File]::ReadAllText() even in a pipeline. About 95% faster! `Get-Content` is...

As you stated, knowing PowerShell is obviously key. PowerShell itself is deeply rooted in .NET and so is WinForms. I would strongly recommend to take a beginner's class in C#. May it be online video, book or in person, it will enable you to read and understand concepts. Many tips and tricks and samp...

That is not how PowerShell 7 and the underlying framework works. All these DLLs and associated files are not generated for fun, they are required. Here is an article from a while ago that explains things in more detail: https://www.sapien.com/blog/2020/08/12/packaging-scripts-for-powershell-7-and-ne...

Yes that tracks. It seems a genuine Windows 11 machine acts differently than an updated one.
This, by the way, is not the only thing that is different. Keeps it interesting. We will keep looking.

Yes, we are aware and it has already been fixed.

We have identified the issue. It will be part of an upcoming service build.

We have identified the issue. It will be part of an upcoming service build.

Use a name of Exename.xx.xx.xx
Create a post- build script that retrieves the version number of Exename.xx.xx.xx.exe
and renames the file.
(Get-Command "Exename.xx.xx.xx.exe").FileVersionInfo.FileVersion
will retrieve the version number.
You can take it from there.

If the file disappears or is blocked from writing, it is your anti-virus scanner. It quarantines the newly created file.
Check your logs and submit a quarantined file to your anti-virus vendor.