BleepingComputer.com: Failed Command Prompt

Jump to content

  • 2 Pages +
  • 1
  • 2
  • You cannot start a new topic
  • You cannot reply to this topic

Failed Command Prompt

#16 User is offline   FlannelBack 

  • Forum Regular
  • PipPipPip
  • Find Topics
  • Group: Members
  • Posts: 154
  • Joined: 08-October 07

Posted 31 January 2011 - 02:38 PM

That particular command is designed to restore the OS(Windows XP in this case) security policies back to the installation defaults.

Can you do a "Search" to see if the file secsetup.inf exists? It should be in the folder C:\WINDOWS\repair.
I ask because of the error message: "Warning 2: The system cannot find the file specified".

Is Diskeeper still throwing errors when you try to do a boot time defrag?

#17 User is offline   IdahoBiker 

  • Member
  • PipPip
  • Find Topics
  • Group: Members
  • Posts: 96
  • Joined: 09-January 11
  • Gender:Male
  • Location:I_Da_Ho

Posted 31 January 2011 - 05:06 PM

View PostFlannelBack, on 31 January 2011 - 02:38 PM, said:

That particular command is designed to restore the OS(Windows XP in this case) security policies back to the installation defaults.

Can you do a "Search" to see if the file secsetup.inf exists? It should be in the folder C:\WINDOWS\repair.
I ask because of the error message: "Warning 2: The system cannot find the file specified".

Is Diskeeper still throwing errors when you try to do a boot time defrag?


Well at this point, "secsetup.inf " is right there in C:\WINDOWS\repair.
I received about 16 of these: "Warning 2: The system cannot find the file specified".
I can attach a List of the Other Warning 2 Errors if You want to Look...
as far as Diskeeper goes, will let Ya know when it runs....or attempts too....:whistle:


#18 User is offline   FlannelBack 

  • Forum Regular
  • PipPipPip
  • Find Topics
  • Group: Members
  • Posts: 154
  • Joined: 08-October 07

Posted 01 February 2011 - 11:03 PM

Quote

I can attach a List of the Other Warning 2 Errors if You want to Look...
Not at this point, but might need to look into this one "Warning 5: Access is denied. Error taking ownership of machine", depends on how things work. That Warning 5 may indicate the reason behind these two messages:

    AutoNTFS ??? We did not find the Diskeeper Boot Time String in the Registry Key and
    AutoNTFS ??? Failure to Reset the Boot Time execute Registry Key

Just have to wait and see if the secedit command took care of the problem or not. Those two messages are probably why the Diskeeper folks wanted you to run the secedit command. If Diskeeper is still having problems, you might contact their support again and tell them you executed the secedit command successfully but the results haven't solved the problem.

They might want the info from this file: Scesrv.log located in the C:\WINDOWS\Security\Logs folder. Keep us informed.

This post has been edited by FlannelBack: 01 February 2011 - 11:06 PM


#19 User is offline   mikeyww 

  • New Member
  • Pip
  • Find Topics
  • Group: Members
  • Posts: 1
  • Joined: 30-December 11

Posted 30 December 2011 - 11:50 AM

You can fix the error by copying "c:\Program Files\Diskeeper Corporation\Diskeeper\AutoNTFS.exe" to "c:\WINDOWS\system32\".

This post has been edited by mikeyww: 30 December 2011 - 12:02 PM


Share this topic:


  • 2 Pages +
  • 1
  • 2
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users