Announcement

Collapse
No announcement yet.

Farg'n M$ $M$ POS...

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    So try using REGEDT32.EXE instead
    Been there, done that, got the t-shirt, didn't work. Even logged into Regedt32.exe as the SYSTEM user.

    I'm working on getting Windows PE and a couple of other recommedned tools. Will let you know when I have a fix.

    Jammrock
    “Inside every sane person there’s a madman struggling to get out”
    –The Light Fantastic, Terry Pratchett

    Comment


    • #17
      Originally posted by Jammrock
      Very interesting. I'll see if I can get a copy of it somewhere.

      Jammrock
      ERD Commander 2002 might help you too. From www.winternals.com

      Comment


      • #18
        Originally posted by Kurt
        ERD Commander 2002 might help you too. From www.winternals.com
        Have a copy of that, haven't had time to test it.

        Jammrock
        “Inside every sane person there’s a madman struggling to get out”
        –The Light Fantastic, Terry Pratchett

        Comment


        • #19
          EUREKA!!!!!

          The key to the fix was WinPE! Thanks to the two MURCers for getting me a copy

          Quick sum of the fix:

          1) Boot to the WinPE CD and wait for the 'factory -winpe' command to finish and the blinking cursor in the command prompt window.

          2) Run regedit by typing: REGEDIT

          3) Go to: File -> Load Hive... Click OK through the errors.

          4) In the 'Load Hive' dialoge window, find your way to C:\WINNT\SYSTEM32\CONFIG (or where ever your Windows installation is) and load the file called: SOFTWARE (there is no file extension).

          5) You will be asked to provide a key name, it doesn't matter what you call it as long as you do not duplicate another key name on the branch, so I will call it: SMS

          6) Expand the SMS key until you reach 'Microsoft' and click/highlight the Microsoft key.

          7) Edit -> Permissions... in the main Regedit menu.

          8) Click on the 'Advanced' button and go to the 'Auditing' tab.

          9) Check both boxes at the bottom of the windows ("Inherit from parent the auditing entries..." and "Replace the auditing entries on all child objects...") and click 'Apply'.

          10) OK, OK

          11) Go to the SMS key and delete it!

          This will work for any key that is locked out by inheriting the auditing permissions from a parent object. For example if it is a sub-key of SMS that you cannot delete, but you have Full Control for the SMS key, you can inherit the Auditing permissions down the SMS key branch to delete the troubleshome key.

          That's it!

          W00T1F1C4T10N!!1!!

          Jammrock
          “Inside every sane person there’s a madman struggling to get out”
          –The Light Fantastic, Terry Pratchett

          Comment


          • #20
            Wow.

            .

            .

            I mean: Wow.

            Not exactely an easy solution?

            But Im glad You got it to work!!


            ~~DukeP~~

            Comment

            Working...
            X