Hi Iain,
Great, that's looking a lot better. SFC has found a few more corrupt files that DISM didn't detect, but they're easily fixable:
SFCFix Script
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
- Download SFCFix.exe (by niemiro) and save this to your Desktop.
- Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
- Save any open documents and close all open windows.
- On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
- Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
- SFCFix will now process the script.
- Upon completion, a file should be created on your Desktop: SFCFix.txt.
- Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.
https://dl.dropboxusercontent.com/u/16537616/Fixes/SFCFix/Scripts/iainshreeve/SFCFix.zip
SFC Scan
- Click on the Start button and in the search box, type Command Prompt
- When you see Command Prompt on the list, right-click on it and select Run as administrator
- When command prompt opens, copy and paste the following commands into it, press enter after each
sfc /scannow
- Upload your CBS log again (hopefully for the last time!)
After this has run, try running Windows Update and let me know how it goes.
Fingers crossed!
Tom
P.S. Thanks for letting me know the command didn't go through, I can see exactly where the error lies. The strings with the percent symbols at either end are called environment variables and are a feature of Windows that is very helpful to us helpers. When something calls an environment variable, Windows will lookup the location and carry on the command with that location - this helps as it allows me to copy files to your Desktop without knowing your username. The problem in this case was that your username contains a space, so the command completely breaks as it's trying to run this:
copy C:\Windows\logs\cbs\cbs.log C:\Users\Iain & Vicki\Desktop\cbs.txt
The copy command takes the following structure: copy <source> <destination>. So in this case, it's trying to copy your CBS log to the C:\Users\Iain folder (which doesn't exist) and then it has a load of junk at the end of the command which it doesn't understand.
I've used this command for a long, long time and this is the first time it's been an issue - fortunately it's nothing dangerous, just a little inconvenient for us. It doesn't matter here as you know the drill uploading your CBS log, but if it interests you: to avoid the problems with spaces, you need to add quotes around the strings like so:
copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
(No need for one on %windir% as that's located at C:\Windows\ which can't possibly contain spaces).
