Windows 10: Restore Corrupt Roaming Profile from Good Local Profile?

Windows complains that my roaming profile is corrupt and says that it is logging me in with a local profile. This profile is missing a few customizations but seems to otherwise OK. Fixing this profile would be less work than reconfiguring a default profile, which is what the usual methods of dealing with a corrupt profile would have me do. Is there some way to use the local profile as the basis of a new roaming profile? Am I better advised to dispense with roaming profiles altogether and use 3d party software to keep my local profile in sync with my NAS?
BTW, even though Windows claims to use a local profile, it is still writing to the roaming profile on the NAS.

:)

 

Windows 10 roaming profile includes AppData\Local & LocalNow folders

Existing Windows 7 & Windows 8.1 domain environment with accounts configured to use roaming profiles stored on a Windows 2012 server using DFS file share.

New Windows 10 Pro built for testing and logged on with an existing domain account. First hint something was wrong was the "Roaming profile not fully synchronised" errors. Looking the event log reveals lots of access denied errors from the user profile service
attempting to copy to/from AppData\Local and AppData\LocalNow.

Looking in the new v5 profile sub-folder created automatically, there is indeed three sub-folders:

• Roaming - expected
• Local - shouldn't be there
• LocalNow - shouldn't be there

The Local & LocalNow folders are not in the v2 profile from the existing Windows 7 & 8.1 clients.

Aside from these access denied errors and pop-up warning, including Local & LocalNow in the roaming profile is a really bad idea as it really slows down the log on & off process as they tend to contain large number of large files, e.g. cached application
data. The whole idea of splitting Local & LocalNow out is so this temporary/rebuildable data can be kept out of the profile.

Any idea why this is happening?

Thanks, Rob.

 

What causes a corrupted profile

Good luck with that.

I have a half dozen machines, plus at least the same again as VMs. I have never yet seen a corrupt profile. My longest serving machine has a profile that was migrated from Windows 7 back in 2015 and has survived every version upgrade since then, up to and including 2004.

While I have yet to experience a corrupt profile, I could suggest looking for a common factor. For example, were they all Microsoft Accounts? Perhaps an error in syncing corrupted them? All my accounts are local accounts, if that's any help.

 

CCC Profiles that disappear

id suggest a spyware check