User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.119 Safari/537.36

Steps to reproduce:

Tried to send file as attachment in email using the "send as email attachment" button in Nitro PDF Reader and Adober Acrobat Reader DC and Adobe Acrobat 8.1. Also right-clicked on file and selected "send to: mail recipient". Using in Windows 7 Professional.

Actual results:

The first couple of times a new dialogue box came up asking if it was okay that another program wanted to use Thunderbird (to attach the file, I presume). I said yes, and then nothing happened. The third time I tried, I ticked the box to not ask every time. So that doesn't even come up now. Nothing, no-go, nada happening. Except frustration.

Expected results:

Thunderbird should have opened a window with a new email to write with the file already attached.

Jorg, possible regression from Bug 393302 or bug 494239 (correction: bug 594239, not 494239) here I think.

I can confirm that send to mail recipient does not work in 60.5.2 here. I get a dialog asking to size the image I try and send and then nothing. Under 50.5.0 (not a mistake I missed 5.1) I had the same result followed by a silent disappearance of Thunderbird from the task list. Using the 64Bit version.

When sending a file the following is shown in the error console

NS_ERROR_NOT_AVAILABLE: Cannot call openModalWindow on a hidden window nsPrompter.js:340

I don't have access to bug 494239. Yes, bug 393302 and its friends bug 1521007 and bug 594239 were included in TB 60.5.2 after some time in TB 65 beta 3 and 4 without negative feedback.

Have to tried a reboot after upgrading? We need to know the bit-ness of your Windows (32/64 bit) and the bit-ness of your TB (32/64 bit). BTW, we had similar reports for in bug 1524762, see attachment 9042611 [details], but we thought that was related to the MAPISendMailW implementation which we did not ship in TB 60.5.2 and also withdrew from TB 66 beta 2. BTW, bug 1524762 has links to some videos that show that the functionality is working, and it also works for me on Windows 10 64bit with TB 60.5.2 64bit. But that doesn't help the reporter.

Inventing bug...494239 Not sure where I made that number up from but I think just a typo of 594239. I don't have access to 494239 either.

I can confirm I have Thunderbird 64 60.5.2 installed on Windows 10 64bit. Installed it to test from the FTP releases using the full installer as an automated update had not occurred. The install performed an automated restart of windows. Previous version was 60.5.0. 60.5.0 simply disappeared from the windows task list when I used send to mail recipient (image file only tested).

My results with the 64 bit version are

1 I am asked for a scaling of the image I have elected to send
2. Nothing. Except the error console warning. So I assume it has some relevance.

A later test using send to > mail recipient with Thunderbird closed waited, and then launched Thunderbird daily 65 after asking if I wanted to allow my profile to be used to send mail. A check on my mail client in windows shows nothing daily related.

The version starting is Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:65.0) Gecko/20100101 Thunderbird/65.0a1 (2018-11-21) (64bit)I assume that was the last daily build I installed.

If I send an image file I see a size request and nothing. If I select an RDF file I get the daily launch and then nothing.

After three failures Thunderbird just disappeared from the task manager

TB disappearing from the task manager is simply a crash.

It's worrying that TB 65 Daily is started. That's an indication that something is screwed on the machine. This is all very brittle. TB 60.5.2 must be the last mail app installed and it must be Windows' default.

Hmm, doesn't appear to be working on my laptop where I've just installed 60.5.2. It was fine on my desktop. Sigh.

