Jump to content


Phylum

All Schedule Updates fail with ErrorCode 2096 / Return Code 0x800f0803 / Error Code -2146498512

Recommended Posts

When applying updates via schedule updates, they're all failing with ErrorCode 2096 / Return Code 0x800f0803 / Error Code -2146498512

  • I imported a stock Windows 7 Enterprise with SP1 (x64) WIM last night
  • I performed scheduled updates which successfully applied 93 updates.
  • This morning, I went through Scheduled Updates again, and it shows 71 updates need to be applied.
  • I'm trying to apply those updates via Scheduled Updates but they're all failing with the same set of errors.

Processing image at index 1 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:02:32 PM 10352 (0x2870)

Mounting image at index 1. Image file='D:\ConfigMgr_OfflineImageServicing\12300119\updated-install.wim', MountDirectory='D:\ConfigMgr_OfflineImageServicing\12300119\ImageMountDir', ImageFileType='WIM', Mode='ReadWrite' SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:02:32 PM 10352 (0x2870)
Image OS information : MajorVersionMS = 6, MinorVersionMS = 1, MajorVersionLS = 7601, MinorVersionLS = 18015 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:25:03 PM 10352 (0x2870)
Checking if update (1 of 71) with ID 16811634 needs to be applied on the image. 1 content binarie(s) are associated with the update. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:25:04 PM 10352 (0x2870)
Applicability State = APPLICABLE, Update Binary = D:\ConfigMgr_OfflineImageServicing\fc38fd35-1f4f-4c53-ba73-090c80368750\windows6.1-kb2835364-x64.cab. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:26:11 PM 10352 (0x2870)
Applying update with ID 16811634 on image at index 1. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:26:11 PM 10352 (0x2870)
Failed to install update with error code -2146498512 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:26:33 PM 10352 (0x2870)
InstallUpdate returned code 0x800f0830 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:26:33 PM 10352 (0x2870)
STATMSG: ID=7911 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=SCCMSERVER.F.Q.D.N SITE-123 PID=15324 TID=10352 GMTDATE=Fri Jun 27 19:26:33.398 2014 ISTR0="16811634" ISTR1="12300119" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:26:33 PM 10352 (0x2870)
Failed to install update with ID 16811634 on the image. ErrorCode = 2096 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:26:33 PM 10352 (0x2870)
Checking if update (2 of 71) with ID 16811689 needs to be applied on the image. 1 content binarie(s) are associated with the update. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:26:33 PM 10352 (0x2870)
Applicability State = APPLICABLE, Update Binary = D:\ConfigMgr_OfflineImageServicing\28ed6c22-0b13-4202-a27a-17618cc6728e\windows6.1-kb2840631-x64.cab. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:26:40 PM 10352 (0x2870)
Applying update with ID 16811689 on image at index 1. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:26:40 PM 10352 (0x2870)
Failed to install update with error code -2146498512 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:26:48 PM 10352 (0x2870)
InstallUpdate returned code 0x800f0830 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:26:48 PM 10352 (0x2870)
STATMSG: ID=7911 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=SCCMSERVER.F.Q.D.N SITE-123 PID=15324 TID=10352 GMTDATE=Fri Jun 27 19:26:48.430 2014 ISTR0="16811689" ISTR1="12300119" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:26:48 PM 10352 (0x2870)
Failed to install update with ID 16811689 on the image. ErrorCode = 2096 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:26:48 PM 10352 (0x2870)
Checking if update (3 of 71) with ID 16812324 needs to be applied on the image. 1 content binarie(s) are associated with the update. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:26:48 PM 10352 (0x2870)
Applicability State = APPLICABLE, Update Binary = D:\ConfigMgr_OfflineImageServicing\62ad16de-b149-43c7-83ff-5e68fad8de26\windows6.1-kb2847927-x64.cab. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:26:55 PM 10352 (0x2870)
Applying update with ID 16812324 on image at index 1. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:26:55 PM 10352 (0x2870)
Failed to install update with ID 16812324 on the image. ErrorCode = 2096 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:27:03 PM 10352 (0x2870)
Checking if update (4 of 71) with ID 16815183 needs to be applied on the image. 1 content binarie(s) are associated with the update. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:27:03 PM 10352 (0x2870)
Applicability State = APPLICABLE, Update Binary = D:\ConfigMgr_OfflineImageServicing\5096a2f8-d460-4cc9-9b84-5bb1c4a22255\windows6.1-kb2862966-x64.cab. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:27:10 PM 10352 (0x2870)
Applying update with ID 16815183 on image at index 1. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:27:10 PM 10352 (0x2870)
Failed to install update with error code -2146498512 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:27:17 PM 10352 (0x2870)
InstallUpdate returned code 0x800f0830 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:27:17 PM 10352 (0x2870)
STATMSG: ID=7911 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=SCCMSERVER.F.Q.D.N SITE-123 PID=15324 TID=10352 GMTDATE=Fri Jun 27 19:27:17.208 2014 ISTR0="16815183" ISTR1="12300119" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:27:17 PM 10352 (0x2870)
Failed to install update with ID 16815183 on the image. ErrorCode = 2096 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:27:17 PM 10352 (0x2870)
Checking if update (5 of 71) with ID 16815205 needs to be applied on the image. 1 content binarie(s) are associated with the update. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:27:17 PM 10352 (0x2870)
Applicability State = APPLICABLE, Update Binary = D:\ConfigMgr_OfflineImageServicing\bea7d7ae-09fe-486a-8a84-6190970c7779\windows6.1-kb2861855-x64.cab. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:27:24 PM 10352 (0x2870)
Applying update with ID 16815205 on image at index 1. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:27:24 PM 10352 (0x2870)
Failed to install update with error code -2146498512 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:27:31 PM 10352 (0x2870)
InstallUpdate returned code 0x800f0830 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:27:31 PM 10352 (0x2870)
STATMSG: ID=7911 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=SCCMSERVER.F.Q.D.N SITE-123 PID=15324 TID=10352 GMTDATE=Fri Jun 27 19:27:31.452 2014 ISTR0="16815205" ISTR1="12300119" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:27:31 PM 10352 (0x2870)
Failed to install update with ID 16815205 on the image. ErrorCode = 2096 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:27:31 PM 10352 (0x2870)
Checking if update (6 of 71) with ID 16815279 needs to be applied on the image. 1 content binarie(s) are associated with the update. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:27:31 PM 10352 (0x2870)
Applicability State = APPLICABLE, Update Binary = D:\ConfigMgr_OfflineImageServicing\88cc81ec-b8b5-4c60-8dfa-ce430024142d\windows6.1-kb2849470-x64.cab. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:27:38 PM 10352 (0x2870)
Applying update with ID 16815279 on image at index 1. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:27:38 PM 10352 (0x2870)
Failed to install update with error code -2146498512 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:27:46 PM 10352 (0x2870)
InstallUpdate returned code 0x800f0830 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:27:46 PM 10352 (0x2870)
STATMSG: ID=7911 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=SCCMSERVER.F.Q.D.N SITE-123 PID=15324 TID=10352 GMTDATE=Fri Jun 27 19:27:46.081 2014 ISTR0="16815279" ISTR1="12300119" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:27:46 PM 10352 (0x2870)
Failed to install update with ID 16815279 on the image. ErrorCode = 2096 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:27:46 PM 10352 (0x2870)
Checking if update (7 of 71) with ID 16815432 needs to be applied on the image. 1 content binarie(s) are associated with the update. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:27:46 PM 10352 (0x2870)
Applicability State = APPLICABLE, Update Binary = D:\ConfigMgr_OfflineImageServicing\f3497d26-7995-4f66-8b3e-fdb692093111\windows6.1-kb2844286-v2-x64.cab. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:27:54 PM 10352 (0x2870)
Applying update with ID 16815432 on image at index 1. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:27:54 PM 10352 (0x2870)
Failed to install update with error code -2146498512 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:28:01 PM 10352 (0x2870)
InstallUpdate returned code 0x800f0830 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:28:01 PM 10352 (0x2870)
STATMSG: ID=7911 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=SCCMSERVER.F.Q.D.N SITE-123 PID=15324 TID=10352 GMTDATE=Fri Jun 27 19:28:01.719 2014 ISTR0="16815432" ISTR1="12300119" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:28:01 PM 10352 (0x2870)
Failed to install update with ID 16815432 on the image. ErrorCode = 2096 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:28:01 PM 10352 (0x2870)
Checking if update (8 of 71) with ID 16815924 needs to be applied on the image. 1 content binarie(s) are associated with the update. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:28:01 PM 10352 (0x2870)
Applicability State = APPLICABLE, Update Binary = D:\ConfigMgr_OfflineImageServicing\1287f24a-6df3-4845-9181-451e37873202\windows6.1-kb2803821-v2-x64.cab. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:28:08 PM 10352 (0x2870)
Applying update with ID 16815924 on image at index 1. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:28:08 PM 10352 (0x2870)
Failed to install update with error code -2146498512 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:28:15 PM 10352 (0x2870)
InstallUpdate returned code 0x800f0830 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:28:15 PM 10352 (0x2870)
STATMSG: ID=7911 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=SCCMSERVER.F.Q.D.N SITE-123 PID=15324 TID=10352 GMTDATE=Fri Jun 27 19:28:15.544 2014 ISTR0="16815924" ISTR1="12300119" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:28:15 PM 10352 (0x2870)
Failed to install update with ID 16815924 on the image. ErrorCode = 2096 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:28:15 PM 10352 (0x2870)
Checking if update (9 of 71) with ID 16816368 needs to be applied on the image. 1 content binarie(s) are associated with the update. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:28:15 PM 10352 (0x2870)
Applicability State = APPLICABLE, Update Binary = D:\ConfigMgr_OfflineImageServicing\46953317-9ed4-49b3-9d2e-0463dffec251\windows6.1-kb2853952-x64.cab. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:28:22 PM 10352 (0x2870)
Applying update with ID 16816368 on image at index 1. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:28:22 PM 10352 (0x2870)
Failed to install update with error code -2146498512 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:28:29 PM 10352 (0x2870)
InstallUpdate returned code 0x800f0830 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:28:29 PM 10352 (0x2870)
STATMSG: ID=7911 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=SCCMSERVER.F.Q.D.N SITE-123 PID=15324 TID=10352 GMTDATE=Fri Jun 27 19:28:29.568 2014 ISTR0="16816368" ISTR1="12300119" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:28:29 PM 10352 (0x2870)
Failed to install update with ID 16816368 on the image. ErrorCode = 2096 SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:28:29 PM 10352 (0x2870)
Checking if update (10 of 71) with ID 16816380 needs to be applied on the image. 1 content binarie(s) are associated with the update. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:28:30 PM 10352 (0x2870)
Applicability State = APPLICABLE, Update Binary = D:\ConfigMgr_OfflineImageServicing\35f3690e-3ef4-42b2-8e85-98b6ab342bfd\windows6.1-kb2836943-v2-x64.cab. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:28:35 PM 10352 (0x2870)
Applying update with ID 16816380 on image at index 1. SMS_OFFLINE_SERVICING_MANAGER 6/27/2014 3:28:35 PM 10352 (0x2870)

