Is your TB 32-bit or 64-bit? Help/About TB. Is Quickbooks 32-bit or 64-bit? If QB is 32-bit, TB must also be 32-bit.

QB is 32 bit. The help-about in QB does not state if 32 or 64, but the start path is C:\Program Files (x86)\Intuit\QuickBooks Enterprise Solutions 19.0\QBW32EnterpriseWholesale.exe

TB is 32 bit. Currently running 60.9.1 (32-bit). When/if it automatically updates to TB 68.4.1, it no longer works with QB. I assume the updated 68.4.1 would have been 32 bit? Or would it auto update to a 64 bit version?

- GMB

No telling what the update process does this week. It might have installed the new 64-bit version in the Program File (x86) folder instead of Program Files.

The 32-bit version can be downloaded here:

https://www.thunderbird.net/en-US/thunderbird/all/

Note the 64-bit version is displayed more prominently than 32-bit, which is probably inadvisable.

Install 68.4.1 32-bit over 60 32-bit, set TB as default client during Advanced setup, then restart computer (important). Report if QB sends files to TB.

Even if the previous update installed the 32-bit version, running the full installer often fixes MAPI issues like sending files from apps like QB.

Did you get updated to the 64bit version of Thunderbird?

If so remove it and install a 32bit version.

Working better now I hope. There is a bug somewhere about 64bit MAPI not working..

One of the users sent me a screen shot after the update, and it was 68.4.1 32 bit. So it did not change to 64 bit, but was not compatible with QB.

Would a fresh install of 32 bit 68.4.1 give a better (compatible) result? I'm a little hesitant to pursue at this time after spending half a day chasing down the problem and finally getting it to work again with 60.9.1 (if it ain't broke, don't fix it).

I attempted to check the "don't update" option, but if it continues to update with compatibility issues, will need to look further for a more permanent solution.

- GMB

If it aint broke, don't fix it. But can you tell me what you had to do.

MAPI has been particularly problematic in the last 18 months and the last major fix about a year ago broke just about everything and was roled back. THe current situation is 64bit is not working, but that "might" have to do with updating DLL's in the register. Hence my question. We do not get much information from folks that can express themselves.

Some bugs I follow on the subject are https://bugzilla.mozilla.org/show_bug.cgi?id=1601879 and https://bugzilla.mozilla.org/show_bug.cgi?id=1530820

The later being 60.5 and the first V68.2. If you can add to the quantum of knowledge, that would be great.

The issues started in September, 2019 when we migrated our cloud based QB to a new host. I installed TB 68.1.1 on the new server, but could not get QB to recognize it. I can't remember if it was the 32 or 64 bit version. Very likely 64 bit as I didn't realize it would make a difference.

After a few rounds of finger pointing between the host and intuit as to why it was not compatible, one of the intuit techs suggested that the latest TB was not compatible and that I should install on older version. I noted that TB 60.9.0 was working on our old server, so installed that version and it became compatible with the new setup.

All was good until a few days ago when some of the users (there are 5 of us regularly using the system) complained that they could no longer email forms from QB. At first I though that QB may have updated and caused an incompatibility. Then I remembered that I'd had problems with the newer versions of TB so checked the TB version. Sure enough TB had updated to 68.4.1 32 bit.

I contacted our host tech, had them uninstall TB and then install TB 60.9.1. On Options - Advanced, I clicked to let me choose whether to install updates, but did not uncheck the "Use a background service to install updates". As I opened TB a 2nd time, it automatically updated to 68.4.1 and compatibility was lost.

So I contacted our host again and had them repeat the process. I then unchecked the "Use a background service" and checked the box for "Never check for updates". I instructed the other 4 users to do the same. However, often the update portion would be greyed out and not allow changes. Not sure why. Perhaps it would not allow this change if another user had TB open?

Well I logged onto the server this morning only to see that TB had updated itself again (likely from another user who could not change the greyed out options) and is again not compatible.

So unfortunately it is broke again.

What are my most likely chances of success? Will uninstalling TB, downloading a fresh 32 bit version of 68.4.1 installing and restarting allow QB compatibility?

Or is there a sure-fire way to prevent 60.9.0 or 60.9.1 from updating itself?

Your expertise is appreciated!

- GMB

One other item. I installed the Owl for Exchange add on back in September. This allows TB to sync with our exchange based email system and syncs email between the various devices of each user. Works great except when TB automatically updates itself! - GMB

If you have TB set to 'Check for updates but let me choose to install them', it will not update automatically unless, like some users, you have some other app, like the software update utility built into some security programs such as Avast or Kaspersky. The latter, especially, has played havoc with 'updates'.

As for the MAPI/QB issue, yes, you should run the full installer over the existing TB, as recommended above, set TB as default during setup and restart the computer. You may ask why running the full installer is any different from updating from an older version, but in fact this method has resolved MAPI issues for other users, both for TB 60 and 68. It's not guaranteed to fix QB sending to TB, as this may depend on other factors, such as corrupted Windows settings or the presence of Outlook, but it is an easy, worthwhile step.

