Roaming user profiles in Windows 10, Windows Server 2016 and later versions are incompatible with roaming user profiles in earlier versions of Windows.
For example, when you try to deploy Windows 10 in an environment that uses roaming profiles in Windows 7, you experience the following behavior:
- After you use a user account that has an existing Windows 7 or Windows 8.1 profile to logs on to a Windows 10-based computer for the first time, the components from Windows 10 read and change the profile state.
- Certain Windows 7, Windows 8.1 or Windows 10 features may not work as expected because the expected profile state isn't present.
For example, Start menu does not start. Cortana, Taskbar is unresponsive. And taskbar icons are missing.
- When you try to use the same user account to log on to a Windows 7-based computer, the user profile modification that was performed in Windows 10 may not work as expected in Windows 7 or Windows 8.1.
After you use a user account that has an existing Windows 7, Windows 8, or Windows 8.1 profile to log on to a Windows 10-based computer for the first time, a "v5" or "v6" version of the profile is created.
By default, Windows 10 clients uses a "v5" profile folder extension. On earlier versions of Windows, the default version was "v2" unless the hotfixes that are described in the following articles are applied and the steps that are mentioned in the articles are followed.
Note Roaming, mandatory, super-mandatory, and domain default user profiles that were created in one version of Windows must be kept isolated from those that were created in another version of Windows. Each version of Windows will have its own profile version
Make sure that you did not disable Profile Versioning.
By default, profile versioning is enabled in Windows 10, Windows Server 2016 and later versions of Windows. This behavior is by design and was implemented because of the incompatibilities between profile versions. If user accounts that use roaming profiles log on to both Windows 10 and earlier versions of Windows, there must be a profile for each version type.
For more information about profile versions and how to deploy roaming user profiles, see General information about how to deploy roaming user profiles
For more information about Mandatory Profiles, see Create mandatory user profiles.