Microsoft Outlook 2019 16 34 Sedan
-->
Office for Mac that comes with a Microsoft 365 subscription is updated on a regular basis to provide new features, security updates, and non-security updates. The following information is primarily intended for IT professionals who are deploying Office for Mac to the users in their organizations.
Note
Microsoft Outlook 2019 - en-us is frequently set up in the C: Program Files Microsoft Office folder, but this location can differ a lot depending on the user's choice when installing the application. The full command line for uninstalling Microsoft Outlook 2019 - en-us is C: Program Files Common Files Microsoft Shared ClickToRun. Microsoft Office 2019 Professional Plus is conceived to level up online collaboration on all the platforms and apps included in the pack: Excel 2019, Word 2019 and PowerPoint 2019. This enables you to co-author your document with your team member instantly and smoothly. نرم افزار Microsoft Outlook ابزاری است که از ایمیلهای شما به صورت آنلاین پشتیبانی میکند. نسخه 16.34: رفع باگ ها. نرم افزار Microsoft Outlook 2019 نسخه 16.35 برای مک قدیمی (نسخه جدیدتر موجود هست). نرم افزار Microsoft Outlook 2019 نسخه 16.29 برای مک قدیمی (نسخه جدیدتر موجود هست) نرم افزار Microsoft Outlook 2019 نسخه 15.40 برای مک قدیمی (نسخه جدیدتر موجود هست).
- Starting with Version 16.21, Microsoft Teams will be installed by default for new installations if you're using the Office suite install package. For more information, see Microsoft Teams installations on a Mac.
- For security reason, Microsoft has deprecated the use of SHA-1. Learn more
- Starting with the 16.17 release in September 2018, this information also applies to Office 2019 for Mac, which is a version of Office for Mac that’s available as a one-time purchase from a retail store or through a volume licensing agreement.
- The update history information for version 16.16 and earlier also applies to Office 2016 for Mac, which is also a version of Office for Mac that’s available as a one-time purchase. Older versions up to and including 16.16 can be activated with an Office 2016 for Mac volume license. You can’t activate version 16.17 or later with an Office 2016 for Mac volume license. For information about Office 2016 for Mac releases from September onward, see Release notes for Office 2016 for Mac
- For information about the features, security updates, and non-security updates that are included in a given release of Office for Mac, see Release notes for Office for Mac.
- If you want early access to new releases, join the Office Insider program.
Most current packages for Office for Mac
The following table lists the most current packages for the Office suite and for the individual applications. The Office suite includes all the individual applications, such as Word, PowerPoint, and Excel. All packages are 64-bit only. The build date is listed in parentheses, in a YYMMDD format, after the version number. The install package is used if you don't have the application already installed, while the update package is used to update an existing installation.
To view release notes, see Release notes.
October 13, 2020
Version 16.42 (20101102)
| Application | Download links | SHA-256 hash for install package |
|---|---|---|
| Office suite (with Teams) | Install package | 8AC425F0E31869B32C323F4349FB48E9B1C3A114B77EA68897D97C50D9B8BECB |
| Office suite (without Teams) | Install package | 5FA1084BD240BF10FAAF94D908492939807EAD8E014582DCB2ADE7ECC484276B |
| Word | Install package Update package | 21C54A78343B106A93FFD176130DEB9A6C9154F56EB58446FC27192D1E191995 |
| Excel | Install package Update package | 2235E4FE0741CE013777E2B6811AD9EFF738F9A724860FBA0DFD31976BF96E62 |
| PowerPoint | Install package Update package | EAF6B82C2042BD4D026779CEB4A58E0B92C8E320A9797C77CA3A588FD94B19EB |
| Outlook | Install package Update package | 566A1BD7AD446FCDD31156EBCA3FBD7F8F8BB2EFBCC8F3217CB55AA16A586420 |
| OneNote | Update package | Not applicable |
Release history for Office for Mac
The following table provides release history information and download links for Office for Mac. The table is ordered by release date, with the most recent release date listed first. The build date is listed in parentheses, in a YYMMDD format, after the version number. All releases after August 22, 2016 are 64-bit only. All releases prior to August 22, 2016 are 32-bit only.
Note
Download links are only provided for the most recent releases.
| Release date | Version | Install package | Update packages |
|---|---|---|---|
| October 13, 2020 | 16.42 (20101102) | Office suite (with Teams) Office suite (without Teams) | Word, Excel, PowerPoint, Outlook, OneNote |
| September 15, 2020 | 16.41 (20091302) | Office suite (with Teams) Office suite (without Teams) | Word, Excel, PowerPoint, Outlook, OneNote |
| August 11, 2020 | 16.40 (20081000) | Office suite (with Teams) Office suite (without Teams) | Word, Excel, PowerPoint, Outlook, OneNote |
| July 14, 2020 | 16.39 (20071300) | Office suite (with Teams) Office suite (without Teams) | Word, Excel, PowerPoint, Outlook, OneNote |
| June 16, 2020 | 16.38 (20061401) | Office suite (with Teams) Office suite (without Teams) | Word, Excel, PowerPoint, Outlook, OneNote |
| May 12, 2020 | 16.37 (20051002) | Office suite (with Teams) Office suite (without Teams) | Word, Excel, PowerPoint, Outlook, OneNote |
| April 21, 2020 | 16.36 (20041300) | Office suite (with Teams) Office suite (without Teams) | |
| April 14, 2020 | 16.36 (20041300) | Word, Excel, PowerPoint, Outlook, OneNote | |
| March 10, 2020 | 16.35 (20030802) | Office suite (with Teams) Office suite (without Teams) | Word, Excel, PowerPoint, Outlook, OneNote |
| February 11, 2020 | 16.34 (20020900) | Office suite (with Teams) Office suite (without Teams) | Word, Excel, PowerPoint, Outlook, OneNote |
| January 14, 2020 | 16.33 (20011301) | Office suite (with Teams) Office suite (without Teams) | Word, Excel, PowerPoint, Outlook, OneNote |
| December 10, 2019 | 16.32 (19120802) | Office suite (with Teams) Office suite (without Teams) | Word, Excel, PowerPoint, Outlook, OneNote |
| November 12, 2019 | 16.31 (19111002) | Office suite (with Teams) Office suite (without Teams) | Word, Excel, PowerPoint, Outlook, OneNote |
| October 15, 2019 | 16.30 (19101301) | Office suite (with Teams) Office suite (without Teams) | Word, Excel, PowerPoint, Outlook, OneNote |
| September 18, 2019 | 16.29.1 (19091700) | Word, Excel, PowerPoint | |
| September 10, 2019 | 16.29 (19090802) | Office suite (with Teams) Office suite (without Teams) | Word, Excel, PowerPoint, Outlook, OneNote |
| August 13, 2019 | 16.28 (19081202) | Office suite (with Teams) Office suite (without Teams) | Word, Excel, PowerPoint, Outlook, OneNote |
| July 16, 2019 | 16.27 (19071500) | Office suite (with Teams) Office suite (without Teams) | Word, Excel, PowerPoint, Outlook, OneNote |
| June 11, 2019 | 16.26 (19060901) | ||
| May 14, 2019 | 16.25 (19051201) | ||
| April 16, 2019 | 16.24 (19041401) | ||
| March 27, 2019 | 16.23.1 (19032603) | ||
| March 12, 2019 | 16.23.0 (19030902) | ||
| February 20, 2019 | 16.22 (19022000) | ||
| January 24, 2019 | 16.21 (19011700) | ||
| January 16, 2019 | 16.21 (19011500) | ||
| December 11, 2018 | 16.20 (18120801) | ||
| November 13, 2018 | 16.19 (18110915) | ||
| October 16, 2018 | 16.18 (18101400) | ||
| September 11, 2018 | 16.17 (18090901) | ||
| August 14, 2018 | 16.16 (18081201) | ||
| July 10, 2018 | 16.15 (18070902) | ||
| June 13, 2018 | 16.14.1 (18061302) | ||
| June 12, 2018 | 16.14.0 (18061000) | ||
| May 24, 2018 | 16.13.1 (18052304) | ||
| May 23, 2018 | 16.13.1 (18052203) | ||
| May 15, 2018 | 16.13.0 (18051301) | ||
| April 11, 2018 | 16.12.0 (18041000) | ||
| March 19, 2018 | 16.11.1 (18031900) | ||
| March 13, 2018 | 16.11.0 (18031100) | ||
| February 13, 2018 | 16.10.0 (18021001) | ||
| January 26, 2018 | 16.9.1 (18012504) | ||
| January 18, 2018 | 16.9.0 (18011602) | ||
| December 12, 2017 | 15.41.0 (17120500) | ||
| November 14, 2017 | 15.40.0 (17110800) | ||
| October 10, 2017 | 15.39.0 (17101000) | ||
| September 12, 2017 | 15.38.0 (17090200) | ||
| August 15, 2017 | 15.37.0 (17081500) | ||
| July 21, 2017 | 15.36.1 (17072101) | ||
| July 11, 2017 | 15.36.0 (17070200) | ||
| June 16, 2017 | 15.35.0 (17061600) | ||
| June 13, 2017 | 15.35.0 (17061000) | ||
| May 16, 2017 | 15.34.0 (17051500) | ||
| April 11, 2017 | 15.33.0 (17040900) | ||
| March 14, 2017 | 15.32.0 (17030901) | ||
| February 16, 2017 | 15.31.0 (17021600) | ||
| January 11, 2017 | 15.30.0 (17010700) |
You are using MS Outlook 2019, 2016, 2013 or 2010 smoothly to manage your emails, messages, and other email accounts, but then you suddenly start receiving errors while opening Outlook. Errors like “unable to open Outlook PST file,” or “Outlook PST file is not a personal folder file” often become a major obstacle for users in accessing their Outlook data. In such situations, people run toward Microsoft or third-party solutions to fix the Outlook errors.
When you look for solutions related to Outlook PST repairing, you will find a lot of options to fix the PST files. But do you think all those solutions work every time? What if the reason behind your PST file corruption is something related to your system configuration?
Instant Solution
Try automated tool Kernel for Outlook PST Repair to repair Outlook 2019 corrupt PST file. It supports Office 365 Outlook, 2019, 2016, 2013, 2010, 2007.
There could be various reasons behind the Outlook 2019, 2016, 2013 or 2010 PST file corruption. And you should look for a PST repair solution based on that corruption reason. For example, the most common reasons behind PST file corruption are:
- Due to data storage device failure
- Faulty networking device
- Virus or malware infection
- Abruptly shutting down Outlook
If the hard disk on your system has some bad sectors, and the PST file is stored in any of these sectors, chances are you won’t be able to open and read your PST files with Outlook.
As you know, a PST resides on the network server, and you try to access it via a client computer or network links. So, if any of the networking devices is not working properly or have issues, then the remote access to PST file can make it corrupted.
Our system is always prone to virus attacks and malware, which might affect the functionality of PST files and make them inaccessible. So, having a reliable anti-virus on your system is recommended.
We often tend to shut down Outlook abnormally when we are in a hurry. But we forget that doing so makes the PST file prone to corruption errors. Thus, you should always close Outlook normally.
These are some of the reasons that define how a PST file gets corrupted. However, sometimes there are problems with the Outlook program as well, such as if the PST file size is too big, MS Outlook becomes unstable to handle it while making the file corrupted.
Now, let’s come to the main discussion – repairing corrupt Outlook 2019, 2016, or 2013 PST files. In this article, we will be covering the effective methods to repair corrupt/damaged or inaccessible PST files.
Methods to repair Outlook 2019, 2016, 2013 and 2010 PST File
Generally, there are two reliable methods that can be used to repair corrupt PST files. The first method, i.e., the manual method involves using the inbuilt utility “ScanPST,” provided by Microsoft. The second method is third-party software.
1st Method – Repair Outlook 2019, 2016, 2013 and 2010 with ScanPST
Also known as Inbox Repair tool, ScanPST allows you to repair corrupt/damaged PST files. You can access this inbuilt utility from your computer drive.
- For Outlook 2019/2016/2013/2010C:Program Files (x86)Microsoft OfficeOffice16C:Program Files (x86)Microsoft OfficeOffice14
Now, follow the below steps to use the ScanPST software.
- Double-click on the launcher to start the ScanPST tool.
- Click Browse to add the PST file that you want to repair, and then click Start to scan the file.
- Once the scanning is complete, hit the Repair button to start the repairing process.
- It will take a few seconds for the ScanPST tool to repair the PST file. After fixing the file, you can import it to Outlook.
Note: To create a backup for this PST file, check the checkbox “Make a backup of scanned file before repairing.”
However, if you still face any after importing to Outlook, it means the PST file is not repaired properly. So, we have an alternative solution of Scanpst.exe for you.
2nd Method-Kernel Outlook PST Repair
It is an advanced Outlook PST repair tool that allows you to access your corrupt/damaged PST files by repairing it quickly with smart algorithms. With this software, you can retrieve lost/deleted mailbox items and export them in different formats. Now, let’s get to the working process of this tool:
- After downloading the software, install it on your system.
- On launching the software, a pop-up window will appear on the screen. Click Browse to select the file that you want to repair, and click “Next.”
- The tool will start repairing the PST file. Once it is complete, you will be able to see the content of PST file in the left pane. You can preview the emails/items of the file by selecting any folder.
- To save the repaired PST file, click Save. A pop-up window will appear on the screen, select the PST file option, and click Next.
- The filtration window will appear on the screen, apply specific filters to the PST file, such as From, To, Subject, Item type, etc. and click Next after applying the filters.
- In the next step, if you want to split the PST file, then use the Split option, and then click Next.
- Select a location to save the recovered PST file and click Finish.
- A notification will appear on the screen confirming “PST file has been saved.” Click “OK” to end the process.
Note: You can also find the specific PST files by clicking the Search button.
And that’s how you can repair the corrupt/damaged PST files for any Outlook version.
Conclusion
Repairing corrupt/damaged PST files could be very complicated if you don’t know the reason behind its corruption. However, with the help of the ScanPST tool, most of the PST files can be repaired easily. In case, if the ScanPST utility doesn’t work, you can always opt for Kernel PST Repair that is specially designed to resolve PST Corruptions. It supports all MS Outlook versions: Outlook 2019, 2016, 2013, 2010, 2007, 2003, 2002, and 2000.
Watch Video: To View the complete process of Outlook PST Repair
More Information
-->The information in this specification is applicable to thefollowing Microsoft products or supplemental software. References to productversions include updates to those products.
Microsoft Exchange Server 2007
Microsoft Exchange Server 2010
Microsoft Exchange Server 2013
Microsoft Exchange Server 2016
Microsoft Exchange Server 2019
Microsoft Office Outlook 2007
Microsoft Outlook 2010
Microsoft Outlook 2013
Microsoft Outlook 2016
Microsoft Outlook 2019
Exceptions, if any, are noted in this section. If an updateversion, service pack or Knowledge Base (KB) number appears with a productname, the behavior changed in that update. The new behavior also applies tosubsequent updates unless otherwise specified. If a product edition appearswith the product version, behavior is different in that product edition.
Unless otherwise specified, any statement of optionalbehavior in this specification that is prescribed using the terms'SHOULD' or 'SHOULD NOT' implies product behavior inaccordance with the SHOULD or SHOULD NOT prescription. Unless otherwisespecified, the term 'MAY' implies that the product does not followthe prescription.
<1>Section 2.2.2.3: The X-ClientCanHandle header is used to indicatethe capabilities that the client supports when the client is not Outlook.Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019do not use this header. Exchange 2007, Exchange 2010, and the initial releaseof Exchange 2013 do not support processing of the X-ClientCanHandle header.Exchange 2013 cumulative update 6, Exchange 2016, and Exchange 2019 supportprocessing of the X-ClientCanHandle header.
<2>Section 2.2.4.1.1.1.1: Exchange 2007 and the initial release version ofExchange 2010 do not include the AutoDiscoverSMTPAddress element. The AutoDiscoverSMTPAddresselement was introduced in Microsoft Exchange Server 2010 Service Pack 1(SP1).
<3>Section 2.2.4.1.1.1.2: Exchange 2007, and the initial release version ofExchange 2010 do not include the DefaultABView element. The DefaultABViewelement was introduced in Exchange 2010 SP1.
<4>Section 2.2.4.1.1.2.3: The MicrosoftOnline element is not supportedby Exchange 2007, Exchange 2010 and Exchange 2013.
<5>Section 2.2.4.1.1.2.4: The ConsumerMailbox element is not supportedby Exchange 2007, Exchange 2010 and Exchange 2013.
<6>Section 2.2.4.1.1.2.5: The AlternativeMailbox element is notsupported by Exchange 2007.
<7>Section 2.2.4.1.1.2.5.1: The DisplayName element is not supported byExchange 2007.
<8>Section 2.2.4.1.1.2.5.2: The LegacyDN element is not supported byExchange 2007.
<9>Section 2.2.4.1.1.2.5.3: The Server element is not supported byExchange 2007.
<10>Section 2.2.4.1.1.2.5.4: Exchange 2007 and Exchange 2010 do not supportthe SmtpAddress element. Office Outlook 2007 and Outlook 2010 ignore theSmtpAddress element.
<11>Section 2.2.4.1.1.2.5.5: The Type element is not supported byExchange 2007.
<12>Section 2.2.4.1.1.2.5.5: Exchange 2007 and Exchange 2010 do not supportthe 'TeamMailbox' value for the Type element. Office Outlook2007 and Outlook 2010 ignore AlternativeMailbox elements with a value of'TeamMailbox' in the child Type element.
<13>Section 2.2.4.1.1.2.6.4: The Negotiateauthenticationmethod is not implemented in Exchange 2007, Exchange 2010, Office Outlook 2007,or Outlook 2010.
<14>Section 2.2.4.1.1.2.6.4: The 'anonymous' value for the AuthPackageelement is not implemented in Exchange 2007, Exchange 2010, Office Outlook2007, or Outlook 2010.
<15>Section 2.2.4.1.1.2.6.9: Exchange 2007 does not support the EcpUrlelement.
<16>Section 2.2.4.1.1.2.6.10: Exchange 2007 does not support the EcpUrl-aggrelement.
<17>Section 2.2.4.1.1.2.6.11: Exchange 2007 and Exchange 2010 do not supportthe EcpUrl-extinstall element. Office Outlook 2007 and Outlook 2010ignore this element.
<18>Section 2.2.4.1.1.2.6.12: Exchange 2007 does not support the EcpUrl-mtelement.
<19>Section 2.2.4.1.1.2.6.13: Exchange 2007 and Exchange 2010 do not supportthe EcpUrl-photo element. Office Outlook 2007 and Outlook 2010 ignorethis element.
<20>Section 2.2.4.1.1.2.6.14: Exchange 2007 and Exchange 2010 do not supportthe EcpUrl-publish element.
<21>Section 2.2.4.1.1.2.6.15: Exchange 2007 does not support the EcpUrl-retelement.
<22>Section 2.2.4.1.1.2.6.16: Exchange 2007 does not support the EcpUrl-smselement.
<23>Section 2.2.4.1.1.2.6.17: Exchange 2007 and Exchange 2010 do not supportthe EcpUrl-tm element. Office Outlook 2007 and Outlook 2010 ignore thiselement.
<24>Section 2.2.4.1.1.2.6.18: Exchange 2007 and Exchange 2010 do not supportthe EcpUrl-tmCreating element. Office Outlook 2007 and Outlook 2010ignore this element.
<25>Section 2.2.4.1.1.2.6.19: Exchange 2007 and Exchange 2010 do not supportthe EcpUrl-tmEditing element. Office Outlook 2007 and Outlook 2010ignore this element.
<26>Section 2.2.4.1.1.2.6.20: Exchange 2007 and Exchange 2010 do not supportthe EcpUrl-tmHiding element. Office Outlook 2007 and Outlook 2010 ignorethis element.
<27>Section 2.2.4.1.1.2.6.21: Exchange 2007 does not support the EcpUrl-umelement.
<28>Section 2.2.4.1.1.2.6.26: Exchange 2007, Exchange 2010, and the initialrelease of Exchange 2013 don't support the GroupingInformation element.The GroupingInformation element was introduced in Microsoft ExchangeServer 2013 Service Pack 1 (SP1).
<29>Section 2.2.4.1.1.2.6.27.1: The 'LiveIdFba' value of theAuthenticationMethod attribute is not implemented in Exchange 2007, Exchange2010, Exchange 2013, Exchange 2016, Exchange 2019, Office Outlook 2007, Outlook2010, Outlook 2013, Outlook 2016, and Outlook 2019.
<30>Section 2.2.4.1.1.2.6.38: Exchange 2007, Exchange 2010, Office Outlook2007, and Outlook 2010 do not support the ServerExclusiveConnect element.
<31>Section 2.2.4.1.1.2.6.41: Exchange 2007 and Exchange 2010 do not supportthe EcpUrl-extinstall element. Office Outlook 2007 and Outlook 2010ignore this element.
<32>Section 2.2.4.1.1.2.6.46: Exchange 2007 and Exchange 2010 do not supportthe 'EXHTTP' value for the Type element. Office Outlook 2007and Outlook 2010 ignore Protocol elements with a Type childelement that has a value of 'EXHTTP'.
<33>Section 2.2.4.1.1.2.6.46: Exchange 2007, Exchange 2010, Exchange 2013,Exchange 2016, and Exchange 2019 do not support the 'POP3' value forthe Type element.
<34>Section 2.2.4.1.1.2.6.46: Exchange 2007, Exchange 2010, Exchange 2013,Exchange 2016, and Exchange 2019 do not support the 'SMTP' value forthe Type element.
<35>Section 2.2.4.1.1.2.6.46: Exchange 2007, Exchange 2010, Exchange 2013,Exchange 2016, and Exchange 2019 do not support the 'IMAP' value forthe Type element.
<36>Section 2.2.4.1.1.2.6.46: Exchange 2007, Exchange 2010, Exchange 2013,Exchange 2016, and Exchange 2019 do not support the 'DAV' value forthe Type element.
<37>Section 2.2.4.1.1.2.7: Exchange 2007 and Exchange 2010 do not support the PublicFolderInformationelement. Office Outlook 2007 and Outlook 2010 ignore the PublicFolderInformationelement.
<38>Section 3.1.5.4: Office Outlook 2007 and Outlook 2010 ignore the ServerExclusiveConnectelement.
<39>Section 3.1.5.4: Office Outlook 2007 and Outlook 2010 ignore Protocolelements that contain a Type element with the 'EXHTTP' value,and do not ignore Protocol elements that contain a Type elementwith the 'EXPR' value in this case.
<40>Section 3.1.5.4: Office Outlook 2007 and Outlook 2010 ignore Protocolelements that contain a Type element with the 'EXHTTP' value.
<41>Section 3.2.5: Exchange 2007, Exchange 2010, and the initial release ofExchange 2013 do not support processing of the X-MapiHttpCapabilityheader. Exchange 2013 SP1, Exchange 2016, and Exchange 2019 support processingof the X-MapiHttpCapability header only when it is specifically enabled.
