Same problem from 2019. Was hoping this had been fixed by now?

Same problem from 2019. Was hoping this had been fixed by now?

Same problem from 2019. Was hoping this had been fixed by now?

It will not be fixed as essentially it is deliberate. See https://support.mozilla.org/en-US/kb/dedicated-profile-thunderbird-installation

However it is actually not all that hard to force a change of profile.

You can use the profile manger as discussed here https://support.mozilla.org/en-US/kb/using-multiple-profiles Personally I prefer to use about:profiles as I documented here https://thunderbirdtweaks.blogspot.com/2019/09/i-lost-my-profilemail-on-update-to.html

Thanks for the reply, and I had read your responses from before. I'm new to T-bird, though used to use Eudora back in the day. Couple of questions ...

re: It will not be fixed as essentially it is deliberate. see .. from the link: ''Some users have multiple program installations of Thunderbird on the same computer; for example, Thunderbird 38, Thunderbird 45, Thunderbird 52 and Thunderbird 60, each installed in a separate program folder. In these older Thunderbird installations it was allowed to share the same profile by default. "'

But I'm not trying to have multiple installs, just one a new laptop?

re: You can use the profile manger ..

This seems to require being able to run T-bird to e.g. to access the profile manager. As the uploaded image of the error message shows, my only option is OK, and then T-bird shutdowns.

re: Personally I prefer to use about:profiles as I documented here

I read that. My understanding was it involved manual copying of files into the new profiles on the new laptop? I figured surely something must have changed since you wrote that.

This problem still leaves me confused; and have talked w/ a buddy that is a long time user of T-bird, albeit on Linux of late. He's never seen this. The problem doesn't seem related to multiple profiles on a machine, rather that the profile was created (on a different machine) under 32-bit T-bird on Windows rather than 64-bit. As I mentioned, If on the new laptop I instead simply install 32-bit T-bird, it works fine. If I install 64-bit ON TOP OF the 32-bit install, it works fine, abeit the .exe is located in the wrong place.

re: this tutorial https://support.mozilla.org/en-US/kb/moving-thunderbird-data-to-a-new-computer

This seems to work only if one is going 32-bit to 32-bit, not 32-bit to 64-bit (as is the problem I'm having)

Maybe the answer is you can't use a profile from 32-bit T-bird on another computer with 64-bit T-bird? (without manual intervention). My guess is that (and I have not tried this yet), based on what i found DID work is that:

1. start with 32-bit on new laptop with profile from old computer 2. install 64-bit on top of 32-bit install (albeit in the wrong Program Files folder) .. this uses the UPGRADE feature 3. uninstall T-bird (get get the exe out of the wrong folder) 4. reinstall 64-bit T-bird (not an upgrade at this point) and it would hopefully like the (one and only) profile on the new machine

The other option .. upgrade Outlook on old machine to 64 bit (which it should have been from the start .. curse you MS)

This is ultimately about moving 20+ years of e-mail in PST format under Outlook.

Have you tried taking the profile folder itself from the 32-bit version and using tools>import>import from another installation? That approach is new since 102 was released.

Hi David -

re: using tools>import>import from another installation?

By another installation, do you mean another install of T-Bird on the new system? I did try building a blank T-bird install (64-bit) on the new system, hooked up to some random e-mail address of mine. I then tried importing the 32-bit profile (from the old machine, placed in the exact location on new) .. no go. Didn't work.

It is like 64-bit T-bird just does not like profiles built under a 32-bit version of T-bird.

The last test I'm going to do will be what I mentioned before

1. start with 32-bit on new laptop with 32-bit profile from old computer (I know this works fine) 2. install 64-bit on top of 32-bit install (albeit in the wrong Program Files folder) .. this uses the UPGRADE feature 3. uninstall T-bird (get get the exe out of the wrong folder) 4. reinstall 64-bit T-bird (not an upgrade at this point) and it would hopefully like the (one and only) profile on the new machine

This will hopefully a) get the profile over to something 64-bit likes and b) get T-bird installed in the proper 64-bit Program folder. While I guess it's OK to have 64-bit T-bird running out of the 32-bit folder, knowing MS I feel like I need to understand why this does not work so it doesn't come back to bite my later.

Thanks for your help

I will add, this whole problem is rooted in the fact that on Windows 10 T-Bird has to be 32-bit to import from Outlook 32-bit. I started this journey w/ 64-bit T-bird trying to talk to 32-bit Outlook which did not fly .. pun intended. I saw this problem mentioned elsewhere and the solution was to downgrade T-bird (seemed safer than monkeying w/ Outlook). I'll keep futzing around

I am sorry you are disappointed that outlook can only communicate with 32bit apps. There is nothing anyone here can do about that.

You copy the entire profile to a USB drive. You use the tools> import and select "choose a profile folder" you then point the file open dialog to the profile folder on the USB drive (the correct folder will contain prefs.js). Then let it import.

I am trying it out on a 50gb profile at the moment. I sort of expect failure due to size. But we will see.

re: I am sorry you are disappointed that outlook can only communicate with 32bit apps. There is nothing anyone here can do about that.

Right, not trying to lay blame. Just explaining how and why I got here.

Well it imported, spent hours messing with oauth authorizations as they apparently did not import. However, it works as it said it would on the box for mail and accounts.

Well thanks for your help. I'll probably just upgrade Outlook to 64-bit on the old machine, re-import to 64-bit T-bird on the old machine and give it all try again on the new machine. Again, thanks.