Hey fellow enthusiasts,
CMD does not run at all and no command file can trigger it (e.g. .bat) on my built, in Windows 10.
I've been having this issue for a while now and I've been searching around for a fix, but I haven't had any luck so far.
I have tried all of the "recommended" actions on google's search results, for the first couple of pages, except formatting my machine, or getting a new SSD -as nothing else is "misbehaving".
I've been occasionally using PowerShell instead, but I am very curious and annoyed as to why my CMD behaves like that, therefore, here I am, seeking for some 💡 enlightenment 💡
Cheers,
CMD does not run at all and no command file can trigger it (e.g. .bat) on my built, in Windows 10.
I've been having this issue for a while now and I've been searching around for a fix, but I haven't had any luck so far.
I have tried all of the "recommended" actions on google's search results, for the first couple of pages, except formatting my machine, or getting a new SSD -as nothing else is "misbehaving".
I've been occasionally using PowerShell instead, but I am very curious and annoyed as to why my CMD behaves like that, therefore, here I am, seeking for some 💡 enlightenment 💡
Cheers,