For when Windows XP really is on its knees

Discussion in 'Windows OS's' started by zeus, Jul 22, 2003.

  1. zeus

    zeus out of date

    Likes Received:
    0
    Trophy Points:
    36
    I found these instructions on a website you need to be a member of to read the posts..... and signups are always turned off too! so I couldnt link to it.

    So thanks to the French guy Markii at subz.

    If windows xp is that knackered it wont even boot into safe mode, and theres stuff you wanna keep, try this.

    Since its first posting many people have replied saying how well it worked for them.......
    Im off to delete some critical files to see how good it really is ;)

    He loves his English swear words.... ive changed the ones Ive seen, sorry for any I may have missed!



    TUTORIAL ABOUT HOW TO RESTORE YOUR MESSED UP WINDOWS:


    Microsoft Windows® Recovery Console

    The Recovery Console provides system repair and recovery functionality.
    Type EXIT to quit the Recovery Console and restart the computer.

    1: C:\WINDOWS

    Which Windows Installation would you like to log onto
    (To cancel, press ENTER)?


    Go ahead and hit the number 1 on your keyboard, or whichever number corresponds to the operating system you were using when havoc struck. Enter your administrator password, and then hit enter. You're in! Now it's time to run with the big dogs! Do not be afraid, dear reader, I am here to help you.

    If you type the following commands into your computer, it will work magic, akin to going back in time. There are three parts to this process, but believe me, they take much less time than reinstalling Windows XP and all your applications. So follow along with me, and keep in mind that each command must be typed exactly as you see it here. Please note that this procedure assumes that Windows XP is installed to the C:\Windows folder. Make sure to change C:\Windows to the appropriate windows folder if it's at a different location. The copy commands will answer you with a little "file copied" message. The delete commands just move on to the next line. Because of the way your Web browser displays individual lines, a command might look to you like it's two lines, so I've separated each command by an empty line. But anyway, type the whole command in one line, and when you've finished typing that command, hit the Enter key. Be sure to include the spaces I've included between each word here:
    md tmp
    copy C:\windows\system32\config\system C:\windows\tmp\system.bak
    copy C:\windows\system32\config\software C:\windows\tmp\software.bak
    copy C:\windows\system32\config\sam C:\windows\tmp\sam.bak
    copy C:\windows\system32\config\security C:\windows\tmp\security.bak
    copy C:\windows\system32\config\default C:\windows\tmp\default.bak
    delete C:\windows\system32\config\system
    delete C:\windows\system32\config\software
    delete C:\windows\system32\config\Sam
    delete C:\windows\system32\config\security
    delete C:\windows\system32\config\default
    copy C:\windows\repair\system C:\windows\system32\config\system
    copy C:\windows\repair\software C:\windows\system32\config\software
    copy C:\windows\repair\sam C:\windows\system32\config\sam
    copy C:\windows\repair\security C:\windows\system32\config\security
    copy C:\windows\repair\default C:\windows\system32\config\default
    Now you can relax for a minute. You've made it through the first part! Way to go! Now what did you just do? I'll tell you. You first made a temporary directory called "tmp" (md tmp), and then into it, you copied all the files that boot up Windows. Then you deleted all those startup files, one of which is the stinker that got you into this mess in the first place. After that, you copied into that same place fresh startup files from a special repair directory. When you reboot, Windows will look for those files where it always does, and there won't be a stinker in the bunch. The only thing is, there won't be all your settings for all those applications you run every day, either. But not to worry. Right now, you're sitting in something like a lifeboat -- it's not the original ship, but it'll get you back to where you need to go. We'll get everything back to that comfortable place, but only after we go through steps 2 and 3.

    Now type Exit and watch your computer restart into Windows XP again. Be sure not to tell it to boot from the CD this time. But wait. That's not the way you had XP set up before this disaster struck! That's OK. We're in a lifeboat right now -- this isn't your comfy cruise ship, not just yet. Hang in there. I'm going to show you how to restore your system to the way it was the moment before you told it to install that errant application, or whatever it was you did, so follow along and we'll go to part 2.

    Part 2
    Here's where you'll copy the saved registry files from their backed up location by using System Restore. This folder is not available in Recovery Console and is normally not visible -- Microsoft is protecting you from yourself by hiding it from you and locking it away from you. But we have the keys. Before you start this procedure, you'll need to change several settings to make that folder visible:

    1. Start Windows Explorer.

    2. On the Tools menu, click Folder options.

    3. Click the View tab.

    4. Under Hidden files and folders, click to select Show hidden files and folders, and then click to clear the "Hide protected operating system files (Recommended)" check box.

    5. Click Yes when the dialog box is displayed that confirms that you want to display these files.

    6. Double-click the drive where you installed Windows XP to get a list of the folders. It's important to click the correct drive.

    7. Open the System Volume Information folder. This folder appears dimmed because it is set as a super-hidden folder. If you're using the FAT32 file system, this will be easy. If you're using NTFS, it won't let you open the folder, but here's how to get around that: Right-click on that system volume information folder and select Sharing and Security. Then click the Security tab. (No security tab? Skip two paragraphs.) Click Add, and then in the box that's labeled "Enter the object names to select," type the name of the user that's at the top of the Start menu -- that's probably you. [Damn it, why do they say object names when it's people's names? I guess that's Microsoft for you.]

    Anyway, make sure you type the name the way it's listed there on the Start Menu. I made the mistake of typing my first name only and it wouldn't let me in. Type first and last name if that's how it's written on the top of the Start menu. After you've typed that in, click OK a couple of times and finally that monster will let you in.

    But what if you don't see a Security tab? Try this: Click to select the checkboxes in the "Network sharing and security" area -- one is labeled "Share this folder on the network" and the other is labeled "Allow network users to change my files." Change the share name to something short, like sysinfo. Then it'll let you in. After you're done with this entire rescue operation, you might want to go back and change these back to the way they were before, for maximum security.

    OK. Now here you are, in the inner sanctum where only the high priests go. Be not afraid, all ye who enter here. As Microsoft so eloquently puts it:

    NOTE : This folder contains one or more _restore {GUID} folders such as "_restore{87BD3667-3246-476B-923F-F86E30B3E7F8}".

    8. Open a folder that was not created at the current time. You may have to click Details on the View menu to see when these folders were created. There may be one or more folders starting with "RP x under this folder. These are restore points.

    9. Open one of these folders to locate a Snapshot subfolder; the following path is an example of a folder path to the Snapshot folder:

    C:\System Volume Information\_restore{D86480E3-73EF-47BC-A0EB-A81BE6EE3ED8}RP1Snapshot

    From the Snapshot folder, copy the following files to the C:\Windows\Tmp folder (you can use your mouse, you're in Windows now, remember?):
    _registry_user_.default
    _registry_machine_security
    _registry_machine_software
    _registry_machine_system
    _registry_machine_sam

    This is how Microsoft explains this: "These files are the backed up registry files from System Restore. Because you used the registry file created by Setup, this registry does not know that these restore points exist and are available. A new folder is created with a new GUID under System Volume Information and a restore point is created that includes a copy of the registry files that were copied during part one. This is why it is important not to use the most current folder, especially if the time stamp on the folder is the same as the current time."

    Anyway, you're still not done. Don't worry, the magic is about to begin. Believe me, if you do this in front of your friends, they'll start thinking you're some kind of god. So, heavenly father, get ready to dazzle 'em.

    Now it's time to place those files you just made visible to the Recovery Console where they belong. And to do that, we need to get back into the Recovery Console. So, make sure your CD is in the drive, and restart Windows, this time hitting any key when it tells you to do that if you want to boot from CD. Yes, you want to boot from CD, so you can launch your old cryptic pal, the Recovery Console. Type R after it goes through that file-reading routine that looks like an install but isn't. Then you're back into our dark-suited friend with its ominous command line. It's kinda like going into the basement to fix some broken pipe or something. But we're not scared. The command line is our flashlight and friend. Here we go:

    Part 3
    In part three, you delete the existing registry files, and then copy the System Restore Registry files to the C:\Windows\System32\Config folder:

    From within Recovery Console, type the following commands:
    Del c:\windows\system32\config\sam
    Del c:\windows\system32\config\security
    Del c:\windows\system32\config\software
    Del c:\windows\system32\config\default
    Del c:\windows\system32\config\system
    copy c:\windows\tmp\_registry_machine_software c:\windows\system32\config\software
    copy c:\windows\tmp\_registry_machine_system c:\windows\system32\config\system
    copy c:\windows\tmp\_registry_machine_sam c:\windows\system32\config\sam
    copy c:\windows\tmp\_registry_machine_security c:\windows\system32\config\security
    copy c:\windows\tmp\_registry_user_.default c:\windows\system32\config\default
    Now. You're done! Type exit and your computer will reboot into whichever restore file you chose. But wait. If it's not the right one, that's OK, you can now go into your System Restore area and pick a different restore point if you want. There's a whole calendar full of them in there. I bet you didn't know that Windows XP is watching just about every move you make, taking notes all the while. It can restore about any state you had on that machine. And the best part is, even when it's doing all that, it's still 10% faster than Windows 2000 according to our extensive tests here at the Midwest Test Facility. Here's how to get into that restore area if you're not happy with the current restore point:

    1. Click Start, then click All Programs.

    2. Click Accessories, and then click System Tools.

    3. Click System Restore, and then click Restore to a previous Restore Point.

    Sheesh, before this I hated the command line. Many of you probably still do. But when it saves your butt like this, you have to feel grateful. I should send out a badge of courage for all you intrepid souls who followed me into these dark gallows, the basement of Windows XP. I hope this routine was successful in bringing your computer back to life. I know how it feels to have your computer down for the count. As a wise old man once told me, "When your computer crashes, it's like your dog just died." He was so right.
     
  2. Healthsmart

    Healthsmart Geek Trainee

    Likes Received:
    0
    Trophy Points:
    1
    Will this work on windows 10 I have the exact same problem
     

Share This Page