[German]Another addendum: Microsoft has already confirmed a bug in Windows 10 V1809 at the end of June 2019, which caused a delay in shutting down the operating system. The bug was fixed in Windows 10 Version 1903. There will probably be no bug fix for Windows 10 Version 1809. Here some information about this topic.
The problem
During shutdown, systems running Windows 10 October 2018 Update (version 1809) took up to 60 seconds to shut down. The bug occurred on systems with a USB Type C port when a dock or charging cable was connected. The whole thing was described in the tech community article UCSI based USB Type-C systems may see a shutdown delay if connect changes race with power transition.
The reason was a bug in the implementation of the USB Type-C Connector System Software Interface (UCSI) software in Windows 10, version 1809. The bug can lead to a delay of 60 seconds in the system sleep or shutdown process. This occurs when the power is turned off while the UCSI software is busy with a new connection or disconnect process on a USB Type C port.
Apart from the extra minute required for the sleep or shutdown under these circumstances, this error has no effect on the normal functionality of USB Type-C on your machine. The system and the Type C USB ports should continue to function properly after the next wake or restart of the system.
Microsoft has fixed the bug in Windows 10 V1903
The bug only occurs in Windows 10 Version 1809 (Build 17763). Based on the feedback Microsoft received from affected users, this bug in Windows 10 Version 1903 (May 2019 Update) has been fixed by a modified implementation. Microsoft recommends that affected users upgrade to the new operating system version.
From this formulation I conclude that Microsoft does not intend to fix this bug in Windows 10 Version 1809 (Build 17763). Affected parties can resolve this with a workaround by disconnecting the USB Type C connection before shutting it down. (via)
This bug is really annoying. The bug was earlier fixed in the previous version but later came into action in the recent version of Windows 10. this blog helped me find out the solution.