Windows 7 Won't Boot After Virus Removal

I'm running Windows 7 Ultimate?I ran ESet security and it found and deleted two infections in Appdata/roaming - (I noted that it was reading trial mode at the bottom of the windows screen which I never noticed before but at least that was when it was still functioning. I restarted the computer, was welcomed by the Asus menu screen first and then when it goes to load windows, it says "loading windows files" and then goes to the automatic repair feature. It says corrupt file in problem details and proceeds to conclude that it can't fix it. In the advanced features, I have tried the startup repair with no luck, the system restore with no luck - tried all restore points listed and after many many 30 min intervals, it comes back that it cannot restore to the previous state. There are no disk images and no memory problems. Command Prompt will run (although one time it did not and simply shut down). I booted from DVD and tried repair from that with no more luck than before, however, did find it strange that when it looked for the windows installation it found one called windows and one called Microsoft Windows - same partition size, all details the same, not sure what's up with that.

I followed the info under Windows cannot start/.exe files cannot run forum up until ubunto is concerned something about the cd and usb running I can get it to make the mbr.bin file but can't get it to recognize the usb to put it on to check it out or the balance of what's next? Also, at the Automatic System repair it reads:

Startuprepairoffline
6.1.7600.16385
6.1.7600.16385
unknown
212009913
autofailover
13
corruptfile
1033 locale 1D

It doesn't identify an actual corrupt file name it says it can't determine the root of the problem.Tried to run Windows 7 upgrade from the disk but because I'm not in windows that won't work and also because I'm running SP1 and I don't have the disk for SP1.I've downloaded Unetbootin and Ubontu but don't know how to work them to get things fixed I've also tried unloading the windows update cache but still nothing because prior to this problem it was failing on all windows updates and have noticed other people comment that that was their problem - still no luck.