New
#31
@Bear I don't think so - but I'd have to play with a new VM to test it out.
@Neil In that case, try booting to Safe Mode and trying from there.
@Bear I don't think so - but I'd have to play with a new VM to test it out.
@Neil In that case, try booting to Safe Mode and trying from there.
and attached... (we renamed it in order to copy it) fingers crossed...
The file has no errors in it - and no SFC scan data.
Did you actually run the SFC /SCANNOW command? if so, it doesn't appear to have worked, for some reason. Please try it again.
we ran the scan yesterday and it said no problems...
Unfortunately, what the screen says and what the log says are not always the same thing.
I've seen logs where the scan obviously stopped part-way through, but which were displayed as 'nothing found' - delving into the detail found the cause and allowed resolution.
re-scanned and nothing found... what is the scan file called? - searched for "sfcdetails.txt" and couldn't find it...
That does look OK - I'd have preferred the full CBS.log file, but...
Let's have a look at that windowsupdate.log file.
99% of the time, the 0x8024200d error you're getting simply means that the update needs to be installed using the standalone download.
Pleas download a fresh copy of the standalone from here...
https://www.microsoft.com/en-gb/down...s.aspx?id=5842
You'll need the windows6.1-KB976932-X64.exe file.
Then try running that.
If it fails, post the new windowsupdate.log file. and any log file the error shows you is created.