When I run a .ps (STIG) file in powershell admin mode, I tell the output to save in my desktop and not public documents (same problem in this location too). The file is saved but I am denied access to open even though I am on a local admin account (call this account Bravo).

I’ve looked at the properties of the document and it has the Admin group listed with Full control but it also lists the original Local admin account (account Alpha) on its own. I have logged into Alpha and had no problem opening the file but then when logging back into Bravo, the file suddenly can open. I deleted the Alpha account thinking and reading forums saying do this to fix my problems, but I see that now when I rerun the ps file, the Alpha account is no longer there but instead a S-numbers…. has replaced it. The owner of the output is the Administrator group. I’ve checked the UAC group policies but with no luck there either. How can I get the output files to open without have to every time go into the properties to unlock the Bravo access?