windows boots into black screen with command prompt

Page 1 of 2 12 LastLast

  1. Posts : 15
    Windows 10 Home 64bit
       #1

    windows boots into black screen with command prompt


    Noticed today that there was an update ready to install so I went ahead with it. During the update process I accidentally hit f8 at my bios screen and booted into windows boot manager. Realizing my mistake I went ahead and exited it and hoped that the update would be unaffected. Windows said the update was 100% complete and loaded into my sign on screen. However, when I signed in I was met with a black screen and an instance of cmd running. I can load the rest of the windows UI by running explorer.exe in cmd and the system works absolutely fine from what I can tell. But, no matter what when I sign into my main admin account it always boots up with a black screen with cmd running.

    Interestingly enough though, I made a new account and the issue is not present there. I would just do a system restore however it fails to complete successfully, it gives me a failed to extract file error. Even when doing a system restore from the startup settings menu it still will not complete successfully, I get an unspecified error has occurred error code 80070003. I've also tried booting into safe mode and the same issue with the black screen with cmd and system restore occur.I've checked msconfig and the safe boot and No GUI options are both unchecked... Any assistance would be greatly appreciated.

    Other things I've tried:
    SFC check
    checking regedit to make sure explorer.exe is set to run on start up
    windows update repair tool - which does tell me that there are errors with the windows update components and can't repair them.
    running the system image health command in powershell
    Last edited by jabales; 07 Aug 2018 at 23:08.
      My Computer


  2. Posts : 43,010
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #2

    Hi, you might try this: scan down or search for 'Best Answer' towards the end:
    cmd prompt appears instead of booting windows after using Hitmanpro to remove a trojan - [Solved] - Windows 7

    Approach registry edits with caution: back up appropriately.

    System Restore: notoriously unreliable as regards restoring.

    We strongly and continually urge users to use disk imaging routinely before and after major changes and periodically - e.g. Macrium Reflect (free) + external storage. Not the same as System Restore, but gives a way to restore Windows and any other partitions imaged should things go badly wrong - even if you need a new disk.

    When you have resolved the CMD prompt dialogue box issue, then try
    Reset Windows Update in Windows 10 | Windows 10 Tutorials
      My Computers


  3. Posts : 15
    Windows 10 Home 64bit
    Thread Starter
       #3

    dalchina said:
    Hi, you might try this: scan down or search for 'Best Answer' towards the end:
    cmd prompt appears instead of booting windows after using Hitmanpro to remove a trojan - [Solved] - Windows 7

    Approach registry edits with caution: back up appropriately.

    System Restore: notoriously unreliable as regards restoring.

    We strongly and continually urge users to use disk imaging routinely before and after major changes and periodically - e.g. Macrium Reflect (free) + external storage. Not the same as System Restore, but gives a way to restore Windows and any other partitions imaged should things go badly wrong - even if you need a new disk.

    When you have resolved the CMD prompt dialogue box issue, then try
    Reset Windows Update in Windows 10 | Windows 10 Tutorials
    Thanks, Dalchina that helped solve my issue. I checked the registry for the folder winlogon under HKEY_CURRENT_USER and found a shell key with a value of %comspec%. Its actually kinda funny because this is something that I've already checked and I saw that that was the value a day or so ago but, since it didn't have any mention of cmd.exe I thought it was just normal for it to be there. I figured since the guy in the thread you mentioned said it was ok to delete this key regardless it wouldn't hurt if I went ahead and deleted it anyway even though the setting value has nothing to do with running cmd on start up, from what I can tell. Anyways, I went ahead and deleted it and that fixed my issue.

    Any idea as to what %comspec% value even does? Or, how that shell key got in that folder to begin with?

    Thanks so much for getting back to me. These forums rock!
      My Computer


  4. Posts : 43,010
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #4

    Weird thing.. no no idea, sorry. Glad it helped- not one I've seen before.

    Please post back with outcome of work on Windows Update.
      My Computers


  5. Posts : 15
    Windows 10 Home 64bit
    Thread Starter
       #5

    dalchina said:
    Weird thing.. no no idea, sorry. Glad it helped- not one I've seen before.

    Please post back with outcome of work on Windows Update.
    So, I downloaded the .bat file and ran it. At first it told me it failed to run because it was unable to stop background intelligent services. I went to services.msc and disabled that and then it got stuck on a different error saying it coudln't stop cryptographic services, which when I tried to disable in services always came back as being put in manual start up mode instead of disabled after I restarted.
      My Computer


  6. Posts : 43,010
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #6

    Did you remember to do this?
    Right click or press and hold on the .bat file, and click/tap on Run as administrator.

    Otherwise sounds like you have permissions problems or services corruption of some sort.

    Try Tweaking.com's free cautious repair tool; limit your choice of repairs to those necessary.
    E.g. 03 (Service Permissions), 26 (important services), 17 (Windows Updates)
      My Computers


  7. Posts : 15
    Windows 10 Home 64bit
    Thread Starter
       #7

    dalchina said:
    Did you remember to do this?



    Otherwise sounds like you have permissions problems or services corruption of some sort.

    Try Tweaking.com's free cautious repair tool; limit your choice of repairs to those necessary.
    E.g. 03 (Service Permissions), 26 (important services), 17 (Windows Updates)
    Yep that seemed to be issue. It completed successfully though it said it was denied access to certain files.
      My Computer


  8. Posts : 43,010
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #8

    Try running the Windows Update Troubleshooter again and see what that says now.

    If it still fails, try Tweaking.com's tool, then the Troubleshooter again.
      My Computers

  9.   My Computer


  10. Posts : 43,010
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #10

    @TairikuOkami - thanks - that problem was solved (post #3) - unless you think there's something more.

    Now looking at the WU problem mentioned in #1.
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 22:24.
Find Us




Windows 10 Forums