sfc /scannow and Dism problems - can't install updates

Hi guys, recent errors have come up in my system and I'm not sure what the cause is or the best way of fixing it. If I run sfc /scannow I get either this:



Or after restarting/shutting down some other message telling me a system repair is pending and requires a reboot. That's issue 1 - I have rebooted and rescanned many times now and it won't fix.

I scanned because windows is will not install a current batch of updates (it does a couple of about 10 then fails), so I ran Dism /Online /Cleanup-Image /RestoreHealth and was getting this error:



That's issue 2. Any suggestions as to how I might fix it (I'm a total noob so please be nice!). Oh also I can't open the cbs.log file and it's 45mb so I dunno if that would be any help?

Edit: It's almost as if Windows is not registering the restart, originally I wanted to turn off Hyper-V in Control Panel>Programs>Turn Windows Features Off or On. Now when I try this I get a message stating "Windows requires a reboot to return the system to it's original state". But I've restarted it loads of times and it still won't work!

I did a quick search and found another person who had the "the name of an attribute in an identity is not within the legal range" error and turns out his OS install was corrupted due to a bad RAM stick. It was 7 though. But maybe you have similar situation.

Hmm I hope not, I have 16gb RAM and it's only a year old, it's showing up in the task manager / dxdiag as the full amount but I don't know how I can be sure. Plus I don't think that would be related to windows failing to install updates right?

There is a memory diagnostic tool in Control Panel/Administrative tools and yes system corruption could cause update failures.

Not saying it IS your problem, simply trying to give you some ideas. This is one where maybe Brink (the site admin) or one of the more knowledgeable members might chime in.

Thanks for the info popeye, I ran the tool and it did indeed pick up some kind of memory problem:


Although it doesn't really tell me anything else. So really this has raised more questions than it answers:
1. Maybe this particular problem existed all along in my machine and I just never noticed and it's not related to my other issues (I have never run this tool before)
2. Could I have caused this error myself? Or is it definitely an issue at the hardware level?

If you've got time read on and I'll explain: I ask this because today, I attempted to install Virtual Box and Mac OS X. It was running nicely, until I restarted my machine and it would not boot. A quick google told me Virtual Box has compatibility issues with Hyper-V on Windows 8 and it messes up the boot sequence, and to turn off Hyper-V. The only option to boot was the System Restore Windows suggested, which I followed and wiped Virtual Box. Next I went to reinstall the Windows updates which I believe were wiped by the system restore, and that's when the reinstall failed.

So what now?! Thanks again.

First, you have to get the memory issue sorted out. How many sticks do you have? If more than one then you can pull one at a time and rerun the memory test. If only one, then you are kind of SOL and will have to buy another.

As far as the all the other goes, I know nothing about OS X and Hyper-V so not much help there.

If everything was installed with bad memory then I wouldn't trust any of it. Could have introduced subtle corruption into everything on the software side.

Yeah I know what you mean, so it sounds like one of the sticks has died or something. I guess it's hard for me to tell maybe they have been like that since installation and I never noticed because I saw 16gb in the task manager and thought great they're all fine!

I have this kit which consists of 4 sticks:

An 850w Corsair PSU so I don't think power is the issue (although I have a GTX 680 card), and the motherboard is the
(I pasted them from an email and it put them in a box...weird! ) So you think I should take each one out, load windows with one at a time and run the mem diagnostics tool again?

Edit: I have since managed to turn off Hyper-V, and windows is not showing up any more updates and managed to install some too, so possibly now my only issue this the RAM problem

Yes, I would pull 3 sticks, run test, add another, run test.......you get it. Good luck!