Powershell "RunAs" causing recycle bin issues. Would like some input please.

Question

I developed a script to assist our UserAdmins with creation of AD user accounts and create home folders on the server shares.  I am encountering an issue with the recycle bin becoming corrupt when the user first logs in.  This script must be run
with an elevated account with permissions to the shares.  I also noted a change in the way the recycle bin is displayed in the share.
The home folder is created using: 
New-Item -ItemType Directory -Force -Path $directory
If I log into my machine as my elevated account and run powershell/powershell_ise, all is well.  The recycle bin displays as "Recycle Bin" with the correct icon image
However, if I log into my machine with my non-elevated account and select "Run as a different user" for Powershell or Powershell_ISE and use my same elevated account from above the users receive "corrupt" recycle bin errors when logging
in or viewing the recycle bin properties.  Additionally, recycle bin is now listed as "$Recyle.Bin" and is using a folder icon.  This issue is resolved by removing the users AD account from the home folder permissions and re-adding it with
identical permissions.
I see this behavior using Win8.1 x64 as well as Win7 x64 Enterprise.
On another somewhat relevant topic, when launching Powershell_ISE with "Run as a different user" it often freezes and must be forcibly closed.  Could be relevant, could be coincidence.
I appreciate any input you may have regarding this issue.
Thanks,
Jeff

Answer 1

I'm trying not to come off as combative, but I feel you are misunderstanding or I am not being clear. The recycle bin is auto-created when the user first logs into the machine as is are the sub folders to the parent folder.  All of the desktop.ini files,
recycle bin folders and various other user profile objects are created upon first login by that user inside of the folder created in the PowerShell script.  Prior to this the user admins were manually creating the same parent folder with their elevated
accounts.  Given the isolated conditions in which it works vs when it doesn't there is no indication that permissions are causing this issue.
I'll try to explain why the issue, I believe, lies with PowerShell.
1) Launch a PowerShell session from the current logged in elevated account
2) Run the script
3) Users home folder is created
4) Upon user logging in for the first time the user profile objects are created in the home folder on the share
5) No issues with recycle bin
vs - from the same machine, same script
1) Launch a PowerShell session with "Run as different user" context using the same account from above
2) Run the script
3) users home folder is created
4) Upon user logging in for the first time the user profile objects are created in the home folder on the share
5) Recycle bin is corrupt and icon is wrong
The only thing that changes between these 2 scenarios is the way in which PowerShell is run.
It's the same computer, the same test user account, the same share, same GPOs and AppSense policies.
Scenario 1 is run from elevated account logged into local machine
Scenario 2 is run from non-elevated account with "Run as different user" context using the elevated account
I know I'm sounding like a broken record but it doesn't make sense AppSense or GPO or even folder permission would cause an issue when the folder is being created using the same account in both situations.