jpbp200

I created a folder in NETLOGON and put delprof2.exe in it then the below script runs at startup. You can put delprof2.exe anywhere that can be accessed at startup I guess. Put the path to the folder of choice where delprof2.exe is in the "" where it says [PATH TO DELPROF] New-PSDrive -Name "delprof" -PSProvider "FileSystem" -Root "[PATH TO DELPROF]" $Profiles = Get-WmiObject Win32_UserProfile | Where-Object Special -eq $false $localProfiles = $Profiles | Where-Object LocalPath -notmatch "default" $paths = $localProfiles.LocalPath $usernames = $paths -split "C:\\Users" $localProfiles | ForEach-Object Delete cd delprof: foreach ($username in $usernames) {& .\delprof2.exe /q /id:$username /i /r} cd C: Remove-PSDrive -Name "delprof"

So the workaround I have in place is to delete the profiles using a combination of the PS command AND delprof2.exe run in a single script at startup. This does completely remove the profile and I have not seen the issue since.

Hi Jason, thanks, yes I realise that. I mentioned further on in my post that BOTH methods work when run on the affected workstation. It is when they are invoked from a script set to run via GPO that the issues arise.

So here are my experiences..... I have UE-V enabled and when I first sign on to a machine UWP app works OK. I have delprof.exe running as a script at logoff and when this happens the profile appears to be deleted OK but when a new profile is created I start to see the app failures described by the OP. If I delete the profile using System/system Info/ advanced system settings/user profiles etc etc this deletes the newly created (but now corrupted) profile OK and next logon works OK again. If I run Get-WmiObject Win32_UserProfile | Where-Object Special -eq $false | ForEach-Object Delete this gives errors but does fix the issue. However it leaves the profile folder in C:\Users so subsequent logins get the .000 .001 extensions. Also if delprof.exe is run manually on the machine it does completely remove the profile and folder and subsequent logins are OK. The issue seems to be that if you use a script to delete a profile (no matter how you do it) then you see these errors the next time the profile is created but if you use the tools manually then the issue is not present. A colleague has tested a script that runs BOTH Get-WmiObject Win32_UserProfile | Where-Object Special -eq $false | ForEach-Object Delete AND delprof.exe and reports that using both these tools in a single script run at logoff deletes the profiles cleanly and does not cause the issue when a subsequent new profile is created.

Thanks very much for sharing that. Very helpful indeed.

I had a similar issue which was resolved by updating the graphics drivers. In fact graphics driver updates are the cause of quite a few unrelated sort of problems these days it seems....

https://www.tes.com/jobs/vacancy/deputy-network-manager-durham-452465 PM me if you have any questions.