Profiles are compatible only between the following client and server operating system pairs:
- Windows 8.1 and Windows Server 2012 R2
- Windows 8 and Windows Server 2012
- Windows 7 and Windows Server 2008 R2
- Windows Vista and Windows Server 2008
For example, if you try to deploy Windows 8 in an environment that uses roaming, mandatory, super-mandatory, or domain default profiles in Windows 7, you experience the following:
- After you use a user account that has an existing Windows 7 profile to log on to a Windows 8-based computer for the first time, the components from Windows 8 read and modify the profile state.
- Certain Windows 8.1 features may not work as expected because the expected profile state is not present.
- 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 8 may not work as expected in Windows 7.
- Roaming, mandatory, super-mandatory, and domain default user profiles have to be isolated between versions of Windows.
- For more information about this issue in Windows 8.1, click the following article number to view the article in the Microsoft Knowledge Base: 2890783 Incompatibility between Windows 8.1 roaming user profiles and roaming profiles in earlier versions of Windows
Hotfix informationTo prevent this issue, follow these steps before deploying roaming, mandatory, super-mandatory, or domain default profiles in an environment where users will be used other versions of the operating system in addition to Windows 8 or Windows Server 2012:
- Install the hotfix that is described in this article.
- Create a new registry entry by following the steps that are described in the "Registry information" section.
- Restart the computer.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
PrerequisitesTo apply this hotfix, you must be running Windows 8 or Windows Server 2012.
Registry informationImportant This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
- Swipe in from the right edge of the screen, and then tap Search. Or, if you are using a mouse, point to the lower-right corner of the screen, and then click Search. In the search box, type regedit, and then tap or click regedit. If you are prompted for an administrator password, type the password. If you are prompted for confirmation, provide confirmation.
- Locate and then tap or click the following registry subkey: HKEY_LOCAL_MACHINE\System\CurrentControlset\Services\ProfSvc\Parameters
- On the Edit menu, point to New, and then tap or click DWORD Value.
- Type UseProfilePathExtensionVersion.
- Press and hold or right-click UseProfilePathExtensionVersion, and then tap or click Modify.
- In the Value data box, type 1, and then tap or click OK.
- Exit Registry Editor.
- You can disable this feature by setting the value of the UseProfilePathExtensionVersion registry entry to 0. However, user profile corruption occurs if you continue roaming user profiles between Windows 8.1-based computers and other operating systems.
- You can use the Group Policy Preference (GPP) Computer Configuration Registry Preference item to populate the registry key on multiple computers. For more information about this, go to the following Microsoft website:
- You can safely apply this hotfix on all operating systems. If these profile types are not being used, the registry setting is ignored.
Restart requirementYou must restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace a previously released hotfix.
Note This method may not apply to all customers because of the following limitations, and it is recommended that these customers apply this hotfix and configure the UseProfilePathExtensionVersion registry entry as described previously:
- The Set roaming profile path for all users logging onto this computer Group Policy setting has to be applied on every client computer where the roaming profile is used, and then applies to all users who log on to the computer.
- The Set roaming profile path for all users logging onto this computer Group Policy setting can only set one file server location for all users who log on to the computer. If the profile storage is partitioned by groups of users, which is common in large organizations, a Distributed File System (DFS) namespace has to be used to have a consistent logical profile naming scheme for this policy to function as needed. Use of a DFS namespace allows the consistent logical path to resolve to different physical servers to support the partitioning of profile storage by user group.
ID do Artigo: 2887239 - Última Revisão: 26/01/2014 - Revisão: 1