Hello Windows Insiders!
As we've been working through feedback and telemetry, we've found a bug that hit a small portion of users. I'll outline the details below on what the bug is and how to work around it (hint: reboot!).
Who: Windows Insiders in the Fast ring on 20H1 builds
What: A (very) small number of users may find that their device is "stuck" on a build somewhere between 18912 and 18926
Why: We have identified a bug in a build delivery function that causes the process to hang, causing update scans to not complete successfully.
To resolve: A device reboot will bypass the issue and allow users to scan for updates.
A fix for this bug is available in builds 18927 and higher, but we'd like to share the word to help folks bypass who may be impacted.
Thank you as always!