These updates are all related to Remote Desktop Protocol vulnerabilities.
They all appear to be related to the RDP 8.1 update KB2923545, so I'd try the offline installer for that update first...
https://support.microsoft.com/en-us/kb/2923545 - pick the right one for your system and see if it will install. If not, I need to know the exact error message.
Last edited by NoelDP; 31 Aug 2016 at 02:01. Reason: typo
Installed. Ran windows update just now but "windows could not search for new updates" with error code 800700DE
Hi Noel, I ran checkSur then check for updates, 4 updates remaining...
KB2992611
KB3020388
KB3075226
KB3126446
OK- with any luck forcing an offline install of each should work if we get them in the right order...
Go to the Update Catalog Center - Microsoft Update Catalog and download all the updates - then install them in this order...
2992611
3020388
3075226
3126446
(it's a little surprising that the order coincides with the numbering - KB numbers are generated at the start of a project, rather than at the end, so they are quite often out-of-sync!)
See if that gets them all in.
Hi,
Yep kind of a silly restriction and Micro... is supposed to be removing ie as a requirement but no telling when they will :)
Might want to pick up KB3020369 & KB3172605 while on the catalog too o.p. might need it later
Those 2 alone have done good things
But the o.p. doesn't seem to have issues finding updates just installing them :/
Cheers.
Apparently the ActiveX (IE only) requirement will be dropped in October once the revised update proceedure is adopted.
Roy
Thanks TrashZone, those 2 have been installed by windows update earlier on.
Seems like the issue with Windows Update is solved for now, thanks so much for the help everyone especially Noel, you have been a great help!
I might open another thread soon thou, I have been experiencing slow start up with windows for a month and that is how I found out I have issues with windows update. Thought the start up will return to normal SSD speed after I fixed update problem but apparently this is not the case :S
Anyhow I am very happy with solving one of the problems, appreciate all your effort along the way, cheers!
Check the size of your CBS.log files - I've noticed a number of machines having problems as they get CBS.log files approaching 3GB in size!!
When starting, check the Task Manager and see if certain processes keep taking up CPU time - also check the Performance Monitor to see what's chewing up the disk, if anything.
Quote