Using CMD does a force shutdown in less than 30 secs

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • m2e2
    New Member
    • Jan 2008
    • 1

    Using CMD does a force shutdown in less than 30 secs

    Hello,

    I am using a Windows XP Pro SP2. I have run Spybot, Ad-Aware, Clamwin and Symantec 10.1.6.6000 to verify if its virus related. Checked Startup and disabled it using Safemode to isolate source. Check if there was a BAT file created a few days earlier. But came up with nothing.

    Every time I used Start/Run/CMD or click CMD shortcut from Quick Launch, a second window that warns me my windows XP will force shutdown everything in less than 30 secs. Don't have even have enough time to disable it using cmd window or take a screen shot.

    I can't use CMD at all and stump on what to do.

    I'm going to try increasing the timeout to 600 secs via Start/Run/shutdown /t:600 but it will only delay.

    Can you please help me resolve my problem ?

    m2e2
  • vin1826
    New Member
    • Feb 2008
    • 1

    #2
    i've got the same problem, anybody has the solution for this????

    Comment

    • dafodil
      Contributor
      • Jul 2007
      • 389

      #3
      Simply run the cmd and type shutdown -a and enter. This will abort the shutdown. Try to check the startup for any mysterious bat or exe files.

      Comment

      • AmberJain
        Recognized Expert Contributor
        • Jan 2008
        • 922

        #4
        I faced a similar problem last year. I checked everything but got no success. But after a few days I got the problem. Actually my c:\windows\syst em32\cmd.exe file was replaced by a malicious batch file which had a shutdown command in it.
        So you must simply replace old cmd.exe with a new cmd.exe one [probably from your friend's PC]

        Comment

        • AmberJain
          Recognized Expert Contributor
          • Jan 2008
          • 922

          #5
          ~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~ ~~~~~~~
          !!!!!!!!!!!!! IMPORTANT !!!!!!!!!!!!
          ~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~ ~~~~~~~
          SORRY for a misleading post. Well when I said in my reply to this thread (check out #4 above) that

          " my c:\windows\syst em32\cmd.exe file was replaced by a malicious batch file which had a shutdown command in it. "

          I meant to say that my original cmd.exe was replaced by a malicious exe file (with same name as original cmd.exe) which called a batch file which had a shutdown command in it and caused the disaster.

          So you must simply replace malicious cmd.exe with a new cmd.exe.
          _______________ _______________ _______________ _______________ _
          SORRY AGAIN to everyone. I will make it sure that I never post such a misleading reply in future.

          Comment

          Working...