[SOLVED] SFC Corruptions and Windows Update broken

T

teros

Member
Joined
Mar 10, 2013
Posts
18
Location
FIN
Hi. I read it down this topis and wondered could You be able to help me also. I'm dealing with Win7 Enterprise and windows update.

First I had an error with shut down button showing that there are updates to be installed and when clicking shut down it started to install
them for a second and then just shutted down. And also same time windows update from start menu or control panel were not doing anything when clicking.
I tried many kind of ways to solve that but then just found that couple of dll files were missing from system32 folder.
I copied missing files from other win7 machine.

Now there are any updates to be installed in shut down button and windows update is starting - BUT with a window 'The page failed to load'.
I have tried now Fix helpers from windows support and sfc /scannow. SFC founds some files unable to repair but that's where my skills are used.
 
Hello, and welcome to Sysnative :)

Please download and install the System Update Readiness Tool from here: What is the System Update Readiness Tool?

Please save the download somewhere convenient you can later find it as we may well need it again later. Save you a second download :)

Also please be aware that the tool can take up to an hour (very occasionally even longer) to complete. Please be patient.

Once it has completed, please upload C:\Windows\Logs\CBS\CheckSUR.persist.log.

Thank you!

Richard
 
Thx. I forgot to mention yesterday that I tried to do that couple of times. Somehow installation of Windows6.1-KB947821-v26-x64.msu
does not work:

Failed.jpg

In addition to this: third time my computer made this:

BSinfo.jpg

Do You have any other ideas other than reinstalling win?

BR Tero
 
teros said:
Thx. I forgot to mention yesterday that I tried to do that couple of times. Somehow installation of Windows6.1-KB947821-v26-x64.msu
does not work:

View attachment 3524

In addition to this: third time my computer made this:

View attachment 3525

Do You have any other ideas other than reinstalling win?

BR Tero
Click to expand...

Don't worry, we shouldn't have to reinstall Windows, certainly not yet :) Your primary problem is caused by a corrupt Windows Update agent, hence why SURT won't install. Then there is a small secondary inconvenience I will use SURT to help fix after that. And, hopefully, you will then be good to go :)

So, let's go after the Windows Update Agent corruption first.

WARNING: This fix has been created specifically for this user. If you are not this user, do not follow these instructions as you may cause serious harm to your computer.

Download a copy of SFCFixScript.zip attached to this post, and save it to your Desktop.

Then download a copy of SFCFix.exe from here: https://www.sysnative.com/forums/downloads/sfcfix/, and also save it to your Desktop.

Single click on SFCFixScript.zip and drag and drop it on top of SFCFix.exe. SFCFix will open and perform a fix.

A logfile called SFCFix.txt will open (and be saved to your Desktop). Please copy and paste the report into your next reply.


Next, your BSOD problem is, I think, completely unrelated to your Windows Update problem. In addition, I am a Windows Update specialist, and unfortunately do not know much about fixing BSODs. It would be for the best for you to receive help from those with experience in this area, not me. So, can I please suggest you follow these instructions here: https://www.sysnative.com/forums/bs...g-instructions-windows-8-7-windows-vista.html

and post a new thread in the BSOD Forum here: BSOD, Crashes, Kernel Debugging

They will help you with that. Please give a little note to say that I sent you, and that I do not believe your BSOD is caused by the corruptions I see in your Windows Update logfiles (which are all fairly minor).

Thank you!

Richard

P.S. Thank you so much for giving such detailed and clear posts informing me of what is going on. It really makes my job much easier :)
 

Attachments

Last edited:
Many thx for Your time and also positive feedback.
I did as You adviced and here's the log file.

View attachment SFCFix.txt

Yes. I deal Your thoughts about BSOD problem. I think it more or less something to do with the hardware and drivers.
But I'll continue with that after the update issue is burried.

BR Tero

EDIT: I rebooted and now it installed all 14 updates which were in queue. But still if I go to Control Panel / Windowa Update ; it opens wiht text: The page failed to load. :D
But hey many thx already!
 
teros said:
Many thx for Your time and also positive feedback.
I did as You adviced and here's the log file.

View attachment 3527

Yes. I deal Your thoughts about BSOD problem. I think it more or less something to do with the hardware and drivers.
But I'll continue with that after the update issue is burried.

