Got the same issue.
This is an example of very bad UI. Simple/dumbed down UI is only good when it works.
But when things go wrong, the UI should give as much relevant information as possible in order to diagnose the problem, find the cause, and work out solution(s).
Instead, we get "user thinks something's probably not working but UI says it's still working, but UI is lying since it's been doing that for hours (probably eternally if left to its own) and
no indication of progress". Then we're told to try various ways to "probably solve" the problem without knowing exactly what the problem is.
Compare with almost 20 years ago:

Error message might be cryptic, but it's so clear where is the error during installation progress, and what went wrong.
Now: On the pursuit to "hide" complexity, it actually made things that used to be difficult but possible (helpful error messages), to become near impossible (no error message at all).