Solved Windows 7 Pro 64 bit repair install fails

[karlsnooks]

geverl,
There is an inconsistency here. your report to Golden speaks or errors. the .txt file you posted does not show any.

would you do me a favor?
Boot up into safe mode.
run cmd.exe
cd /d %windir%/logs/cbs
del *.*
exit

Now your old cbs files are deleted.
now use following command:
sfc /scannow
you will now have a fresh cbs.log file.
due to a peculiarity of Win 7.
exit from the command prompt.
reboot back into normal mode.

now regenerate that sfcdetails.txt file

thanks,
karl

 

[geverl]

Well it still doesn't show any errors.

 

[karlsnooks]

and did sfc give you that msg about error that could not be fixed this last time?

 

[geverl]

Yes

 

[karlsnooks]

Please see Option 3 of this tutorial. Perhaps the explanation there is better.
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

 

[geverl]

This is EXACTLY what I did every time. Here is again the output of sfc /scannow:
"C:\Windows\Logs\CBS>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files but was unable to fix some of th
em.
Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example
C:\Windows\Logs\CBS\CBS.log"
And there's once again no error in the text file.
I've no explanation for it, but that's just the way it is.

 

[geverl]

Are you using the latest official ISO installer w/SP1 for the Repair Install? If not download it using steps 1 and 2 from Clean Reinstall - Factory OEM Windows 7.
I am using the official ISO SP1 installer.

Next establish a Clean Boot as shown in Troubleshooting Steps for Windows 7. If this fails to resolve the problem, then disable your AV in both listed locations.
Fails to resolve the problem.

Run SFC -SCANNOW Command as suggested until it finds no integrity violations, and then run a full Disk Check if necessary from Elevated Command Prompt .
I've already run a full disk check as documented in the other forum (cf. my first post here) and I am in no mood to waste that time again.

Have you had a bootloader such as GRUB on the HD? This may require wiping the HD to Clean the boot sector with Diskpart Clean Command before a Clean Reinstall - Factory OEM Windows 7.
I've a dual boot system with GRUB 1.99 in the MBR. Once again, I am here to AVOID a clean reinstall and I am not going to wipe my HD.

You should also not be afraid of a Clean Reinstall as it solves all problems and if you follow the steps in the tutorial will yield a perfect install which few users have. You can then save a backup image so you never have to reinstall again.
It will take me days to reinstall and reconfigure all the software, thank you very much. An operating system that is worth its name should not have to be reinstalled every year!

The process also familarizes you with your computer much more and puts an end to dragging out frustration. We are also here to help you at every step, and are the recognized leaders in this field.

If you are the recognized leaders in the field, how come nobody seems to be able to understand what's happening with my system?

 

[gregrocker]

You didn't report back a single step which I gave you and then ask me this?

I was referring to Clean Reinstall, to reassure you that we would have your back because I read that you were worried about having to do that.

You'll get no help insulting volunteers who have helped thousands of users here, and have been awarded the highest honors in the tech world for it.

Take it to a shop.

 

[karlsnooks]

geverl,

Since I can not explain what is showing, then the alternatives are two:
1. zip up the cbs.log file and upload. I'll read the entire file (and use find) to tocate the corrupt entries
or
2. follow the excellent detailed instructions and procedures given by GregRocker.

What I had thought would be quick and simple (and always has been) is sure dragging out.

and true, in this much time you would have been able to complete all of Greg's recommendations.

 

[geverl]

You didn't report back a single step which I gave you and then ask me this?

I was referring to Clean Reinstall, to reassure you that we would have your back because I read that you were worried about having to do that.

You'll get no help insulting volunteers who have helped thousands of users here, and have been awarded the highest honors in the tech world for it.

Take it to a shop.

I'm lost here: it is my understanding that a "Clean Reinstall" will require me to reinstall all software and reconfigure everything. Am I missing something?

I am not insulting anyone.

 

[geverl]

You didn't report back a single step which I gave you and then ask me this?

I was referring to Clean Reinstall, to reassure you that we would have your back because I read that you were worried about having to do that.

You'll get no help insulting volunteers who have helped thousands of users here, and have been awarded the highest honors in the tech world for it.

Take it to a shop.

I don't know whether you saw it, but I did comment on your different points within the quote.

 

[gregrocker]

I've a dual boot system with GRUB 1.99 in the MBR. Once again, I am here to AVOID a clean reinstall and I am not going to wipe my HD.

This is a known issue with GRUB bootloader on the HD. It corrupts Win7 in many ways including blocking a Repair Install. The only solution at that point is to Clean Reinstall making sure to wipe the HD using Diskpart Clean Command .

As I explained earler you only have to get a Clean Reinstall once then save a Win7 backup image to use in place of future reinstalls, to re-image the HD or its replacement in 20 minutes.

The only safe way to dual boot using GRUB is on separate HD's or using this procedure outlined by one of our Moderators: Dual boot Ubuntu-Win7

One intermediate step you might try is to backup Ubuntu partition using Macrium, then wipe that partition using free Partition Wizard which may remove GRUB sufficiently to resolve the Win7 corruption. Partition Wizard Use the Bootable CD - Option Two.

However it is likely the boot sector itself which needs wiping.

 

[SIW2]

Well done Noel for putting all that effort in.

There are 3 things I would try :

1. Pop the dvd in the drive, try running repair install in compatibility mode - rt click setup.exe and under the compatibility tab select the earliest o/s that is listed ( I think it is Vista SP1 ).

I am not hopeful that will work - but it's worth a go.

2. You could try replacing those 20 or so files by copying them from the dvd.You would need another o/s - or preferably a decent pe to open up the install.wim with 7-zip and copy them to their respective locations.

3. Do you have Shadow Copies?

If you can't get repair install to work - this is the best way to avoid a clean reinstall.

If so, and it is from before the trouble started - it is possible to replace the entire o/s from a shadow copy.

I would probably have done this a lot earlier.

 

[geverl]

I've a dual boot system with GRUB 1.99 in the MBR. Once again, I am here to AVOID a clean reinstall and I am not going to wipe my HD.

This is a known issue with GRUB bootloader on the HD. It corrupts Win7 in many ways including blocking a Repair Install. The only solution at that point is to Clean Reinstall making sure to wipe the HD using Diskpart Clean Command .

As I explained earler you only have to get a Clean Reinstall once then save a Win7 backup image to use in place of future reinstalls, to re-image the HD or its replacement in 20 minutes.

The only safe way to dual boot using GRUB is on separate HD's or using this procedure outlined by one of our Moderators: Dual boot Ubuntu-Win7

One intermediate step you might try is to backup Ubuntu partition using Macrium, then wipe that partition using free Partition Wizard which may remove GRUB sufficiently to resolve the Win7 corruption. Partition Wizard Use the Bootable CD - Option Two.

However it is likely the boot sector itself which needs wiping.

After 2 days of work, I'm fully operational again. Given the useless "error messages" provided by my "professional" operating system, I can only assume that gregrocker was right and that the dual boot with GRUB 1.99 in the MBR caused the problem. So I've followed the instructions and done a diskpart clean on the whole disk, then a reinstall of everything.

Many thanks to all of you for your energy and efforts to help, which I very much appreciate.

Cheers,

Gilles

 

[carrotguy]

Simple Fix

Assign a drive letter to that hidden partition and everything should be ok.

Hope this helps someone else out.