BR Tero

EDIT: I rebooted and now it installed all 14 updates which were in queue. But still if I go to Control Panel / Windowa Update ; it opens wiht text: The page failed to load. :D
But hey many thx already!
Click to expand...

Log looks awesome, and we are making progress :)

Please have another attempt at System Update Readiness Tool and upload C:\Windows\Logs\CBS\CheckSUR.persist.log.

Thank you!

Richard
 
I did also the CMD command and it succeed.

upandrunnig.jpg upandrunnig2.jpg

Had to say that You guys are not having MVP for no reason!
Many thx again to You niemiro aka. Richard.

I think this case is closed for now.
 
teros said:
I did also the CMD command and it succeed.

View attachment 3529 View attachment 3530

Had to say that You guys are not having MVP for no reason!
Many thx again to You niemiro aka. Richard.

I think this case is closed for now.
Click to expand...

That is great news, but...

...please wait one more post! Basically, those lines in CheckSUR.log are important.

Basically, although I have fixed Windows Update in general, it will still fail on certain types of updates. Best to fix it properly now. I will be back very shortly.

Richard
 
First, please drag and drop SFCFix2.txt on top of SFCFix.exe.It may fail. We shall see. Not to worry if it does.

Then please download Manifests.zip attached to this post. Please extract the two contained files (i.e. not the .zip file itself) into C:\Windows\Temp\CheckSur\Winsxs\Manifests

Then please re-run the System Update Readiness Tool.

Once it has finished, please upload a new C:\Windows\Logs\CBS\CheckSUR.log

We are nearly finished, just best to finish the job off properly and fix up these final corruptions so they don't come back to cause you headaches later.

Richard
 

Attachments

teros said:
Had to say that You guys are not having MVP for no reason!
Many thx again to You niemiro aka. Richard.

I think this case is closed for now.
Click to expand...

Thank you :)

I am happy to have got you this far.

As for MVP, well, that is very kind of you :) But I still don't have very many posts, not really enough for MVP.

But even if I did, which I don't, I wouldn't be eligible anyway as I am only 17 (MVP requires 18+)

Richard
 
Let's fix the last one manually and get this over and done with.

Navigate to the C:\Windows\winsxs\amd64_microsoft-windows-windowsupdateclient-ui_31bf3856ad364e35_7.6.7600.256_none_53a2379cf1953527\ folder, right click on it and select Properties.
Under the Security tab, click Advanced.
Under the Owner tab, click Edit.
Click "Other Users and Groups".
Click Advanced.
Click "Find Now".
Scroll down and double click on Everyone.
Click OK THREE times.
Click on the Permissions tab.
Under type Deny, single click on any entries and click Remove. (N.B.: There may not be any Deny entries, in which case just ignore this step. Just remove any that do exist)
Click OK.
Click Edit (now on the standard file Property window under the Security tab).
Click Add.
Click Advanced.
Click "Find Now".
Scroll down and double click on Everyone.
Click OK.
Single click on Everyone and then tick the "Full Control" box under Allow.
Click OK TWO times.

Now please extract and copy the attached file (wucltux.dll) into C:\Windows\winsxs\amd64_microsoft-windows-windowsupdateclient-ui_31bf3856ad364e35_7.6.7600.256_none_53a2379cf1953527\

Finally:

Navigate to the C:\Windows\winsxs\amd64_microsoft-windows-windowsupdateclient-ui_31bf3856ad364e35_7.6.7600.256_none_53a2379cf1953527\ folder, right click on it and select Properties.
Under the Security tab, click Advanced.
Click on the Permissions tab (should be the default tab).
Click Change Permissions
Select and click Remove onthe ALLOW: Everyone entryyou just added.
Click OK.
Go to Owner tab.
Click Edit.
Click "Other Users and Groups".
Paste in "NT Service\TrustedInstaller"
Click OK.
Put the check in "Replace owner on subcontainers and objects".
Click Yes on any message boxes which pop-up.
Click Continue on any Access is Denied messages.
Click OK out of the final message box.
Click OK out of everything.

Good luck!

Richard

P.S. Just get these instructions as close as you can - exact isn't a requirement here, strange as that may seem (there are several possible perfectly good settings - therefore it is forgiving of slight mistakes).
 

Attachments

You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top