Windows 10: Command Prompt Not Opening

Discus and support Command Prompt Not Opening in Windows 10 Support to solve the problem; Recently attempting to open Command prompt, ordinary or as administrator, it flashes for perhaps 2 seconds and then disappears. I tried the following... Discussion in 'Windows 10 Support' started by Detonate, Apr 3, 2018.

  1. Detonate Win User

    Command Prompt Not Opening


    Recently attempting to open Command prompt, ordinary or as administrator, it flashes for perhaps 2 seconds and then disappears. I tried the following commands
    sfc /scannow
    DISM /Online /Cleanup-Image /RestoreHealth
    But none of these seem to work, I'm wondering if there are any fixes for this issue

    :)
     
    Detonate, Apr 3, 2018
    #1

  2. Java not opening .jar files, opening command prompt and crashing

    Every time I try to run a .jar file, java opens a command prompt window and then closes it. Nothing happesn. I have tried reinstalling java multiple times and have tried 32 bit and 64 bit(I have 64 bit os). Please help because at the moment, this makes
    Java useless which blocks off a massive portion of my computer's use.
     
    Kain Schneider, Apr 3, 2018
    #2
  3. Snipping Tool and Command Prompt not opening

    I tried to open snipping tool and command center, but they won't open. I tried googling but most people's Snipping Tool has an error message whilst mine does not. Also can't open Command Prompt so most people's option about running sfc/scannow is out.

    So far it seems like only 2 those are affected, other externally downloaded apps work just fine.
     
    Katanauser, Apr 3, 2018
    #3
  4. zbook New Member

    Command Prompt Not Opening

    Open administrative powershell and type or copy and paste:
    1) sfc /scannow
    2) dism /online /cleanup-image /scanhealth
    3) dism /online /cleanup-image /restorehealth
    4) chkdsk /scan
    5) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread
     
    zbook, Apr 3, 2018
    #4
  5. zbook New Member
    It's good to have a backup.
    Glad that it got sorted out.
     
    zbook, Apr 5, 2018
    #5
  6. Jaxon Win User
    Jaxon, Apr 5, 2018
    #6
  7. Detonate Win User
    Windows PowerShell
    Copyright (C) Microsoft Corporation. All rights reserved.

    PS C:\WINDOWS\system32> sfc /scannow

    Beginning system scan. This process will take some time.

    Beginning verification phase of system scan.
    Verification 100% complete.

    Windows Resource Protection did not find any integrity violations.
    PS C:\WINDOWS\system32> dism /online /cleanup-image /scanhealth

    Deployment Image Servicing and Management tool
    Version: 10.0.16299.15

    Image Version: 10.0.16299.334

    [==========================100.0%==========================] No component store corruption detected.
    The operation completed successfully.
    PS C:\WINDOWS\system32> dism /online /cleanup-image /restorehealth

    Deployment Image Servicing and Management tool
    Version: 10.0.16299.15

    Image Version: 10.0.16299.334

    [==========================100.0%==========================] The restore operation completed successfully.
    The operation completed successfully.
    PS C:\WINDOWS\system32> chkdsk /scan
    The type of the file system is NTFS.

    Stage 1: Examining basic file system structure ...
    333312 file records processed.
    File verification completed.
    13924 large file records processed.
    0 bad file records processed.

    Stage 2: Examining file name linkage ...
    22132 reparse records processed.
    406088 index entries processed.
    Index verification completed.
    0 unindexed files scanned.
    0 unindexed files recovered to lost and found.
    22132 reparse records processed.

    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
    36389 data files processed.
    CHKDSK is verifying Usn Journal...
    37900504 USN bytes processed.
    Usn Journal verification completed.

    Windows has scanned the file system and found no problems.
    No further action is required.

    116640767 KB total disk space.
    39895664 KB in 163528 files.
    121820 KB in 36390 indexes.
    0 KB in bad sectors.
    446511 KB in use by the system.
    65536 KB occupied by the log file.
    76176772 KB available on disk.

    4096 bytes in each allocation unit.
    29160191 total allocation units on disk.
    19044193 allocation units available on disk.
    PS C:\WINDOWS\system32>
     
    Detonate, Apr 5, 2018
    #7
  8. zbook New Member

    Command Prompt Not Opening

    When you open administrative command prompt now how does it respond?
    What is/are the methods that you are using to open administrative command prompt?
     
    zbook, Apr 5, 2018
    #8
  9. Detonate Win User
    Detonate, Apr 5, 2018
    #9
  10. zbook New Member
    Malwarebytes blocks opening the download to view the video.
    Please use one drive or drop box or google links so that there is less likely to have malware, PUPs, etc.
    Malwarebytes: Website blocked due to malvertising
     
    zbook, Apr 5, 2018
    #10
  11. Detonate Win User
    https://drive.google.com/open?id=1CcDYT7YROUFGYP9_d7w3xA8BK0dt9vg7

    System not repair: C:/Windows/system32/logs/SrtTrail.txt

    Startup Repair diagnosis and repair log
    ---------------------------
    Last successful boot time: ‎06.‎04.‎2018 17:20:12 (GMT)
    Number of repair attempts: 2

    Session details
    ---------------------------
    System Disk = \Device\Harddisk0
    Windows directory = C:\WINDOWS
    AutoChk Run = 0
    Number of root causes = 1

    Test Performed:
    ---------------------------
    Name: Check for updates
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms

    Test Performed:
    ---------------------------
    Name: System disk test
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms

    Test Performed:
    ---------------------------
    Name: Disk failure diagnosis
    Result: Completed successfully. Error code = 0x0
    Time taken = 125 ms

    Test Performed:
    ---------------------------
    Name: Disk metadata test
    Result: Completed successfully. Error code = 0x0
    Time taken = 63 ms

    Test Performed:
    ---------------------------
    Name: Disk metadata test
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms

    Test Performed:
    ---------------------------
    Name: Target OS test
    Result: Completed successfully. Error code = 0x0
    Time taken = 31 ms

    Test Performed:
    ---------------------------
    Name: Volume content check
    Result: Completed successfully. Error code = 0x0
    Time taken = 16 ms

    Test Performed:
    ---------------------------
    Name: Boot manager diagnosis
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms

    Test Performed:
    ---------------------------
    Name: System boot log diagnosis
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms

    Test Performed:
    ---------------------------
    Name: Event log diagnosis
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms

    Test Performed:
    ---------------------------
    Name: Internal state check
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms

    Test Performed:
    ---------------------------
    Name: Check for pending package install
    Result: Completed successfully. Error code = 0x0
    Time taken = 2406 ms

    Test Performed:
    ---------------------------
    Name: Boot status test
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms

    Root cause found:
    ---------------------------
    Boot status indicates that the OS booted successfully.

    ---------------------------
    ---------------------------
    Session details
    ---------------------------
    System Disk = \Device\Harddisk0
    Windows directory = C:\WINDOWS
    AutoChk Run = 0
    Number of root causes = 1

    Test Performed:
    ---------------------------
    Name: Check for updates
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms

    Test Performed:
    ---------------------------
    Name: System disk test
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms

    Test Performed:
    ---------------------------
    Name: Disk failure diagnosis
    Result: Completed successfully. Error code = 0x0
    Time taken = 125 ms

    Test Performed:
    ---------------------------
    Name: Disk metadata test
    Result: Completed successfully. Error code = 0x0
    Time taken = 2235 ms

    Test Performed:
    ---------------------------
    Name: Disk metadata test
    Result: Completed successfully. Error code = 0x0
    Time taken = 15 ms

    Test Performed:
    ---------------------------
    Name: Target OS test
    Result: Completed successfully. Error code = 0x0
    Time taken = 16 ms

    Test Performed:
    ---------------------------
    Name: Volume content check
    Result: Completed successfully. Error code = 0x0
    Time taken = 203 ms

    Test Performed:
    ---------------------------
    Name: Boot manager diagnosis
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms

    Test Performed:
    ---------------------------
    Name: System boot log diagnosis
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms

    Test Performed:
    ---------------------------
    Name: Event log diagnosis
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms

    Test Performed:
    ---------------------------
    Name: Internal state check
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms

    Test Performed:
    ---------------------------
    Name: Check for pending package install
    Result: Completed successfully. Error code = 0x0
    Time taken = 2656 ms

    Test Performed:
    ---------------------------
    Name: Boot status test
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms

    Root cause found:
    ---------------------------
    Boot status indicates that the OS booted successfully.
     
    Detonate, Apr 5, 2018
    #11
  12. Detonate Win User
    Nothing no work. Back-up old restored. Problem gone!
     
    Detonate, Apr 6, 2018
    #12
