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...
161 comments
Read more

Windows 7 Offline files will not go Online when connected to network

By
Issue Several laptop users move between networks, domain, home, etc and when they attempt to access DFS shares explorer status is working offline.  The issue only resolves it self after a reboot. Connecting directly to the share works and i am able to ping network resources.  This behavior occurs for VPN users as well. Possible Causes "slow-link mode". In win7 (with default settings) a client will enter slow-link mode if the latency to the server is above 80ms. In slow-link mode all writes are made to the local cache and a background sync only happens every 6 hours.  Depending on your connection the default slow link detection speed is 64,000 bps On client computers running Windows 7 or Windows Server 2008 R2, a shared folder automatically transitions to the slow-link mode if the round-trip latency of the network is greater than 80 milliseconds, or as configured by the "Configure slow-link mode" policy. After transitioning a folder to the slow-link mode, Offline Fil...
151 comments
Read more

SCCM Software Update - Job error 0x80004005 Failed to Add Update Source for WUAgent

By
SCCM Software Updates - Failed to Add Update Source for WUAgent  Today I have been looking at a range of servers (Server 2008 /R2 2012 /R2) that were failing to communicate with the Software Update Point (SUP) in SCCM and retrieve deployment policy. The UpdateDeployment.log was reporting the Job error 0x80004005 Job error (0x80004005) received for assignment ({af7a48e6-d550-4070-dd9b-ecc234567584}) action UpdatesDeploymentAgent 12/6/2017 10:32:27 AM 2096 (0x0830) The WUAHandler.log  was reporting "Unable to read existing WUA Group Policy object" and "Failed to Add Update Source for WUAgent " Unable to read existing WUA Group Policy object. Error = 0x80004005. WUAHandler 12/6/2017 3:41:00 AM 2828 (0x0B0C) Failed to Add Update Source for WUAgent of type (2) and id ({3AAB6A76-CE2D-4E8A-9F11-123AE69612A1}). Error = 0x80004005. WUAHandler 12/6/2017 11:03:31 AM 2276 (0x08E4) Until the agent can report back to the SUP, SCCM will not be able to summarize Software Update sta...
4 comments
Read more