Up to version 1703 inclusive, the method described here worked well, but now it is impossible to enable the inactive mail client this way - because of its absence in the OS. In the most recent cumulative update of Windows 10 at the time of writing - 'Fall Creators Update', version 1709 - Microsoft has finally done what the fans of good old Outlook Express and its subsequent reincarnation Windows Mail were so afraid of: they uprooted it from the file system and Windows registry. As a result, you are now reading the second series of the saga. Geeks found missing keys in the registry, and MAPI returned to work. The most common function of MAPI is to attach files or folders via the context menu Send to - Mail recipient of the File Manager, as well as from external programs - for example, MS Office utilities.Īs I hoped, the collective intelligence overcame this problem. Being brief and shallow, one can define MAPI as the interface which allows you to manage the mail client from the external environment. But this state was not completely working, since the MAPI (Messaging Application Programming Interface) functionality for WinMail has not been restored.

In the previous post, it was described how to return Windows Mail to its working state after updating Win10 to version 1709, in which Microsoft removed it from the system. Implementation of Windows Mail into Windows 10 version 1709. Implementation of Windows Mail into Windows 10 version 1709 Enabling Windows Mail in post-Vista Microsoft OSs :: CONTENTĮnabling Windows Mail in Windows 7 - retrospective review three years later

Autoit outlook read receipt