Whenever a major Windows update starts to roll out there are always a number of bugs that slip past Microsoft's internal testing team and horde of Insiders. With the Windows 10 May 2020 Update that was certainly the case but nothing severely impactful or disastrous seemed to plague users. HEXUS reported on an Intel Optane bug, which was really little more than an annoyance. Intel has since shared a fix for the error messages that can occur.
Another quite widely reported issue for those that took the plunge and updated to Windows 10 May 2020 Update concerned printer functionality. The issue was due to Microsoft's Print Spooler tech misbehaving, with some losing the ability to print their documents, even to 'software printers' like Adobe PDF.
The fix(es) from Microsoft are described as follows:
Addresses an issue that might prevent certain printers from printing. The print spooler might generate an error or close unexpectedly when attempting to print, and no output will come from the affected printer. You might also encounter issues with the apps you are attempting to print from, such as receiving an error, or the app might close unexpectedly. This issue might also affect software-based printers, such as when printing to PDF.
Depending upon your Windows version, you can grab the update to fix printer issues at the following links: Click here for versions 1909 or 1903, here for version 1809, and here for version 1803. They should become available via Windows Update in the not-too-distant future.
Microsoft Edge improvements
With the Windows 10 May 2020 Update people got the latest version of Microsoft Edge delivered, the one based upon Chromium. Microsoft has been busy customising the open source browser to deliver its signature experience and integrate well with Windows and its services.
Yesterday it was detailed that the browser has been refined further, recently, to manage memory more efficiently. In a blog post Principal PM Manager of Microsoft Edge, Kim Denny, said that the latest version of the browser used up to 27 per cent less memory in tests. It was explained that the significant memory optimisation was largely the fruit of Windows segment heap memory improvements which are now available for Win32 applications.
