I can't get command prompt, any advise?
how to fix Sihost.exe-systems warning hard error not known windows 10
hello does anyone know how to fix Sihost.exe- systems warning hard error unknown in windows 10 I can not open pc other than safe command prompts but tend to use safe command prompt or command prompt due to other seem to lock up
happen when downloading sound driver update
Windows for home | Windows 10 | Windows update
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
55 answers
Sort by: Most helpful
-
Anonymous
2018-06-16T20:07:46+00:00 -
Anonymous
2018-06-16T16:22:06+00:00 So it looks like the new update caused a partition issue and gave you an X drive. What you need to do is go cd c:\ to get to the C drive and rerun the following
sfc /scannow
Then run
dism /online /cleanup-image /restorehealth
That should work. Remember to run it in the C drive not the X drive
How do you get to the right place to do this? Command prompt is not an option.
-
Anonymous
2018-06-16T16:06:06+00:00 How do you get to "restore previous version"??? I'm trying to do that, but I don't have any way to open anything....
-
Anonymous
2018-06-11T14:49:58+00:00 Got same error. but thanks anyway.. this was more help than I got from MS
-
Anonymous
2018-06-11T14:25:38+00:00 I faced this problem too. First it was the black screen with a long message. I restarted my com and then I received Sihost.exe and explorer.exe error messages.
Looking through all the various suggestions gave me a headache (total tech noob here).
What I did was forcing my com to enter automatic repair (reboot the com 3 times).
Troubleshoot and head all the way to Restore previous version.
The restoring took about 15-20mins for me and my com is back (and hence I can type this).
I think this would be the easiest way. I don't know if it will work for everybody but it worked for me. I'm taking extra precaution not to let windows update again until this stupid update issue is solved for good.