Windows 10: Intermittent failure to load roaming profile: The process cannot access the file because it...

I have a small AD domain with Windows 10 Pro x64 and Windows 8.1 Pro x64 clients. The clients experience intermittent failure to load their roaming profiles as discussed in great length in this over five-year-old thread:

https://social.technet.microsoft.co...file-redirected-folder?forum=win10itprogeneral

Why is this still a problem five years later?

What can I do to prevent this?

:)

 

One machine can't load roaming profiles

We have a number of machines, and they all access roaming profiles from our NAS.

Recently, after moving it from one desk in one building to a desk in another building, one win 8.1 machine cannot load roaming profiles.

It has full network access, and the domain controler and NAS are on the local network (the other building connects through a VPN tunnel).

How do I persuade the errant machine to pick up roaming profiles?

 

Restore Corrupt Roaming Profile from Good Local Profile?

It definitely was *not* a default profile I was seeing, as it contained many (but not all) of the *user-specific* customizations I had already made. Meanwhile, the system seems to have miraculously recovered, When I logged in this morning, I had my roaming profile again. The only change I made which might account for this is that I disabled Azure AD registration in gpedit.msc. It was spamming my event log with 304 and 307 errors, and I have only a local DC, not Azure AD.

- - - Updated - - -

P.S. I forgot to mention above that I had also disabled fast startup. However I rejoiced too soon. The problem is repeatable. If I log on via Ethernet (connected to the same router as the NAS which is serving as DC and file server), the login successfully loads the roaming profile. If I log in via WLAN (on a router separated from the NAS by an additional router), I get the error message about using a local profile.
I presume that this is a timing problem: once I am logged in, I can see all of the mapped drives on the NAS.
Is it reasonable to suppose that the system is trying to load the roaming profile before the network connection is available?
Is there a way to test this hypothesis or, better still, to ensure reliable timing?
Furthermore, why doesn't the local profile look like the roaming profile?
I thought the whole point of a roaming profile was to duplicate it locally for use when the client PC has no connection to the server.

- - - Updated - - -

P.S. I did a little digging in the event log. The recent occurrences do not show:

as I expected, but

instead.
This is surprising because at some of these times this was the only client PC running in the domain.

 

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.