Recently, we reported about a bug that slows down the shutdown process in Windows 10 October 2018 Update.
Microsoft acknowledged the fact that the shutdown process may be delayed for around 60 seconds in some cases.
The delay is caused by a USB Type-C controller connected to your PC. However, the same issue also affected the new Windows 10 May 2019 Update. Microsoft stated that:
A bug in the USB Type-C Connector System Software Interface (UCSI) software implementation in Windows 10, version 1809 can cause a 60 second delay in the system sleep or shutdown process if the power-down happens while the UCSI software is busy handling a new connect or disconnect event on a USB Type-C port.
Problem fixed for Windows 10 v1903
The tech giant fixed the issue for the recent OS version. Microsoft recently released a patch to fix the shutdown bug in Windows 10 May 2019.
Microsoft rolled out Windows 10 cumulative update KB4501375 on June 27. According to the support document, Microsoft recommends its users to download Windows 10 version 1903 to resolve the issue.
This is resolved in Windows 10 version 1903, please update to the latest released build if you are impacted by this bug.
At the time of writing this article, there is no confirmation from Microsoft about its plans to fix the bug in October 2018 Update.
There are many users who are not willing to update their systems. If you are one of those, we have a temporary solution for you. You should proceed to the shutdown process once you have unplugged the Type-C controller.
This is how you can speed up the shutdown process on your Windows PC.
Next Patch Tuesday falls on July 9
Microsoft is all set to release July Patch Tuesday updates on July 9. These update will bring a new series of security and non-security improvements for Windows 10.
However, it seems like those who are running Windows 10 October Update may need to wait for the July Patch Tuesday Updates.
As a matter of fact, there is no permanent fix available at the moment. Remember, you still have the option to upgrade to Windows 10 v1903 to resolve the issue.