Already tried registry "DisableCMD" and user configuration, also it works on the hidden administrator account. Managed to take this picture before it closed:
I had the same problem on the same day as you (Jan 10 2018). Then I remembered that earlier in the day Avast had put a file consent.exe in its virus chest. I restored that file and everything worked as normal again. So I guess that Avast is throwing up a false positive for that file at the moment and we both were the victims. If you are not using Avast, it might nevertheless be worth checking your consent.exe file. I do hope that this helps.
I had the same problem on the same day as you (Jan 10 2018). Then I remembered that earlier in the day Avast had put a file consent.exe in its virus chest. I restored that file and everything worked as normal again. So I guess that Avast is throwing up a false positive for that file at the moment and we both were the victims. If you are not using Avast, it might nevertheless be worth checking your consent.exe file. I do hope that this helps.
and windowsimage repair returns this:Windows Resource Protection did not find any integrity violations.
cmd still not working after restartPath :
Online : False
ImageHealthState : Healthy
RestartNeeded : False