If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
"Reboot to Access Restore" Fix Does Not Work
Win Me Up-to-Date: Per Q274092 I Do Not Find "wininit.ini"
to rename so Did scanreg /fix per next instructions. After first scanreg /fix On 8-24 I manually created Sys Restore Point and observed system created another hour later but I then got [paraphrase] "Must Reboot to access Restore" today (8-26). Any Ideas how to prevent continuing need to Reboot to access System Restore? Thanks! |
#2
|
|||
|
|||
try this...
Start|Run type SCANREG /FIX click OK - Windows will reboot (are you running Norton software???) -- Noel Paton (MS-MVP 2002-2004, Win9x) Nil Carborundum Illegitemi http://www.btinternet.com/~winnoel/millsrpch.htm http://tinyurl.com/6oztj Please read http://dts-l.org/goodpost.htm on how to post messages to NG's "Craig S" wrote in message ... Win Me Up-to-Date: Per Q274092 I Do Not Find "wininit.ini" to rename so Did scanreg /fix per next instructions. After first scanreg /fix On 8-24 I manually created Sys Restore Point and observed system created another hour later but I then got [paraphrase] "Must Reboot to access Restore" today (8-26). Any Ideas how to prevent continuing need to Reboot to access System Restore? Thanks! |
#3
|
|||
|
|||
Thanks, Noel. Junked Norton last year system lock-ups
(use NOD32-Spyware Blaster-Spybot S&D-AdAware 6 )& I ran scanreg /fix twice. Don't see other K-Base articles this issue. -----Original Message----- try this... Start|Run type SCANREG /FIX click OK - Windows will reboot (are you running Norton software???) -- Noel Paton (MS-MVP 2002-2004, Win9x) Nil Carborundum Illegitemi http://www.btinternet.com/~winnoel/millsrpch.htm http://tinyurl.com/6oztj Please read http://dts-l.org/goodpost.htm on how to post messages to NG's "Craig S" wrote in message ... Win Me Up-to-Date: Per Q274092 I Do Not Find "wininit.ini" to rename so Did scanreg /fix per next instructions. After first scanreg /fix On 8-24 I manually created Sys Restore Point and observed system created another hour later but I then got [paraphrase] "Must Reboot to access Restore" today (8-26). Any Ideas how to prevent continuing need to Reboot to access System Restore? Thanks! . |
#4
|
|||
|
|||
There is no KB article that mentions SCANREG /FIX but there is one that
IMO erroneously suggests SCANREG /RESTORE. Erroneously because SCANREG /RESTORE can only fix the error if it has happened in the last five days by replacing the faulty registry with a backup copy. SCANREG /FIX however fixes the problem 99.9% of the time regardless of how long ago the damage was caused by repairing the damaged entry however what that entry might be I have never managed to establish. I don't feel this particular problem is necessarily related to the use of (faulty) software from Symantec. I'll leave Noel to follow up the problem. -- Mike Maltby MS-MVP "Craig S" wrote ... Thanks, Noel. Junked Norton last year system lock-ups (use NOD32-Spyware Blaster-Spybot S&D-AdAware 6 )& I ran scanreg /fix twice. Don't see other K-Base articles this issue. |
#5
|
|||
|
|||
Thanks, Mike! FYI to assist others in future & per your
Reply 1st sentence below: Following from KB Q274092: If the previous steps do not resolve the problem ( finding & renaming "wininit.ini" to .xxx), run the following command to repair the damaged portions of your registry: scanreg /fix SYMPTOMS: When you attempt to run System Restore, you may receive the following error message: System Restore cannot run until you restart the computer. Please restart the computer, and then run System Restore again -----Original Message----- There is no KB article that mentions SCANREG /FIX but there is one that IMO erroneously suggests SCANREG /RESTORE. Erroneously because SCANREG /RESTORE can only fix the error if it has happened in the last five days by replacing the faulty registry with a backup copy. SCANREG /FIX however fixes the problem 99.9% of the time regardless of how long ago the damage was caused by repairing the damaged entry however what that entry might be I have never managed to establish. I don't feel this particular problem is necessarily related to the use of (faulty) software from Symantec. I'll leave Noel to follow up the problem. -- Mike Maltby MS-MVP "Craig S" wrote ... Thanks, Noel. Junked Norton last year system lock- ups (use NOD32-Spyware Blaster-Spybot S&D-AdAware 6 )& I ran scanreg /fix twice. Don't see other K-Base articles this issue. . |
#6
|
|||
|
|||
When the heck did that one appear?????
I know it's dated May 2003, but I'd swear the 'scanreg /fix' hasn't been in it that long! - although my records say that it's been there at least since December...... Doh! Thanks for pointing it out! -- Noel Paton (MS-MVP 2002-2004, Win9x) Nil Carborundum Illegitemi http://www.btinternet.com/~winnoel/millsrpch.htm http://tinyurl.com/6oztj Please read http://dts-l.org/goodpost.htm on how to post messages to NG's "FYI to Mike M - MS-MVP" wrote in message ... Thanks, Mike! FYI to assist others in future & per your Reply 1st sentence below: Following from KB Q274092: If the previous steps do not resolve the problem ( finding & renaming "wininit.ini" to .xxx), run the following command to repair the damaged portions of your registry: scanreg /fix SYMPTOMS: When you attempt to run System Restore, you may receive the following error message: System Restore cannot run until you restart the computer. Please restart the computer, and then run System Restore again -----Original Message----- There is no KB article that mentions SCANREG /FIX but there is one that IMO erroneously suggests SCANREG /RESTORE. Erroneously because SCANREG /RESTORE can only fix the error if it has happened in the last five days by replacing the faulty registry with a backup copy. SCANREG /FIX however fixes the problem 99.9% of the time regardless of how long ago the damage was caused by repairing the damaged entry however what that entry might be I have never managed to establish. I don't feel this particular problem is necessarily related to the use of (faulty) software from Symantec. I'll leave Noel to follow up the problem. -- Mike Maltby MS-MVP "Craig S" wrote ... Thanks, Noel. Junked Norton last year system lock- ups (use NOD32-Spyware Blaster-Spybot S&D-AdAware 6 )& I ran scanreg /fix twice. Don't see other K-Base articles this issue. . |
#7
|
|||
|
|||
MS are inconsistent in the wording of their KB articles when it comes to
the workings of system restore. For example KB274092 says to use scanreg /fix whereas KB303354 says to use scanreg /restore. Due to this and other inconsistencies and omissions I find it far easier to use my own postings than refer to the KB. -- Mike Maltby MS-MVP FYI to Mike M - MS-MVP wrote: Thanks, Mike! FYI to assist others in future & per your Reply 1st sentence below: Following from KB Q274092: If the previous steps do not resolve the problem ( finding & renaming "wininit.ini" to .xxx), run the following command to repair the damaged portions of your registry: scanreg /fix SYMPTOMS: When you attempt to run System Restore, you may receive the following error message: System Restore cannot run until you restart the computer. Please restart the computer, and then run System Restore again |
#8
|
|||
|
|||
Umm - thanks, Mike! - I think!g
Unfortunately, I've never had the problem, either, so have never had the opportunity to bugchase it. Craig,,,,, Now - where to go from here, if Scanreg /fix doesn't work???? thinking aloud, so this could ramble on a bit!g I ASSume that you've checked for the presence of a WININIT.INI file? - and for the presence of any malware? What's in the startup list in MSCONFIG? from the sound of it, you change the system fairly frequently - what was the reason for the manual restore point you created just before the problem hit? - what was the system point created for (it shouldn't have created one automatically as the clock would have been reset after the manual point, AIUI). Have you run any registry cleaners recently (specifically in the relevant period?) - have you got Spybot S&D set to Immunise? - did you run it in the relevant period? - what registry entries did you remove/lock/restore with it? Probably best if I sleep on it - it's been a long week! - if you can answer the above before I wake up again, then I'll see what I can find in the morning. G'night all! -- Noel Paton (MS-MVP 2002-2004, Win9x) Nil Carborundum Illegitemi http://www.btinternet.com/~winnoel/millsrpch.htm http://tinyurl.com/6oztj Please read http://dts-l.org/goodpost.htm on how to post messages to NG's "Mike M" wrote in message ... There is no KB article that mentions SCANREG /FIX but there is one that IMO erroneously suggests SCANREG /RESTORE. Erroneously because SCANREG /RESTORE can only fix the error if it has happened in the last five days by replacing the faulty registry with a backup copy. SCANREG /FIX however fixes the problem 99.9% of the time regardless of how long ago the damage was caused by repairing the damaged entry however what that entry might be I have never managed to establish. I don't feel this particular problem is necessarily related to the use of (faulty) software from Symantec. I'll leave Noel to follow up the problem. -- Mike Maltby MS-MVP "Craig S" wrote ... Thanks, Noel. Junked Norton last year system lock-ups (use NOD32-Spyware Blaster-Spybot S&D-AdAware 6 )& I ran scanreg /fix twice. Don't see other K-Base articles this issue. |
#9
|
|||
|
|||
I've had two daily Restore Points work correctly so I
presume I'm OK. Thanks to both of you for your interest! I hope I don't post you back a recurrance. -----Original Message----- Umm - thanks, Mike! - I think!g Unfortunately, I've never had the problem, either, so have never had the opportunity to bugchase it. Craig,,,,, Now - where to go from here, if Scanreg /fix doesn't work???? thinking aloud, so this could ramble on a bit!g I ASSume that you've checked for the presence of a WININIT.INI file? - and for the presence of any malware? What's in the startup list in MSCONFIG? from the sound of it, you change the system fairly frequently - what was the reason for the manual restore point you created just before the problem hit? - what was the system point created for (it shouldn't have created one automatically as the clock would have been reset after the manual point, AIUI). Have you run any registry cleaners recently (specifically in the relevant period?) - have you got Spybot S&D set to Immunise? - did you run it in the relevant period? - what registry entries did you remove/lock/restore with it? Probably best if I sleep on it - it's been a long week! - if you can answer the above before I wake up again, then I'll see what I can find in the morning. G'night all! -- Noel Paton (MS-MVP 2002-2004, Win9x) Nil Carborundum Illegitemi http://www.btinternet.com/~winnoel/millsrpch.htm http://tinyurl.com/6oztj Please read http://dts-l.org/goodpost.htm on how to post messages to NG's "Mike M" wrote in message ... There is no KB article that mentions SCANREG /FIX but there is one that IMO erroneously suggests SCANREG /RESTORE. Erroneously because SCANREG /RESTORE can only fix the error if it has happened in the last five days by replacing the faulty registry with a backup copy. SCANREG /FIX however fixes the problem 99.9% of the time regardless of how long ago the damage was caused by repairing the damaged entry however what that entry might be I have never managed to establish. I don't feel this particular problem is necessarily related to the use of (faulty) software from Symantec. I'll leave Noel to follow up the problem. -- Mike Maltby MS-MVP "Craig S" wrote ... Thanks, Noel. Junked Norton last year system lock- ups (use NOD32-Spyware Blaster-Spybot S&D-AdAware 6 )& I ran scanreg /fix twice. Don't see other K-Base articles this issue. . |
#10
|
|||
|
|||
Make sure you're OK - test System Restore using the regime on my web
site..... http://www.btinternet.com/~winnoel/quiktipsr.htm Good Luck - and let us know the EXACT error messages you get (if any - hopefully none!) -- Noel Paton (MS-MVP 2002-2004, Win9x) Nil Carborundum Illegitemi http://www.btinternet.com/~winnoel/millsrpch.htm http://tinyurl.com/6oztj Please read http://dts-l.org/goodpost.htm on how to post messages to NG's "Craig S" wrote in message ... I've had two daily Restore Points work correctly so I presume I'm OK. Thanks to both of you for your interest! I hope I don't post you back a recurrance. -----Original Message----- Umm - thanks, Mike! - I think!g Unfortunately, I've never had the problem, either, so have never had the opportunity to bugchase it. Craig,,,,, Now - where to go from here, if Scanreg /fix doesn't work???? thinking aloud, so this could ramble on a bit!g I ASSume that you've checked for the presence of a WININIT.INI file? - and for the presence of any malware? What's in the startup list in MSCONFIG? from the sound of it, you change the system fairly frequently - what was the reason for the manual restore point you created just before the problem hit? - what was the system point created for (it shouldn't have created one automatically as the clock would have been reset after the manual point, AIUI). Have you run any registry cleaners recently (specifically in the relevant period?) - have you got Spybot S&D set to Immunise? - did you run it in the relevant period? - what registry entries did you remove/lock/restore with it? Probably best if I sleep on it - it's been a long week! - if you can answer the above before I wake up again, then I'll see what I can find in the morning. G'night all! -- Noel Paton (MS-MVP 2002-2004, Win9x) Nil Carborundum Illegitemi http://www.btinternet.com/~winnoel/millsrpch.htm http://tinyurl.com/6oztj Please read http://dts-l.org/goodpost.htm on how to post messages to NG's "Mike M" wrote in message ... There is no KB article that mentions SCANREG /FIX but there is one that IMO erroneously suggests SCANREG /RESTORE. Erroneously because SCANREG /RESTORE can only fix the error if it has happened in the last five days by replacing the faulty registry with a backup copy. SCANREG /FIX however fixes the problem 99.9% of the time regardless of how long ago the damage was caused by repairing the damaged entry however what that entry might be I have never managed to establish. I don't feel this particular problem is necessarily related to the use of (faulty) software from Symantec. I'll leave Noel to follow up the problem. -- Mike Maltby MS-MVP "Craig S" wrote ... Thanks, Noel. Junked Norton last year system lock- ups (use NOD32-Spyware Blaster-Spybot S&D-AdAware 6 )& I ran scanreg /fix twice. Don't see other K-Base articles this issue. . |
|
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Sys Restore Won't Work | MAL | General | 1 | August 21st 04 09:12 PM |
how to access restore points | RB | General | 10 | August 3rd 04 05:12 AM |
COA Product ID doesn't work on restore | Brad | General | 4 | July 17th 04 06:29 PM |
Cannot ENABLE System Restore. Help! | aa | General | 0 | July 3rd 04 04:05 PM |
Making 98 work with Win Office 2000 runtimes of Access? | Brian Gaff | General | 1 | June 21st 04 06:26 PM |