New
#141
If you look in previous posts. This solution has been given on this forum by the user Sildur
But you should check the \c4a1b8896ce9fbfea96c1ee6890d52a5\ folder. It is different on every computer. You must search for the Windows10.0-kb3122947-x64.cab file and use the path accordingly.
Just checked four comps here. Two successfully updated with 22947 but the other two didn't see the update at all.
Weird or is there a rational explanation?
The original TH2 update was somewhat stable. SFC /Scannow would result in no integrity issues found. The change from .11 to .17 and any updates after that have resulted in several stability issues and begining a trend to not so stable at the moment. Updates are downloading ok but, unbalancing things around here. Not to happy with this. I wish I had solutions to offer but, it seems that most people here are experiencing there own unique problem. I have solved all my problems however, the sfc /scannow run yields integrity issues with the hash strings (does ms think joe new computer guy or advanced user can correct this) yet dism longest versions to restore health and the sfc /scannfile yeild no integrity issues found. Source files from tech bench website or the MCT cannot be found yet they are there. i.e. intsall.wim or install.esd. I got other things to do Redmond. Just sayin.