dooley_do

If you are using 1607 then enable shared PC mode, which can be configured to deal with this based on disk space or age of profile.

Interesting, might have to give it a try again with a mandatory profile...

I've not done any solid testing. On a VM I see an initial logon time of about 40 seconds using shared mode and with many of the modern apps removed using a local profile...

With 1607 we've started using Shared PC mode, seems to delete reliably. With 1511 as we have AppSense Environment Manager I was using the flip to guest technique at logoff which basically sets the profile type as guest when you logoff and this makes Windows delete it.

If you want to delete profiles after logoff in 1607 consider using Shared PC mode via MDM or Provisioning package: https://technet.microsoft.com/en-us/itpro/windows/manage/set-up-shared-or-guest-pc I've started using this and so far so good. I am not sure if the mechanisms for deleting the profile have changed compared to using the GPO setting...

I've yet to get a Mandatory Profile to work reliably in any release of W10 so still using standard local profiles and deleting then after logoff!

I believe we have resolved this. It is caused by users having "Enable Chrome to run in the background" enabled. This then creates a Run key in the users registry which makes Chrome run at logon but with no windows. This process seems to then stop a real instance of Chrome from appearing the foreground. I disabled the ability to run in the background via GPO to prevent the problem. I still needed to remove that key from users who already had it present though.

I have the same issue in a standard Windows 7 x64 environment with roaming profiles. User local profiles are deleted at logoff. I can't make it happen with a test account but I think it might be related to users who sign into Chrome, perhaps some add-ins/apps they have installed are screwing it? If I delete the users profile they can load it at next attempt but next login after that it fails to load.