Microsoft released the final version of Windows 10 version 1903, the May 2019 Update, at the end of May 2019. The release replaces Windows 10 version 1809 and will be around for longer because Windows 10 19H2, the second feature update of 2019, will just be a cumulative update and not a full feature update.
The new feature update for Windows 10 has had its share of issues but was not nearly as buggy as the Windows 10 version 1809 update that Microsoft had to pull for about six weeks because of major issues.
Microsoft revealed in June that the new update was available to all administrators who ran manual update checks but failed to highlight that plenty of upgrade blocks were in place that prevented the upgrade to the new version of Windows 10.
Some longstanding upgrade blocks have been lifted as of July 11, 2019. The Release Information page for the feature update lists three issues marked as resolved. Systems that were affected by these issues previously are no longer blocked from finding the update via Windows Update.
The three issues that are resolved are:
Microsoft confirms that the upgrade hold is no longer in place and notes that it may take up to 48 hours before affected devices may find the new feature update when admins run manual checks for updates in Windows Update.
This issue is now resolved and the safeguard hold has been removed. Please note, it can take up to 48 hours before you can update to Window 10, version 1903.
It may take until July 13, 2019 before the new update is listed on Windows Update. The update is listed as an optional upgrade if the device runs Windows 10 version 1809. If an older version of Windows 10 is installed, it may be installed right away without giving the admin any option. (via Deskmodder)
Some Windows 10 version 1903 devices may enter a restart notifications loop after installing the KB4507453 which was released as part of the July 2019 Patch Day.
The issue affects some devices only. The notification to restart the device after the installation of the update does not go away after the restart on affected devices. Windows notifies the user that a restart is required, but no matter the times the system is restarted, continues to display the notification.
Microsoft has not acknowledged the issue yet. A potential workaround involves using the restart option displayed by the restart prompt to resolve it. (via Günter Born)
Some Windows 10 users reported that the SFC /Scannow option was not working properly after the installation of the most recent updates for the operating system. The issue was traced back to the most recent Windows Defender definitions that interfered with the program execution. (via Windows Latest)
Last but not least, a new black screen issue reportedly affects Remote Desktop Protocol windows on Windows 10 version 1903. (via Windows Latest)
Now You: Which version of Windows do you run currently? Any issues?Advertisement
Advertising revenue is falling fast across the Internet, and independently-run sites like Ghacks are hit hardest by it. The advertising model in its current form is coming to an end, and we have to find other ways to continue operating this site.
We are committed to keeping our content free and independent, which means no paywalls, no sponsored posts, no annoying ad formats or subscription fees.
If you like our content, and would like to help, please consider making a contribution:
Ghacks is a technology news blog that was founded in 2005 by Martin Brinkmann. It has since then become one of the most popular tech news sites on the Internet with five authors and regular contributions from freelance writers.