logo elektroda
logo elektroda
X
logo elektroda

Windows 10 Pro x64 Upgrade: Black Screen & Cursor Instead of Login Screen, Post-Major Update

siewcu 18513 6
ADVERTISEMENT
Treść została przetłumaczona polish » english Zobacz oryginalną wersję tematu
  • #1 16434357
    siewcu
    Level 35  
    A few days ago I installed the last major update to Windows 10, in my case Pro x64. Everything went smoothly, but ... When starting up, after a standard spinning circle, instead of the login screen, the screen turns off. As soon as it is possible to start, which is possible only when going through repairing the system from the emergency mode menu - which still fails, the system normally only starts once. After reboot, the screen turns off again instead of the login screen. In addition, once it has started, it is closing the flap in the laptop and lifting it again (options of making up etc are turned off), the only thing is the black screen and the cursor visible on it. Turning off the button, or if I did not have anything turned on it normally by Alt + F4 and shut down the system, restarting and again black screen ... I tried installing other graphics card drivers, removing them, all the rest of the devices does not report problems and has the latest drivers available . I spread my hands because I can not find a solution - and advice on solving similar problems does not work. Has anyone already met with a similar problem? How can I try to solve this? Because so far the only option for using a computer is to run it and keep it on 24/7 ... And this is not a solution.
  • ADVERTISEMENT
  • #2 16434399
    rtj71
    IT specialist
    Have you uninstalled these updates and reinstalled?
  • ADVERTISEMENT
  • #3 16434413
    siewcu
    Level 35  
    Unfortunately, she is not on the list. This is one update, a large window informing about it etc ... I do not know if it was Creators Update, Redstone 2, Redstone 3, or what it's called, but I also had it on the second computer (though I did not pay attention to its name) and there are no problems. Unless it's a matter of the old laptop - Dell E6510. If I found an option to remove it somewhere, it would be simpler, but unfortunately I can not see it anywhere. I installed the update on Friday, there is no update on the list that can be removed.
  • ADVERTISEMENT
  • #4 16435129
    rtj71
    IT specialist
    In that case, use system restore.
  • #5 16435597
    mrdadi
    Level 11  
    reset the computer several times in this way ... that:

    - when you load the system (on the windows 10 logo screen) you turn off the electricity ...
    and so 4 times ...

    for 5 you let it go and start repairing the computer, and you choose it - Run normally :-)

    Pozdrowka
  • ADVERTISEMENT
  • #6 16435663
    siewcu
    Level 35  
    rtj71 wrote:
    In that case, use system restore.

    There is no restore point before installing this update ...

    Added after 36 [seconds]:

    mrdadi wrote:
    reset the computer several times in this way ... that:

    - when you load the system (on the windows 10 logo screen) you turn off the electricity ...
    and so 4 times ...

    for 5 you let it go and start repairing the computer, and you choose it - Run normally :-)

    Pozdrowka

    Without turning it off, but via the emergency mode menu, it usually starts up in most cases.
  • #7 16438164
    siewcu
    Level 35  
    Problem solved.

    Settings - Updates and recovery - Recovery - Return to the previous build (although I'm not sure if it was not back to the previous version). The moment has passed, the problems are over.

Topic summary

After installing a major update to Windows 10 Pro x64, the user experienced a black screen with only a cursor visible instead of the login screen. Attempts to repair the system through emergency mode were initially unsuccessful, and the user could only boot the system intermittently. Suggestions included uninstalling the update, using system restore, and a method of force rebooting the system multiple times to trigger repair options. Ultimately, the user resolved the issue by reverting to the previous build through the recovery settings, eliminating the problems encountered post-update.
Summary generated by the language model.
ADVERTISEMENT