<img src="//bat.bing.com/action/0?ti=5794969&amp;Ver=2" height="0" width="0" style="display:none; visibility: hidden;">

Error fix: Microsoft SCCM 2012 Error Code Ox87D00668 (.NET Patching Issue)

[fa icon="long-arrow-left"] Back to all posts

[fa icon="pencil'] Posted by John Certeza [fa icon="calendar"] September 13, 2016

Here's how to fix Microsoft System Center Configuration Manager (SCCM) 2012 error code 0X87D00668: Failed to install update(s), Software update still detected as actionable after apply.

SCCM_Error_0X87D00668.png

So your SCCM patch deployment isn't going well and you check Software Center on the affected machine and it shows a failed status on two .NET 4.5.2 patches: MS16-035 (3135996) and MS16-091 (3163251).

SCCM_Available_Software.png

Logically you'd think that you can install the patch manually from Microsoft, however it'll error out with "Software Update KBXXXXXXX Installation Wizard does not apply, or is blocked by another condition on your computer. Please click the link below for more details". The error is similar to this screen shot:

Dot_NET_Patching_Error

Let's Fix It:

  1. Download all the failed patches manually to a location of your choosing, then run one of the failed patches:

  1. When the patch is extracting to a temporary location, take note of the file path:

Dot_Net_Patch_Extracting

  1. While the error screen is still in front of you, make a copy of the folder:

Dot_Net_Copy_Folder

  1. Copy:

Dot_Net_Copy_Folder_2

  1. Hit Cancel on the Error Screen and it will remove the original folder, leaving you with the copied folder.
  2. Browse into your copied folder (in my case it was C:\4ab93829f31d530b6087ca - Copy), and run the .MSP file:

Dot_Net_MSP_Patch

This will let you partially patch .NET.  If it doesn't work repeat the process on the other manual download, till you get one of the MSP files to install. 

  1. After you have a successful partial patch, run the full manual patch from the .EXE files you downloaded earlier:

Dot_Net_Manual_DownloadsDot_Net_Proper_Patching.png

Dot_Net_Proper_Patching2.png

  1. After manually patching, reboot the affected server and on the next SCCM inventory, you'll be compliant. 

Also, per some investigation on Google, this process may work for Visual Studio installations hanging up .NET prerequisites. If you try this fix, let me know if it works as well!


Microsoft Silver Partner, and a Microsoft Certified Solutions Expert (MCSE) and Microsoft Certified Professional (MCP).

Topics: Microsoft, How To Guide

John Certeza
Written by John Certeza

John is a Systems Engineer on the Managed Services team at Lewan Technology.

  • View & Submit Comments

[fa icon="envelope"] Subscribe to Email Updates



[fa icon="comments-o"] Follow us

Get even more great content, photos, event info and industry news.



[fa icon="calendar"] Recent Posts