[SOLVED] SFC Corruptions and Windows Update broken
- Thread starter teros
- Start date
OK, please use the name "SYSTEM" instead.
Thank you!
Richard
P.S. If this attempt succeeds, all that is left to do is run sfc /scannow one more time and check that you get a positive result. If you manage to set the SYSTEM account, and sfc /scannow gives a positive result, you are free to go :)
That is a shame. Just one final problem left (0 length file - not something SURT will pick up, hence why we re-ran SFC at the end)
We must repeat the last procedure but for a subtly different folder and another file. Please be careful to get the right folder.
But the good news is that the file you just manually replaced has been accepted by SFC :)
So...
Navigate to the C:\Windows\winsxs\amd64_microsoft-windows-w..wsupdateclient-core_31bf3856ad364e35_7.6.7600.256_none_d5f513f25190f276\ 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 (wuauclt.exe) into C:\Windows\winsxs\amd64_microsoft-windows-w..wsupdateclient-core_31bf3856ad364e35_7.6.7600.256_none_d5f513f25190f276\
Finally:
Navigate to the C:\Windows\winsxs\amd64_microsoft-windows-w..wsupdateclient-core_31bf3856ad364e35_7.6.7600.256_none_d5f513f25190f276\ 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". If it fails again, again use "SYSTEM".
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.
Please get the file from the attachment here: https://www.sysnative.com/forums/wi...ruptions-windows-update-broken.html#post42295
Then one final SFC and check for a positive result.
Good luck!
Richard
Hello again :)
I am very sorry this is dragging on a bit now. I know it probably feels like fixing without any benefit, but in its current state, Windows Update will probably work for all updates - until Microsoft releases one of their "updates for Windows Update" updates (Windows Update Agent updates), at which point it may or may not break (I genuinely do not know).
I obviously cannot stop you from walking away, and I would be more than happy to continue to help you in half a year's time or whatever if you run into difficulties then, but I would personally like to finish this off properly now.
Let's have a quick scan of wuauclt.exe to see what's going on, then we will have one last shot at a fix.
Please drop on this latest SFCFix script.
Richard
Thank you for that. Nothing got changed during the last fix. Not quite sure why???
Anyway, it is just this final file, and once this is fixed, all will be well.
Please follow the instructions included below again. However, this time, please actively delete the current wuauclt.exe file before replacing it with the one attached to this post. Please ensure that its file size is the correct 57KB (I think what is currently there will show 0KB). Only if it is correct close up the permissions and re-run SFC. If it is still incorrect, just stop and I will try to work out why it is going wrong.
Navigate to the C:\Windows\winsxs\amd64_microsoft-windows-w..wsupdateclient-core_31bf3856ad364e35_7.6.7600.256_none_d5f513f25190f276\ 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 delete wuauclt.exe from C:\Windows\winsxs\amd64_microsoft-windows-w..wsupdateclient-core_31bf3856ad364e35_7.6.7600.256_none_d5f513f25190f276\
Next, please copy in the wuauclt.exe attached to this post. Please make sure not to get it confused with any others you may have lying around. Check its file size to be sure.
Finally:
Navigate to the C:\Windows\winsxs\amd64_microsoft-windows-w..wsupdateclient-core_31bf3856ad364e35_7.6.7600.256_none_d5f513f25190f276\ 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". If it fails again, again use "SYSTEM".
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.
Richard
Awesome news!
Don't worry about it, these things happen to all of us.
You are now free to go. And I feel much happier knowing that I have fixed everything, so thank you.
Anyway, it has been an absolute pleasure to work with you. I hope you enjoy your newly working Windows Update!
And good luck getting your BSOD issues resolved too :)
Richard
Thank you :)
The BSODs certainly looked to be the VPN software. Fingers crossed for that too :)
Have a great day!
Richard
Has Sysnative Forums helped you? Please consider donating to help us support the site!