Microsoft Visual C++ 2015 Redistributable (x64) returns error 0x80240017 when installed on Windows Server 2012 R2
We had a request for a windows 2012 R2 server from our electronic team. I built the server, used WSUS to patch it then checked with the MS servers for updates. I scanned one more time and it came back fully patched, but the team was not able to install Microsoft Visual C++ 2015. After a lot of back and forth, I found a post on MSDN forum about this issue. Turns out there is a KB that doesn’t seem to be provided by WUS automatically. its KB 2919335. Here’s the notes from the post:
Visual Studio 2015 C++ Redistributable requires Windows Server 2012 R2 with Update (KB2919335).
KB2919335 will not install without KB2919442 already being installed.
However, at the present time, KB2919442 is not provided automatically via Windows Update to Windows Server 2012 R2.
Your original suggestion of installing KB2919442 is along the right lines. The actual fix is:
1. Download and install KB2919442.
2. Run windows update, which will download and install KB2919335. Alternatively manually download and install KB2919335.
3. Install Visual Studio 2015 C++ Redistributable.
Once I installed KB2919335 and rebooted. I had about 175 more patches waiting for me…. ?
Now I’m on the search on how to deploy this KB automatically to the rest of our 2012 R2 server next patch window.
This post was a serious time saver, thank you! Add Windows 2012 r2 to the list of MS operating systems that won’t update to current patch level without manual installation of a KB or 2. At least Win 7 hangs trying to get updates to let you know something is up when starting from a fresh install. A fresh install of 2012 r2 installs a few patches, and then indicates everything is fully patched. Install the 2 KB’s above and the flood of current patches shows up.
I’m glad I could help. it was driving me crazy, and the app team was breathing down my neck to get it fixed 🙂
Thanks for your post. But my server 2012R2 says it’s not applicable and wouldn’t allow me to install 2919355. The worst thing is that it starts installing the 2919355 and goes on for about 90% before giving up and rolling back. Very frustrating and i can’t see the light at the end of the tunnel The deafening silence from Microsoft on this matter says a lot about them as a reliable software house.
Thank you very much for the post, it was really helpful.