Thank you Noel! I believe this started after the 'Win10 upgrade' that was forced on Win7 users, corrupted some of the files when I uninstalled the Win10 software. It never installed, just parked the installer files on the hard drive but the update issues started right after.
Neal
Oh good grief! - I forgot all about it
I'm snowed under at work at the moment - I'll try and post the fix over the weekend.
Sorry!
Not a problem. Work is starting to look like Snowpocalypse for me as well.Just finishing 11 days straight at work.
Neal
Youch! sorry about that, but it's been really crazy at work for the past few months
The problem I'm having here is that there have been very few times when this particular error type has appeared in a CheckSUR log - and I've forgotten how to deal with them (if I ever knew!).
In theory it should just be a case of placing the relevant files in the Winsxs folder, and running SFC to get the files in place.
I'll have to dig into my archive of updates for these files - which with luck I'll be able to do this afternoon - and see if I can find them!
I appreciate your working with me on this and I fully understand being crazy at work! If you need me to do anything (short of a shotgun blast to the hard drive), just let me know.
Neal
Hmmm - I just came across what may be the cause of the problem, which would avoid messing about with the files themselves.
Is KB3004394 installed as an update?
If so then you need to install http://support.microsoft.com/en-us/h...-then-run-wind
If it's not installed, then we'll have to do the replacement.
I looked through the installed updates and did not see KB3004394 as being installed. There are only two KB3004xxx updates installed and the 394 isn't one of them.
Quote