SAPIEN Technologies

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.

We have one Windows 11 machine that exhibits this behavior 90% of the time. Other times it works fine.
We also have tow other Windows 11 machines where this works flawlessly all the time.
So question for you, is your machine an original Windows 11 machine or was it updated from Windows 10?

Yes, we identified the problem. An update for this will be available shortly.

Oh goody a puzzle
So what is the PowerShell version? This is all a little strange. I have never heard of files staying open once the process that opened them terminates.
Are you certain the process terminates?

.NET (which is the underlying architecture) does have a notion of secure location. But then it would not run at all. At least as far as I know. You need to find out which process has your files open, otherwise it is just guesswork. LockHunter will tell you who has the files open. Assuming your scrip...