[SOLVED] Corrupt File Not Fixed by SFCFix

[derezzed]

I installed new Windows Updates for Windows 7 on Thursday (the last of which was KB3177467). Friday morning, my laptop would no longer boot into Windows (Windows did not need to restart after installing KB3177467, so this is the first time I'd tried booting since its installation). Last night, after trying many different things, I finally got my laptop to boot back into Windows normally. (I wrote down the steps I took, in case it's pertinent.) The last thing I did, which seemed to be what got Windows booting again, was replacing windows/system32/winload.exe with windows/system32/boot/winload.exe.

After booting into Windows, I ran sfc /scannow, and it told me there were corrupted files it couldn't fix. I ran SFCFix.exe, which fixed two of three corrupt files. Then I ran sfc /scannow again, then SFCFix again, and this is the log from the final run:


SFCFix version 3.0.0.0 by niemiro.
Start time: 2016-10-17 12:36:35.959
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.








AutoAnalysis::
CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-bootres_31bf3856ad364e35_6.1.7601.17514_none_9d42c69298905ee5\bootres.dll




SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 1
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 0
SURT total detected corruption count: 0
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0
AutoAnalysis:: directive completed successfully.








Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2016-10-17 12:41:09.536
----------------------EOF-----------------------


Just to reiterate, the only thing that is wrong with my laptop at the moment (that I know of, anyway) is that sfc and SFCFix are telling me there's a corrupt file.

After creating this thread, I used SFCFixScript.txt to post the CBS logfiles to the server. It says "Collect:: directive completed successfully."

 

[Aura]

Hi derezzed :)

My name is Aura and I'll be assisting you with your issue. Follow the instructions below please.

SFCFix - Fix Time

WARNING! The following fix is specific to the user's system in this thread. No one else should follow the instructions below to apply that fix, as it could damage your system. If you need assistance with an issue, please start a new thread and someone will assist you shortly.

Follow the instructions below to download and execute a SFCFix fix, and provide the log.

• Download SFCFix and move the executable on your Desktop;
• Download the attached SFCFix.zip and move the archive to your Desktop;
  Note: Make sure that the file is named SFCFix.zip, do not rename it.
• Save any work you have open, and close every programs;
• Drag the SFCFix.zip archive file over the SFCFix.exe executable and release it;
  
  
• SFCFix will launch, let it complete;
• Once done, a file will appear on your Desktop, called SFCFix.txt;
• Open the file, then copy and paste its content in your next reply;

SFCFix.zip

 

[derezzed]

Thank you so much for your help!

I followed your directions. Here is the file text:

SFCFix version 3.0.0.0 by niemiro.
Start time: 2016-10-21 19:39:00.691
Microsoft Windows 7 Service Pack 1 - amd64
Using .zip script file at C:\Users\jenn\Desktop\SFCFix.zip [0]








PowerCopy::
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_microsoft-windows-bootres_31bf3856ad364e35_6.1.7601.17514_none_9d42c69298905ee5\bootres.dll


Successfully copied file C:\Users\jenn\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-bootres_31bf3856ad364e35_6.1.7601.17514_none_9d42c69298905ee5\bootres.dll to C:\Windows\winsxs\amd64_microsoft-windows-bootres_31bf3856ad364e35_6.1.7601.17514_none_9d42c69298905ee5\bootres.dll.


Successfully restored ownership for C:\Windows\winsxs\amd64_microsoft-windows-bootres_31bf3856ad364e35_6.1.7601.17514_none_9d42c69298905ee5\bootres.dll
Successfully restored permissions on C:\Windows\winsxs\amd64_microsoft-windows-bootres_31bf3856ad364e35_6.1.7601.17514_none_9d42c69298905ee5\bootres.dll
PowerCopy:: directive completed successfully.








Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 3 datablocks.
Finish time: 2016-10-21 19:39:03.421
Script hash: g6pi1mNH+yfEszGRaVYzu2kadSRwoPhZa0ID/E4WOH8=
----------------------EOF-----------------------



I think I was mistaken in my original post about nothing else being wrong. I use a Toshiba laptop, which came with three partitions: C: has Windows 7, D: is what it boots from, and X: is where the recovery disc is located. I did get Windows 7 booting again, but I did it by replacing winload.exe with an older version and changing which partition the computer's booting from, from D: to X:. That feels like it could be a problem in the future. (I used Cute Partition Management on the Ultimate Boot CD to change the boot flag.)

