KB 2670838 - The EVIL UPDATE

FYI:

 

On 11 June 2013, Microsoft released at least three (3) Optional, non-security updates for Win7 SP1 (i.e., KB2808679, KB2834140 & KB2836502), two are related to KB2670838 & one addresses an "internal URL port scanning" issue.

Mr. Pa Bear;

I'm following this thread & would like to ask a question of you: Below I've copied 2 posts pulled from this same thread, attributing "some" problem to outdated DisplayLink drivers for a USB port replicator. I don't possess deep hardware or software knowledge, but this "solution" doesn't strike me as being relevant to the IE10 & KB2808679 update & installation failures.

Do outdated DisplayLink drivers make any sense as a fix?

I'm a bit more cautious because MS Issue/Service Advisories state that this problem is common to quite a few OEM notebooks, all of which support AMD graphics. While MS has published an extensive list mfg. names & notebook model numbers, Samsung is not among them. 

So naturally, I'm on a Samsung running a Nvidia chip & utilize HDMI to connect an external monitor.  I'm obviously experiencing this issue, but don't want to make any hasty (possibly harmful) mis-steps enroute to a resolution.

What immediately follows is my previous post, followed by the 2 DisplayLink thread comments.

Thanks for your time, assistance & insight! .... Rob

---- (My response to your comment re: June updates) ----

Earlier today (12 June 2013 ) in my circumstance,  KB2834140 successfully installed alongside 3 security updates, though KB2808679 failed, with another shot at it to be taken a bit later.  KB2836502 couldn't be bothered to show up today (& of course, no phone call, Again!) so I'll be researching shortly. - UPDATE: MS Update KB2836502 wasn't applicable to my system: Samsung QX410 notebook running Win7 Home Premium SP 1.0

____________________________________________________________________________________________________

1.)

brianhey replied on June 10, 2013

The problem maybe your USB port replicator (they are the worst). It has to do with the Displaylink software.  Update it to the lastest version http://www.displaylink.com/support/downloads.php.

As of this post it is at V7.2 M1.

I have found two docs one from Kensington and One usb HDMI convert with this same issue and both were fixed after updating the displaylink driver.

I know this post is older but I hope this helps someone.

____________________________________________________________________________________________________

2.)

MS7 user replied on June 12, 2013

This might have been the problem, this port replicator has always been a bit balky.  But I am not going to go out of my and load up MS Explorer 10 just to test it;  I use Firefox and Chrome.  Hopefully this might have fixed the every-other day freezing of the port replicator, but maybe not.  That could be caused by my Logitech sound system.   Great sound, and sub-woofer; worth at least some trouble.

Thanks,

Earlier today (12 June '13 ) in my circumstance,  KB2834140 successfully installed alongside 3 security updates, though KB2808679 failed, with another shot at it to be taken a bit later.  KB2836502 couldn't be bothered to show up today (& of course, no phone call, Again!) so I'll be researching shortly.

Should June's updates fail to resolve IE 10 compatibility, I propose that as a collective, followers of this thread either A.) chuck it all & move directly on to IE 11 in July, or B.) coordinate a time & date to conduct rites of exorcism.

Disclaimer: I am not now, nor have I ever been Catholic & am therefore somewhat dubious about prospects for realizing any personal benefit from PcExorcism (or, maybe PCIeXorcism???). Matters are further complicated as my kit is Samsung & may express a preference for Buddhism, or Confucianism, maybe even Muism.

I vote for - WORK DARN YA!

This might have been the problem, this port replicator has always been a bit balky.  But I am not going to go out of my and load up MS Explorer 10 just to test it;  I use Firefox and Chrome.  Hopefully this might have fixed the every-other day freezing of the port replicator, but maybe not.  That could be caused by my Logitech sound system.   Great sound, and sub-woofer; worth at least some trouble.

Thanks,

Microsoft:

Why don't you fix the errors caused by KB 2670838 instead of having my computer re-install it as part of IE 10 without giving me any warning that it was going to do that?

This update has two effects on my system*; 1. For whatever reason, it turns the lower taskbar turquoise, 2. Explorer 9 or 10 and Chrome 25 get a 60 delay in information typed into them with internet speeds reminiscent of dial-up, while Firefox 19 ceases to function at all; The internet becomes essentially non-usable.

I wasted an entire day on this two weeks ago including an hour on the phone with one of your technicians when it was first installed.  He had no idea what the problem was and I eventually gave up and uninstalled it.  My problems ceased immediately upon its removal.

I had to go to an internet forum to learn that many people had these problems and how to set my updates to not automatically be installed.  That proved to be no help as when installing IE10 this EVIL UPDATE (KB 2670838) just re-appeared again with no notice in your description that this might happen.  Now I guess I will never install an update again since you provide no clues as to what it could do.

* My system info:

HP Envy, Windows 7 Home Premium, two screens attached using an HP usb notebook port replicator.  Buy the way, this HP port replicator is a piece of garbage that has to be rebooted (the replicator - not the PC) as it freezes once or twice a day.  But I thinks that's on HP - not you. 

What I am having a massive impact is Fraps not working correctly. It still works with flash games and other things, but now when I do the dmw (desktop option), it shows a blank screen with a glitchy cursor. Please help.

FYI:

On 11 June 2013, Microsoft released at least three (3) Optional, non-security updates for Win7 SP1 (i.e., KB2808679, KB2834140 & KB2836502), two are related to KB2670838 & one addresses an "internal URL port scanning" issue.