https://support.mozilla.org/en-US/questions/1276900

Do you have multiple users accessing the same TB profile? It's one thing to have users accessing the same mail account simultaneously, but if the profile is shared, that probably explains why update settings are greyed out, plus a host of other potential problems.

re :Owl for Exchange add on I notice that it does not say it is compatible with tb version 68. It would be the responsibility of the author to make it compatible. Suggest you contact the author and enquire on when, if all at, this addon will be updated. There is a support email address mentioned on the web page. https://addons.thunderbird.net/en-US/thunderbird/addon/owl-for-exchange/

TB has updated itself to 68.4.1 The Owl add on appears to be working fine with 68.4.1, but QB is not recognizing TB.

I plan to attempt a clean install of 68.4.1 on Monday.

To do a full clean install, can I simply uninstall the upgraded 68.4.1 and then install 68.4.1 from a fresh download? Should I reboot between uninstall and reinstalling?

- GMB

Owl claims it's compatible with TB 60 and higher - there's no mention of a maximum supported version, whereas ExQuilla, by the same authors, only claims to work with 60-68.

You could uninstall the current 68 first, but it's not necessary. Just run the full installer over the existing setup as suggested above and restart afterwards. Make sure you have only the 32-bit version installed.

I ran the full installer. Surprised that it worked, as I don't have Admin rights on the server. But said installation complete and asked if I wanted to open TB. I check no, then requested a reboot from our host.

After reboot I logged on, opened TB, then opened QB and tried to link them for sending forms. But Thunderbird did not show as an option.

So it appears that 68.4.1 32 bit is not compatible with Quickbooks, even on a new install.

Now I need to see if there is a way to prevent 60.9.1 from updating.

I see there is a McAfee Endpoint Security on our server. Could this be causing TB to update? There is also a Mozilla Maintenance Service that installed with TB - could this be the upgrading culprit?

- GMB

If TB is set to check for updates but ask to install, in Options/Advanced/Update, it won't update without your permission, although you may get notifications every day. But if there's some other app that 'manages' software updates, you might be updated without your consent. I'm not familiar with McAfee Endpoint Security, but McAfee products have long caused headaches for TB users. I realize you may not have control over the entire software environment, but I don't know if the McAfee on your system has any effect on TB updates.

Still struggling - TB keeps updating itself.

One one thing I noticed as I tried moving one of the profiles from the C: drive to D: drive (to save space on the limited C:Drive) is that most of the users have 2 profiles listed. One is *.default and the other is *.default-release.

Are the -release profiles specific to TB 68 and could they be triggering TB to upgrade?

If so what is the best solution to this?

- GMB

Trying to think of some ways to outsmart TB from updating.

Is it true you can have 2 different versions on TB installed on the same computer and accessing the same email database? If so, could I leave TB 68.4.1 on the C: drive and then install 60.9.1 on the D: drive?

Or uninstall TB 68.4.1 from the C: drive and install 60.9.1 on the D: Drive? If McAfee is triggering the updates, perhaps it might ignore programs on the D: drive?

Would 60.9.0 or some earlier version (assuming I could get it) be less prone to updating?

Still not sure what is causing the updates. I asked a tech from our server if McAfee would trigger updates in other software and he said "no". But he did not seem to have a firm grasp on how the server worked - other techs I spoke to previously seemed to be much more knowledgeable.

- GMB

From Help/Troubleshooting, about:profiles, you can delete a profile if it is not used and has no important data. A profile ending in default-release would have been created during a botched upgrade to 68. If you have only one version of TB installed, 32 or 64 bit, I don't think the spurious upgrades are related to the -release profile. But there have been so many issues with this update, that I couldn't rule it out.

You can have multiple versions installed on the same computer, e.g. I have the release and beta versions, but you have to be careful with managing the profiles that each version uses. Before 68, you could run the same profile with release and beta versions, although not the best practice, but now it's more complex. In my case, the presence of two versions doesn't cause any unwanted updates.

I understand there's a way to apply group policies to control TB 68 updates, but it's not an area I'm familiar with.

Here I have checked NOT to install updates.

But then when I go to Help - About, it says that I am on the release upgrade channel and to restart to update.

Why does About say it will update?

- GMB

Not sure about what it may update to, but try modifying the following first:

• Exit Thunderbird.

• In search type: Run
• Select the 'Run.app'

• Type: regedit
• click on OK

If asked to continue say yes.

Locate:

• HKEY_LOCAL_MACHINE\Software\Policies\Mozilla
• Right click on 'Mozilla' and select 'New' > 'Key'
• Call it 'Thunderbird'

You will get the path HKEY_LOCAL_MACHINE\Software\Policies\Mozilla\Thunderbird.

• Right click on 'Thunderbird' and select 'New' > 'DWORD (32bit) Value'
• It will appear in the right pane - name it : DisableAppUpdate
• Double click on 'DisableAppUpdate' to open a small window so you can edit the DWORD value.

Note: Even if you are running 64-bit Windows you must still create a 32-bit DWORD value.

• Set its value to 1.
• Click on OK

Start Thunderbird