Windows 10: CMD Broken

Hi, recently, I updated my NVIDIA Drivers, after this, my CMD won't start anymore, it briefly opens and then closes, even trying using the CMD via PowerShell does nothing I followed the steps from this thread: https://answers.microsoft.com/en-us...s-broken/fdbebffe-9ed5-4851-9aa0-61dbcf92bc61 , and the only thing I was able to do was opening normal CMDwithout admin privilege, it doesn't work in a new profile, please help.

:)

 

Windows and CMD- renaming a file in CMD

Steps I've done

Here what happens

• 
  turn on PC
  
• 
  start windows
  
• 
  get blue screen ( message NTFS file)
  
• 
  it reboots returns to diagnosing PC
  
• 
  Diagnose and repair fails
  
• 
  I move to advance options
  
• 
  will not reset windows , I click on CMD
  

things I've tried
commands:

reagentc /disable

reagentc /enable

*************************FAILED
not recognized
**********************************

Please advise

• 
  

 

laptop doesnt boot automatically

This is what happened.

1. Did a repair install and later disabled hibertnate in CMD.
2. Enabled legacy option ROM in BIOS.
3. After a few times startup ( i used the system in such mode for 5 days), changed boot option back to default.
4. Vola!! It boots automatically to win10 without any keypress. Tested it with many starts to confirm the same.
5. Re-enabled hibernate option using CMD and later selected Fast Startup.
6. System booted normally, without the need for any keypress.

I do not know exactly whether such steps resolved the problem or what else happened, hence cannot suggest above steps.

Many thanks to all members who helped to troubleshoot problems.

 

Is my graphics card broken?

UPDATE: Please see here.

I have a Sapphire HD 4830.

When I boot into XP all is initially fine and I am able to see the desktop.

However, when I click on the start bar and navigate a few steps, I receive an immediate white screen of death and a total irrecoverable lock-up.

I am confused about what this could mean and I would be grateful for any suggestions on the best course of action to test and repair the problem.

Does this sort of issue suggest that the graphics card is irretrievably broken?