Microsoft brings popular extra

Microsoft has now also added an optional and non -safety -relevant update for Windows 10. It is the preview for June Patch Day. This time there are no new functions in the actual sense, because an old feature returns.

These are an overview of the changes

Despite the approaching support end for Windows 10, Microsoft continues to publish monthly updates – including innovations and improvements. The latest version, Build 19045.5917, brings improvements for Rich Calendar function and contains technical corrections for GDI and Winsas. With this update, all optional May updates are now available for end users, because previously Windows 11 versions 23h2 and 24h2 have been supplied with new versions.

Calendar flyout gets back seconds

The optional update KB5058481 also restores the second display in the calendar flyout. This function had previously been removed by Microsoft, which had caused resentment among users. This is particularly important for Windows 10 users, as in contrast to Windows 11, there is no native option to display seconds in the task tinker clock. The second display in the calendar flyout was often the only solution to read the time exactly without using third-party software. To overview of the further changes, we translated the changelog:

Release notes at a glance

• [Kalender-Flyout]
• Bring the watch view, which shows seconds on the calendar that was previously removed.
• Improves the Richcalendar function by expanding the period for upcoming events to 30 days.
• Add the description text for the weather button in the Richcalendar.
• [GDI/GDI+]
• Fixed: Some GB18030-2022 characters on level 2 are not rendered.
• Fixed: Some GB18030 signs are rendered wider. In addition, the sample sales are not reproduced correctly.
• [Mobile Operator Profiles]
• Updated: Country and Operator Settings Asset (Cosa) Profiles have been updated.
• [WinSaS]
• Fixed: A problem in the context of the Windows Account Sync Consent System in markets of the European Economic Area, in which secondary accounts were not recognized, which led to an increased server load.