Any problems with KB3119142

[meebers]

Not seeing anyone mentioning this KB that I just received as part of windows update. Seems like a no brainer but you can never tell if Win 10 is lurking. C++ from 2012. https://support.microsoft.com/en-us/kb/3119142

 

[yurii2016]

i've registered just to reply.

it looks like you are right. i'm on windows 8.1 and i've blocked about 10 attempts to reinstall windows 10 on my system or any other its spying parts.

Problem is, I cannot install this KB3119142 update! HOPEFULLY. It says installed successfully but never installs. (i think, because it doesn't have some other spying stuff.. devs didn't think out some crap)

also, today i've blocked another (4th or 5th time) getwin10app nonsense in security updates section.

watch out


p.s.
here same topic Win8 to 8.1 update questions - Page 2 - Windows 8 and Windows 8.1

 

[GoneToPlaid]

KB3119142 tries to fix an issue with programs built using Visual Studio 2012 Update 4 in which some function exports may be missing. This can cause the programs to throw errors or not run at all. Except that the "fix" via this update is worse than the original problem.

Also related is the equally botched KB2999226 which updates the Windows 10 universal C runtime. KB2999226, once installed, causes a host of problems with Windows core files (check your Windows event viewer logs to see the issues), and uninstalling it then causes even more problems since your original C runtimes and registry settings are corrupted. Note that KB2999226 is a revised version of this same update which was originally released back in August or September 2015, only to be pulled. This latest KB2999226 update version is equally messed up. One would think that MS would get this update right the second time around, but no, they created even more issues with this recent release of this "updated" KB2999226. Maybe MS will get it right sometime next year.

In other words, these updates create an ugly mess not only after they are installed, but create an even uglier mess after they are uninstalled. After uninstalling these updates, you will discover that Office won't launch, and you will discover that other programs which rely on specific C++ runtimes will throw errors if they even launch at all. I finally managed to use System Restore to restore my Win7 machines to a date prior to installing this update. But even after completing the successful system restores, Office wouldn't start. I had to use a FixIt tool to remove office, and then I had to reinstall Office.

 

[meebers]

I hid the update when I first saw it. Looks like it will remain there! Its a PITA to have to investigate every KB now just to keep unwanted changes out.

 

[Baddog22556]

I hid the update when I first saw it. Looks like it will remain there! Its a PITA to have to investigate every KB now just to keep unwanted changes out.

It may be a PITA for some but due diligence keeps a smooth running system from going FUBAR.