Skip to main content

SCCM 2012 R2 - Offline servicing error: 'Failed to install update with error code -2146498513' and 'ErrorCode = 2095'

By
SCCM 2012 R2 - Offline servicing error
I attended a customer site in which their Windows 8 image was failing to OfflineService through ConfigMgr 2012 with the error 'Failed to install update with error code -2146498513' and 'ErrorCode = 2095'

Log extract:

Checking if update (1 of 13) with ID 16795476 needs to be applied on the image. 1 content binarie(s) are associated with the update. SMS_OFFLINE_SERVICING_MANAGER 12/2/2015 2:35:56 PM 7876 (0x1EC4)
dism.exe tool info: version=10.0.10586.0, architecture=9 SMS_OFFLINE_SERVICING_MANAGER 12/2/2015 2:35:56 PM

7876 (0x1EC4)
Applicability State = APPLICABLE, Update Binary = C:\ConfigMgr_OfflineImageServicing\740bf77e-4e9d-4817-81fb-ea9f3b35fd63\windows8-rt-kb2871389-x64.cab. SMS_OFFLINE_SERVICING_MANAGER 12/2/2015 2:36:51 PM 7876 (0x1EC4)
Applying update with ID 16795476 on image at index 1. SMS_OFFLINE_SERVICING_MANAGER 12/2/2015 2:36:51 PM 7876

(0x1EC4) dism.exe tool info: version=10.0.10586.0, architecture=9 SMS_OFFLINE_SERVICING_MANAGER 12/2/2015 2:36:51 PM

7876 (0x1EC4)
Failed to install update with error code -2146498513 SMS_OFFLINE_SERVICING_MANAGER 12/2/2015 2:37:05 PM 7876

(0x1EC4)
InstallUpdate returned code 0x800f082f SMS_OFFLINE_SERVICING_MANAGER 12/2/2015 2:37:05 PM 7876 (0x1EC4)
STATMSG: ID=7911 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=LabCM2012r2.Contoso.local

SITE=P01 PID=2484 TID=7876 GMTDATE=Wed Dec 02 14:37:05.926 2015 ISTR0="16795476" ISTR1="P0100012" ISTR2="1" ISTR3=""ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_OFFLINE_SERVICING_MANAGER 12/2/2015 2:37:05

PM 7876 (0x1EC4)
Failed to install update with ID 16795476 on the image. ErrorCode = 2095 SMS_OFFLINE_SERVICING_MANAGER 12/2/2015 2:37:05 PM 7876 (0x1EC4)


Resolutuion:

Offline Servicing is the act of installing Windows updates.  Conventionally servicing is done in an online state refering

that the operating system is up and running when a change is made.  Online servicing  is done via Windows Update.   Offline

means that the installation is happening against a non-running version of Windows.  ConfigMgr mounts the WIM file with DISM

and then install updates against the mounted directory. This distrinction is important as certain updates cannot be installed offline i.e Service Packs. Teh registry key ..Component Based Servicing hold information pertaining to pending updates. When the key 'SessionsPending' has the value 3 ConfigMgr cannot continue with OfflineServicing and updates will read 'APPLICABLE' but error with 'error code -2146498513'

To resolve it would be advisable to recreate a custom Windows Image file and run Updates Online (rebooting).  If you are unable to recreate your Windows Image follow these commands below modifying the Registry of the Wim Offline.

dism /mount-wim /wimfile:C:\temp\install.wim /index:1 /mountdir:c:\temp\mount

reg load HKLM\MyKey c:\temp\mount\windows\system32\config\software

Find the registry key
HKLM\MyKey\Microsoft\Windows\CurrentVersion\Compnent Based Servicing\SessionsPending
Take ownership of root Key
Assign Full Control to Administrator
Edit the DWORD Exclusives to value 0 (in my case it was 3)

Unload the registry
reg unload HKLM\MyKey

Commit the changes to the wim
C:\>dism /unmount-wim /mountdir:c:\temp\mount /commit

Labels:

Comments

Post a Comment

Popular posts from this blog

SCCM Unknown computer not able to see Task Sequences after installing Current Branch 1702

By
Soon after installing SCCM CB 1702 we were unable to see Task Sequences deployed to the unknown collection. This issue was identified as a random system taking the GUID of the 'x64 Unknown Computer (x64 Unknown Computer)' record. As a result it was now a known GUID; as we were only deploying Task Sequences to the Unknown collection none were made available. 'x64 Unknown Computer (x64 Unknown Computer)' record 'x86 Unknown Computer (x86 Unknown Computer)' record To get the GUID of your unknown systems open SQL management studio and run the following command: --Sql Command to list the name and GUID for UnknownSystems record data select ItemKey, Name0,SMS_Unique_Identifier0 from UnknownSystem_DISC Using the returned GUID (SMS_Unique_Identifier0) we can find the hostname that has been assigned the 'x64 Unknown Computer (x64 Unknown Computer)' GUID by running the query below. --x64 Unknown Computers select Name0,SMS_Unique_Identifier0,Decommissioned0 from Sys...
167 comments
Read more

KB5025885: How to manage the Windows Boot Manager revocations for Secure Boot changes associated with CVE-2023-24932

By
This article outlines the protection against the publicly disclosed Secure Boot security feature bypass involving the BlackLotus UEFI bootkit (CVE-2023-24932). It includes steps to enable the necessary mitigations and provides guidance on creating bootable media. I will provide: - An overview of the CVE issue. - Pre-requisite actions within ADK. - Detection and remediation scripts for CVE-2023-24932. - Instructions for creating a WinPE Boot.wim file to support systems that have undergone remediation. - A breakdown of the files changed and how to boot WinPE to support systems before remediation. 1. Secure Boot Security Feature Bypass Vulnerability CVE-2023-24932 see MSRC CVE-2023-24932 is a security vulnerability involving the BlackLotus UEFI bootkit, which allows attackers to bypass Secure Boot protections. This vulnerability enables the execution of malicious code at the UEFI level, potentially leading to persistent and evasive threats. Mitigations for this issue include updates to th...
Post a Comment
Read more

Java 7 update 21 (1.7.0_21) Enterprise Repackaged Security Medium Deployment with SCCM

By
------------------------------------------------------------------------------------------------- Java 7 update 45 Enterprise deployment complete walk through http://www.syswow64.co.uk/2013/10/java-7-update-45-enterprise-deployment.html -------------------------------------------------------------------------------------------------- The issue on many blogs and articles is around creating the 'deployment.config' and 'deployment.properties' files for an enterprise deployment.  In my case i wanted to set the security level to 'Medium', but everytime I open the Java control panel it was set to the default HIGH setting. Solution 1 Create the following directory path 'C:\Windows\sun\java\deployment' 2 Create a file called 'deployment.config' in this directory and open with Notepad. Copy the two line below #################### deployment.system.config = file\:\\C\:\\WINDOWS\\Sun\\Java\\Deployment\\deployment.properties deployment.system...
15 comments
Read more