Microsoft has rolled out a cumulative update to Windows 10 1809 users following fixes for 1607, 1703, and 1709 last week. KB4505658 fixes many frustrating issues in the OS, including ones with Internet Explorer, resetting app permissions, upgrade reliability, and more.
Many of these fixes are the same as we saw last week’s updates, with some additional changes unique to the version. Generally, they’re fairly minor fixes and improvements, but they should add to the feeling of stability and refinement in older versions.
The highlights for build 17763.652 are as follows:
- “Updates an issue that may cause Internet Explorer to stop working when you drag a tab to create a new window.
- Updates an issue that prevents newly installed or updated applications from appearing in Windows search results.
- Updates an issue that prevents the Save and Save As options in Microsoft Office 2010 applications from working when high contrast mode is on.
- Updates an issue that prevents a device from recognizing a Microsoft account until you sign out and sign in again.
- Updates an issue that affects applications that manage files, folders, and device settings.
- Improves compatibility with the Window-Eyes screen reader application.
- Updates an issue to keep your App permissions settings when resetting your device.
- Improves reliability when upgrading from Windows 10, version 1703.”
Though we won’t dive into the full, giant list of fixes here, it’s worth noting that this build has several known issues to consider. Users of Clustered Shared Volumes (CSVs) may not that they’re unable to perform operations like renaming on folders. To fix get around this, users currently have to perform the process as an admin.
Additionally, some devices with Asian language packs will get a component not found error. They must re-install recent language packs and install the April 2018 cumulative update to fix this.
More frustratingly, some PCs are experiencing a black screen on boot after installing updates. Though this looks scary, Microsoft says a restart will fix this, and a patch will roll out soon. You can read the full release notes for build 17763.652 here.