Yes, my data are backed up offsite at Carbonite (very slow to recover), as well as on a USB external hard drive (both direct copy/paste AND windows files/folders backup).
I will need to update/refresh everything, especially 10-years worth of emails, all my documents, etc before proceeding with any of this.
Thanks,
MM
Sometimes you'll need to run SFC several times to get it to repair all files, and running from Command Line can work better if it presents any problems.
The point in obtaining the new installer with SP1 would be to run the Repair Install which is amazingly effective even on bloated factory preinstalls, and has always been the solution I've found to repair SFC Irreparable System Files.
Another option is to uninstall SP1 to run a Repair Install with the current DVD: http://windows.microsoft.com/en-US/w.../uninstall-sp1
Based on your hesitation with the Recovery Partition option, if you're unable to find a Win7 Installation DVD with SP1, what I would consider is wiping the HD to clean reinstall with either a slipstreamed DVD or your pre-SP1 DVD, then immediately install SP1 from Windows Updates. Make this a perfect install so you can save its image after setup and never have to reinstall again: Reinstalling Windows 7 - Windows 7 Forums
Hello, again:
I need further clarification on how to run sfc /scannow from command prompt at boot, as per my last post.
I first ran sfc /scannow from within Windows (I guess?).
But I do not understand the steps in the tutorial about how to run it offline.
The only media I have are my Windows install DVD (no SP1) and my repair disc I created in 2/2010 (also no SP1).
Since this is just a sfc /scannow (not a repair install), can I use either disk as the "source" from which to repair the system files?
If so, I do not understand steps 5 and 7 in the tutorial, as to which drive is which. (The OS partition I am trying to repair is C:, and the media from which I will be trying to run sfc will be in D: or E: (my optical drives).
Also, I assume I first need to boot into F2 in order to change the order of the boot options to put the CD first, or is that not necessary if the system is able to boot from C:?
Please advise -- I'm sorry for not understanding. With so many people replying, I am becoming a bit overwhelmed.
Also: please note, the system otherwise works fine, and I have done at least 2 warm restarts this morning without incident. So, the only mystery is whether a cold start from a normal shutdown will work.
Thanks,
MM
When you get here, in Method One use this letter as seen by WinRE not the optical drive or what you THINK the drive letter is.
OK, yes, I think I understand that part, BKD.
1) But I do not understand step 7 where one has to manually specify the drive/partition/location (sorry, I do not know the proper terminology) letters. In the tutorial, it looked as though the example used F: for both. Can you please explain a bit further?
2) And I still do not understand whether or not I need to change the boot order in the BIOS first, or am I not actually trying to boot from the repair/install disk?
3) Would I use the Windows install DVD or the repair disc I created?
4) If the system has restarted at least twice today without incident, does that in any way predict whether the problem might be resolved, in which case it might also boot OK cold? (Note: since the problem first began, it has only been cold starts that were a problem.)
5) Could you please explain further the tcpmon.ini corruption detected by sfc earlier today -- what it means, what I need to do?
6) Is it your best educated guess that trying these procedures (sfc /scannow offline, another startup repair, etc) is worth the effort, based on the severity of the corruption?
I am sorry for the torture.
It's pretty miserable at my end, too.
I sure do appreciate your assistance!
Thanks
To all the great folks helping:
UPDATE:
SFC /scannow "online": Same results as before. Only corrupt tcpmon.ini, could not fix.
SFC /scannow "offline" using Windows install DVD: Same as above (log attached).
Startup repair: No problems found. This is an improvement from when it was run on 3/16 when the problems began (and before the system restore & other fixes in the last few days).
Quick scans with KIS, MBAM and SAS: all clean (nothing suggests infection, unless this is some well-hidden rootkit that has escaped detection by both KIS & MBAM real-time protection).
Several restarts and at least 2 shutdown/cold boot sequences have been OK.
Computer is behaving normally for now.
However, everything worked for a day or so after the system restore last week, before breaking again 2 days later for no apparent reason.
Questions remaining:
1) What shall I do about corrupt tcpmon.ini? (Conflicting info on the web -- "do nothing" to "reset TCP/IP stack" to "repair install of Windows" (which is not an option for me).)
2) What else should I do now?
I am VERY grateful for your help & your patience,
Quote