After the redesigned dictation toolbar was added to Microsoft Office version 2206 last week, Microsoft pushed a set of new fixes to its Office products. If you are following us on Office Insider Channel, the company releases a new Office build every Friday and there is no exception this week. The latest build 15330.20004 has been released to the insiders who are in the Windows Beta Channel, and it adds the following fixes.
What's new and improved in Microsoft Office Version 2206 (Build 15330.20004)
Microsoft Word
- Fixed an issue where similar but distinct images may be handled incorrectly.
- Fixed an issue where the “Insert” and “Cancel” labels were not visible in high-contrast themes.
- Fixed an issue where the interaction mode showed “Editing” when a document was in read-only mode.
- Fixed an issue where the user could not re-enable Autosave after it had been switched off.
- Fixed an issue that was preventing the application from discarding a document that had stopped responding, leading to a recurring sync process.
Microsoft Excel
- Fixed a visual glitch in the Formula bar.
- Fixed an issue where similar but distinct images may be handled incorrectly.
- Fixed an issue where the “Insert” and “Cancel” labels were not visible in high-contrast themes.
Microsoft PowerPoint
- Fixed an issue where similar but distinct images may be handled incorrectly.
- Fixed an issue where the “Insert” and “Cancel” labels were not visible in high-contrast themes.
- Fixed an issue where a blank slide was displayed when exporting images, icons, and videos to PDF.
Microsoft Outlook
- Fixed an issue that was causing users to see multiple copies of a shared calendar rendered in certain circumstances.
Microsoft OneNote
- Fixed an issue where, after inserting a shape or line onto the canvas, the user was unable to drag or resize the item.
Microsoft Project
- Fixed an issue where the user would open a project previously set to 100% complete only to find that the progress status had reverted to a lesser value.
Microsoft Access
- Fixed a performance issue where existing code from a user that previously ran without incident was taking much longer to run.
Have a question? Or, a comment? Let's Discuss it below...
Thank you for visiting our website!
We value your engagement and would love to hear your thoughts. Don't forget to leave a comment below to share your feedback, opinions, or questions.
We believe in fostering an interactive and inclusive community, and your comments play a crucial role in creating that environment.
