Hi,
Has anyone tried a system restore from the RC1 install disk? Mine lists about 8 restore points, but when I select one, it tells me that "You must enable System Protection for this drive." and it will not restore.. I understand that from the Brink tutorial on this topic of System Restore, that it�s supposed to be on my default. There is no way I can check to see if it is on or off, because my computer will not boot. I certainly didn�t turn it off, so I�m wondering what is going on. It doesn�t seem to make sense to create restore points if you can�t use them, but you know the old saying� It might be interesting as well as prudent to check and see if yours is turned on like it is suposed to be.
Doug
Has anyone tried a system restore from the RC1 install disk? Mine lists about 8 restore points, but when I select one, it tells me that "You must enable System Protection for this drive." and it will not restore.. I understand that from the Brink tutorial on this topic of System Restore, that it�s supposed to be on my default. There is no way I can check to see if it is on or off, because my computer will not boot. I certainly didn�t turn it off, so I�m wondering what is going on. It doesn�t seem to make sense to create restore points if you can�t use them, but you know the old saying� It might be interesting as well as prudent to check and see if yours is turned on like it is suposed to be.
Doug
System Restore works. Only thing i can think of is that your system restore files got corrupt or are too outdated to be used?
The latest point is only a few days old. If you're running RC1 can you confirm for me that System Protection is on by default. Also, have you tried it from the dvd install disk?
System Restore is on by default on RC. I would try it but the last image i have is from a few weeks ago.
When booted to the Install DVD and clicking repair, somewhere along the way, you should be offered to start a command prompt.
1. At the command prompt, type rstrui.exe, and then press ENTER.
If asked for a password, type password and press enter. If no password has been made, but it still asks you for one, just press enter.
It should tell you if system restore has started. If so, go to 3.
2. If that doesn't work, try typing this in the command prompt:
%systemroot%\system32\restore\rstrui.exe
3. close the command prompt and go directly to the restore my computer option and see if it will now run.
This is how to start system restore when in safe mode, for whatever reason, you may have to do this with the install dvd repair/restore option. I've used the install disk to run a restore and had no problems, so not sure why it isn't working for you.
Good Luck
1. At the command prompt, type rstrui.exe, and then press ENTER.
If asked for a password, type password and press enter. If no password has been made, but it still asks you for one, just press enter.
It should tell you if system restore has started. If so, go to 3.
2. If that doesn't work, try typing this in the command prompt:
%systemroot%\system32\restore\rstrui.exe
3. close the command prompt and go directly to the restore my computer option and see if it will now run.
This is how to start system restore when in safe mode, for whatever reason, you may have to do this with the install dvd repair/restore option. I've used the install disk to run a restore and had no problems, so not sure why it isn't working for you.
Good Luck
�� Quote: Originally Posted by OEM 
When booted to the Install DVD and clicking repair, somewhere along the way, you should be offered to start a command prompt.
At the command prompt, type rstrui.exe, and then press ENTER.
If asked for a password, type password and press enter. If no password has been made, but it still asks you for one, just press enter.
If that doesn't work, try typing this in the command prompt:
%systemroot%\system32\restore\rstrui.exe
If either works, close the command prompt and go directly to the restore my computer option and see if it will now run.
Good Luck
At the command prompt, type rstrui.exe, and then press ENTER.
If asked for a password, type password and press enter. If no password has been made, but it still asks you for one, just press enter.
If that doesn't work, try typing this in the command prompt:
%systemroot%\system32\restore\rstrui.exe
If either works, close the command prompt and go directly to the restore my computer option and see if it will now run.
Good Luck
from command (run as admin if possible) rstrui.exe /offline:C:\windows
If C:\ is not your win7 drive change to appropiate.
If you have a restore point set it will always choose the last point.
Hi,
Thank you for the comment. I was able to run System Restore. However, it gave me the error message that said "You must enable System Protection for this drive". As I understand it, System Protection is ON by default and I certaintly did not turn it OFF.
I have eight restore points listed and selecting any of them gives me this message. Is there any way I can turn it ON now?
Thank you for the comment. I was able to run System Restore. However, it gave me the error message that said "You must enable System Protection for this drive". As I understand it, System Protection is ON by default and I certaintly did not turn it OFF.
I have eight restore points listed and selecting any of them gives me this message. Is there any way I can turn it ON now?
Doug,
I confirm that this condition is definitely not unique. I had the same problem. Further detail: Whereas the Restore Points are listed (indicating that the System Protection and System Restore is ON), the check box for the drive cannot be filled with a check, and therefore the Next box is grayed-out. When trying to fill the check box, the response, 'You must enable System Protection for this Drive' doesn't make sense.
I couldn't use a Restore Point and didn't have an image of the system to restore. An "in place" upgrade from the install disk wouldn't work either. (Strangely, the software responded by indicating that I had booted from the disk, asked me to remove it and run the upgrade after booting normally; a rediculous suggestion.) Fortunately, I did have one other option: I used the command prompt to go to \Windows\system32\config and found that I had recent backup files for four hives. By renaming them to the active files names, my problem was solved.
The only other discussion of this condition with Win7 RC (that I can find) was in Microsoft TechNet concurrently. That's here:
Windows 7 RC Crashed On Recent Software Install
Ronnie, the moderator, offered a logical suggestion on May 30. He wrote:
I confirm that this condition is definitely not unique. I had the same problem. Further detail: Whereas the Restore Points are listed (indicating that the System Protection and System Restore is ON), the check box for the drive cannot be filled with a check, and therefore the Next box is grayed-out. When trying to fill the check box, the response, 'You must enable System Protection for this Drive' doesn't make sense.
I couldn't use a Restore Point and didn't have an image of the system to restore. An "in place" upgrade from the install disk wouldn't work either. (Strangely, the software responded by indicating that I had booted from the disk, asked me to remove it and run the upgrade after booting normally; a rediculous suggestion.) Fortunately, I did have one other option: I used the command prompt to go to \Windows\system32\config and found that I had recent backup files for four hives. By renaming them to the active files names, my problem was solved.
The only other discussion of this condition with Win7 RC (that I can find) was in Microsoft TechNet concurrently. That's here:
Windows 7 RC Crashed On Recent Software Install
Ronnie, the moderator, offered a logical suggestion on May 30. He wrote:
Go to the command prompt in the repair options. Type:Unfortunately, the man with the problem reported that it didn't work. So, unless you backed up the hives and can get to them through the command prompt, or unless you have a system image, or unless some new fix comes along from Microsoft, I don't see a way out. What I can provide is validation about the circumstances, information on what hasn't worked, suspecions that this issue is the consequence of unproven code, and some empathy.
net start vss
Press ENTER.
This should start the System Protection Service.
Type the following command.
rstrui.exe
Press ENTER.
This command should start System Restore.
Does anyone know if a solution was ever found to this problem? I've got a retail version of Win7 Pro-64, and managed to screw up my registry pretty good (combination of a missed reboot after a windows update and a clean/optimize using cleanmypc).
I've got a couple good System Restore point options, but like the others here, System Restore is claiming that System Protection isn't enabled on my C drive. Very frustrating.
I've got a couple good System Restore point options, but like the others here, System Restore is claiming that System Protection isn't enabled on my C drive. Very frustrating.
One thing to try is to run a restore from the recovery console via the install DVD - restores sometimes work without windows running that will not when inside the OS
�� Quote: Originally Posted by Barman58 One thing to try is to run a restore from the recovery console via the install DVD - restores sometimes work without windows running that will not when inside the OS
Norton Utilities blew up my registry on an optimization/defrag/compress, which caused me to have the same problem described above. I checked \windows\system32\config and there were two registry hives with "rmbak" extensions... I renamed their corresponding live hive files to a "bak" extension and copied the "rmbak" files over the live hive files. This allowed me to boot up successfully. I was then able to go into Norton Utilites and restore the original registries (don't know if that was necessary but I did it just to be safe). I then uninstalled Norton Utilities forever.
Make sure yoe go to the Norton site and download the Norton Removal tool - sometimes things remain after a full un-install.
jbaileyn, I got the exact same result, running the exact same program; Norton Utilities. Do you mind explaining how exactly you were able to boot up your system?
Sure, GTXND. Forgive me if I oversimplify but I'll include each step in case you're not familiar with navigating command lines (I was a tech support guy in college 20 years ago; old habits die hard). Also, changing registry files can be VERY DANGEROUS... I would only do it as a last resort before reinstalling Windows 7.
I first booted from the Windows 7 install disc to get to the system recovery console. I then selected Command Line. From there, I had to change from the X: drive to the C: drive by typing "C:". I then typed "cd \windows\system32\config" to get to the registry file directory. By typing "dir" I could see that two of the five hive files (default, sam, security,software, and system) had recent copies with an "rmbak" extension: default.rmbak and software.rmbak. I then executed the following commands:
ren software software.bak
copy software.rmbak software
ren default default.bak
copy default.rmbak default
I would suggest you execute the "ren" then "copy" commands as above for any other hives that have "rmbak" backups with the same date/time stamp. This ensures your registry remains in sync. You can now reboot and see if your computer comes up.
Here is an alternative suggestion if you don't have these "rmbak" files (if the above worked, don't do these steps; these would be a last-last resort before reinstalling Windows 7). From where we left off above type "dir RegBack". See what the time/date stamp is on the hive files there. If recent (use your judgment; mine is a couple days old so I would have probably used it had I not had the rmbak files, as I hadn't installed much in that time), you could do the following to restore that backup registry:
ren default default.bak
ren sam sam.bak
ren security security.bak
ren software software.bak
ren system system.bak
copy RegBack\*.*
Reboot and see what happens. If this worked, you may have to reinstall any software that was installed after the time/date stamps of the files in the RegBack directory.
One final note: I did try to restore to an earlier restore point once I made the above fixes. It kept coming up with an error. Therefore, I suggest creating a new restore point once the computer recovers, just so you have a clean one.
I first booted from the Windows 7 install disc to get to the system recovery console. I then selected Command Line. From there, I had to change from the X: drive to the C: drive by typing "C:". I then typed "cd \windows\system32\config" to get to the registry file directory. By typing "dir" I could see that two of the five hive files (default, sam, security,software, and system) had recent copies with an "rmbak" extension: default.rmbak and software.rmbak. I then executed the following commands:
ren software software.bak
copy software.rmbak software
ren default default.bak
copy default.rmbak default
I would suggest you execute the "ren" then "copy" commands as above for any other hives that have "rmbak" backups with the same date/time stamp. This ensures your registry remains in sync. You can now reboot and see if your computer comes up.
Here is an alternative suggestion if you don't have these "rmbak" files (if the above worked, don't do these steps; these would be a last-last resort before reinstalling Windows 7). From where we left off above type "dir RegBack". See what the time/date stamp is on the hive files there. If recent (use your judgment; mine is a couple days old so I would have probably used it had I not had the rmbak files, as I hadn't installed much in that time), you could do the following to restore that backup registry:
ren default default.bak
ren sam sam.bak
ren security security.bak
ren software software.bak
ren system system.bak
copy RegBack\*.*
Reboot and see what happens. If this worked, you may have to reinstall any software that was installed after the time/date stamps of the files in the RegBack directory.
One final note: I did try to restore to an earlier restore point once I made the above fixes. It kept coming up with an error. Therefore, I suggest creating a new restore point once the computer recovers, just so you have a clean one.
An update on my end, I got my system up and running by doing the same as jbaileyn - i.e. restoring the SYSTEM & SOFTWARE sections of the registry through DOS prompt. Never did find any way to get System Restore working, with it insisting that System Protection was turned off on my C: drive. I double checked it once I got booted up again, it's definitely turned on, so I don't know what the deal is . . . but it sure makes me nervous about the feature for the future.
Oh, and I tested the cleanmypc registry tools some more - the error fixing part of the software wasn't the culprit, it seems to be the registry defrag that killed my system. And my original hypothesis of it somehow being combined with a Windows Critical Update may not be accurate either, a second go-around of the defrag screwed my registry again, even without a pending update.
For what it's worth, the tech I exchanged e-mails with from Cleanmypc was very helpful. He said they're gonna do some more testing on their end to try and reproduce my results on a 64-bit OS.
Oh, and I tested the cleanmypc registry tools some more - the error fixing part of the software wasn't the culprit, it seems to be the registry defrag that killed my system. And my original hypothesis of it somehow being combined with a Windows Critical Update may not be accurate either, a second go-around of the defrag screwed my registry again, even without a pending update.
For what it's worth, the tech I exchanged e-mails with from Cleanmypc was very helpful. He said they're gonna do some more testing on their end to try and reproduce my results on a 64-bit OS.
jbaileyn, I need to thank you publicly for posting the great description of the problem you encountered and your step by step instructions for resolving it.
Apparently at about the exact same time that you submitted your post, I ran Norton Utilites' registry defrag tool on my 64x Windows 7 computer. After the program tried to restart my computer to complete the process, I only got the "blue screen of death." When neither System Restore nor Startup Repair would work to get my computer going again, I panicked.
After collecting my thoughts, I tried chatting with Norton. Their first level of tech support was unable to help me. I would have to wait a day or two for someone to get back to me. That wasn't going to work.
Then I used another computer to do a Google search. After just a couple of minutes I found your post. I followed it to the letter and it worked perfectly!
So, jbaileyn, thanks for posting so articulately about your problem and your handy solution. If you're in Northern California, I'll have to buy you a beer.
Apparently at about the exact same time that you submitted your post, I ran Norton Utilites' registry defrag tool on my 64x Windows 7 computer. After the program tried to restart my computer to complete the process, I only got the "blue screen of death." When neither System Restore nor Startup Repair would work to get my computer going again, I panicked.
After collecting my thoughts, I tried chatting with Norton. Their first level of tech support was unable to help me. I would have to wait a day or two for someone to get back to me. That wasn't going to work.
Then I used another computer to do a Google search. After just a couple of minutes I found your post. I followed it to the letter and it worked perfectly!
So, jbaileyn, thanks for posting so articulately about your problem and your handy solution. If you're in Northern California, I'll have to buy you a beer.
�� Quote: Originally Posted by Daemione Oh, and I tested the cleanmypc registry tools some more - the error fixing part of the software wasn't the culprit, it seems to be the registry defrag that killed my system. And my original hypothesis of it somehow being combined with a Windows Critical Update may not be accurate either, a second go-around of the defrag screwed my registry again, even without a pending update.
For what it's worth, the tech I exchanged e-mails with from Cleanmypc was very helpful. He said they're gonna do some more testing on their end to try and reproduce my results on a 64-bit OS.
For what it's worth, the tech I exchanged e-mails with from Cleanmypc was very helpful. He said they're gonna do some more testing on their end to try and reproduce my results on a 64-bit OS.
Still, I really want to figure out what the problem is with System Restore. As far as I can tell, it works when running it from a successful Windows boot. It's running it from the rescue/repair non-booting options where I (we) get the "System Protection is turned off" error.
jbaileyn,
Thank you so much for the fix you have posted here, I would have been screwed without it. I joined the forums just so I could thank you for what you have done, it helped me heaps! My error came about with Auslogics Regdefrag, which seemed to affect my win7 64 bit system in the same way other members have experienced.
Once again, thanks for such a clear and concise description of how to fix the problem, many thanks indeed.
Happy New Year!
Thank you so much for the fix you have posted here, I would have been screwed without it. I joined the forums just so I could thank you for what you have done, it helped me heaps! My error came about with Auslogics Regdefrag, which seemed to affect my win7 64 bit system in the same way other members have experienced.
Once again, thanks for such a clear and concise description of how to fix the problem, many thanks indeed.
Happy New Year!
I also want to publicly thank you for your post.
I did not have the .rmbak files listed so I went on to the bottom part of your post to look for answers.
I copied the files as specified out of the RegBack file. I was then able to use system restore.
Unfortunately the restores didn't fix the problem. The computer is still unable to start.
This situation makes a great case for having backups done regularly
I did not have the .rmbak files listed so I went on to the bottom part of your post to look for answers.
I copied the files as specified out of the RegBack file. I was then able to use system restore.
Unfortunately the restores didn't fix the problem. The computer is still unable to start.
This situation makes a great case for having backups done regularly
Hi just want to say that this post saved me from a full re-install of Windows.
I stupidly tried to compact my registry too last night, with the same as above.
I couldn't get into system32 via dos because when I used the dir command on C:\ it only listed "program files" and "programfiles (x86)" and a shortcut link to my d drive
Though this post gave me the idea to slave the hard drive on a working system and navigate to system32\config on the slaved drive and physically find and rename the rmbak files and move the corrupted ones away.
Hooked it back up and it worked a treat - many thanks again for all the advice here.
I stupidly tried to compact my registry too last night, with the same as above.
I couldn't get into system32 via dos because when I used the dir command on C:\ it only listed "program files" and "programfiles (x86)" and a shortcut link to my d drive
Though this post gave me the idea to slave the hard drive on a working system and navigate to system32\config on the slaved drive and physically find and rename the rmbak files and move the corrupted ones away.
Hooked it back up and it worked a treat - many thanks again for all the advice here.
Many many thanks for the workaround on this one!
I too made the mistake of using a registry defragmenter and end up in the same place with no possibility to system restore despite available points.
This really made my week.
Thanks again!
I too made the mistake of using a registry defragmenter and end up in the same place with no possibility to system restore despite available points.
This really made my week.
Thanks again!
Thanks for share. Was troubleshooting a BSOD 0x000000F4 in normal and safe mode. System restore had checkpoints but they wouldn't run, got a, "turn on drive protection error".
Anyway the manual restore of the default and software hives worked for me. Saved me a reinstall.
Anyway the manual restore of the default and software hives worked for me. Saved me a reinstall.
Many thanks jbaileyn,
You saved me from a full system restore
You saved me from a full system restore
�� Quote: Originally Posted by jbaileyn Sure, GTXND. Forgive me if I oversimplify but I'll include each step in case you're not familiar with navigating command lines (I was a tech support guy in college 20 years ago; old habits die hard). Also, changing registry files can be VERY DANGEROUS... I would only do it as a last resort before reinstalling Windows 7.
I first booted from the Windows 7 install disc to get to the system recovery console. I then selected Command Line. From there, I had to change from the X: drive to the C: drive by typing "C:". I then typed "cd \windows\system32\config" to get to the registry file directory. By typing "dir" I could see that two of the five hive files (default, sam, security,software, and system) had recent copies with an "rmbak" extension: default.rmbak and software.rmbak. I then executed the following commands:
ren software software.bak
copy software.rmbak software
ren default default.bak
copy default.rmbak default
I would suggest you execute the "ren" then "copy" commands as above for any other hives that have "rmbak" backups with the same date/time stamp. This ensures your registry remains in sync. You can now reboot and see if your computer comes up.
Here is an alternative suggestion if you don't have these "rmbak" files (if the above worked, don't do these steps; these would be a last-last resort before reinstalling Windows 7). From where we left off above type "dir RegBack". See what the time/date stamp is on the hive files there. If recent (use your judgment; mine is a couple days old so I would have probably used it had I not had the rmbak files, as I hadn't installed much in that time), you could do the following to restore that backup registry:
ren default default.bak
ren sam sam.bak
ren security security.bak
ren software software.bak
ren system system.bak
copy RegBack\*.*
Reboot and see what happens. If this worked, you may have to reinstall any software that was installed after the time/date stamps of the files in the RegBack directory.
One final note: I did try to restore to an earlier restore point once I made the above fixes. It kept coming up with an error. Therefore, I suggest creating a new restore point once the computer recovers, just so you have a clean one.
I first booted from the Windows 7 install disc to get to the system recovery console. I then selected Command Line. From there, I had to change from the X: drive to the C: drive by typing "C:". I then typed "cd \windows\system32\config" to get to the registry file directory. By typing "dir" I could see that two of the five hive files (default, sam, security,software, and system) had recent copies with an "rmbak" extension: default.rmbak and software.rmbak. I then executed the following commands:
ren software software.bak
copy software.rmbak software
ren default default.bak
copy default.rmbak default
I would suggest you execute the "ren" then "copy" commands as above for any other hives that have "rmbak" backups with the same date/time stamp. This ensures your registry remains in sync. You can now reboot and see if your computer comes up.
Here is an alternative suggestion if you don't have these "rmbak" files (if the above worked, don't do these steps; these would be a last-last resort before reinstalling Windows 7). From where we left off above type "dir RegBack". See what the time/date stamp is on the hive files there. If recent (use your judgment; mine is a couple days old so I would have probably used it had I not had the rmbak files, as I hadn't installed much in that time), you could do the following to restore that backup registry:
ren default default.bak
ren sam sam.bak
ren security security.bak
ren software software.bak
ren system system.bak
copy RegBack\*.*
Reboot and see what happens. If this worked, you may have to reinstall any software that was installed after the time/date stamps of the files in the RegBack directory.
One final note: I did try to restore to an earlier restore point once I made the above fixes. It kept coming up with an error. Therefore, I suggest creating a new restore point once the computer recovers, just so you have a clean one.
thumbs up for u Also had to say THANKYOU for the Command Prompt solution of making backups, and then copying the RegBack. Saved my entire day that I couldn't lose to ReInstalling Win after a RegDefrag.
I also registered just to thank you jbaileyn. I did the same as geekygirl above and was able to start Windows up again!
My original symptom was a black screen as soon as the initial Windows start splash screen completed.
My original symptom was a black screen as soon as the initial Windows start splash screen completed.
jbaileyn.....You are my hero. Typed everything you suggested, and it worked like a charm. THANK YOU, THANK YOU, THANK YOU.
You know, I used to have some understanding of computers, but I guess it has mostly evaporated. (I'm still using a Northgate OmniKey/Ultra keyboard if that gives you any idea of the time frame.)
In any case, even more kudos to GTXND for rescuing us from a mal-compaction of the registry by Norton Utilities. Worked like a charm.
In any case, even more kudos to GTXND for rescuing us from a mal-compaction of the registry by Norton Utilities. Worked like a charm.
jbaileyn you are the best!!!!
I had tried various forum "solutions", none worked, this was right on! I followed your steps, ended up using the second option as I did not have the "rmbak" files. Just caution everyone for some reason when I first did the steps it switched me to the "X:" drive, just make sure you switch back to the "C:" drive before executing the second option if you find the first doesn't work. I have never posted a reply on a forum, but had to register just to reply and say THANK YOU!!!!
I had tried various forum "solutions", none worked, this was right on! I followed your steps, ended up using the second option as I did not have the "rmbak" files. Just caution everyone for some reason when I first did the steps it switched me to the "X:" drive, just make sure you switch back to the "C:" drive before executing the second option if you find the first doesn't work. I have never posted a reply on a forum, but had to register just to reply and say THANK YOU!!!!
Hey.
I have a Netbook so i can not use any CD or so.
I followed the steps in the second option till "RegBack"
Now i have a problem do do theses steps:
ren default default.bak
ren sam sam.bak
ren security security.bak
ren software software.bak
ren system system.bak
copy RegBack\*.*
I tried to run the commands but it simply won't work.I get " 'system.bak' is not recogmized as an internal or external command, operable programm or batch files."
How do i exactly type in the above commandy after C:\Windows\System32\config>
It would make my life so much easier right now if i could get this fixed. Thank you very very much for your help! =)
�� Quote: Originally Posted by jbaileyn
I have a Netbook so i can not use any CD or so.
I followed the steps in the second option till "RegBack"
Now i have a problem do do theses steps:
ren default default.bak
ren sam sam.bak
ren security security.bak
ren software software.bak
ren system system.bak
copy RegBack\*.*
I tried to run the commands but it simply won't work.I get " 'system.bak' is not recogmized as an internal or external command, operable programm or batch files."
How do i exactly type in the above commandy after C:\Windows\System32\config>
It would make my life so much easier right now if i could get this fixed. Thank you very very much for your help! =)
�� Quote: Originally Posted by jbaileyn Sure, GTXND. Forgive me if I oversimplify but I'll include each step in case you're not familiar with navigating command lines (I was a tech support guy in college 20 years ago; old habits die hard). Also, changing registry files can be VERY DANGEROUS... I would only do it as a last resort before reinstalling Windows 7.
I first booted from the Windows 7 install disc to get to the system recovery console. I then selected Command Line. From there, I had to change from the X: drive to the C: drive by typing "C:". I then typed "cd \windows\system32\config" to get to the registry file directory. By typing "dir" I could see that two of the five hive files (default, sam, security,software, and system) had recent copies with an "rmbak" extension: default.rmbak and software.rmbak. I then executed the following commands:
ren software software.bak
copy software.rmbak software
ren default default.bak
copy default.rmbak default
I would suggest you execute the "ren" then "copy" commands as above for any other hives that have "rmbak" backups with the same date/time stamp. This ensures your registry remains in sync. You can now reboot and see if your computer comes up.
Here is an alternative suggestion if you don't have these "rmbak" files (if the above worked, don't do these steps; these would be a last-last resort before reinstalling Windows 7). From where we left off above type "dir RegBack". See what the time/date stamp is on the hive files there. If recent (use your judgment; mine is a couple days old so I would have probably used it had I not had the rmbak files, as I hadn't installed much in that time), you could do the following to restore that backup registry:
ren default default.bak
ren sam sam.bak
ren security security.bak
ren software software.bak
ren system system.bak
copy RegBack\*.*
Reboot and see what happens. If this worked, you may have to reinstall any software that was installed after the time/date stamps of the files in the RegBack directory.
One final note: I did try to restore to an earlier restore point once I made the above fixes. It kept coming up with an error. Therefore, I suggest creating a new restore point once the computer recovers, just so you have a clean one.
I first booted from the Windows 7 install disc to get to the system recovery console. I then selected Command Line. From there, I had to change from the X: drive to the C: drive by typing "C:". I then typed "cd \windows\system32\config" to get to the registry file directory. By typing "dir" I could see that two of the five hive files (default, sam, security,software, and system) had recent copies with an "rmbak" extension: default.rmbak and software.rmbak. I then executed the following commands:
ren software software.bak
copy software.rmbak software
ren default default.bak
copy default.rmbak default
I would suggest you execute the "ren" then "copy" commands as above for any other hives that have "rmbak" backups with the same date/time stamp. This ensures your registry remains in sync. You can now reboot and see if your computer comes up.
Here is an alternative suggestion if you don't have these "rmbak" files (if the above worked, don't do these steps; these would be a last-last resort before reinstalling Windows 7). From where we left off above type "dir RegBack". See what the time/date stamp is on the hive files there. If recent (use your judgment; mine is a couple days old so I would have probably used it had I not had the rmbak files, as I hadn't installed much in that time), you could do the following to restore that backup registry:
ren default default.bak
ren sam sam.bak
ren security security.bak
ren software software.bak
ren system system.bak
copy RegBack\*.*
Reboot and see what happens. If this worked, you may have to reinstall any software that was installed after the time/date stamps of the files in the RegBack directory.
One final note: I did try to restore to an earlier restore point once I made the above fixes. It kept coming up with an error. Therefore, I suggest creating a new restore point once the computer recovers, just so you have a clean one.
I still can't believe that worked. Some of the commands said "Command not found". But I typed in exactly what was said. Pressed Restart. Chose boot normally.BAM, there was my logon. Best feeling ever. thank you!!!!!!!!!!!!!!
�� Quote: Originally Posted by jbaileyn Here is an alternative suggestion if you don't have these "rmbak" files (if the above worked, don't do these steps; these would be a last-last resort before reinstalling Windows 7). From where we left off above type "dir RegBack". See what the time/date stamp is on the hive files there. If recent (use your judgment; mine is a couple days old so I would have probably used it had I not had the rmbak files, as I hadn't installed much in that time), you could do the following to restore that backup registry:
ren default default.bak
ren sam sam.bak
ren security security.bak
ren software software.bak
ren system system.bak
copy RegBack\*.*
Reboot and see what happens. If this worked, you may have to reinstall any software that was installed after the time/date stamps of the files in the RegBack directory.
One final note: I did try to restore to an earlier restore point once I made the above fixes. It kept coming up with an error. Therefore, I suggest creating a new restore point once the computer recovers, just so you have a clean one.
ren default default.bak
ren sam sam.bak
ren security security.bak
ren software software.bak
ren system system.bak
copy RegBack\*.*
Reboot and see what happens. If this worked, you may have to reinstall any software that was installed after the time/date stamps of the files in the RegBack directory.
One final note: I did try to restore to an earlier restore point once I made the above fixes. It kept coming up with an error. Therefore, I suggest creating a new restore point once the computer recovers, just so you have a clean one.
Hello Doug,
You can try doing the following.. I hope you will be able to recover from it..
Run System Restore in Safe Mode
Start Windows in safe mode. To run Windows in safe mode, turn on or restart your computer. When the splash screen from the PC�s manufacturer is displayed, hold down the F8 key. You will see a text based screen with several options appear that will look a lot like Figure 1 below. Using the up and down arrow keys, select the option �Safe Mode�, then hit the enter key on your keyboard. The computer will start Windows in safe mode which is Windows with a limited set of files and drivers. If Windows loads normally, try repeating the instructions above.
Next start System Restore. You can access System Restore from the System Tools menu in the Accessories group. Select the restore point that you want and follow the onscreen instructions. Your computer will restart, Windows will load and present a dialog box telling you whether or not System Restore was successful. If System Restore was not successful, try the next approach.
Run System Restore in a Clean Boot Environment
Start Windows by performing a clean boot. Below, there are links to instructions for different versions of
Next start System Restore. You can access System Restore from the System Tools menu in the Accessories group. Select the restore point that you want and follow the onscreen instructions. Your computer will restart, Windows will load and present a dialog box telling you whether or not System Restore was successful.
You can try doing the following.. I hope you will be able to recover from it..
Run System Restore in Safe Mode
Start Windows in safe mode. To run Windows in safe mode, turn on or restart your computer. When the splash screen from the PC�s manufacturer is displayed, hold down the F8 key. You will see a text based screen with several options appear that will look a lot like Figure 1 below. Using the up and down arrow keys, select the option �Safe Mode�, then hit the enter key on your keyboard. The computer will start Windows in safe mode which is Windows with a limited set of files and drivers. If Windows loads normally, try repeating the instructions above.
Next start System Restore. You can access System Restore from the System Tools menu in the Accessories group. Select the restore point that you want and follow the onscreen instructions. Your computer will restart, Windows will load and present a dialog box telling you whether or not System Restore was successful. If System Restore was not successful, try the next approach.
Run System Restore in a Clean Boot Environment
Start Windows by performing a clean boot. Below, there are links to instructions for different versions of
Next start System Restore. You can access System Restore from the System Tools menu in the Accessories group. Select the restore point that you want and follow the onscreen instructions. Your computer will restart, Windows will load and present a dialog box telling you whether or not System Restore was successful.
Where do I click to indicate that this has been solved? I only see links for "unsolved".
�� Quote: Originally Posted by jmrpjb Where do I click to indicate that this has been solved? I only see links for "unsolved".
I've answered your query by PM
Cheers
Dave
Found a work around to get system restore to work when it gives you this error. Did all the rest of the things everyone proposed but all no go. Although i still have to find out if the restore will work correctly or not, as it is working on the laptop as i'm typing this on my desktop. So, the trick was to change up drive letters in command line with diskpart command. Here are the steps to do so, as soon as you have the command prompt going.
-type "diskpart" in the command line (don't type in any of the quotes on any command, just using those to simplify determining where the command starts and stops)
-type "list volume"
-Now it shows you which volume is assigned which letter. in my case system reserved was volume 1 and windows drive was volume 2. so we need to remove the C from system reserved and swap out the letters.
-for my case, i typed "select volume 1" to select system reserved, just use volume number you got from previous step.
- then type "remove letter=c"
-then select windows drive volume, for my it was volume 2, so i typed "select volume 2"
-now type "assign letter=c"
-after that you need to go back to system reserved volume, as it needs a letter to be read and is needed for system restore. so again type "select volume 1" or whatever number you had.
-and finally type "assign letter=d"
-now you just have to type "exit" to get out of diskpart.
Then either go to c:\windows\system32 and type "rstrui" or exit the command prompt and click system restore. That should've done the trick and you will not get the system protection error anymore and will be able to restore like normal. Hope this helps some of you!! enjoy!
-type "diskpart" in the command line (don't type in any of the quotes on any command, just using those to simplify determining where the command starts and stops)
-type "list volume"
-Now it shows you which volume is assigned which letter. in my case system reserved was volume 1 and windows drive was volume 2. so we need to remove the C from system reserved and swap out the letters.
-for my case, i typed "select volume 1" to select system reserved, just use volume number you got from previous step.
- then type "remove letter=c"
-then select windows drive volume, for my it was volume 2, so i typed "select volume 2"
-now type "assign letter=c"
-after that you need to go back to system reserved volume, as it needs a letter to be read and is needed for system restore. so again type "select volume 1" or whatever number you had.
-and finally type "assign letter=d"
-now you just have to type "exit" to get out of diskpart.
Then either go to c:\windows\system32 and type "rstrui" or exit the command prompt and click system restore. That should've done the trick and you will not get the system protection error anymore and will be able to restore like normal. Hope this helps some of you!! enjoy!
Jbaileyn - I never get what I need from forums...until now
Thanks for sending your advice and writing in such a way that anyone unfamiliar with command prompt could follow along. I thought I was going to have to take out in to a "professional". I'm glad I found your reply before I did...Thank you!!!
Thanks for sending your advice and writing in such a way that anyone unfamiliar with command prompt could follow along. I thought I was going to have to take out in to a "professional". I'm glad I found your reply before I did...Thank you!!!
Hi.
I have found a way to resolve this problem The command should be:
Rstrui.exe /offline:C:\windows=active thats all, you will be able to restore system...
I have found a way to resolve this problem
The command should be:Rstrui.exe /offline:C:\windows=active thats all, you will be able to restore system...
Dear all, thanks to your post System Restore failed, I also found a solution for my registry problem.
When running Windows 8.1 x64 a copy of the registry information is saved in c:\windows\system32\config\RegBack so you can make a copy of these registry files to your c:\windows\system32\config directory and that solved the issue I had of Windows 8.1 not starting up correctly after some modfication had been made manually to my registry (while using the PC Tune-Up application).
Success !
When running Windows 8.1 x64 a copy of the registry information is saved in c:\windows\system32\config\RegBack so you can make a copy of these registry files to your c:\windows\system32\config directory and that solved the issue I had of Windows 8.1 not starting up correctly after some modfication had been made manually to my registry (while using the PC Tune-Up application).
Success !
This Thread is very Old.. Why is this not solved ? and Why are people still answering it ?
�� Quote: Originally Posted by jbaileyn Sure, GTXND. Forgive me if I oversimplify but I'll include each step in case you're not familiar with navigating command lines (I was a tech support guy in college 20 years ago; old habits die hard). Also, changing registry files can be VERY DANGEROUS... I would only do it as a last resort before reinstalling Windows 7.
I first booted from the Windows 7 install disc to get to the system recovery console. I then selected Command Line. From there, I had to change from the X: drive to the C: drive by typing "C:". I then typed "cd \windows\system32\config" to get to the registry file directory. By typing "dir" I could see that two of the five hive files (default, sam, security,software, and system) had recent copies with an "rmbak" extension: default.rmbak and software.rmbak. I then executed the following commands:
ren software software.bak
copy software.rmbak software
ren default default.bak
copy default.rmbak default
I would suggest you execute the "ren" then "copy" commands as above for any other hives that have "rmbak" backups with the same date/time stamp. This ensures your registry remains in sync. You can now reboot and see if your computer comes up.
Here is an alternative suggestion if you don't have these "rmbak" files (if the above worked, don't do these steps; these would be a last-last resort before reinstalling Windows 7). From where we left off above type "dir RegBack". See what the time/date stamp is on the hive files there. If recent (use your judgment; mine is a couple days old so I would have probably used it had I not had the rmbak files, as I hadn't installed much in that time), you could do the following to restore that backup registry:
ren default default.bak
ren sam sam.bak
ren security security.bak
ren software software.bak
ren system system.bak
copy RegBack\*.*
Reboot and see what happens. If this worked, you may have to reinstall any software that was installed after the time/date stamps of the files in the RegBack directory.
One final note: I did try to restore to an earlier restore point once I made the above fixes. It kept coming up with an error. Therefore, I suggest creating a new restore point once the computer recovers, just so you have a clean one.
I first booted from the Windows 7 install disc to get to the system recovery console. I then selected Command Line. From there, I had to change from the X: drive to the C: drive by typing "C:". I then typed "cd \windows\system32\config" to get to the registry file directory. By typing "dir" I could see that two of the five hive files (default, sam, security,software, and system) had recent copies with an "rmbak" extension: default.rmbak and software.rmbak. I then executed the following commands:
ren software software.bak
copy software.rmbak software
ren default default.bak
copy default.rmbak default
I would suggest you execute the "ren" then "copy" commands as above for any other hives that have "rmbak" backups with the same date/time stamp. This ensures your registry remains in sync. You can now reboot and see if your computer comes up.
Here is an alternative suggestion if you don't have these "rmbak" files (if the above worked, don't do these steps; these would be a last-last resort before reinstalling Windows 7). From where we left off above type "dir RegBack". See what the time/date stamp is on the hive files there. If recent (use your judgment; mine is a couple days old so I would have probably used it had I not had the rmbak files, as I hadn't installed much in that time), you could do the following to restore that backup registry:
ren default default.bak
ren sam sam.bak
ren security security.bak
ren software software.bak
ren system system.bak
copy RegBack\*.*
Reboot and see what happens. If this worked, you may have to reinstall any software that was installed after the time/date stamps of the files in the RegBack directory.
One final note: I did try to restore to an earlier restore point once I made the above fixes. It kept coming up with an error. Therefore, I suggest creating a new restore point once the computer recovers, just so you have a clean one.
I appreciate the post my good friend!
...to see how many people you've helped over the years
Add me to the list! Great job. THANK YOU for saving me from a reinstall.
Add me to the list! Great job. THANK YOU for saving me from a reinstall.
Jbaileyn, thank you so much! You introduced a young 'un to the world of command prompt, and saved my computer!
Hallo guys,
I just joined cause I have problems with this blue screen. I made bootable USB with my Windows 7 64 bit and I tried to apply jbaileyn's solution but I can't change X:\Sources> to any other letter. Also, my Windows is on D partition, not on C.
System Recovery Options recognized Windows 7 on D partition but when I try to do System Restore, I get that "You must enable System Protection for this drive." message and it is related to C drive (again, my Windows 7 is on D)
I remember the cause: I did a registry clean with one old software that does not support 64bit systems. And now I feel so stupid.
Anybody has an idea what to do?
Again, I would like to apply jbaileyn's solution but when I type C: or D: it says "The syntax of the command is incorrect." and it goes back to X:\Sources>
Thanks for any suggestions!
I just joined cause I have problems with this blue screen. I made bootable USB with my Windows 7 64 bit and I tried to apply jbaileyn's solution but I can't change X:\Sources> to any other letter. Also, my Windows is on D partition, not on C.
System Recovery Options recognized Windows 7 on D partition but when I try to do System Restore, I get that "You must enable System Protection for this drive." message and it is related to C drive (again, my Windows 7 is on D)
I remember the cause: I did a registry clean with one old software that does not support 64bit systems. And now I feel so stupid.
Anybody has an idea what to do?
Again, I would like to apply jbaileyn's solution but when I type C: or D: it says "The syntax of the command is incorrect." and it goes back to X:\Sources>
Thanks for any suggestions!
Thanks a lot, it worked out! 
Avoided new clean installation of Win7. Huuhhh
Thanks a lot!!!
Avoided new clean installation of Win7. Huuhhh
Thanks a lot!!!
Thank you jbaileyn!! You, sir/madam, win the Internet... the whole thing! Struggled through a bunch of things until I found this thread. Worked first time. (Once I realized my primary hdd was actually D:, not C:, spazzed out for a second.)
�� Quote: Originally Posted by jbaileyn Here is an alternative suggestion if you don't have these "rmbak" files (if the above worked, don't do these steps; these would be a last-last resort before reinstalling Windows 7). From where we left off above type "dir RegBack". See what the time/date stamp is on the hive files there. If recent (use your judgment; mine is a couple days old so I would have probably used it had I not had the rmbak files, as I hadn't installed much in that time), you could do the following to restore that backup registry:
ren default default.bak
ren sam sam.bak
ren security security.bak
ren software software.bak
ren system system.bak
copy RegBack\*.*
Reboot and see what happens. If this worked, you may have to reinstall any software that was installed after the time/date stamps of the files in the RegBack directory.
One final note: I did try to restore to an earlier restore point once I made the above fixes. It kept coming up with an error. Therefore, I suggest creating a new restore point once the computer recovers, just so you have a clean one.
ren default default.bak
ren sam sam.bak
ren security security.bak
ren software software.bak
ren system system.bak
copy RegBack\*.*
Reboot and see what happens. If this worked, you may have to reinstall any software that was installed after the time/date stamps of the files in the RegBack directory.
One final note: I did try to restore to an earlier restore point once I made the above fixes. It kept coming up with an error. Therefore, I suggest creating a new restore point once the computer recovers, just so you have a clean one.
Spent 12 hours straight, trying to fix this
laptop again. Tried every trick in the book. I will put Linux on when the warranty expires next year. I ran my main Linux server for a week with no valid partition table, fat thumbed a command and destroyed it. The OS did not care if I killed the table, so I mirrored a drive, set-up grub and rebooted, like new again. It is a critical system with 32TB of storage on it -- has all my backups and data for a dozen years.
When it comes to the laptop, it seems I do more work keeping Windows 8.1 running than I do getting work done with it. Your post saved me! Worked like a charm. Cannot thank you enough.
DavePHL's is the preferred solution but jbailey's should work for most.
Having spend the last several days in an endless loop of Startup>Automatic Repairs not working to solve a BSOD, I want to publicly give a huge THANK YOU to jbaileyn for his solution after I had run Norton Registry Clean-up that resulted in the BSOD and no amount of solutions would fix the problem. Just like faceman had reported in his later post, my problem arose immediately after running the Norton registry clean-up process which end in a "please restart your computer" - that when the mess begins. My advice is DO NOT RUN NORTON CLEAN-UP under any circumstances. Also, I must report that my experience after contact with Norton Support (who caused the problem) was absolutely abysmal - their advice was to contact either the manufacturer or Microsoft. When I asked them to explain to me where the registry back-up file was kept - they couldn't or wouldn't. (I knew there must be a backup somewhere because the message generated before running Registry Clean-up is along the lines of "creating registry backup"). I then demanded that they either escalate the matter to a higher level or let me talk to a Manager. The response - you'll have to call back!!!
To jbaileyn you answered the questioned that Norton wouldn't - again a huge thank you to you and forums like Seven Forum for providing many many solutions to user's problems and filling a space that the big guys like MS and Norton refuse to without charging an arm and a leg.
To jbaileyn you answered the questioned that Norton wouldn't - again a huge thank you to you and forums like Seven Forum for providing many many solutions to user's problems and filling a space that the big guys like MS and Norton refuse to without charging an arm and a leg.
Không có nhận xét nào:
Đăng nhận xét