I've checked the following but I'm still having trouble:

  • Running SCCM 2012 R2 (5.0.7958.1000)
  • DISM version is 6.3.9600.16384
  • There's enough disk space even with the WIM mounted (90+GB)
  • NTFS permissions are fine for %windir%\temp and D:\ConfigMgr_OfflineImageServicing
  • SCEP is installed:
    • exclusions have been created for %windir%\temp, D:\ConfigMgr_OfflineImageServicing, both 32-bit and 64-bit dism.exe and dismhost.exe (among others: 1, 2)
    • real-time protection is disabled
  • No other AV installed
  • No other third-party suites installed (e.g.: AV or Firewall) that interfere with files, processes etc.
  • Checked state of 'Exclusive' & 'TotalSessionPhases' by loading the registry of the WIM (reg load HKLM\mykey D:\mount\windows\system32\config\software); Both were set to 0.

I can upload the offline serving log in its entirety but its more of what I pasted above.

My objective is to fully patch the WIM before I apply other updates offline (e.g.: KB277551-v2, KB2732673, KB2728738). This way I can begin test deployments with a fully patched WIM as of 'now' and create our reference image which will have Office 2010 installed and fully patched. From there, the WIM will be updated either quarterly (or monthly) via Schedule Updates, after we've performed our regression tests.

