After changing the motherboard you may need to reactivate your system with Microsoft. Sometimes even changing the motherboard with the same kind you will have to reactivate.
that has already been done, but didn't solve the problem.
There are all sorts of things that can cause Windows Update to return errors. Here's a couple of common ones:
There are lots of other causes, those are just a few that came to mind. MS is potentially responsible for one of the above, if our suspicious are correct, but the rest are third party software.
- Interference from AV (be it firewall, or file protection)
- Hard disk faults (can cause registry corruptions - example)
- Bugs in Windows Update (there are far too many 80B0100 errors around for it to be normal, so we think that there is a bug somewhere)
- Registry cleaners (caused 2500+ errors in this thread
Tom
i use avast, but i have not ever used a registry cleaner on this computer. i guess it could be a hard drive, but nothing became problematic until after i got my RMA motherboard back. even though i didn't change the hardware at all, windows somehow probably got buggy and thought the chipset got reset. a fresh reinstall is just such a pain, especially because only the OS in on the SDD and everything else is on an HDD. i guess if that windows updater tool works, for now that will be enough for me.
Could you copy and paste the contents of this log file for me please:
C:\Windows\Logs\CBS\CheckSUR.persist.log
Tom
that file is ridiculously huge. i can't seem to paste it or upload it to the server. any other ideas?
My Computer
At a glance
W7 64i5-2500kG.Skill 8GB DDR3 1600Radeon 7850 OC
- OS
- W7 64
- CPU
- i5-2500k
- Motherboard
- Gigabyte UD3H
- Memory
- G.Skill 8GB DDR3 1600
- Graphics Card(s)
- Radeon 7850 OC
- Sound Card
- Onboard
- Monitor(s) Displays
- Acer 27"
- Hard Drives
- OCZ SSD 60GB
- PSU
- OCZ 700w