Jump to content











Photo
- - - - -

My CMD prompt is broken and I cant figure out why


  • Please log in to reply
4 replies to this topic

#1 AnonVendetta

AnonVendetta

    Silver Member

  • Advanced user
  • 781 posts
  • Location:A new beginning.....
  • Interests:Self-development, computing

Posted 01 April 2020 - 12:28 PM

So, on the 20th, my CMD prompt broke. It launches then quickly closes. Other stuff which depends on CMD stopped working too.

Info: Win10 Ent LTSC x64
Last time of Windows/Metro app updates: approx 3 weeks ago
Last driver update: Nvidia, on the 20th
Last software install: Doom Eternal, on the 20th, from Bethesda launcher application

I had preordered this game months ago, but it was not available for download til the 20th. A few hrs later, i noticed CMD didnt work. running SFC from PowerShell reveals no corrupt files.

I contacted Bethesda support, they say this game should not have installed anything that would break CMD. Multiple people I know that bought it for PC, say their CMD works. Uninstalling/reinstalling game does not help.

I'd really like to get to bottom of this, dont want to reinstall Windows. Thanks!

#2 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 15396 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 02 April 2020 - 08:35 AM

How (exactly) are you trying to open the cmd prompt window?

 

Post also an example of some "stuff which depends on CMD".

 

Try running a simple batch with a PAUSE statement, such as:

@ECHO OFF

ECHO Hi this should stay open.

PAUSE

 

What happens?

 

:duff:

Wonko



#3 AnonVendetta

AnonVendetta

    Silver Member

  • Advanced user
  • 781 posts
  • Location:A new beginning.....
  • Interests:Self-development, computing

Posted 03 April 2020 - 06:13 AM

I was just about to try your suggestions...until I tried to boot W10 and hit a backlit black screen with a cursor. Waited several mins, nothing happens. Had to salvage my personal files and do an emergency install, all is fine now. Looks like I've been denied my chance to figure this out.

#4 rajbps

rajbps
  • Members
  • 1 posts
  •  
    United Kingdom

Posted 04 April 2020 - 08:09 AM

That sound like something went in windows 10. Do you know if this problem started after any updates by any chance?



#5 AnonVendetta

AnonVendetta

    Silver Member

  • Advanced user
  • 781 posts
  • Location:A new beginning.....
  • Interests:Self-development, computing

Posted 04 April 2020 - 08:59 AM

@rajbps: Honestly, I dont know. But, Windows being Windows, and Microsoft being Microsoft, *SOMETHING* is bound to go wrong sooner or later, even without user error. My guess is that updates probably had something to do with it, but with a delayed result. I aquitted Doom Eternal, I've reinstalled it and CMD still works.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users