Win 10 booting into command prompt

There's a thread about this from almost two years ago - windows boots into black screen with command prompt - but I tried adding the suggested code and still am booting into the command prompt. I type explorer.exe and all is well till the next boot. I have attached a screenshot of Autoruns and Regedit startup.

Check out the date on the fist two entries in Autoruns, year is 1917!

I don't know where to go from here, and help is appreciated!

Windows Version 1809, OS Build 17763.1039

Run SFC Command in Windows 10 | Tutorials




Have you tried running some file repairs, such as sfc and dism?

I tried sfc /scannow and it said there were some files it couldn't fix, pointing me to a log file that was filled with arcane information, none of which was labeled as a problem file. Will try dism.

In regedt goto HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Shell it should have explorer as a value if it has cmd prompt thats the problem change it more details Black Screen and Command Prompt Open at Logon - No Explorer Shell >> Winhelponline

chroma601 said:

I tried sfc /scannow and it said there were some files it couldn't fix, pointing me to a log file that was filled with arcane information, none of which was labeled as a problem file. Will try dism.

Yes, DISM can repair the Component Store that SFC relies on to do its repairs. You may need to go through the DISM followed by SFC cycle up to three time to complete all possible repairs, rebooting after each.

From the elevated command prompt:
"C:\windows\system32>DISM /Online /Cleanup-Image /ScanHealth

Deployment Image Servicing and Management tool
Version: 10.0.17763.771

Image Version: 10.0.17763.1039

[==========================100.0%==========================] The component store is repairable.
The operation completed successfully.

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 found corrupt files but was unable to fix some of them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag."

Is the next step a reboot and retry?

Samuria said:

In regedt goto HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Shell it should have explorer as a value if it has cmd prompt thats the problem change it more details Black Screen and Command Prompt Open at Logon - No Explorer Shell >> Winhelponline

this is probably the answer. Very common error since Vista...

chroma601 said:

Windows Resource Protection found corrupt files but was unable to fix some of them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag."

Is the next step a reboot and retry?

Use Option Five in the SFC tutorial to read the relevant results from CBS.log.

Run SFC Command in Windows 10

If they say SFC couldn't repair a file because there was a problem with the component store copy, then run DISM again, restart then run SFC again. If no component store problem was reported, just restart and run SFC again. It does say in the tutorial that...

"... Sometimes it may take running the sfc /scannow command up to 3 times with Fast Startup turned off and restarting the computer after each time to completely fix everything that it's able to".

Samuria said:

In regedt goto HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Shell it should have explorer as a value if it has cmd prompt thats the problem change it more details Black Screen and Command Prompt Open at Logon - No Explorer Shell >> Winhelponline

Unfortunately, it has explorer.exe -

- - - Updated - - -

Attached are the results of the elevated command prompt findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"

chroma601 said:

Attached are the results of the elevated command prompt findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"

It contains lines such as...
Could not reproject corrupted file \??\C:\ProgramData\Microsoft\Windows\Models\\SBCModel.json; source file in store is also corrupted

This means you need to make further repairs to the component store using DISM, after which you should restart before using SFC again.