Can I Use the Same User Profile on 32-bit and 64-bit Windows?

This article is part of Helge’s Profile Toolkit, a set of posts explaining the knowledge and tools required to tame Windows user profiles.

More and more people are upgrading to a 64-bit version of Windows. Many of them would probably like to keep their existing configuration. The question is: can you use the 32-bit profile on Windows x64? Is there even such a thing as a 32-bit or a 64-bit user profile? Or are profiles independent of the system’s bitness?

Profiles and Operating System Bitness

We had those very questions at sepago, so we performed some tests. First, we analyzed the entire file system and registry content of a default profile on x86 and on x64 Windows. When comparing the results, we found zero differences. Then we tried to log on to a 64-bit machine with a profile created on a 32-bit system. All went well - no mysterious signs, no funny sounds, nothing. We also did it the other way around, again, without noticeable wrath of the gods.

That answers the question: Can you use a 32-bit profile on a 64-bit machine? Yes, you can!

You Can - But Should You?

The fact that something is possible does not mean that it is clever. Although technically possible, using profiles across OS bitnesses has the potential for trouble. If you want to know why, just search for “Program Files (x86)” in the HKEY_CURRENT_USER hive on a 64-bit system. You will find many references (unless you installed 64-bit software only, which I doubt). Applications store file system paths to all kinds of configuration files, helper executables and installation directories in the registry. In the case of 32-bit applications on 64-bit Windows those paths all start with “Program Files (x86)”. Now use the same registry hive on a 32-bit machine that has the same 32-bit applications installed … and all paths are invalid. 32-bit Windows does not have a WoW64 subsystem that redirects 32-bit processes from “C:\Program Files” to “C:\Program Files (x86)”.

What are the consequences?

Profile sharing across operating system bitnesses may cause applications to malfunction in strange ways. Some programs may be entirely unaffected, whereas others may not work at all. How exactly your most important application is going to deal with such a situation cannot be foreseen - because one thing is certain: that its developers never thought such a thing might happen.

Not to forget: shared profiles are not supported.

Comments

Related Posts

Free Script: User Profile Domain Migration with SetACL

This article is part of Helge’s Profile Toolkit, a set of posts explaining the knowledge and tools required to tame Windows user profiles. When administrators migrate user accounts between domains, they typically re-ACL those server resources users have access to. In plain English: they copy or move the permissions from the accounts of the old domain to the corresponding accounts of the new domain. There are various ways to do that. In this article, I present a simple way to re-ACL roaming user profiles.
User Profiles

New OS = New Profile = User State Lost. True or False?

New OS = New Profile = User State Lost. True or False?
Going to Windows 7 or Server 2008 (R2) means trouble. Let me use an analogy to explain why. You are in charge of moving people from their old houses to shiny new buildings. You have planned everything perfectly. The new homes are beautiful and located in a great neighborhood. But still, after moving house, people start to complain. They do not feel at home. You forgot to take all those seemingly unimportant things that make a house a home: pictures, plants, all sorts of personal stuff. Impossible, you say? People would never leave their personal belongings behind? I agree: when it comes to moving house, not taking at least most of the personal stuff is highly unlikely. But in IT it is common practice.
User Profiles

Latest Posts