I think what caused this problem, besides Windows update, is a program I used called Win7BootUpdater.exe (I've used it for over five years, and until last week it had never caused a problem). I opened it up again, not to use but as a barometer to see if things were back to normal. Just running the program gave me the error "The bootmgr path in the BCD is either invalid or is a not yet supported type." I know absolutely nothing about the bootmgr, BCD, or any of that stuff, so I don't know what that means; I just know the error is new.

I have not tried to boot from the D: drive since replacing winload.exe. Since getting back into Windows 7, I don't want to go trying things blindly that might cause more problems. If you need a more comprehensive list of everything I did to the computer while trying to fix it, I can give you that, it's just a long list and I don't want to bombard you with information you don't need.

 

[Aura]

Are you able to give me a screenshot of your Disk Management utility so I can see how the partitions are set up?

 

[derezzed]

I went into Cute Partition Manager and double checked things while I was at it. It doesn't include the partitions' names, and it turns out, it doesn't list the partitions in order. So, the first time I ever opened up Cute Partition while trying to get my computer to boot into Windows, the boot flag = yes for the 1.46 GB partition, and I changed it to boot flag = yes for the 14.13 GB partition. It's still set to boot from the 14.13 GB partition.

At the time when I changed the boot flag, booting from the 1.46 GB partition took me to a bright turquoise screen (blank, nothing would happen, I had to do a hard reset). Changing it to boot from the 14.13 GB partition took me into the Recovery Essentials, until I replaced winload.exe, after which it loaded into Windows 7.

Attached is the screenshot of the Disk Management utility.

 

[Aura]

What if you set the boot flag for the C: partition, what happens then?

 

[derezzed]

I set the boot flag for the C: partition. It booted normally into Windows 7.

I tried opening up the Win7BootUpdater.exe program, and as it was opening it gave me these errors:
"The winload.exe path in the BCD is either invalid or is a not yet supported type"
"The winresume.exe path in the BCD is either invalid or is a not yet supported type"
"The bootmgr path in the BCD is either invalid or is a not yet supported type"

Just to be clear, I want to point out that I do not know which partition the Toshiba laptop was originally set to boot from. I don't even know which partition is which, other than the C: partition being the large one where Windows 7 is located. All I know is that the first time I opened up Cute Partition Manager, the boot flag was set for the 1.46 GB partition, but because my laptop wasn't booting up properly I don't know if that's the correct factory setting for the Toshiba laptop.

Edit: Attached is a screenshot of the Disk Management utility after having set the boot flag for the C: partition.

 

[Aura]

If you're able to boot, then it should be fine. At any point, that issue isn't really Windows Update related, so I would suggest you to continue in the Windows 7 section if you want to get to the bottom of it :) Also, as long as you're able to enter the Toshiba Recovery Environment the way you're supposed to, I don't think the rest matters. Playing with boot settings is always dangerous and I don't advice it.

 

[derezzed]

I just worry that, because the laptop stopped booting into Windows after a Windows update, that it could happen again, and since the ​Boot Configuration Data seems to be different than what's expected, next time the problem could be worse. That's only a personal fear, and if it's irrational then I'll stop worrying about the boot settings. I've never encountered this problem before, so I'm just trying to make sure I'm being as thorough as I need to be. Of course, I also don't want to make the problem worse myself by trying to fix it.

Is there any way to help prevent this from happening again in the future? Like, is there a certain number of days I should wait before installing new Windows Updates so that any problems with the updates have been found and removed?

Also, I noticed that Windows Update is telling me I have one important update to install: KB3177467, which is the update I installed just before Windows stopped booting up. Any idea if I should hide it or if this is a necessary update that I need to install? I put it into Google, and one of the results on the first page is "Windows update KB3177467 crashes windows 7 causing system to boot loop."

Windows update KB3177467 crashes windows 7 causing system to boot loop - Microsoft Community

It recommends replacing winload.efi, which is one of the few things I never tried. Back before I got Windows to boot again, I did try to rebuild the BCD the way the article suggests, and it never seemed to work (it would tell me there were zero Windows installations).

 

[Aura]

That KB is related to the Windows Servicing Stack, so I doubt it would affect winload.efi in any way. What you can try to do is create a Restore Point, try to install the update again and if it fails and you end up in the Recovery PE, restore your system to the Restore Point you created previously. This is what I would do.

 

[derezzed]

Unfortunately, that didn't work last time. One of the first things I did from System Recovery Options was try to restore my system to a Restore Point that was made before installing the new update: it threw an error and didn't complete successfully. When I went to try again, there were no Restore Points, anymore. Is that a problem that can be fixed? Or is there a similar option that's more reliable than a Windows Restore Point?

 

[Aura]

I don't know any option more reliable than a Restore Point. Obviously you could take a back-up of your Registry and restore it if things goes South, though it is something I've never tried. The other option would be a system image, even though it's not the shortest path there is.

 

[derezzed]

Unfortunately, one of the things I tried when Windows wouldn't boot was using a backup of the Registry, and that had no effect, either. I'm sure making a system image of over 500 GB would be a long process. For now, I guess I'll just not install that update. I'll probably start waiting a couple weeks to install any update that's not security related.

Thank you so much for your help! I really appreciate it, and it was very cool of you to put up with all of my questions. :)

 

[Aura]

No problem derezzed, you're welcome :)