Try the Seatools test again. If the DOS one doesn't work, use the one for Windows again. Failing that, do you have a spare hard drive? We could do a test install and see if that is it. I know it'd frustrating, but we will try to get to the bottom of it.
The DOS version wouldn't run again. However the Windows version passed the drive on both the short and long generic tests.
As for a spare drive, I don't think I have one floating around that's any good, unfortunately.
Ok, that would be the best test.
Try running the sfc /scannow again
open an elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.
SFC found some things, but after 3 restarts still can't seem to repair them. CBS.log is just over 3MB, so it's beyond the upload limit here. I could try compressing it to a .zip file if you like, or run the findstr command and output to a new text file.
First look in Windows Updates for KB3022345. If it is installed, uninstall it. Then set WU to download Updates but let me decide what to install. That update will come back again. Just right click it and select hide. That should take care of it and you can set your Windows Updates as you like then.
If that is not the problem, zip them up and see if you can get below the size limit, if you can't upload them to OneDrive or Dropbox and set them to Public and we'll see if we can get Noel to come back.
That particular KB file was indeed installed, so I went ahead and uninstalled it.
Great, now set Windows Update to check with you before installing. When you see that update there, right click it and select hide. It shouldn't install again. Then you should be able to set Windows update back to automatic if you want to.
After a reboot after uninstalling that update, try the system file scanner again.
SFC results remained the same: it found things but was unable to repair.
I actually zipped up CBS.log (7zip; .zip file type; ultra compression) prior to doing this, just to see if the file size was going to pass the site's requirement (which it does); do you want me to send that copy and a copy of the new one, or just the newest?
Or take another path entirely?
Alrighty, here they are.
Quote