Troubleshooting Windows 7 Failure to Boot

gregrocker said:

sbuxman said:

mig2 said:

Thanks for your help.

Results of the Windows Defender Offline Full Scan:

Trojan:Win32/Dynamer!dtc Severe Active Remove
Exploit:Java/CVE-2012-1723.AQT Severe Active Remove
Trojan:Win32/Alureon Severe Active Remove

So do I now follow the instruction to remove them by clicking "Apply actions?" There's much larger Red Button in the window behind that says, "Clean PC." Do I click that after removing the infections?

Thanks...waiting for your recommendations.

Please follow the step given:

3. If infection cleans up enough that Windows 7 will start then run SFC -SCANNOW Command to check for damaged System files.

If not post back the virus scan results in our Security forum for expert help.

I know that Aleuron has a special tool to remove it, but our Security experts will know the latest bootable tool for all infections.

While you wait you can google each infection to research this information yourself.

If you can get into Safe Mode install, update and run Malwarebytes which is comprehensive.

You want to know that the virus is cleaned up before proceeding to Step 4.

The computer would not boot into Windows without the same white on black as before, and when I attempted to start Windows normally, I was still taken back to the white on black, so I'm posting the full scan results in the Security forum.

Also, when the Startup Repair attempted to run on its own, I was given the message: "Startup Repair cannot repair this computer automatically" I'm leaving the system right there until I hear back from the Security forum folks...discouraging...but always hopeful...I enjoy being a crimestopper : )

While you wait you can also run SFC -SCANNOW Run in Command Prompt at Boot to see if System files are ready to repair manually.

Were you able to get into Safe Mode with Networking to run Malwarebytes?

If you don't immediately find the tools recommended for each of those viruses, then I'd run another bootable A/V.

gregrocker said:

While you wait you can also run SFC -SCANNOW Run in Command Prompt at Boot to see if System files are ready to repair manually.

Were you able to get into Safe Mode with Networking to run Malwarebytes?

If you don't immediately find the tools recommended for each of those viruses, then I'd run another bootable A/V.

While I was waiting, I read the tut for SFC -SCANNOW Run in Command Prompt at Boot[/URL] to see if System files are ready to repair manually. It says that a Win7 Full Installation CD can be used or a created system repair disk. I think I have the former from a past creation (from an .iso file) using Digital River's downloaded file. Can I use it now instead of a created system repair disk? Now, I am able to get into Safe Mode with Networking, so I'll follow your suggestion to run that first.

sbuxman said:

gregrocker said:

While you wait you can also run SFC -SCANNOW Run in Command Prompt at Boot to see if System files are ready to repair manually.

Were you able to get into Safe Mode with Networking to run Malwarebytes?

If you don't immediately find the tools recommended for each of those viruses, then I'd run another bootable A/V.

While I was waiting, I read the tut for SFC -SCANNOW Run in Command Prompt at Boot[/URL] to see if System files are ready to repair manually. It says that a Win7 Full Installation CD can be used or a created system repair disk. I think I have the former from a past creation (from an .iso file) using Digital River's downloaded file. Can I use it now instead of a created system repair disk? Now, I am able to get into Safe Mode with Networking, so I'll follow your suggestion to run that first.

Never mind that last good news, Windows is running another Startup Repair on its own, so, no, I'm not actually able to get into -- and stay in -- Safe Mode With Networking.

So is it time for the full installation CD or a system repair disk to check on the damaged files, SCANNOW Run in Command Prompt at Boot?

Yes, whichever you have should work - although you'll need Installer with SP1 if you have SP1 installed as you should. It is provided in Troubleshooting step 5.

gregrocker said:

Yes, whichever you have should work - although you'll need Installer with SP1 if you have SP1 installed as you should. It is provided in Troubleshooting step 5.

Ugh...I got the following message at the end of the scan:

"Windows Resource Protection did not find any integrity violations."

Now what? I'm running it one more time just in case I get a different result.

Did the WDO scan claim to clean up the infection? Run it again to see if it did, or thinks it did.

Run Startup Repair up to 3 separate times with reboots in between each to check all parameters.

Next boot into Recovery Options Command line to run bootrec /fixmbr and bootrec /fixboot and the other commands in How to use the Bootrec.exe tool in the Windows Recovery Environment to troubleshoot and repair startup issues in Windows

gregrocker said:

Did the WDO scan claim to clean up the infection? Run it again to see if it did, or thinks it did.

Run Startup Repair up to 3 separate times with reboots in between each to check all parameters.

Next boot into Recovery Options Command line to run bootrec /fixmbr and bootrec /fixboot and the other commands in How to use the Bootrec.exe tool in the Windows Recovery Environment to troubleshoot and repair startup issues in Windows

OK, I'm starting another Full Scan using WDO. It will take 4 hours, but hey, nothing else has worked yet. Was just getting ready to try bootrec...is this the same bootrec winpart procedure mentioned in the SFC tut, i. e., the one tried by Brink...??

You can run bootrec and other commands in tut first. No harm if they don't work.