Version 2005 (Build 12827.20538)
Security updates listed here
Feature updates
Outlook
- Better results—in a jiffy: We've updated the Search experience to make it smarter, faster, and more reliable than ever. Learn more
Word
- Say it another way: When you want to say it differently, Rewrite is there to help. Rewrite offers alternatives for finessing your phrases.
See details in blog post
Resolved issues
Access
- Fixed an issue to be able to call the Date/Time Extended data type into your code without experiencing any crash in your app.
- Fixed an issue so you can now revert back to your most updated Access version, and use DAO/VBA to manage and edit a decimal data type.
Excel
- Fixed an issue where Excel could become unresponsive after using Ctrl+Shift+Arrow keys to scroll when the Excel window is shared through Teams.
- In some cases, clicking a hyperlink to a place within the same workbook will cause the workbook to be hidden.
- Fixed an issue which caused CustomUI XML for a custom ribbon tab to be removed when saving to SharePoint/OneDrive.
- Addresses an issue where Excel may crash when attempting to insert PivotTables into a chart sheet.
Outlook
- Addresses an issue that caused users to experience a crash when submitting feedback from an Admin Notification.
- Addresses an issue that caused searching for a feature in Suggest a Feature to return no results and leave the user with no option to submit a new feature idea.
- Addresses an issue that caused users to see Outlook continuously prompt them to run the Inbox Repair tool.
- Addresses an issue that caused users of Windows 10 server versions to see the warning "Antivirus status: Invalid. This version of Windows supports antivirus detection, but no antivirus was found" despite having anti virus correctly installed.
- Addresses an issue that caused users to experience intermittent hangs and crashes in some scenarios.
- Addresses an issue that caused users of the Shared Calendar improvements to see calendar failures.
- Addresses an issue that caused users to see the "The rules on this computer do not match the rules on Microsoft Exchange" message when updating their rules in Outlook.
- Addresses an issue that caused users to see the creation date of attachments that they copied to their file system via drag and drop getting set to January 1, 4501.
- Addresses an issue where Outlook failed to enable Data Loss Protection policy tips people for users who had paid for the service who are on M365 Business Plus plans.
- Addresses an issue with the clp auditing event for the reply/forward label.
PowerPoint
- This fixes a crash when users have both modern and legacy comments in a file, thus triggering an upgrade on the comments.
- We have fixed a crash issue with suggestion pane.
Project
- Fixed an issue where the ProjectBeforeTaskChange event doesn't fire when there is a change to the project summary task - either the project start/task field.
- Fixed an issue where a task that is marked 100% complete is wrongly changing to be less than 100% complete.
Skype
- When a user is given a policy that moves them to Teams Only, they were still able to use the Skype for Business Outlook add-in to schedule meetings. After this update, you will no longer be able to schedule Skype for Business meetings after the client reads the policy indicating the user is Teams Only, and enters meeting join only mode. Additionally the Skype for Business Outlook Add-in will not activate itself while starting up if it sees the Skype for Business client is in meeting join only mode.
Word
- Resolved an issue that may have caused a crash when dragging some content from the app.
Office Suite
- This change addresses potential hangs when loading and playing animated content such as GIFs or 3D models.
- We have resolved the ValidateInstall fail rate issue by setting the Bing Addon install validation to true by default and considering the MSI return success as an install success.
- This update fixes an issue in Microsoft Office where Visual Basic for Applications projects with references that are expected to be found by searching locations specified in the PATH environment variable may not be found properly at runtime, leading to VBA runtime errors.
- This update fixes an issue in Visual Basic for Applications in Microsoft Office where certain VBA projects that contain references to code libraries with DBCS characters in the library name or library path would be viewed by the Office application as corrupt on load.
- The office host was crashing in windows, when an add-in is being activated while the registry key HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main\TabProcGrowth is set to zero. This change would fix this issue.
Source: https://docs.microsoft.com/en-us/off...n-2005-july-14
Latest Office Updates for Windows
How to Check for Updates in Office 2016 and Office 2019 for Windows
Understanding Office 365 ProPlus Updates for IT Pros (CDN vs SCCM)