RecEnv.exe Application Error

Let me better explain my situation, because I am getting different messages now:

On startup, it fails to boot into Windows 7. I get Windows Error Recovery with 2 options: Launch Startup Repair (recommended) and Start Windows Normally

When I choose Launch Setup Repair, it says it cannot repair this computer automatically. The Problem Details are:

Problem Even Name: StartupRepairOffline
Problem Signature 01: 6.1.7600.16385
Problem Signature 02: 6.1.7600.16385
Problem Signature 03: Unknown
Problem Signature 04: 21200566
Problem Signatuer 05: AutoFailover
Problem Signature 06: 19
Problem Signature 07: BadPatch
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

I hit Finish, then it shuts down.

Then I boot into the system DVD, and selected Repair your computer, which gives me the System Recovery Options:

I selected Startup Repair, and every test was completed successfully with a 0 x 0, except one, and it said:

Root cause found:
A patch is preventing the system from starting
Repair action: System files integrity check and repair
Result: Failed. Error code = 0 x 490

The odd thing is, when I repeat this test, this same error code appears, but later on it also says:
Root cause found:
Startup repair has tried several times but still cannot determine the cause of the problem

I tried "bootrec /fixmbr" and "bootrec /fixboot" and got "The operation completed successfully messages" for both, but they didn't work.

I ran sfc from the command prompt and got the message: "There is a system repair pending which requires reboot to complete. Restart Windows and run sfc again."

I also tried "bootsect /nt60 SYS /mbr" and got the message: "Successfully updated NTFS filesystem bootcode. Successfully updated disk bootcode."

I also ran"bootrec /scanos" and "bootrec /rebuildbcd" from the command prompt and got the message: "Total identified Windows installations: 0"

Could this be my problem? That even though Windows 7 is listed above as "(recovered)", and you said previously that this not a big deal, that it could just be renamed later; that maybe Windows 7 is just corrupted beyond repair? I'm hoping that's not the case.

I really do appreciate your assistance with this.

sfc cannot be run from recovery environment. At least not that way. You're doing the SFC command to the windows recovery environment itself.

bootsect and bootrec commands are not needed now. bootsector and mbr are fine.

Why did you rebuild bcd?

It still says badpatch now (so it did rebuild succesfully?)

Problem Signature 07: BadPatch

Repair action: System files integrity check and repair
Result: Failed. Error code = 0 x 490

this is actually the saem as an offline SFC

A patch is preventing the system from starting... some patch has to be uninstalled.

In recovery environment (preferable from DVD) you can enter "system restore". Assume the following

12-jan last restore point
10-jan 12:15 another restore point
10-jan 11:59 another restore point

restore restore point 10-jan 12:15, because you did boot successfully afterwards and ceated 12 jan restore point. So go back to restore point prior to last successful boot.

Post results

The restore points I mentioned earlier have now been erased by this issue. I did a system backup two weeks ago using EaseUS Todo backup. I will have to do a reinstall, and then restore the system backup I did two weeks ago - if that's my last option.

Also, why do you think the MBR and bootsector are fine?

I rebuilt the BCD and used the bootsect and bootrec because I saw those as possible solutions to the 0 x 490 error code issue in this Forum.

I came across an option for correcting my inability to boot into Safe Mode from another Windows 7 forum: typing "rename d:\windows\system32\drivers\classpnp,sys classpnp.old" in the Windows 7 RE command prompt. But that didn't work. ( D: is where the Windows 7 partition is.)

Do you have any suggestions regarding fixing my inability to boot into Safe Mode? At least from there I could try clean booting and attempt to identify the specific problem.

Thanks again, cheers!

I came across an option for correcting my inability to boot into Safe Mode from another Windows 7 forum: typing "rename d:\windows\system32\drivers\classpnp,sys classpnp.old" in the Windows 7 RE command prompt=> most people talk about classpnp.sys errors. But that isn't he problem at all!! classpnp.sys is just the last driver loaded as on all machines. After that it freezes... so the problem is AFTER loading drivers.

your system is booting so MBR sees active partition. MBR is just a jump to load and run bootsector of partition flagged "active". That bootsector runs bootmgr and that file rads the bootmenu \boot\bcd

All work fine beacuse you are in windows!!! There is a problem within windows!!

"system backup" 2 weeks ago? How did you made that? Did you backup all partitions?

please post screenshot of disk management with all fields visible. Bootmenu will be the same or will be easy reapairable.

What partitions did you backup 2 weeks ago? Best thing to do is a restore. Because due to the memory problems the disk is somewhat corrupt!

You can access the win7 partition from within winxp. Please save important documents from that partition prior to doing a partition restore.

Do you have a bootable CD with EaseUS ToDo Backup, so you can restore? If not install EaseUS on winxp and restore from there.