Several affected users have reported that they’ve been able to resolve the issue by booting up in Safe mode and resetting the Winsock component.

In this case, you should be able to resolve the issue by fixing the corrupted file with SFC and DISM. Whenever this happens, the login process is effectively broken, which ends up triggering this issue. There’s one particular file (NTUSER.dat) with the potential of becoming corrupted.