Thema:

Command Prompt Not Opening

Loading...
  1. Command Prompt Not Opening - Similar Threads - Command Prompt Opening

  2. Command prompt not opening

    in Windows 10 BSOD Crashes and Debugging
    Command prompt not opening: Hi All, Whenever I try to open a command prompt in windows 10 it crashes automatically. Please assist how to fix the same. https://answers.microsoft.com/en-us/windows/forum/all/command-prompt-not-opening/cc3ba5c9-0dda-421b-b0af-d3e128135a1c
  3. Unable to open command prompt

    in Windows 10 Software and Apps
    Unable to open command prompt: Hi everyone, I have been unable to open command prompt for past week or so (not sure when exactly it started). I am using Windows 10 version 1909 (I have all Windows updates installed). I have read somewhere that the issue might be that the user file got corrupted and as a...
  4. Windows Command Prompt is not opening...

    in Windows 10 BSOD Crashes and Debugging
    Windows Command Prompt is not opening...: So I was trying to open the command prompt and every time the command prompt opened for a short while and it closes by itself. I mean it just flashes for a moment and I can't see a thing. I created a new administrator account and tried to open it and it worked. But I can't...
  5. Command prompt not opening

    in Windows 10 BSOD Crashes and Debugging
    Command prompt not opening: Hi, I recently installed a windows 10 update and noe cmd.exe does not work. I hvae tried many different methods to open it but all that happens is a small window flashes up ont he screen for a split second then dissapears. any ideas? s8on...
  6. Command Prompt not opening. Clicking on Command Prompt opens the default folder location in...

    in Windows 10 BSOD Crashes and Debugging
    Command Prompt not opening. Clicking on Command Prompt opens the default folder location in...: Hi, I'm using windows 10. I have no idea why my command prompt is not launching properly and is instead opening up the default folder in File Explorer i.e. File Explorer is opening up in the command prompt default start up folder. Please help. FYI. I recently downloaded...
  7. command Prompt opens by itself

    in Windows 10 BSOD Crashes and Debugging
    command Prompt opens by itself: I am running Windows 10 home version 1803 on my HP laptop, . 2 days ago the Command prompt box started opening when I start my PC and also during normal usage. The box opens for just a few seconds and then closes. What could be the cause of this and how can I stop this from...
  8. Can you open Elevated Command Prompt from Command Prompt?

    in Windows 10 Support
    Can you open Elevated Command Prompt from Command Prompt?: I have read everything I can find on Error messages regarding looping of Preparing to Repair. I can not open my computer to Windows...it never loads. I started experiencing problems a while ago. Finally, I would be able to get on line, but only for about a minute before it...
  9. I can not open command prompt.

    in Windows 10 Support
    I can not open command prompt.: I can not open command prompt. Every time I open it I got error message come up. *Sad The message is said [ The application is not start up right Press OK to close] [img] 25131
  10. Command Prompt won't open

    in Windows 10 Support
    Command Prompt won't open: Hi, whenever I try to open the Command Prompt in Win10 (cmd.exe) I get the following pop up: cmd.exe - Application Error The Application was unable to staart correctly (0XCoooo142). Click OK to close the application. I should add this was an upgrade to Win10 Any help...