What evidence is there that they aren't? The file names match VC 12, the file versions match a known VC 12 release, they are straight from Microsoft, and they work perfectly fine with all the applications I tested it with (it simply wouldn't work if it wasn't). Remember VC 12 is VC 2013, VC 11 is VC 2012 etc, VC 14 is VC 2015. Sure you aren't confusing the versions?
They aren’t VC12 because they aren’t redistributable and don’t come with any known VC12 version. The version number is a red herring.
Actually the last redist had this version number placed on it, but they were the old files. That's why I said REAL, the version number of the files match the last known redistributable. Microsoft don't always just release the latest redists openly on their download site. Many times the proper redistributable .exe could be buried in .msp files inside another update. Furthermore, they may be under a different name just inside the .msp file. It's a bit of a mess really. The WORST aspect of these redists is that there have been security fixes for the runtimes in the past, and fine, these are installed in the system, however if a program just has the loose files in their program folder it will use them instead. Instant security risk!
Let me reiterate: these files come from an unreleased pre-alpha version of VC14 (post-RTM of VC12 if you wish) before they change the version number and may have subtly different behaviors of library functions like printf to the released versions, which can cause unexpected behaviour with actual VC12 programs. If you claim these are real redist files, then prove it— show me their symbols :>
Sorry I would have to disagree with you there. Apart from the version number (which is a known VC12 number) and the filenames, there's the point that it came from a final release Microsoft product. Microsoft would not use pre-alpha runtime files on a RTM release. This is especially true considering the timeline of release, they could have just used the actual VC14 files. Just because it didn't come in a vcredist_(x86/x64).exe file, it doesn't make them invalid.
Had "Minor" Glitch here... after installing latest batch of Updates (1511) WUMT stopped working "Unable to contact server" Internet Explorer, Firefox stopped working “the application was unable to start correctly (0xc0000018)” Yandex OK... So able to find solution that worked/corrected issue for me Spoiler Navigated to the key HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\WindowsNT\CurrentVersion\Windows Located APPINIT_DLLS there and deleted the key (Restarted machine... issue gone)
Encountering no problems overhere, installed 7:15 pm and still have to restart (No time for a restart at the moment)
Only did a quick search to find solution... What gets me.. is no one seems to know why it occurs... ... also it points to software like Mcafee, Minecraft and Steam... non of which reside on my OS
Minimal changes in KB3116900 when compared to the previous 1511 cumulative KB3116908. Of course, everything that was in the previous is in the new one. But here's what changed. 13 components from previous one have been updated to newer versions of either 11.0.10586.20 (if IE related) or 10.0.10586.20. They are: Spoiler amd64_microsoft-windows-i..tmlrendering-legacy_31bf3856ad364e35_11.0.10586.17_none_ca114f4acdfeb052.manifest amd64_microsoft-windows-ieframe_31bf3856ad364e35_11.0.10586.17_none_1c81a7ddc9c773e9.manifest amd64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_11.0.10586.17_none_cb224dda3dd1e5bc.manifest amd64_microsoft-windows-ie-runtimeutilities_31bf3856ad364e35_11.0.10586.11_none_ffc3c51fa7fbf33d.manifest amd64_microsoft-windows-ie-versioninfo_31bf3856ad364e35_11.0.10586.11_none_b745f9ef5071e1c9.manifest amd64_microsoft-windows-microsoftedge_31bf3856ad364e35_10.0.10586.17_none_95257ed9a0ee06ec.manifest amd64_microsoft-windows-oobe-machine_31bf3856ad364e35_10.0.10586.11_none_91acea22b3cf8e64.manifest amd64_microsoft-windows-win32k_31bf3856ad364e35_10.0.10586.3_none_457917c544ddf466.manifest wow64_microsoft-windows-i..tmlrendering-legacy_31bf3856ad364e35_11.0.10586.17_none_d465f99d025f724d.manifest wow64_microsoft-windows-ieframe_31bf3856ad364e35_11.0.10586.17_none_26d6522ffe2835e4.manifest wow64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_11.0.10586.17_none_d576f82c7232a7b7.manifest x86_microsoft-windows-ie-runtimeutilities_31bf3856ad364e35_11.0.10586.11_none_a3a5299bef9e8207.manifest x86_microsoft-windows-ie-versioninfo_31bf3856ad364e35_11.0.10586.11_none_5b275e6b98147093.manifest And one other (amd64_microsoft-windows-coreos-revision_31bf3856ad364e35_10.0.10586.17_none_626edaeec0cd54ca.manifest) was updated to 10.0.10586.29. 25 new (for x64) in KB3116900 are: Spoiler amd64_microsoft.windows.gdiplus.systemcopy_31bf3856ad364e35_10.0.10586.20_none_6b140844a6a34a57.manifest amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.0.10586.20_none_ebaf102ef9e0c54d.manifest amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.10586.20_none_db007f1392e69ef4.manifest amd64_microsoft-windows-a..on-authui-component_31bf3856ad364e35_10.0.10586.20_none_6110bca5c06d8062.manifest amd64_microsoft-windows-c..fe-catsrvut-comsvcs_31bf3856ad364e35_10.0.10586.20_none_f6fbd6ed5073c156.manifest amd64_microsoft-windows-dns-server-service_31bf3856ad364e35_10.0.10586.20_none_d23f5735872a5f64.manifest amd64_microsoft-windows-i..etexplorer-optional_31bf3856ad364e35_11.0.10586.20_none_50e148f1c9356c04.manifest amd64_microsoft-windows-i..meutilities-mincore_31bf3856ad364e35_10.0.10586.20_none_612b9f8742f264ca.manifest amd64_microsoft-windows-ie-htmlactivexcompat_31bf3856ad364e35_11.0.10586.20_none_cf9a59df2b39069e.manifest amd64_microsoft-windows-ntdll_31bf3856ad364e35_10.0.10586.20_none_dd105001acc3726f.manifest amd64_microsoft-windows-ntfs_31bf3856ad364e35_10.0.10586.29_none_2a494c30cdca5b65.manifest amd64_microsoft-windows-rmcast_31bf3856ad364e35_10.0.10586.20_none_d8b73df13880c5c9.manifest amd64_microsoft-windows-scripting-vbscript_31bf3856ad364e35_11.0.10586.20_none_0084efe74956a779.manifest amd64_microsoft-windows-shutdownux_31bf3856ad364e35_10.0.10586.20_none_6101e62151f1fdf8.manifest amd64_microsoft-windows-user32_31bf3856ad364e35_10.0.10586.20_none_5171de011df2458b.manifest wow64_microsoft-windows-i..etexplorer-optional_31bf3856ad364e35_11.0.10586.20_none_5b35f343fd962dff.manifest wow64_microsoft-windows-ntdll_31bf3856ad364e35_10.0.10586.20_none_e764fa53e124346a.manifest wow64_microsoft-windows-scripting-vbscript_31bf3856ad364e35_11.0.10586.20_none_0ad99a397db76974.manifest wow64_microsoft-windows-user32_31bf3856ad364e35_10.0.10586.20_none_5bc6885352530786.manifest x86_microsoft.windows.gdiplus.systemcopy_31bf3856ad364e35_10.0.10586.20_none_0ef56cc0ee45d921.manifest x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.0.10586.20_none_335c47060e5cee53.manifest x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.10586.20_none_22adb5eaa762c7fa.manifest x86_microsoft-windows-a..on-authui-component_31bf3856ad364e35_10.0.10586.20_none_04f2212208100f2c.manifest x86_microsoft-windows-c..fe-catsrvut-comsvcs_31bf3856ad364e35_10.0.10586.20_none_9add3b6998165020.manifest x86_microsoft-windows-ie-htmlactivexcompat_31bf3856ad364e35_11.0.10586.20_none_737bbe5b72db9568.manifest
.17 is coming from: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\BuildLabEx which is updated by windows-os-kernel component while .29 shown in winver is from: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\UBR which is updated by windows-coreos-revision component