Now I also got the "Either there is no default mail client or the current mail client cannot fulfill the messaging request. Please run Microsoft Outlook and set it as the default mail client." message :-(

The difference between the desktop and the laptop is that the laptop as Outlook installed (pre-installed by Dell). When I uninstalled TB, Outlook fired up with messages containing the files I tried to send before using TB with "Send to > Mail recipient". So those requests got queued somewhere. Mike, I can offer you a TeamViewer session on this laptop if you want to check it out.

Neither uninstalling, restarting, re-installing TB fixed anything. Oh boy.

Oh, I checked all the registry entries, so
HKEY_CURRENT_USER\Software\Classes\mailto\DefaultIcon
HKEY_CURRENT_USER\Software\Classes\mailto\shell\open\command
HKEY_CURRENT_USER\Software\Classes\Thunderbird.Url.mailto\DefaultIcon
HKEY_CURRENT_USER\Software\Classes\Thunderbird.Url.mailto\shell\open\command
HKEY_CURRENT_USER\Software\Classes\ThunderbirdEML\DefaultIcon
HKEY_CURRENT_USER\Software\Classes\ThunderbirdEML\shell\open\command

as well as:
HKEY_LOCAL_MACHINE\SOFTWARE\Clients\Mail\Mozilla Thunderbird
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID{29F458BE-8866-11D5-A3DD-00B0D0F3BAA7}\LocalServer32

and they all seemed to be OK.

Hey, checked the download page this morning and it said that the MAPI was fixed, so I downloaded again, installed and hey, it works again! Thanks to all who helped with the fix! Much appreciated! Is there somewhere I'm supposed to mark fixed or is that already taken care of since it says fixed on the download page? This is the first time I've submitted a bug.

~Konce

Thanks for letting us know. It still doesn't work for me, so we'll keep this bug open for further investigation.

I've the same problem, "Send to email recipient" stopped working both from desktop and external applications after upgrade to 60.5.2

OK, now on another desktop machine (which doesn't have MS Office/Outlook installed). Installed TB 60.5.2. "Send to > Mail recipient" works, sending from LibreOffice works. It's all good here. However, in the other room I have that laptop where nothing works. Go figure! :-(

I tracked down my daily load.... it came from HKEY_LOCAL_MACHINE\Software\Classes\mailto\shell\open\command Having fixed that though it still does not work.

Mystery, see comment #12. Do you have Office/Outlook installed?

Yes there is a copy of Outlook installed. Have just spend 2 hours trawling register and win.ini entries. No luck so far, but it looks like there might be another twist to this tale

https://support.mozilla.org/en-US/questions/1251573
and
https://support.mozilla.org/en-US/questions/1251581

I thought that Thunderbird never actually send MAPI mail with out a manual intervention though to click send.

I confirm comment 2, today we have lots of our users that report a similar problem after automatic upgrade from 60.5.1 to 60.5.2. In the error console we can see the message "NS_ERROR_NOT_AVAILABLE: Cannot call openModalWindow on a hidden window nsPrompter.js:340"

Well on my computer (win 10 64bit), the bug appear in thunderbird 60.5.2 32bit, i juste installed thunderbird 64bit from http://ftp.mozilla.org/pub/thunderbird/releases/60.5.2/win64/fr/ and now everything seems working fine. So i guess there is a regression concerning 32bit / 64bit.

(In reply to Guillaume .J from comment #18)

Well on my computer (win 10 64bit), the bug appear in thunderbird 60.5.2 32bit, i juste installed thunderbird 64bit from http://ftp.mozilla.org/pub/thunderbird/releases/60.5.2/win64/fr/ and now everything seems working fine. So i guess there is a regression concerning 32bit / 64bit.

damn, it appears that it fix the right clic sent to ... but still doesn't fix a mapi call from a third part application. ¯_(ツ)_/¯

I can confirm it. I have Thunderbird 32-bit 60.5.2 installed on Windows 7 64bit, send messages from any program not work.
After I downgraded Thunderbird 32-bit version 60.5.1 messages began to be sent.
Further I tried run automatic or manual update (download from official site) to actual verssion 60.5.2 send messages from any program not work.

UPD: A clean install helped fix the error(In reply to dmitry from comment #20)

I can confirm it. I have Thunderbird 32-bit 60.5.2 installed on Windows 7 64bit, send messages from any program not work.
After I downgraded Thunderbird 32-bit version 60.5.1 messages began to be sent.
Further I tried run automatic or manual update (download from official site) to actual verssion 60.5.2 send messages from any program not work.

I can also confirm that installing 60.5.2 fresh over 60.5.2 itself, the problem seems to be fixed.
I made a note of all registry changes during the installation and it seems some traces of 60.5.1 were left behing during the autoupgrade (especially in the uninstall). It also seems that the registry sub-entries are changed from "Mozilla Thunderbird" to just "Thunderbird". I'm also missing some plugins (QuickFolders).

The changed registry entries are here: https://gist.github.com/rvk01/b9a7426360a20d6c91c98cee2f72e36e

(In reply to rvk from comment #22)

I'm also missing some plugins (QuickFolders).

Correction. The plugin seems to be ok.

I can also confirm, it's works with (re)installation of the version 60.5.2. QuickFolders runs also on my installation.

I "repaired" my "sick" laptop by uninstalling the Dell-pre-installed version of M$ Office. Result: "Sent to > Mail recipient" started working immediately, sending from LibreOffice also works.

Maybe there is an issue with the automated upgrade.

Uninstalled the 60.5.2 I got from autoupdate,
installed 60.5.2 64bit from msi, reboot, twice,
Explorer - Send To - Mail recipient works

Beware: use file with plain ascii name for checking,
files with diacritics etc. will fail now

Right, I filed bug 1531724 for that. Strangely enough that worked before when the characters in the filename were on the code page of the Windows system locale. Somehow that must have gotten broken. It still works if you switch the system locale to UTF-8 which is a beta feature in Window 10 1803.

I think this here is the same as bug 1531328

Because, if the calling app sends a recpient, mail was sent, if no recipient was set, nothing did happen (i.e. no composer window shown)

(In reply to Matt from comment #2)

When sending a file the following is shown in the error console

NS_ERROR_NOT_AVAILABLE: Cannot call openModalWindow on a hidden window nsPrompter.js:340

I have the same problem and exactly the same message in the error console.

Windows 10, right clicking on a file on the desktop, choosing option "Send to > Email".
If Thunderbird is running and minimized then nothing happens (besides the message in dev tools console).
If Thunderbird is not running then the main windows shows up, but the expected dialog for composing a new email with the selected file attached does not.

OK, I think we're coming to then end of the tunnel here.

As various reports confirm, installing 60.5.2 from one of
https://www.thunderbird.net/en-US/thunderbird/all/
http://ftp.mozilla.org/pub/thunderbird/releases/60.5.2/win32/
http://ftp.mozilla.org/pub/thunderbird/releases/60.5.2/win64/
fixes the problem.

Sadly there is an additional problem that files with non-ASCII names can't be sent, see bug 1531724. There are two workarounds for that:

1. On Windows 10, set the system code page (under system locale) to UTF-8, which is a beta feature.
   or
2. Reset HKLM\SOFTWARE\Clients\Mail\Mozilla Thunderbird - SupportUTF8 to 0.

We will ship a fix for bug 1531724, but I don't think we will action this bug here.

Looks like we have a few complaints here.

After following the steps from comment #30, does anyone still have the problem that the MAPI_DIALOG flag is ignored?

Sending mail from LibreOffice and the via Windows "Send to > Mail recipient" brings up the Thunderbird compose window for me.

I've tried both the official 32bit version and the unofficial 64bit version on Windows 10 64bit and they both work as expected.

If you don't want to mess with the Windows registry, paste this into a .reg file and merge it:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Clients\Mail\Mozilla Thunderbird]
"SupportUTF8"=dword:00000000

I downloaded and installed the 64 bit TB from the link in comment 30. Everything is again working as expected.

Thanks So Much!!

OK, meanwhile I found the cause of the problem. I installed 60.5.1 and let it update to 60.5.2. Result: The relevant MAPI DLLs were not updated :-( - I filed bug 1531869 for that.

Will there be a release 60.5.3 to fix this? Or do we have to redownload and install 60.5.2?

As detailed in comment #59, the autoupdate is broken. Since I just discovered that, we have no ETA. Your best bet is to follow comment #30 which is a sure fix.

followed Comment #30...still doesn't work.
Send to mail recipient still opens thunderbird, but not attachment or new email opens.

Gary

(In reply to Jorg K (GMT+1) from comment #61)

As detailed in comment #59, the autoupdate is broken. Since I just discovered that, we have no ETA. Your best bet is to follow comment #30 which is a sure fix.

this fix didn't do anything for me...restarted after...same issue.

Downloaded from directory listed..reinstalled and now working.
Thanks for help.

Downloaded per instructions in Comment #30, 32-bt is working again. Fixed.

Can anyone confirm the Comment 30 fix does work on Windows 7 Pro 64bits while installing 32bits version of TB?

Once the .dll issue would be fixed, would the ASCII/UTF8 issue affect such platform?

Is there anyone else this has actually worked for? I have gone through the procedure several times today with out success. Before I start recommending the workaround to affected users I would like to think there was a high likely hood of success.

Yes, Matt, many people have confirmed this to be working, for example see comment #58, comment #64 and comment #65. Also comments in the 32(!) duplicated to all of which I am subscribed (sadly) and on SUMO. I have updated the release notes accordingly: https://www.thunderbird.net/en-US/thunderbird/60.5.2/releasenotes/

My analysis clearly showed that the automatic update failed to update the relevant DLLs.

That said, you setup might have a different problem. If you have Office installed, it might not work for you. My laptop only started working after uninstalling Office. Somehow the Office installation had corrupted the facility to send e-mail via MAPI. On Windows 10 I saw a bazillion fixmapi and mmgaserver processes eventually exhausting the machine's memory and bringing it to a halt. But that experience is not representative.

Downloading and installing from comment 30 worked for me on multiple Win7 computers. Thank you.

(In reply to Richard Leger from comment #66)

Can anyone confirm the Comment 30 fix does work on Windows 7 Pro 64bits while installing 32bits version of TB?

Once the .dll issue would be fixed, would the ASCII/UTF8 issue affect such platform?

I'm running 64-bit Win 7 Pro and 32-bit Thunderbird. I downloaded and installed from comment 30 and the problem is fixed.

(In reply to Matt from comment #74)

Is there anyone else this has actually worked for? I have gone through the procedure several times today with out success. Before I start recommending the workaround to affected users I would like to think there was a high likely hood of success.

Can you confirm:

• Windows version: 7,8,10? 32bits or 64bits? Version?
• Office version (if installed): 2010,2013,2016,2019? 32bits or 64bits?
• Which installer (full link address path) you tried?
• Have you rebooted after uninstall?
• Have you rebooted after install?
• Is Thunderbird still set to be the default email client on the machine?

(In reply to qkeon from comment #77)

(In reply to Richard Leger from comment #66)

Can anyone confirm the Comment 30 fix does work on Windows 7 Pro 64bits while installing 32bits version of TB?

Once the .dll issue would be fixed, would the ASCII/UTF8 issue affect such platform?

I'm running 64-bit Win 7 Pro and 32-bit Thunderbird. I downloaded and installed from comment 30 and the problem is fixed.

Would you be able to confirm the link address (full path) to the installer you used?

(In reply to Richard Leger from comment #79)

(In reply to qkeon from comment #77)

(In reply to Richard Leger from comment #66)

Can anyone confirm the Comment 30 fix does work on Windows 7 Pro 64bits while installing 32bits version of TB?

Once the .dll issue would be fixed, would the ASCII/UTF8 issue affect such platform?

I'm running 64-bit Win 7 Pro and 32-bit Thunderbird. I downloaded and installed from comment 30 and the problem is fixed.

Would you be able to confirm the link address (full path) to the installer you used?

Windows 7 Pro 64-bit
Downloaded Thunderbird 32-bit installer from http://ftp.mozilla.org/pub/thunderbird/releases/60.5.2/win32/en-US/
Installed update - opened TB - Closed TB - Opened again and tried attachment from send to, mail recipient - worked.
All PCs have Office 2010 Standard 64-bit.
One PC required a reboot after installation per message on screen.
TB is the default mail client.

I can confirm that fix from comment 30 works on 32 bit TB on 64 bit Windows 7 and 10. With or without Office 365 installed.

I installed 60.5.2 32 bits from /pub/thunderbird/releases/60.5.2/win32/es-AR/ and the problem is "almost" solved.
Now if I send a mail from another application using MAPI with MAPI_DIALOG flag, the compose window appears. But, it's not modal. The call returns immediately.

I have Windows 10 Pro.

Sure, that always been the case. Are you confusing "modal" (blocking) with synchronous/asynchronous? As I understand the COM interface between the external application and Thunderbird is synchronous, see related bug 1527450 comment #9 (quote):

The COM calls are synchronous: they end when e.g. CMapiImp::SendMailW returns (the return value is passed back to the caller).

However, TB's CMapiImp::SendMailW returns when the compose windows has been launched. Whether the user in the end sends the e-mail or not, is a different question.

All we did in 60.5.2 was to rearrange the COM interface between MAPI DLL and TB process a bit. No behaviour change at all. What caught us was the fact that the installer didn't install the new MAPI DLLs, so the old DLLs were talking to the new interface in TB with detrimental effects. See bug 1531869 for details.

(In reply to EGMM from comment #84)

Bug 865689 gives a hint that it was already working like that at least for the last 6 years. TB has never honored MAPI_DIALOG_MODELESS; and its handling of MAPI_DIALOG was changed to modeless rather long ago. Ergo: comment 84 mentions another bug.

You are right. What I am trying to say is explained in bug 865689.

'Write' window should have opened as a modal dialog; execution of calling routine should wait for closing of modal dialog. MapiSendMail function with MAPI_DIALOG flag should not return a result until user closes 'Write' window by either sending mail (Result=SUCCESS_SUCCESS) or closing without sending (Result=MAPI_E_USER_ABORT).

When I send a mail from another application, usually the compose window appears, I edit the text (or not), send the mail and then I see again the original application. As this used to work fine, I didn´t notice the application didn´t expect the mail to be sent. Now, that version 60.5.2 have this new bug (resolved with reinstallation) I noticed the bug 865689. I think it would be a good idea to solve it, so Thunderbird would worked as other e-mail clients.

(In reply to EGMM from comment #87)

When I send a mail from another application, usually the compose window appears, I edit the text (or not), send the mail and then I see again the original application. As this used to work fine, I didn´t notice the application didn´t expect the mail to be sent. Now, that version 60.5.2 have this new bug (resolved with reinstallation) I noticed the bug 865689. I think it would be a good idea to solve it, so Thunderbird would worked as other e-mail clients.

i agree, we dot have this issue with brother control center, after scanning a document "to email" it usually open the thunderbird compose windows and after 60.5.2 (even full install) this does not work.

Any accented characters at play? Vous êtes français ;-) Did you read comment #30 fully? Most/all people are OK after reinstalling.

Now I have seen, that wehn I will attach a link ("Sent to > Mail recipient"), the email opens. If I try the same link again ("Sent to > Mail recipient"), no email appears. I have no (more) problem with files.

(In reply to Christian Moling from comment #91)

Now I have seen, that wehn I will attach a link ("Sent to > Mail recipient"), the email opens. If I try the same link again ("Sent to > Mail recipient"), no email appears. I have no (more) problem with files.

I can attach every link only for one time.

Is there any hope for a fix via update ?
I have tens of PCs to deal with (in several small companies) + I'm in France so I would have to apply the 2 steps manual fix ...

We'll ship a fix within a week hopefully.

It works properly now after reinstalling 60.5.2 (comment #30)
Thank you for all comments and tha,ks to you Jorg K (comment #90) ... and yes I'm french ;-)

After Reinstall Works in 90%. System Windows 7 X64 gives pop up that i need to change defaults mail program in system settings.. but when i change it to default its do nothing.. and i have the same pop up always i use other programs mail function.

I reinstall thw 60.5.2 32x in win 10 laptop hp omen but the problem remain. The "Sent to > Mail recipient" open the TB but no email with attachment appears.

Yes, because you're in Greece and the file had Greek characters in the name and you didn't apply the registry fix from comment #30?

Thanks, i Reset the HKLM\SOFTWARE\Clients\Mail\Mozilla Thunderbird - SupportUTF8 to 0 and it seems to be ok now.

Notice to all the people affected by this bug: TB 60.5.3 is on the way. If you want to try it:
https://archive.mozilla.org/pub/thunderbird/candidates/60.5.3-candidates/build1/win32/
https://archive.mozilla.org/pub/thunderbird/candidates/60.5.3-candidates/build1/win64/ (unofficial 64bit).

May be better to wait for auto-update to 60.5.3 and see if it fix the issue(s), no? Just a suggestion, as it is an issue linked to the auto-update of TB, not really with the installer itself...

I can confirm this problem also happens with POP3 since updating to TB 60.5.2 I just filed Bug #1532715 about it, after posting a comment in Bug #1339554 but unfortunately before seeing THIS bug report. (Jorg, I see you just caught that...)

FYI: TB 65.0.2 on Windows 7 Pro 32-bit - two DELL PC machines.

FYI: TB 60.5.2 on Windows 7 Pro 32-bit - two DELL PC machines.

Reloaded Version 60.5.3 from this site https://archive.mozilla.org/pub/thunderbird/candidates/60.5.3-candidates/build1/win64/ and it now works perfectly sending direct to email from an HP Color Laserjet

Yes, I can confirm, it works perfect again. (Win7 64bit, TB 60.5.3) delivered via automatic update within TB.
Many thanks to everyone!

After downgrade TB from 60.5.2 -> 60.5.1 and then upgrade it to 60.5.3 from https://www.thunderbird.net/en-US/thunderbird/all/ [downloaded full installer, rebooted before and after upgrade, and after changed into registry] we (in our company) cannot send mails via windows 'send to -> mail recipient' when the attached filename contains our (Polish) national characters - "ś, ć, ę, ł, ó, ż, ź", Windows [Win7 Pro 64bit pl-PL; TB is 32bit] is set for Windows 1250 Code Page. When i rename the file, then i can send it as usual. Changing registry value 'SupportUTF8' to 0 is not working in my environment. Now even downgrade to TB 60.5.1 is not resolving this. Somebody has an some idea ? I have ~100 PC- affected with this :(

(In reply to Robert from comment #109)

That's strange.
Could you - just in case - check both HKEY_LOCAL_MACHINE\SOFTWARE\Clients\Mail\Mozilla Thunderbird and HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Clients\Mail\Mozilla Thunderbird for SupportUTF8 value? (note the WOW6432Node in the second registry path.)

Actually, no. With the Western European code page windows-1252 I can send with äöü, and I'm sure Mike can send Cyrillic, right?

I'm very well aware of your Polish national characters, since I fixed bug 1505315.

Actually, comment #111 was an answer to comment #109:

Somebody has some idea? ... Actually, no. Sadly.

(In reply to Mike Kaganski from comment #110)

Thank you.

I totally forgot about existing of Wow6432Node tree. There was 'SupportUTF8' set to 1.
I'm made changes only for this one registry tree HKEY_LOCAL_MACHINE\SOFTWARE\Clients\Mail\Mozilla Thunderbird.

Maybe (comment #30) should be updated for people like me, who forgot about Wow6432Node :)

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Clients\Mail\Mozilla Thunderbird]
"SupportUTF8"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Clients\Mail\Mozilla Thunderbird]
"SupportUTF8"=dword:00000000

(In reply to Robert from comment #113)

Hmm... actually I hoped that my advice would not work.
As it works, I now don't understand why would installer for 32-bit TB 60.5.3 not set the registry value itself under Wow6432Node, where 32-bit applications are expected to store their configuration? (I'd rather expect that 64-bit registry hive be not updated...) Or do we not ship the registry fix with 60.5.3?

(In reply to Robert from comment #109)

After downgrade TB from 60.5.2 -> 60.5.1 and then upgrade it to 60.5.3 from https://www.thunderbird.net/en-US/thunderbird/all/ [downloaded full installer, rebooted before and after upgrade, and after changed into registry] we (in our company) cannot send mails via windows 'send to -> mail recipient' when the attached filename contains our (Polish) national characters - "ś, ć, ę, ł, ó, ż, ź", Windows [Win7 Pro 64bit pl-PL; TB is 32bit] is set for Windows 1250 Code Page. When i rename the file, then i can send it as usual. Changing registry value 'SupportUTF8' to 0 is not working in my environment. Now even downgrade to TB 60.5.1 is not resolving this. Somebody has an some idea ? I have ~100 PC- affected with this :(

I would suggest the following...

• Uninstall
• Reboot
• Re-install 60.5.3 from http://ftp.mozilla.org/pub/thunderbird/releases/60.5.3/win64/ (
• Reboot
• Try again

Eventually there is a Polish language version of TB available, not that it should make any difference in theory :-)

We shipped this as you had suggested in bug 1531724 comment #2:
https://hg.mozilla.org/releases/comm-esr60/rev/8626d03f14b3cc7b43a656f174c18cb984db3e88

Or http://ftp.mozilla.org/pub/thunderbird/releases/60.5.3/win32 if you wish to install 32bits version, obviously...

Source: https://www.advancedinstaller.com/user-guide/registry-wow6432-node.html

"...

Wow6432Node Registry Key

The Wow6432Node registry entry indicates that you are running a 64-bit Windows version.

The operating system uses this key to display a separate view of HKEY_LOCAL_MACHINE\SOFTWARE for 32-bit applications that run on 64-bit Windows versions. When a 32-bit application writes or reads a value under the HKEY_LOCAL_MACHINE\SOFTWARE\<company>\<product> subkey, the application reads from the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\<company>\<product> subkey.

A registry reflector copies certain values between the 32-bit and 64-bit registry views (mainly for COM registration) and resolves any conflicts using a "last-writer-wins" approach.

..."

See also https://docs.microsoft.com/en-us/windows/desktop/sysinfo/32-bit-and-64-bit-application-data-in-the-registry

(In reply to Jorg K (GMT+1) from comment #116)

Let me think aloud.
TB prior to 60.5.2 didn't set that registry value (neither in 64-bit hive, nor in 32-bit; neither 64-bit TB, nor 32-bit one).
TB 60.5.2 wrote that value - to which hive? That must be clear to someone familiar with NSIS and TB installation technology; but anyway, that must be built into the NSUS installer executable (I suppose), and so the change in bug 1521007, possibly combined with installer architecture, would fully define the registry places affected.
TB 60.5.3 has a change that is different values written into the same registry places, in the same NSIS script sites. So logically, that must ensure, that running a TB 60.5.3 installer of the same architecture over TB 60.5.2 installation should in theory write precisely to same registry places? and - I guess - for 32-bit installer, at least 32-bit registry should have been affected?

I am confused.

I use this one: https://download.mozilla.org/?product=thunderbird-60.5.3-SSL&os=win&lang=pl.
witch is resolve to: https://download-installer.cdn.mozilla.net/pub/thunderbird/releases/60.5.3/win32/pl/Thunderbird%20Setup%2060.5.3.exe

Now send to works as expected :)

(In reply to Mike Kaganski from comment #119)

When i'\ try to figure it out, I'm delete whole registry path for 64-bit apps (HKLM\Software\Cilent\Mozilla.... Uninstall TB 60.5.2 completely, re-install 60.5.0, 60.5.1, 60.5.2, 60.5.3 and 66.0b2 (for tests), and this registry path was rebuild automatically after install of TB was finished. I was thinking i made changes into property registry path.

Well, looks like
https://hg.mozilla.org/releases/comm-esr60/rev/8626d03f14b3cc7b43a656f174c18cb984db3e88#l1.13
does not run for an automatic upgrade install :-( - Sigh.

(In reply to Robert from comment #121)

That was strange for me is, when TB starts is always ask for "default email client in Windows", when i agree with this (after enter admin credentials), restart TB, and it ask again and again for that.

Looks like TB 60.5.3 is now available on the public release channel. I updated both of my machines just now using the standard HELP/ABOUT update buttons in TB and I can confirm that the SEND-TO process works again as it should (that is, as it used to do) -- at least for POP3 on Windows 7 32-bit. Thanks, guys.

BTW, I think the resolution should be changed to "FIXED" (no longer "WFM"), since this seems to be an official public fix and not a workaround hack.

Well, the fix happened in two other bugs: Bug 1531724 and bug 1531869, and the former is still awaiting a follow-up to fix the issue discussed in comment #109 and below.

(In reply to Jorg K (GMT+1) from comment #122)

Well, looks like
https://hg.mozilla.org/releases/comm-esr60/rev/8626d03f14b3cc7b43a656f174c18cb984db3e88#l1.13
does not run for an automatic upgrade install :-( - Sigh.

That was wrong. Mozilla's Windows installer specialist looked at it and he pointed out what could have happened for the 1 to remain in Wow6432Node, see bug 1531724 comment #23 and below. Unless we have further insight into what happened at the Polish site from comment #109, we won't be able to action this any further.

May not be directly linked to this bug but worth mentioning I think...

Source: Bug 1531190 Comment 7 (which has been marked as duplicate of this bug)

"...

Created attachment 9047671 [details]
AnotehrAppicationisAttemptingToSendMail.png

I can confirm as well that on Windows 10 Pro 64bits [Version 10.0.17134.590] with TB 66.0b2 (32-bit) the mail recipient feature does not work as expected and simply crash the application.

While TB up and running, opened File Explorer, right click a .pdf file, selected Sent to > Mail Recipient, the attached warning appeared ("Another application is attempting to send mail using your user profile..."), clicked OK, TB application is Not Responding for a while and then crash (close by itself) without any crash reports generated.

..."

(In reply to Jorg K (GMT+1) from comment #126)

What i've done:

Then TB 60.5.2 was published, it was downloaded Polish, 32bit version of TB from https://www.thunderbird.net/en-US/thunderbird/all/

All my machines have 60.5.1 32bit pl-PL installed on Win7/8.1/10 all is Pro and x64;

deploy this update to my users silently via psexec - e.g. "ThunderbirdInstaller.exe -ms";

On some computers TB was opened [not closed by they users] while upgrade process was started from fullinstaller.

When needed, client computers was rebooted.

next day morning i have meny phone calls, user cannot send via send to, or from Acrobat Reader DC, etc.

I start to search internet for bug info.

O one computer making downgrade to 60.5.1, and it work again.
Manually i upgrade using full installer to 60.5.2. Send to - works.

On other machines i'll try TB 66.0.b2 - send to - work.

I only test one example file, without non-ASCII chars.

Because TB 66.0b2 is not support for Enigmail, i downgraded it to 60.5.2.

Few user give me a notice that cannot send only few files - files contains with non-ASCII characters in filename.

I found registry info (comment #30) that in theory resolve my problem.
i'm add this via psexec.exe:
"reg add "HKLM\SOFTWARE\Clients\Mail\Mozilla Thunderbird" /v "SupportUTF8" /t REG_DWORD /d 0 /f"

but this not resolve my problems. I totally forgot about creating Wow6432Node... I use for it 64bit cmd.exe ["%windir%\Sysnative\cmd.exe"] and 64bit of psexec.exe.

I was think, i make downgrade to 60.5.1 to all users via psexec. But this is not work to...

Then 60.5.3 was published, i deploy TB 60.5.3 in the same way. This is not resolve my issue to.

Then on test machines, i uninstall completely TB, rebooted, delet from program files Thunderbird folder and contains files, install fresh copy, but with no luck - files with non-ASCII chars in filename wont to send as before.

Do it few times, no luck. I even install for tests an old TB 52.9.1 (32bit), but with the same results - files with non-ASCII chars in filename wont to send.

That's is work for me is to deploy via psexec to all users:
"reg add "HKLM\SOFTWARE\Wow6432Node\Clients\Mail\Mozilla Thunderbird" /v "SupportUTF8" /t REG_DWORD /d 0 /f"

I see, but only once - when i'll try to send mail a littile window - that is "other program wants to send mail by using your profile".

(In reply to Robert from comment #129)

When i try to install a fresh copy of TB, i delete whole registry tree (64bit) HKLM\SOFTWARE\Clients\Mail\Mozilla Thunderbird

When i install 32bit of TB, this tree was rebuild automatically - then i was thinking that i manipulate on right registry tree.

(In reply to Robert from comment #130)

Downgrade to 60.5.1 stops working when add registry value of "SupportUTF8" to 64bit tree and upgrade in place from full installer e.g. 60.5.2 -> 60.5.2. But i don't known why.

(In reply to StanoS from comment #107)

Yes, I can confirm, it works perfect again. (Win7 64bit, TB 60.5.3) delivered via automatic update within TB.
Many thanks to everyone!

It isn't true at all... It doesn't work for filenames with special characters... For example names with á,č,ť,ž etc...

(In reply to StanoS from comment #132)

You can try this from (comment #30) but add Wow6432Node to if you use 32bit of TB on 64bit of Windows.

copy and past this to notepad, save as *.reg file, double clik on it and add to registry.

after that, you should be able to send files with names contains non-ASCII characters.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Clients\Mail\Mozilla Thunderbird]
"SupportUTF8"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Clients\Mail\Mozilla Thunderbird]
"SupportUTF8"=dword:00000000

or you use command line as well (start it as administrator)

32bit TB on 64bit Windows:
reg add "HKLM\SOFTWARE\Wow6432Node\Clients\Mail\Mozilla Thunderbird" /v "SupportUTF8" /t REG_DWORD /d 0 /f

Win & TB is 32bit / Win & TB is 64bit.
reg add "HKLM\SOFTWARE\Clients\Mail\Mozilla Thunderbird" /v "SupportUTF8" /t REG_DWORD /d 0 /f

OK, let's clarify a few things here:

The registry setting of "SupportUTF8 1" will break non-ASCII names for any version of Thunderbird.

The installer of 60.5.3 or the automatic update to 60.5.3 will reset the registry settings in HKLM\SOFTWARE\Wow6432Node\Clients\Mail\Mozilla Thunderbird and HKLM\SOFTWARE\Clients\Mail\Mozilla Thunderbird if deployed in the "regular" fashion. If you deploy the installer in a "non-standard" way, it might not be able to write to the registry, see bug 1531724 comment #25.

psexec I'm running with args "-s -e -i" - this is force to using a built-in System account on remote machine to do the job. I think Installer have full access (with write) to this location %ProgramFiles%, %ProgramFiles(x86)%, %ProgramW6432% and HKLM\Software registry hive.
Tomorrow I'll try to do some tests on VM with clean Win7 on them and install/update TB via psexec with and without -s arg.

Further to my Comment 124:

Looks like TB 60.5.3 is now available on the public release channel. I updated both of my machines just now using the standard HELP/ABOUT update buttons in TB and I can confirm that the SEND-TO process works again as it should (that is, as it used to do) -- at least for POP3 on Windows 7 32-bit.

Given the discussions since then, I tested just now on a file copied to a non-ASCII-named file -- the original works as usual, the non-ASCII name fails to trigger anything (SEND-TO does nothing apparent).

So I can confirm only that, after the update to 60.5.3 on the Public Release channel, the SEND-TO process works again as it should (that is, as it used to do) ONLY FOR "NORMAL" ASCII FILE NAMES for POP3 on Windows 7 32-bit.

Which non-ASCII file names work and which ones don't depends on the Windows code page (ACP) used by your system. For example, using "Western European", that is windows-1252, I can send äöü, etc. but not any Polish characters as show in comment #109. For that to work, the machine needs to use windows-1250. If you want to send any file name, including Greek, Hebrew, Thai, Cyrillic, Japanese, Korean, Chinese, etc. you need to set your system code page to UTF-8 which is a beta feature on Windows 10.

If you claim something doesn't work, state your code page and the file name you used.

It could be that for it to work with non-ascii characters, the MAPISendMailW function (UTF8) (In reply to Richard Leger from comment #127)

Source: Bug 1531190 Comment 7 (which has been marked as duplicate of this bug)

"...

Created attachment 9047671 [details]
AnotehrAppicationisAttemptingToSendMail.png

I can confirm as well that on Windows 10 Pro 64bits [Version 10.0.17134.590] with TB 66.0b2 (32-bit) the mail recipient feature does not work as expected and simply crash the application.

While TB up and running, opened File Explorer, right click a .pdf file, selected Sent to > Mail Recipient, the attached warning appeared ("Another application is attempting to send mail using your user profile..."), clicked OK, TB application is Not Responding for a while and then crash (close by itself) without any crash reports generated.

..."

This issue was raised in a separate bug 1524762 already...

(In reply to Jorg K (GMT+1) from comment #137)

Which non-ASCII file names work and which ones don't depends on the Windows code page (ACP) used by your system. For example, using "Western European", that is windows-1252, I can send äöü, etc. but not any Polish characters as show in comment #109. For that to work, the machine needs to use windows-1250. If you want to send any file name, including Greek, Hebrew, Thai, Cyrillic, Japanese, Korean, Chinese, etc. you need to set your system code page to UTF-8 which is a beta feature on Windows 10.

If you claim something doesn't work, state your code page and the file name you used.

Jork, would the MAPISendMailW implementation (not yet shipped) you mentioned in Comment 3, help overcome this issue, or would it still require UTF8 system code page to actually be used once shipped?

MAPISendMailW was in TB 66 beta 1, I withdrew it in TB 66 beta 2 due to crashes (bug 1527450), but it's again being shipped with TB 66 beta 3 now that we corrected the installer which may have been the course of the crashes.

Once shipped, TB will offer both MAPISendMail and MAPISendMailW and it's up to the external application to chose which one to use. We know from testing that "Send to > Mail recipient" uses MAPISendMailW, as does LibreOffice. MS Word 16 uses MAPISendMail unconditionally and also transmits UTF-8 data via that interface, hence bug 1521007 where we started advertising UFT-8 support with detrimental effects and had to withdraw it again.

So yes, once MAPISendMailW has been shipped and doesn't crash, it will solve all "Send to > Mail recipient" issues.

(In reply to Robert from comment #135)

I'm made some test on Win7 Pro x86/x64.

silently upgrade TB 32bit (using installer exec with -ms args) from version 60.5.0, 60.5.1 and 60.5.2 to latest 60.5.3 do changes in both registry hive HKLM\Software\Client... and HKLM\Software\Wow6432Node\ SupportUTF8 is set too 0.

Test is from command line opened as administrator and via PSEXEC with -s arg (using system account to do the job) and without -s arguments (using selected account from admin's group).

But i see strange thing.

installer always exit with exit code 0 (suppose the operation is completed successfully), add/remove programs list is updated - shows TB in current version (60.5.3), install/update date is changed - i see today date), but some users when starting form desktop, taskbar, menu start, quick launch icon is prompted for admins credentials. when i decline this, and go to help / about TB - i see current version number and active button "restart to update". But i don't known why. I see this until i enter the credentials of admin account.

Second thing that i see now is when i try to send mails with attached files with names accented with Polish characters, i cant send them.

When i downgrade to 60.5.1, i can send them, but i see regression like in: bug 1505315 - when i'll try to attach a file named "ąśćżźłóńĄŻŹĆŚĘŃÓŁ.txt" i get: email title: "WysyĹ‚anie wiadomoĹ›ci e-mail: ąśćżźłóńĄŻŹĆŚÄĹĂ“Ĺ.txt" and the body contains "Wiadomość jest gotowa do wysĹ‚ania wraz z nastÄ™pujÄ…cymi zaĹ‚Ä…cznikami (plikami lub Ĺ‚Ä…czami):
ąśćżźłóńĄŻŹĆŚÄĹĂ“Ĺ.txt", i should get: "Wysyłanie wiadomości e-mail: ąśćżźłóńĄŻŹĆŚĘŃÓŁ.txt" and body: "Wiadomość jest gotowa do wysłania wraz z następującymi załącznikami (plikami lub łączami): ąśćżźłóńĄŻŹĆŚĘŃÓŁ.txt"

What i do wrong ? or what i f***** on my machines when i'll try to do tests ?!?

My system code page is Windows 1250 (Central Europe)

both registry hive have SupportUTF8 set to 0, and TB i 60.5.3, i restart whole machines used for tests. I have no idea why previously the Wow6432Node hive tree was not updated to 0.

I'll try tonight to completely remove TB from test machines and install a fresh copy, and see whats happens.

Best regards to all, thanks for your time and attention.

TB 60.5.2/60.5.3, Windows 7 with latest updates.
Send To -> Mail recipient not working for filenames with Cyrillic characters.
Setting HKLM\SOFTWARE\Clients\Mail\Mozilla Thunderbird\SupportUTF8 to 0 or 1 has no effect.
But interesting thing, deleting DWORD HKLM\SOFTWARE\Clients\Mail\Mozilla Thunderbird\SupportUTF8 completely fixes the problem.

For now, pushing GPO to apply at once:
reg delete "HKLM\SOFTWARE\Clients\Mail\Mozilla Thunderbird" /v "SupportUTF8" /f

(In reply to Robert from comment #142)

Test on: Oracle VBox 6.x, Win 7 x64 pl-PL (from official Dell DVD).

Clean Install of Win7, download TB 60.5.1 up to 60.6.0, send to is not working - TB opens, but no windows new message is shown.

I'll test both x86 and x64 version of Thunderbird.

I see in comment #145, alxdlv delete SupportUTF8, i try this and i see whats happen :)

(In reply to alxdlv from comment #145)

For now, pushing GPO to apply at once:
reg delete "HKLM\SOFTWARE\Clients\Mail\Mozilla Thunderbird" /v "SupportUTF8" /f

That's right. Test on 60.6.0 (32 bit). In my environment deleting this key (and if exist in Wow6432Node, i delete it too) and the new message window apper again. Thank you :)

I'm going to make an GPO rule for that :) This is exactly what i need.

So "no key" and "value is 0" are different, how strange is that??

(In reply to Jorg K (GMT+1) from comment #148)

well - that's really unexpected; still I suppose that it'd be better if TB erased that key instead of nullifying it as I did. I did that because of lack of knowledge in the installer technology used, sorry for that; I knew that we should not let it stay 1 - which is correct anyway. If you know how to (and actually do) change that to removal, it would be great.

In reply to Jorg's Comment 148:

In generic programming/logic terms, you can explicitly set a value to zero ("value is zero") by reading a zero, but if the record is missing ("no key"), the code could set any default -- not limited to zero -- and do this deliberately or otherwise.

Deliberately set default if the record is missing...
IF RECORD : Read value
IF NOT RECORD : Nothing was read, so set value = <whatever>
Value is as read OR as deliberately set (which could be deliberately but explicitly non-zero)

Inadvertently set default to incorrect value (bug?)...
Set value = <whatever>
<perhaps do other stuff that doesn't change value>
IF RECORD : Read value
IF NOT RECORD : <do nothing>
Value is as read OR as previously set (which could be arbitrary)

For either case, <whatever> could be zero, or one, or anything (valid or otherwise).

For the inadvertent case, in a bug scenario, value could be arbitrary, which makes the bug harder to find -- the value might accidentally be correct this time and wrong the next, leading to intermittent working and not-working situations.

(In reply to Mike Kaganski from comment #149)

well - that's really unexpected; still I suppose that it'd be better if TB erased
that key instead of nullifying it as I did. I did that because of lack of knowledge
in the installer technology used, sorry for that; I knew that we should not let it stay 1 -
which is correct anyway. If you know how to (and actually do) change that to removal, it would be great.

Filed bug 1545362 for it.

After aabout month of removing this value from registry (witch resolve issue in my environment on more then 200 PC's) i have 2 machines witch Windows 7 is installed from genuine (factory) image/partition recovery from HP/Lenovo/Dell/FSC, etc. - witch we select the OS language at start of installation - removing this value dont resolve this issue. Send to -> mail recipient does nothing, TB opens, but no window with new message do not appear. On one machine (only for test) i reinstall Win7 but from genuine Microsoft DVD with pl-PL and it works.
I'm wondering whats can be on the second one. What i can check...

We're working on bug 1545362 and the registry value will be removed when TB 60.7 ships in May 2019.

I've acknowledge of this problem today when one of our customers had mapi not working with the latest version of Thunderbird. As usual, customer don't have much time for testing so I've solved downgrading to v. 60.5.0 and disabling auto-update.

I have this problem. Thinking that the solution posted above - the one that involves downloading from a certain location - would work even if I downloaded from the Thunderbird website a non-US version of Thunderbird, I did that (for version 68.1.1 x64) and reinstalled. There's still no sendTo - indeed no Thunderbird SendTo file seems to have been created.

Also: some posts refer to the number of some other post(s). Yet, none of the posts that I see are numbered.
Further: often when I log into this site using Github credentials, I lose the page to which I wished to contribute and end up at a search page; and, if I manage to navigate to the URL I need, then, most often, I get asked to log into again - and so on in an infinite loop. That will keep the bug count down! (Still, perhaps it has something to do with my Firefox security extensions.)

Reply to Comment #156...

most often, I get asked to log into again

The login has a "remember me" check box -- should keep you logged in until you log out or reboot. But the login might not persist if you are in running in Privacy mode.

There's still no sendTo - indeed no Thunderbird SendTo file seems to have been created.

Did you catch Comments in the 130's to 140's, where filenames containing strange (certain punctuation and extended) ASCII chars don't seem to trigger a SEND-TO? (Someone please correct me if I'm wrong, but I don't think this part was fully resolved.)

I think that 'remember by email' option applies only if one logs in using Bugzilla credentials, not Github ones. I am managing to type this pretty much only because I've pinned the tab in Firefox.

where filenames containing strange (certain punctuation and extended) ASCII chars don't seem to trigger a SEND-TO?

No, that's not the problem. For, I've tried the sendTo action on files lacking such characters. The problem is that for some reason the computer keeps trying to use Outlook to send the mail. See this screenshot: https://i.postimg.cc/YqSdc12J/image.png

The problem occurs even though: I have Thunderbird set as the default e-mail program; Outlook is not installed; I looked at relevant registry entries and so far as I can tell they seemed correct; I tried reinstalling Thunderbird (as I said); I tried the Windows inbuilt program 'fixMapi' and rebooted.

PS: But I have now found the comment numbers on these the bugzilla pages.

Did you catch Comments in the 130's to 140's, where filenames containing strange (certain punctuation and extended)
ASCII chars don't seem to trigger a SEND-TO? (Someone please correct me if I'm wrong, but I don't think this part was fully resolved.)

I believe that if you have a filename using characters outside the system ANSI code page, then sending may not work without the new MAPISendMailW function which is available in TB 68. It should also work if you chose Unicode/UTF-8 for your system locale. We currently don't have any reports of ongoing malfunction.

@jorg K, @Dan Pernokis

As I said in comment 158: I am having problems with all filenames.

I looked for how to set Thunderbird as the default email program, and I didn't find a specific setting. But there is an implicit setting! Maybe this is what you set, or maybe not. (Perhaps it needs re-setting -- pls read to the end :)

Go to Windows CONTROL PANEL and click on "Default Programs". Scroll down to the very bottom and you should find a special section called "Protocols". Look for the MAILTO protocol (what we called "SendTo" above) and make sure it says Thunderbird. Click the line to change it, and select Thunderbird from the list that comes up, or navigate to Thunderbird.exe and select it that way.

Even if TB is set as the default, the command line spec might not be exactly correct internally. Good if you can verify that it is indeed pointing to the correct installation of TB. But if it's ambiguous in any way, or if you can't for-sure verify that it is correct, perhaps try changing it to something else (to force the issue), then change back it to TB.

IF this was the problem, then any non-special file names should now work. And if you have a current TB, then most if not all filenames should work as well.

@Dan

Yes, I'd navigated the schizoid Windows settings and found that option. It is set to Thunderbird already. But, yes, toggling it seems a good idea. But I've just tried that and no dice.

Then just for good measure, right-click your main TB icon and note the path to the program. Make sure this is the TB you navigated to -- just in case you have a second (old and/or disfunctional) installation somewhere and that's what's trying to execute. I trust that you know this stuff, but I've made the same mistake in another situation, so I just want you to be sure...

Thanks. I think that possibly the remnants of an old x86 installation might be the problem - but I could find no references, in files or the registry, to any old installation. I did find some mailto settings in the registry that pointed to Outlook (which is installed in a pretty much uninstallable way on my computer). I changed those to refer to Tbird. I fold some old TBird profiles and removed them. I tried a fix that involves recreating the 'sendto' item - see here: https://social.technet.microsoft.com/Forums/office/en-US/f6672aab-7376-4669-8af6-3dd60f3b0ebd/ceflauncherexe-not-found?forum=officeitpro

None of this changed the sendTo behaviour (!).

I'm experiencing the same problem and took the same steps @signupemail took. That did not fix the problem. Since upgrading from the 32-bit to the 64 bit version of TB 68.2.2 I the send to mail recipient feature of Windows Explorer is not working. Nothing happens.

I have downloaded the 64-bit installer again and installed it and that didn't fix the problem. I am on Windows 10 1903.

Any other things to try?

Thanks,
Bill

I figured out the problem. It only happens with 64-bit Thunderbird. I uninstalled the 64-bit and installed the 32-bit and send to mail recipient worked fine. I then uninstalled the 32-bit version and installed the 64-bit and it broke again. So I uninstalled the 64-bit version and installed the 32-bit again and it worked fine. I will stick with the 32-bit version.

Bill

Bill, by doing the steps of @signupemail, does that include my Comment #161 (above) regarding default programs? I recently removed (uninstalled) an ancient version of OPERA (browser), and when I did so, a large number of default file & protocol associations disappeared and had to be reset manually -- including the MAILTO: association to TB. Don't know why, it just happened.

I'm going to suggest you look at this setting again anyway. It could be that TB/32 and TB/64 look "different" somehow -- such that the old/current setting always looks for TB/32, and the TB/64 is never seen. So... when you've got TB/64 re-installed and MAILTO: doesn't work again, then try setting (or re-setting, or toggling) the association -- see if it works then. In other words, we need to associate the MAILTO: protocol with the NEW TB/64 installation. Let's not presume the TB/64 installer makes the appropriate changes -- even though it should, it might not actually do so. (Any time an installation tries to preserve an existing profile, certain things might get missed. Removing TB/32 may clear the MAILTO: setting, and installing TB/64 might not set it properly, whereas re-installing TB/32 might set it properly regardless, as you've seen.)

Be aware that I wrote my comment for Windows 7. The procedures might vary slightly on Window 10 -- just do the equivalent.

Dan,

Thanks for the reply. Yes I did look at the default program settings and they pointed to TB already. I changed them to something else and changed them back, but the problem persisted.

I don't see any difference in the was TB/32 and TB/64 look. Since I uninstalled one and installed the other each time, I had only one TB installed at a time. For this reason there was only one TB entry in the list to select so that is what I selected. There is no option that I can see to "browse" to the program and select it. The only options I have are 4 programs and the option to look in the Microsoft App store for more apps.

Thanks,
Bill

To reset TB as default app you could also try this alternative way...

• in Windows settings, set default Mail app to Outlook or Mail...
• then open TB, and set it as default email client from within the app... Tools > Options > Advanced > General > "Always check to see if Thunderbird is the default mail client on startup" is checked > Check Now

About your environment:

• Windows version?
• which version of TB (for both x32 and x64)?
• what is the source of installer you use for both?
• where are you "send to" from? App?
• does filname being sent contains non ANSI characters like in Polish or German for example?
• in both case, x32 and x64 do you see the following regidstry keys?

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Clients\Mail\Mozilla Thunderbird]
"SupportUTF8"

[HKEY_LOCAL_MACHINE\SOFTWARE\Clients\Mail\Mozilla Thunderbird]
"SupportUTF8"

• If yes what value they have for each key and both cases...
• If no, please confirm which one is missing in both cases...

Richard, thanks for the reply. Here are the answers to your questions.

To reset TB as default app you could also try this alternative way...

 - I had already tried this.  It doesn't help.

About your environment:

Windows version?

    -  10.0.1836 Build 18362

which version of TB (for both x32 and x64)?

    -  68.2.2

what is the source of installer you use for both?

    - https://www.thunderbird.net/en-US/thunderbird/all/
    
where are you "send to" from? App?

    - File Explorer, select a file, right click, select Send To, select Mail Recipient

does filname being sent contains non ANSI characters like in Polish or German for example?

    - No

in both case, x32 and x64 do you see the following regidstry keys?

    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Clients\Mail\Mozilla Thunderbird]
    "SupportUTF8"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Clients\Mail\Mozilla Thunderbird] 
    "SupportUTF8"

        - Neither registry entry exists for either version of TB.  Even with both versions installed at the same time they do not exist.  In fact their    appear to be no changes between having just 32-bit, just 64-bit, or both installed at the same time.

Sorry for the formatting of my reply. I am not a regular here and don't know what I did. I just cut and pasted your questions and interspersed my replies.

Bill

(In reply to Richard Leger from comment #169)

To reset TB as default app you could also try this alternative way...

• in Windows settings, set default Mail app to Outlook or Mail...
• then open TB, and set it as default email client from within the app... Tools > Options > Advanced > General > "Always check to see if Thunderbird is the default mail client on startup" is checked > Check Now

Have you tried the above?

Result in both cases?

I have tried both of these and neither helped. Send to mail recipient didn't work with the 64-bit version of TB.

A bit more information. I tried another test. I kept both the 32-bit and the 64-bit versions of TB installed. With the 64-bit version set as the default mail app, send to mail recipient didn't work. With the 32-bit version set as the default mail app, send to mail recipient worked just fine.

Bill

I have managed to reproduce signupemail and wrhenshaw99 issue on Windows 10 1903 (OS Build 18362.476) and I believe issue may be two fold:

• Bug in Windows itself
• and possibly bug in Thunderbird 64bits (or uninstall of 32bits?)

Here are my testings and findings...

• After installing TB 60.9.1 (https://archive.mozilla.org/pub/thunderbird/releases/60.9.1/win32/en-GB/Thunderbird%20Setup%2060.9.1.exe) on a machine with Outlook 2010 already installed, I can set TB as default email client and use SendTo feature from Explorer. I skip integration at installation (unchecked options) and set integration when prompted during TB user profile creation.

• After upgrading manually to TB 68.2.2 (by new install over as auto update would not tirgger upgrade - https://archive.mozilla.org/pub/thunderbird/releases/68.2.2/win32/en-GB/Thunderbird%20Setup%2068.2.2.exe) on the same machine, I can still use TB as default email client and use SendTo feature from Explorer.

The problem is that I had hard time to switch back to Outlook for use with the SendTo feature of File Explorer.

• switching back default app to Outlook in Windows settings did NOT work
• switchinb back via default app > set defaults by app > Outlook > Manage > MailTo set to Outlook, did NOT work either

The only way I could switch back to Outlook as default app for SentTo was to:

• Default Apps > Reset (in Window Settings)
• And resret Outlook as default in Defaul Apps panel
  ==> then I could use again Outlook for SendTo feature...
  ==> the same way I can set TB (32bits) as default app for SendTo feature aka revert back the change...

But that only works with TB 32bits... with TB 64bits NOTHING works... you cannot change settings...

As I decided to uninstall TB 64bits, I noticed that it requested to reboot which I thought was strange... and when when I checked the content of C:\Program Files\Mozilla Thunderbird, three files seemed to remain behind... but I dont know if they are from 32bits or 64bits version of TB... see attached...

If that can be of any help...

Sounds like you have hit upon at least some of the problem I'm having although it is just a bit different for me.

Just a couple notes in my case.

I do not have Outlook. I use only TB.

When I install TB 32-bit I put it in \Program Files (X86). When I install TB 64 bit I put it in \Program Files. This allows me to have both installed at the same time (although I don't typically have both installed).

When I uninstalled TB 64-bit it did not require me to re-boot.

Thanks,
Bill

Further to my previous comment, after machine was rebooted, the three TB files that had remained behind previously have now been deleted.

There is no default app set for Email in Windows Settings, just the + icon appears to add one...

I therefore re-installed TB 68.2.2 (64bits) via the exact same installer as used previously, and make sure to keep install default options as per attached... which incude integration (set TB as default email client).

After install has completed, I can see TB as default Email app in Windows settings and I am now again able to use the File Explorer > Send To option to trigger new message in Thunderbird with the file attached. It works with all filenames (including those with non-ANSI characters).

I haven't checked but it may also be worth to check that when 32bits version is uninstalled and machine is rebooted (prior installing 64bits) and make sure all TB files are properly removed from the correct program files folder.

As the issue is not directly related to this bug and the related registry keys, I would suggest to create a separate regression bug perhaps for further investigation by the TB dev team...

Indepdently from the Windows Settings possible "bug" that prevent switching Send To settings once set... on version Winfdows 10 1903, there might still be some sort of bug in TB or its installer/uninstaller either 32bits or 64bits... which may not help the matter :-)

When doing uninstall/re-install of TB (either to jump version, architecture, or test), it is advisable to reboot machine after uninstall priore re-install... to make sure all TB files are properly deleted/removed as some of them may still be temporarily locked/in use by the system somehow...

Hope that help sort the on going issue...

(In reply to wrhenshaw99 from comment #175)

Sounds like you have hit upon at least some of the problem I'm having although it is just a bit different for me.

I do not have Outlook. I use only TB.

My point was just to confirm Windows bug that you cannot switch the MailTo feature between two mail app via Windows Settings... between TB 32bits and TB 64bits in your case...

When I install TB 32-bit I put it in \Program Files (X86). When I install TB 64 bit I put it in \Program Files. This allows me to have both installed at the same time (although I don't typically have both installed).

When I uninstalled TB 64-bit it did not require me to re-boot.

I would suggest you to:

• uninstall TB 32bits
• reboot
• uninstall TB 64bits
• reboot
• re-install TB 68.2.2 64bits - making sure to keep option Use Thunderbird as my default email client set/checked during install...

In theory that should fix your issue...

Just now I only had TB 32 bit installed.
I installed TB 64 bit and rebooted.
Now I had both TB 32 bit and TB 64 bit installed.

With TB 32 bit set as the default mail program, send to mail recipient worked fine.
With TB 32 bit set as the default mail program, send to mail recipient did not work.

I uninstalled TB 32 bit and rebooted.
I uninstalled TB 64 bit and rebooted.
I reinstalled TB 64 bit and kept the option to Use Thunderbird as my default email client (which I always leave set every time I install TB).

At this point the windows settings showed TB as the default mail client and TB showed itself as the default mail client, but send to mail recipient did not work.

I uninstalled TB 64 bit and rebooted.
I installed TB 32 bit and rebooted.

At this point send to mail client worked just fine.

The problem definitely seems to be in TB 64 bit.

Thanks,
Bill

Sorry, I meant to say in line 5 that with TB 64 bit installed, send to mail recipient did not work.

Bill

Will this bug be addressed? Do I need to move this to a new bug report?

Bill

I'm here because a few minutes ago I face (again... in these decades it's recurrent) the problem of MAPI not working on a newly installed Win10 with TB 68.2.2 64 bit. After a bunch of tests without results I found out that the 32 bit is working and the 64 is not. Basically simply installing the 32 bit over the 64 solves the problem.

PS: OT: installing the 64 bit over the 32 bit, reuses the same "(x86)" path instead of "Program files"

(In reply to Rik from comment #181)

PS: OT: installing the 64 bit over the 32 bit, reuses the same "(x86)" path instead of "Program files"

Oh, I just had an idea: what if this is not an OT, but the real problem? E.g., I didn't follow the default (which was to install into x86), and changed to 64-bit Program Files path when upgraded to x64; and I didn't suffer from the "not working" problem - maybe because of that? Some windows folder redirection in play, which prevents TB's 64-bit DLLs from working?

Hi Mike, maybe it's another problem on top of the other one, because in first instance, I've faced the problem on a newly installed 64 bit and the path was correctly without (x86).

This is what I saw:

1. Installing 64 bit in a new Windows 10 (never installed TB before), installs in the right path but MAPI doesn't work
2. Installing the 32 bit, install in the right path and it works properly
3. Updating any kind of 32 bit to 64, the 64 bit installs in the x86 path and doesn't work

In your case, could be that the 64 bit works as a sum of 2 things:

1. The 32 bit installed the proper MAPI reference
2. The 64 bit, forced to install in the proper path, doesn't break something that the 32 bit did and thanks to that the 64 bit works as well.

I always uninstall whatever version is already installed before installing it again. In other words, each install is a clean install.

It doesn't matter for me whether I install the 64-bit version in Program Files or Program Files (x86), the send to mail recipient option still does not work.

It works just fine for the 32-bit version.

Bill

Mike, Rik,

Have you tried this?

• uninstall TB 32bits
• reboot
• uninstall TB 64bits
• reboot
• re-install TB 68.2.2 64bits - making sure to keep option Use Thunderbird as my default email client set/checked during install...

Cheers,

I know you didn't address your message to me, but I have tried this and it still didn't work.

Bill

This seems to be turning into a self-help session, even though there are - what? dozens of bugs marked as duplicates as this one?

It seems like that. I sure wish someone that is part of Thunderbird support would acknowledge the problem and take ownership of fixing it. What good is it to have a 64-bit version of Thunderbird if it doesn't work properly for many people. Having to revert to the 32-bit version should really not be necessary.

Bill

As this bug has been resolved and recent comments are related to what seems to be a new MAPI issue not directly related to this bug, I have created a new Bug 1601879 (clone of this one) to raise recent issue/concerns to dev team so they can investigate... separately fom here.

If you are affected by issue reported since Comment 165, please follow up and comment in Bug 1601879 from now on.

In this tutorial that is based for the 64 bits users but could be adapted for 32 bits users, I will be attempting to fix your MAPI / Send to -> Mail recipient and send to from external program issue that you may experience in Windows 7, 8, 8.1 or 10 when you use windows with no other mail client than Thunderbird, and that you may (or not) have installed both x86 and x64 version. This is a blunt straight through tutorial, some steps may or not be necessary, but the goal is to fix it all if possible with one procedure, so read the tutorial completly to understand what we start with, what we end with, etc.

While following the procedure, DO NOT DELETE OR MOVE files located in your profile, these are your settings, emails, etc. Usually located at %appdata%\Thunderbird . Optionally, you could make a copy of that directory to have a backup of your profile before we start.

Now let's start by cleaning up the bird cage:

1. Download the lastest version of Thunderbird x86 and x64 version.
2. Install Thunderbird 64 bits, with all default, then Uninstall it, using the control panel.
3. Reboot
4. Install Thunderbird 32 bits, with all default, then Uninstall it, using the control panel.
5. Reboot.
6. Check out *C:\Program Files* and **C:\Program Files (x86)**, and make sure there is no more Thunderbird directory.
7. Check out the following registry Key: Computer\HKEY_CURRENT_USER\Software\Thunderbird\Launcher it will display
   different path to check out for remaining thunderbird files, if it was installed by example, on a local profile instead than inside Program Files directories.
8. Now we will modify C:\WINDOWS\WIN.INI by running an Notepad as Administrator and then by opening that file. Once the file is open in a notepad running as administrator, add the following section at the end of the file:

[Mail]
MAPI=1
CMC=1
CMCDLLNAME=mapi.dll
CMCDLLNAME32=mapi32.dll
MAPIX=1
MAPIXVER=1.0.0.1
OLEMessaging=1

7. Reboot.
8. Install Windows Mail and Calendar from the Microsoft Store.
9. Set Windows Mail as default Email client in Setting -> Applications -> "Default apps"
10. Reboot.
11. Install the Thunderbird x64 version with all defaults in *C:\Program Files*
12. Reboot.
13. Let modify your registry, let create a .reg file with the following content:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows Messaging Subsystem]
"MAPI"="1"
"MAPIX"="1"
"MAPIXVER"="1.0.0.1"
"OLEMessaging"="1"
"CMCDLLNAME"="Mapi.dll"
"CMCDLLNAME32"="Mapi32.dll"
"CMC"="1"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Messaging Subsystem]
"MAPI"="1"
"MAPIX"="1"
"MAPIXVER"="1.0.0.1"
"OLEMessaging"="1"
"CMCDLLNAME"="Mapi.dll"
"CMCDLLNAME32"="Mapi32.dll"
"CMC"="1"

[HKEY_CURRENT_USER\Software\Clients\Mail]
@="Mozilla Thunderbird"

[HKEY_LOCAL_MACHINE\SOFTWARE\Clients\Mail\Mozilla Thunderbird]
@="Mozilla Thunderbird"
"DLLPath"="C:\Program Files\Mozilla Thunderbird\mozMapi32_InUse.dll"

[HKEY_LOCAL_MACHINE\SOFTWARE\Clients\Mail\Mozilla Thunderbird\Capabilities]
"ApplicationDescription"="Thunderbird is a full-featured email application. Thunderbird supports IMAP and POP mail protocols, as well as HTML mail formatting. Built-in junk mail controls, RSS capabilities, powerful quick search, spell check as you type, global inbox, and advanced message filtering round out Thunderbird's modern feature set."
"ApplicationIcon"="C:\Program Files\Mozilla Thunderbird\thunderbird.exe,0"
"ApplicationName"="Thunderbird"

[HKEY_LOCAL_MACHINE\SOFTWARE\Clients\Mail\Mozilla Thunderbird\Capabilities\FileAssociations]
".eml"="ThunderbirdEML"
".wdseml"="ThunderbirdEML"

[HKEY_LOCAL_MACHINE\SOFTWARE\Clients\Mail\Mozilla Thunderbird\Capabilities\StartMenu]
"Mail"="Mozilla Thunderbird"

[HKEY_LOCAL_MACHINE\SOFTWARE\Clients\Mail\Mozilla Thunderbird\Capabilities\URLAssociations]
"mailto"="Thunderbird.Url.mailto"

[HKEY_LOCAL_MACHINE\SOFTWARE\Clients\Mail\Mozilla Thunderbird\DefaultIcon]
@="C:\Program Files\Mozilla Thunderbird\thunderbird.exe,0"

[HKEY_LOCAL_MACHINE\SOFTWARE\Clients\Mail\Mozilla Thunderbird\InstallInfo]
"HideIconsCommand"=""C:\Program Files\Mozilla Thunderbird\uninstall\helper.exe" /HideShortcuts"
"ShowIconsCommand"=""C:\Program Files\Mozilla Thunderbird\uninstall\helper.exe" /ShowShortcuts"
"ReinstallCommand"=""C:\Program Files\Mozilla Thunderbird\uninstall\helper.exe" /SetAsDefaultAppGlobal"
"IconsVisible"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Clients\Mail\Mozilla Thunderbird\Protocols]

[HKEY_LOCAL_MACHINE\SOFTWARE\Clients\Mail\Mozilla Thunderbird\Protocols\mailto]
@="Thunderbird URL"
"FriendlyTypeName"="Thunderbird URL"
"URL Protocol"=""
"EditFlags"=dword:00000002

[HKEY_LOCAL_MACHINE\SOFTWARE\Clients\Mail\Mozilla Thunderbird\Protocols\mailto\DefaultIcon]
@="C:\Program Files\Mozilla Thunderbird\thunderbird.exe,0"

[HKEY_LOCAL_MACHINE\SOFTWARE\Clients\Mail\Mozilla Thunderbird\Protocols\mailto\shell]

[HKEY_LOCAL_MACHINE\SOFTWARE\Clients\Mail\Mozilla Thunderbird\Protocols\mailto\shell\open]

[HKEY_LOCAL_MACHINE\SOFTWARE\Clients\Mail\Mozilla Thunderbird\Protocols\mailto\shell\open\command]
@=""C:\Program Files\Mozilla Thunderbird\thunderbird.exe" -osint -compose "%1""

[HKEY_LOCAL_MACHINE\SOFTWARE\Clients\Mail\Mozilla Thunderbird\shell]

[HKEY_LOCAL_MACHINE\SOFTWARE\Clients\Mail\Mozilla Thunderbird\shell\open]

[HKEY_LOCAL_MACHINE\SOFTWARE\Clients\Mail\Mozilla Thunderbird\shell\open\command]
@=""C:\Program Files\Mozilla Thunderbird\thunderbird.exe" -mail"

[HKEY_LOCAL_MACHINE\SOFTWARE\Clients\Mail\Mozilla Thunderbird\shell\properties]
@="Thunderbird &Options"

[HKEY_LOCAL_MACHINE\SOFTWARE\Clients\Mail\Mozilla Thunderbird\shell\properties\command]
@=""C:\Program Files\Mozilla Thunderbird\thunderbird.exe" -options"

[HKEY_LOCAL_MACHINE\SOFTWARE\Clients\Mail\Mozilla Thunderbird\shell\safemode]
@="Thunderbird &Safe Mode"

[HKEY_LOCAL_MACHINE\SOFTWARE\Clients\Mail\Mozilla Thunderbird\shell\safemode\command]
@=""C:\Program Files\Mozilla Thunderbird\thunderbird.exe" -safe-mode"

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Clients\Mail\Mozilla Thunderbird]
@="Mozilla Thunderbird"
"DLLPath"="C:\Program Files\Mozilla Thunderbird\mozMapi32_InUse.dll"

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Clients\Mail\Mozilla Thunderbird\Capabilities]
"ApplicationDescription"="Thunderbird is a full-featured email application. Thunderbird supports IMAP and POP mail protocols, as well as HTML mail formatting. Built-in junk mail controls, RSS capabilities, powerful quick search, spell check as you type, global inbox, and advanced message filtering round out Thunderbird's modern feature set."
"ApplicationIcon"="C:\Program Files\Mozilla Thunderbird\thunderbird.exe,0"
"ApplicationName"="Thunderbird"

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Clients\Mail\Mozilla Thunderbird\Capabilities\FileAssociations]
".eml"="ThunderbirdEML"
".wdseml"="ThunderbirdEML"

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Clients\Mail\Mozilla Thunderbird\Capabilities\StartMenu]
"Mail"="Mozilla Thunderbird"

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Clients\Mail\Mozilla Thunderbird\Capabilities\URLAssociations]
"mailto"="Thunderbird.Url.mailto"

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Clients\Mail\Mozilla Thunderbird\DefaultIcon]
@="C:\Program Files\Mozilla Thunderbird\thunderbird.exe,0"

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Clients\Mail\Mozilla Thunderbird\InstallInfo]
"HideIconsCommand"=""C:\Program Files\Mozilla Thunderbird\uninstall\helper.exe" /HideShortcuts"
"ShowIconsCommand"=""C:\Program Files\Mozilla Thunderbird\uninstall\helper.exe" /ShowShortcuts"
"ReinstallCommand"=""C:\Program Files\Mozilla Thunderbird\uninstall\helper.exe" /SetAsDefaultAppGlobal"
"IconsVisible"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Clients\Mail\Mozilla Thunderbird\Protocols]

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Clients\Mail\Mozilla Thunderbird\Protocols\mailto]
@="Thunderbird URL"
"FriendlyTypeName"="Thunderbird URL"
"URL Protocol"=""
"EditFlags"=dword:00000002

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Clients\Mail\Mozilla Thunderbird\Protocols\mailto\DefaultIcon]
@="C:\Program Files\Mozilla Thunderbird\thunderbird.exe,0"

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Clients\Mail\Mozilla Thunderbird\Protocols\mailto\shell]

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Clients\Mail\Mozilla Thunderbird\Protocols\mailto\shell\open]

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Clients\Mail\Mozilla Thunderbird\Protocols\mailto\shell\open\command]
@=""C:\Program Files\Mozilla Thunderbird\thunderbird.exe" -osint -compose "%1""

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Clients\Mail\Mozilla Thunderbird\shell]

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Clients\Mail\Mozilla Thunderbird\shell\open]

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Clients\Mail\Mozilla Thunderbird\shell\open\command]
@=""C:\Program Files\Mozilla Thunderbird\thunderbird.exe" -mail"

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Clients\Mail\Mozilla Thunderbird\shell\properties]
@="Thunderbird &Options"

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Clients\Mail\Mozilla Thunderbird\shell\properties\command]
@=""C:\Program Files\Mozilla Thunderbird\thunderbird.exe" -options"

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Clients\Mail\Mozilla Thunderbird\shell\safemode]
@="Thunderbird &Safe Mode"

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Clients\Mail\Mozilla Thunderbird\shell\safemode\command]
@=""C:\Program Files\Mozilla Thunderbird\thunderbird.exe" -safe-mode"

14. Execute the .reg file that you have just created and answer yes for the confirmation so that registry entries are added/updated
15. Reboot.
16. Go in "Default Apps" and under EMAIL we will set Thunderbird as the default Mail Client.
17. Go in "Set Default by App", find Thunderbird and apply all of it default.
18. Reboot.
19. Now setup a test account in Thunderbird, make sure that send and receive work fine.
20. Test to right click on a file in windows explorer and do Send to -> Mail recipient
21. It should also work in others program such as Adobe Acrobat Reader or Accounting applications by example.
22. You can uninstall Windows Mail and Calendar
23. Reboot and make sure everything still work.

Please note that it is possible that after all this is done, you may have to re-add your old profile, usually done by adding the options -P to your thunderbird shortcut on the desktop by example, so that it launch the profile manager before actually starting thunderbird, letting you create a new default profile, and pointing it to the right profile directory, that we had before we started all this, if that was the case.

If this helped you and saved lots of headaches, please share it to at least one other place or something so we can help others with this ... issue, and if you had to add something or do something else, that is not written here, please let me know. I have to say that I am a bit surprised than this problem is still there, 10 years down the road. We used to have this problem back at the beginning of Windows 7... We used to have this in various setup, either without Office/Outlook, or light/stripped version of windows and , It is really the type of problem that you feel like a ping pong ball between Microsoft and Mozilla because of SimpleMAPI and MAPI, etc.... while all you need, is an immediate help and getting things to works.

Best Regards,