Microsoft has posted a new support document warning users of a mysterious bug affecting Windows 10 that causes devices connected to a Thunderbolt Dock to fail after waking up from a particular sleep state.
The new document, titled 'Devices connected through a Thunderbolt Dock stop working after the computer resumes from the S5 power state', details the symptoms and a workaround to a problem that affects Windows 10, version 1709 through to version 1909.
According to Microsoft, there's a 5% failure rate for all devices that are attached to the Thunderbolt Dock after a Windows 10 PC wakes from the 'S5' Soft Off power state.
SEE: 20 pro tips to make Windows 10 work the way you want (free PDF)
S5 is a deeper sleep state than hibernation and involves a full shutdown, causing the system to appear to be off. In fact, it's not completely off.
Microsoft notes the typical scenario for failure to occur is after a user enables Fast Startup on a Windows 10 PC and has several devices, such as a keyboard, mouse, and USB key attached to a Thunderbolt Dock, which is connected to the PC.
After waking the device from S5, users may find that the attached devices stop working even if they're listed in Device Manager.
"When the failure occurs, the functionality of the devices cannot be restored by reattaching the Thunderbolt Dock. Instead, you have to restart the computer," Microsoft notes.
Without this piece of information, users might be stuck in a loop described by Microsoft:
- You connect the Thunderbolt Dock to the computer. Devices on the Thunderbolt Dock are enumerated.
- You press the power button to put the system into a Soft Off (S5) power state. After the screen turns off, you remove the Thunderbolt Dock.
- You wait for the S5 process to finish, plug in the Thunderbolt Dock, and then wait five seconds for the Thunderbolt Dock to become idle.
- You power on the computer. Then, you check whether the mouse, keyboard, and USB key are functional.
As explained, there's a small chance they won't work, at least until the PC has been restarted.
Microsoft doesn't explain why this failure is occurring and doesn't appear to be planning to offer a fix beyond informing users of this workaround.
More on Microsoft and Windows 10 updatesWindows 10: Microsoft unmasks the mysterious 'G' app that stops you shutting downMicrosoft christens Windows 10 20H1 as Windows 10 2004; preps to start testing its successor
Windows 10 1909: Microsoft opens November 2019 Update to more users
Microsoft: If you're on Windows 10 version 1803, you'll be automatically upgraded
Microsoft begins the official rollout of Windows 10 1909
With Windows 10 1909 coming, Windows 10 20H1 hits major milestone
Windows 10 updates: Microsoft kills off Skip Ahead ring for Insiders
Windows 10 version 1903 should just work out of the box, right? Wrong
Why is Windows 10 a mess? Ex-Microsoft engineer blames the culture of 'made-men' Windows 10 users fume: Microsoft, where's our 'local account' option gone?
Windows 10 1909: Microsoft ends 19H2 confusion, puts all testers on same builds
No more buggy Windows 10 updates? Microsoft makes it easier to flag early flaws
How to delete the Windows 10 paging file on every shut-down TechRepublic
Test Microsoft's Chrome-like Edge browser for Windows 10 CNET