I guess the question I should be asking is: What's the proper/correct process for getting a stock WIM (be it Windows 7, Server 2008 R2, Server 2012 etc) fully up to date? What does that process look like and what does the Task Sequence look like?

Help!

Share this post


Link to post
Share on other sites

Personally, i would do a Build & Capture process using your "stock" WIM and ensure that all approved Software Updates are assigned to whatever collection that B&C machine is located in. Then in the B&C Task Sequence make sure you have a Apply Software Updates command in there, this way your stock image gets all of the approved software updates. In addition performing the B&C allows you to "bake in" some of the standard software (if you have it) into the image, e.g., Flash, Silverlight, Adobe Reader, etc and this means when your performing an OSD these apps don't need to be in your TS. That's my 2 cents anyways.

Share this post


Link to post
Share on other sites

Thanks for the reply simulacra75!

We frequently get requests for custom builds of Windows 7 (some with Office 2007, others 2010 or 2013 or no office suite; completely locked down or with non-standard applications etc.) so I wanted to have a fully OS patched WIM I could use over & over. As the year goes on, I'd like to keep that WIM patched (OS wise) so as not to lengthen the imaging process. (They're sticklers when it comes to 'lengthy' imaging times!)

 

From there I would create another Build & Capture Task Sequence to install our standard apps (office, flash, reader etc.), capture that WIM & use that for our main OSD in the next month or so.

 

However that being said, I don't disagree with your comment and that's how I worked around this problem in the mean time.

  1. Scheduled Update'd WIM as much as possible
  2. B&C TS to deploy said WIM
  3. Apply a bunch of known required hotfixes offline (via dism)
  4. Apply all updates (ran that 2 or 3 times to be sure)
  5. Capture WIM

My concern was that this could be an indication of a larger issue. Or that maybe I somehow 'broke' something in the WIM or I did something wrong process wise.

Share this post


Link to post
Share on other sites

Well, i hate to be the bearer of bad news, and i sincerely hope that i'm wrong but the error code that DISM is returning ( 0x800f0830) corresponds to CBS_E_IMAGE_UNSERVICEABLE. This implies that your image is indeed corrupted by the offline "scheduled updates" process and you're not alone in this, it has happened to many more admins. If you mount the .WIM perhaps you can check setupact.log and setuperr.log in C:\windows\Panther or perhaps, CBS.log in C:\windows\logs to confirm (or hopefully disprove) this.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.