I then tried using a domain account without a roaming profile - i.e. I then upgraded it to 2004, and tested - and the problem was back. I then set one up running W10 1909, domain joined and tested. ![]() I set one up running W10 2004 (no other software installed), domain joined it and tested - and it did exactly as described above, so it's nothing to do with Office 365. I've carried out some more investigation, using virtual machines. It only seems to affect the W10 (2004) machines - the terminal servers (Server 2016 and Office 365) are not affected, and removing the local copy of the profile doesn't cause this issue on them. This happens if they log in again, even after a reboot - basically it means that the user account cannot be used on the affected computer. When they click the start button they get the following message: What happens is that once the profile and registry key have been deleted as described above, the start menu is completely broken next time the user logs in. ![]() It has occurred since we upgraded from Office 2013 to 365, but I don't know whether that's related. ![]() Recently on Windows 10 (2004 version), I've encountered a serious problem with this. Been doing this for years with no issues. We use roaming profiles, and for many years (since at least Windows 7 days) the local copy has occasionally become corrupt or stops syncing properly, and sometimes deleting the local copy of the user profile folder and the associated registry key for the user (HKLM\Software\Microsoft\WindowsNT\CurrentVersion\ProfileList) works - next time the user logs in, it pulls down the server copy and work again.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |