...and after all that, the SFC results are error-free, and there are no errors in CheckSUR, or the background CBS.log
The Windowsupdate.log is also totally error-free.
The WU log shows it having installed the KB3065822 update, and completing the installs for KB3065822, KB3074886, and KB3075516.
Let's run through the list of updates you started with...
KB2676562 X 6 - first released in 2012, and not apparently re-released
KB2871997 X 7 - May 2014 - not rereleased
KB3004375 X 7 - Feb 2015
KB3011780 X 7 - Nov 2014
...
KB2882822 X 6 - Oct 2013
KB2952664 X 7 - First released in Oct 2014 - updated multiple times since (first couple had major bugs) (W8/10)
KB3035583 X 5 re-released every month since it first came out to update definitions (W10)
KB3068708 X 8 is an updated version of KB3022345 (W10)
kb2799494 X 2 Feb 2013
The ones tagged (W10) are updates related to the upgrade to Windows 10 (or Windows 8/10)
Currently Windows Updates is having some problems - but I don't honestly have a clue what they mean...
Code:
2015-07-20 20:45:38:930 3184 c8c WUApp WARNING: SetPTextContext called on non-existent id 'updatesAvailable'
2015-07-20 20:45:38:931 3184 c8c WUApp WARNING: SetVisibleDescendent called on non-existent id 'selectedUpdateDetailSizeArea'
2015-07-20 20:45:38:931 3184 c8c WUApp WARNING: SetDescendentText called on non-existent id 'selectedUpdateDetailSize'
2015-07-20 20:45:38:931 3184 c8c WUApp WARNING: SetVisibleDescendent called on non-existent id 'selectedUpdateDetailImportanceArea'
2015-07-20 20:45:38:931 3184 c8c WUApp WARNING: SetDescendentText called on non-existent id 'selectedUpdateDetailImportance'
2015-07-20 20:45:38:931 3184 c8c WUApp WARNING: SetPTextContext called on non-existent id 'updatesAvailable'
2015-07-20 20:45:38:932 3184 c8c WUApp WARNING: SetVisibleDescendent called on non-existent id 'selectedUpdateDetailSizeArea'
2015-07-20 20:45:38:932 3184 c8c WUApp WARNING: SetDescendentText called on non-existent id 'selectedUpdateDetailSize'
2015-07-20 20:45:38:932 3184 c8c WUApp WARNING: SetVisibleDescendent called on non-existent id 'selectedUpdateDetailImportanceArea'
2015-07-20 20:45:38:932 3184 c8c WUApp WARNING: SetDescendentText called on non-existent id 'selectedUpdateDetailImportance'
2015-07-20 20:45:38:932 3184 c8c WUApp WARNING: SetVisibleDescendent called on non-existent id 'selectedUpdateInfo'
2015-07-20 20:45:38:944 3184 c8c WUApp WARNING: SetVisibleDescendent called on non-existent id 'selectedUpdateInfo'
2015-07-20 20:45:38:949 3184 c8c WUApp WARNING: SetVisibleDescendent called on non-existent id 'selectedUpdateDetailSizeArea'
2015-07-20 20:45:38:949 3184 c8c WUApp WARNING: SetDescendentText called on non-existent id 'selectedUpdateDetailSize'
2015-07-20 20:45:38:949 3184 c8c WUApp WARNING: SetVisibleDescendent called on non-existent id 'selectedUpdateDetailImportanceArea'
2015-07-20 20:45:38:949 3184 c8c WUApp WARNING: SetDescendentText called on non-existent id 'selectedUpdateDetailImportance'
2015-07-20 20:45:38:950 3184 c8c WUApp WARNING: SetVisibleDescendent called on non-existent id 'selectedUpdateInfo'
2015-07-20 20:45:38:952 3184 c8c WUApp WARNING: SetVisibleDescendent called on non-existent id 'selectedUpdateDetailSizeArea'
2015-07-20 20:45:38:952 3184 c8c WUApp WARNING: SetDescendentText called on non-existent id 'selectedUpdateDetailSize'
2015-07-20 20:45:38:952 3184 c8c WUApp WARNING: SetVisibleDescendent called on non-existent id 'selectedUpdateDetailImportanceArea'
2015-07-20 20:45:38:952 3184 c8c WUApp WARNING: SetDescendentText called on non-existent id 'selectedUpdateDetailImportance'
I suspect that a full reset of Windows Update is going to be necessary.
Follow the instructions here -
http://www.sevenforums.com/tutorials/91738-windows-update-reset.html - working through the options, and testing Windows Update after each one to see if the behaviour has changed.
At the end, post the results, and the new windowsupdate.log file.