none
SCCM 2012 SP1 Offline Servicing - Failed to install update

    Question

  • Greetings,

    I'm trying to apply updates to my Windows 7 SP1 x64 Operating System Image.  SCCM 2012 SP1.

    From the OfflineServicingMgr.log

    Checking if update (20 of 56) with ID 16808244 needs to be applied on the image. 2 content binarie(s) are associated with the update.  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:30.489+420><thread=12784 (0x31F0)>
    Applicability State = APPLICABLE, Update Binary = E:\ConfigMgr_OfflineImageServicing\c39fc94e-b976-41c9-8b8e-01ad700d8be2\windows6.1-kb2676562-x64.cab.  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:33.329+420><thread=12784 (0x31F0)>
    Applying update with ID 16808244 on image at index 1.  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:33.329+420><thread=12784 (0x31F0)>
    Failed to install update with error code -2146498512~  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:36.272+420><thread=12784 (0x31F0)>
    InstallUpdate returned code 0x800f0830~  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:36.273+420><thread=12784 (0x31F0)>
    STATMSG: ID=7911 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=ISTSCCM03.isllc.local SITE=P01 PID=2476 TID=12784 GMTDATE=Tue Jan 22 22:57:36.273 2013 ISTR0="16808244" ISTR1="P0100024" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:36.274+420><thread=12784 (0x31F0)>
    Failed to install update with ID 16808244 on the image. ErrorCode = 2096  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:36.275+420><thread=12784 (0x31F0)>
    Applicability State = APPLICABILITY_CHECK_NOT_SUPPORTED, Update Binary = E:\ConfigMgr_OfflineImageServicing\06d06abe-595b-4c15-909b-65bd368ae388\mpsyschk.exe.  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:36.276+420><thread=12784 (0x31F0)>
    STATMSG: ID=7917 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=ISTSCCM03.isllc.local SITE=P01 PID=2476 TID=12784 GMTDATE=Tue Jan 22 22:57:36.277 2013 ISTR0="E:\ConfigMgr_OfflineImageServicing\06d06abe-595b-4c15-909b-65bd368ae388\mpsyschk.exe" ISTR1="16808244" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:36.278+420><thread=12784 (0x31F0)>
    Not applying this update binary, it is not supported.   $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:36.280+420><thread=12784 (0x31F0)>
    Checking if update (21 of 56) with ID 16808261 needs to be applied on the image. 1 content binarie(s) are associated with the update.  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:36.327+420><thread=12784 (0x31F0)>
    Applicability State = APPLICABLE, Update Binary = E:\ConfigMgr_OfflineImageServicing\29f0e274-ad1d-4599-bf3d-0c8fa9064e76\windows6.1-kb2660649-x64.cab.  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:39.344+420><thread=12784 (0x31F0)>
    Applying update with ID 16808261 on image at index 1.  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:39.345+420><thread=12784 (0x31F0)>
    Failed to install update with error code -2146498512~  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:42.464+420><thread=12784 (0x31F0)>
    InstallUpdate returned code 0x800f0830~  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:42.464+420><thread=12784 (0x31F0)>
    STATMSG: ID=7911 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=ISTSCCM03.isllc.local SITE=P01 PID=2476 TID=12784 GMTDATE=Tue Jan 22 22:57:42.465 2013 ISTR0="16808261" ISTR1="P0100024" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:42.466+420><thread=12784 (0x31F0)>
    Failed to install update with ID 16808261 on the image. ErrorCode = 2096  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:42.468+420><thread=12784 (0x31F0)>
    Checking if update (22 of 56) with ID 16808368 needs to be applied on the image. 1 content binarie(s) are associated with the update.  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:42.650+420><thread=12784 (0x31F0)>
    Applicability State = APPLICABLE, Update Binary = E:\ConfigMgr_OfflineImageServicing\96815fb1-35a9-4d82-bf16-f3d257800211\windows6.1-kb2656411-x64.cab.  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:45.644+420><thread=12784 (0x31F0)>
    Applying update with ID 16808368 on image at index 1.  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:45.647+420><thread=12784 (0x31F0)>
    Failed to install update with error code -2146498512~  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:48.699+420><thread=12784 (0x31F0)>
    InstallUpdate returned code 0x800f0830~  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:48.700+420><thread=12784 (0x31F0)>
    STATMSG: ID=7911 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=ISTSCCM03.isllc.local SITE=P01 PID=2476 TID=12784 GMTDATE=Tue Jan 22 22:57:48.700 2013 ISTR0="16808368" ISTR1="P0100024" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:48.703+420><thread=12784 (0x31F0)>
    Failed to install update with ID 16808368 on the image. ErrorCode = 2096  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:48.704+420><thread=12784 (0x31F0)>
    Checking if update (23 of 56) with ID 16808433 needs to be applied on the image. 1 content binarie(s) are associated with the update.  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:48.712+420><thread=12784 (0x31F0)>
    

    I can't seem to figure out why about 10 updates installed, and the rest just bomb out. I did go ahead and exclude all the folders from the antivirus, even though I'm running SCEP.

    Thanks

    Tuesday, January 22, 2013 11:02 PM

All replies

  •  0x800f0830 appears to be a generic DISM failure code. Have you verified that you have enough free space available on the C drive of the site server you are running this against?

    Jason | http://blog.configmgrftw.com

    Wednesday, January 23, 2013 2:43 AM
  • i experience the same issue, since SCCM 2012 SP1 installation. win7x64 sp1 iso image.

    error code in my case is

    Failed to install update with error code 5 23.01.2013 11:08:09 7844 (0x1EA4)
    InstallUpdate returned code 0x80070005 23.01.2013 11:08:09 7844 (0x1EA4)

    i already made exclusions in endpoint protection antivirus, but it didn't help.

    i then tried to manually inject the updates into the image, opening a cmd window and typing the DISM commands by hand. it works flawlessly.

    any idea what could be wrong?

    Wednesday, January 23, 2013 11:22 AM
  • 0x80070005= E_ACCESSDENIED. General access denied error.
    What about the permissions (share / NTFS) on the share/folder where the wim is stored? Has the computer account of the site server read/write access?

    Torsten Meringer | http://www.mssccmfaq.de

    Wednesday, January 23, 2013 12:22 PM
  • edit: yes. SCCM server has write permissions to wim store.
    (ignore what i previously posted here, someone hijacked my NFTS permissions :)

    it seems i found the reason: when i disable SCEP completely, it works.

     here is the log when it failed:

    Mounting image at index 1. Image file='C:\ConfigMgr_OfflineImageServicing\WTF000C2\install.wim', MountDirectory='C:\ConfigMgr_OfflineImageServicing\WTF000C2\ImageMountDir', ImageFileType='WIM', Mode='ReadWrite'	23.01.2013 10:48:26	7844 (0x1EA4)
    Image OS information : MajorVersionMS = 6, MinorVersionMS = 1, MajorVersionLS = 7601, MinorVersionLS = 17965	23.01.2013 10:58:35	7844 (0x1EA4)
    Checking if update (1 of 2) with ID 16810305 needs to be applied on the image. 1 content binarie(s) are associated with the update.	23.01.2013 10:58:36	7844 (0x1EA4)
    Applicability State = APPLICABLE, Update Binary = C:\ConfigMgr_OfflineImageServicing\6c7de9ff-eee3-4083-9f85-b7093fefeecf\windows6.1-kb2773072-x64.cab.	23.01.2013 10:59:44	7844 (0x1EA4)
    Applying update with ID 16810305 on image at index 1.	23.01.2013 10:59:44	7844 (0x1EA4)
    Failed to install update with error code 5	23.01.2013 11:08:09	7844 (0x1EA4)
    InstallUpdate returned code 0x80070005	23.01.2013 11:08:09	7844 (0x1EA4)
    STATMSG: ID=7911 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=EGLOSCCM01.eglo.eu SITE=WTF PID=2284 TID=7844 GMTDATE=Mi Jän 23 10:08:09.084 2013 ISTR0="16810305" ISTR1="WTF000C2" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	23.01.2013 11:08:09	7844 (0x1EA4)
    Failed to install update with ID 16810305 on the image. ErrorCode = 5	23.01.2013 11:08:09	7844 (0x1EA4)
    Checking if update (2 of 2) with ID 16810309 needs to be applied on the image. 1 content binarie(s) are associated with the update.	23.01.2013 11:08:09	7844 (0x1EA4)
    Applicability State = APPLICABLE, Update Binary = C:\ConfigMgr_OfflineImageServicing\5772613d-4285-45ab-b453-29c96d48c0a5\windows6.1-kb2786400-x64.cab.	23.01.2013 11:08:18	7844 (0x1EA4)
    Applying update with ID 16810309 on image at index 1.	23.01.2013 11:08:18	7844 (0x1EA4)
    Failed to install update with error code -2146498512	23.01.2013 11:08:27	7844 (0x1EA4)
    InstallUpdate returned code 0x800f0830	23.01.2013 11:08:27	7844 (0x1EA4)
    STATMSG: ID=7911 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=EGLOSCCM01.eglo.eu SITE=WTF PID=2284 TID=7844 GMTDATE=Mi Jän 23 10:08:27.614 2013 ISTR0="16810309" ISTR1="WTF000C2" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	23.01.2013 11:08:27	7844 (0x1EA4)
    Failed to install update with ID 16810309 on the image. ErrorCode = 2096	23.01.2013 11:08:27	7844 (0x1EA4)
    Total number of updates that have been successfully applied on the mounted image is 0	23.01.2013 11:08:27	7844 (0x1EA4)
    UnMounting Image (Commit Changes = 0) ...	23.01.2013 11:08:27	7844 (0x1EA4)
    For image with package ID WTF000C2  and index 1 one or more updates failed to be installed. However processing of updates continued on error per selected by user option.	23.01.2013 11:14:55	7844 (0x1EA4)
    STATMSG: ID=7919 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=EGLOSCCM01.eglo.eu SITE=WTF PID=2284 TID=7844 GMTDATE=Mi Jän 23 10:14:55.539 2013 ISTR0="WTF000C2" ISTR1="1" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	23.01.2013 11:14:55	7844 (0x1EA4)
    STATMSG: ID=7907 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=EGLOSCCM01.eglo.eu SITE=WTF PID=2284 TID=7844 GMTDATE=Mi Jän 23 10:14:55.612 2013 ISTR0="WTF000C2" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	23.01.2013 11:14:55	7844 (0x1EA4)
    Completed processing image package WTF000C2. Status = Success	23.01.2013 11:14:55	7844 (0x1EA4)


    here is the log with disabled SCEP:

    copying file from '\\datastore\SCCMAppSources\OSD\Win7x64\install.wim'	23.01.2013 12:18:11	916 (0x0394)
          to 'C:\ConfigMgr_OfflineImageServicing\WTF000C2\install.wim' ....	23.01.2013 12:18:11	916 (0x0394)
    Copying (25% complete)...	23.01.2013 12:25:39	916 (0x0394)
    Copying (50% complete)...	23.01.2013 12:33:24	916 (0x0394)
    Copying (75% complete)...	23.01.2013 12:41:38	916 (0x0394)
    Copying (100% complete)...	23.01.2013 12:48:58	916 (0x0394)
    STATMSG: ID=7905 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=EGLOSCCM01.eglo.eu SITE=WTF PID=2284 TID=916 GMTDATE=Mi Jän 23 11:48:58.103 2013 ISTR0="WTF000C2" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	23.01.2013 12:48:58	916 (0x0394)
    [Schedule ID 16777236] Started processing image package with ID WTF000C2	23.01.2013 12:48:58	916 (0x0394)
    STATMSG: ID=7906 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=EGLOSCCM01.eglo.eu SITE=WTF PID=2284 TID=916 GMTDATE=Mi Jän 23 11:48:58.123 2013 ISTR0="WTF000C2" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	23.01.2013 12:48:58	916 (0x0394)
    Image package file with ID WTF000C2 contains 1 image(s)	23.01.2013 12:48:58	916 (0x0394)
    Processing image at index 1	23.01.2013 12:48:58	916 (0x0394)
    Mounting image at index 1. Image file='C:\ConfigMgr_OfflineImageServicing\WTF000C2\install.wim', MountDirectory='C:\ConfigMgr_OfflineImageServicing\WTF000C2\ImageMountDir', ImageFileType='WIM', Mode='ReadWrite'	23.01.2013 12:48:58	916 (0x0394)
    Image OS information : MajorVersionMS = 6, MinorVersionMS = 1, MajorVersionLS = 7601, MinorVersionLS = 17965	23.01.2013 12:57:53	916 (0x0394)
    Checking if update (1 of 1) with ID 16810309 needs to be applied on the image. 1 content binarie(s) are associated with the update.	23.01.2013 12:57:53	916 (0x0394)
    Applicability State = APPLICABLE, Update Binary = C:\ConfigMgr_OfflineImageServicing\5772613d-4285-45ab-b453-29c96d48c0a5\windows6.1-kb2786400-x64.cab.	23.01.2013 12:58:41	916 (0x0394)
    Applying update with ID 16810309 on image at index 1.	23.01.2013 12:58:41	916 (0x0394)
    STATMSG: ID=7908 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=EGLOSCCM01.eglo.eu SITE=WTF PID=2284 TID=916 GMTDATE=Mi Jän 23 11:59:18.034 2013 ISTR0="16810309" ISTR1="WTF000C2" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	23.01.2013 12:59:18	916 (0x0394)
    This update binary was successfully updated on the mounted image.	23.01.2013 12:59:18	916 (0x0394)
    Total number of updates that have been successfully applied on the mounted image is 1	23.01.2013 12:59:18	916 (0x0394)
    UnMounting Image (Commit Changes = 1) ...	23.01.2013 12:59:18	916 (0x0394)
    STATMSG: ID=7907 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=EGLOSCCM01.eglo.eu SITE=WTF PID=2284 TID=916 GMTDATE=Mi Jän 23 12:06:39.941 2013 ISTR0="WTF000C2" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	23.01.2013 13:06:39	916 (0x0394)
    Completed processing image package WTF000C2. Status = Success	23.01.2013 13:06:40	916 (0x0394)
    STATMSG: ID=7904 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=EGLOSCCM01.eglo.eu SITE=WTF PID=2284 TID=916 GMTDATE=Mi Jän 23 12:06:40.279 2013 ISTR0="WTF000C2" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	23.01.2013 13:06:40	916 (0x0394)
    Create backup copy for image WTF000C2	23.01.2013 13:06:40	916 (0x0394)
    copying image file '\\datastore\SCCMAppSources\OSD\Win7x64\install.wim' to '\\datastore\SCCMAppSources\OSD\Win7x64\install.wim.bak' ...	23.01.2013 13:06:40	916 (0x0394)
    Copy image ( ID WTF000C2, size 3608 MB )	23.01.2013 13:06:41	916 (0x0394)
    copying file from 'C:\ConfigMgr_OfflineImageServicing\WTF000C2\install.wim'	23.01.2013 13:06:41	916 (0x0394)
          to '\\atdoegfs03\SCCMAppSources\OSD\Win7x64\install.wim' ....	23.01.2013 13:06:41	916 (0x0394)
    Copying (25% complete)...	23.01.2013 13:08:04	916 (0x0394)
    Copying (50% complete)...	23.01.2013 13:09:08	916 (0x0394)
    Copying (75% complete)...	23.01.2013 13:10:18	916 (0x0394)
    Copying (100% complete)...	23.01.2013 13:11:28	916 (0x0394)
    Original image '\\datastore\SCCMAppSources\OSD\Win7x64\install.wim' is backed up at '\\datastore\SCCMAppSources\OSD\Win7x64\install.wim.bak'	23.01.2013 13:11:28	916 (0x0394)
    Automatic update of image WTF000C2 on DPs has not been done - it was not requested when scheduling the image servicing.	23.01.2013 13:11:28	916 (0x0394)

    so it seems SCEP is blocking something.

    how do i set the exception correctly? i put the following in file and folder exclusions:

    %Systemdrive%\ConfigMgr_OfflineImageServicing

    should it be

    %Systemdrive%\ConfigMgr_OfflineImageServicing\*.*

    instead or is there no difference?




    Wednesday, January 23, 2013 12:35 PM
  • Robert,

    I'm having the same issue, but with Server 2008 R2 image only. It's good to hear that it's working after you disable SCEP. By default SCEP "Real-time Protection" is disabled on Configuration Servers. I'm wondering how it's causing...

    Wednesday, January 23, 2013 9:43 PM
  • I was also able to update my WIM after forcing the real-time protection off.
    • Proposed as answer by yannara Thursday, January 31, 2013 12:02 PM
    • Unproposed as answer by yannara Thursday, January 31, 2013 12:02 PM
    Wednesday, January 23, 2013 10:09 PM
  • I spoke too soon.

    Checking if update (37 of 56) with ID 16809922 needs to be applied on the image. 1 content binarie(s) are associated with the update.	SMS_OFFLINE_SERVICING_MANAGER	1/22/2013 3:59:09 PM	12784 (0x31F0)
    Applicability State = APPLICABLE, Update Binary = E:\ConfigMgr_OfflineImageServicing\1dd4dd95-2a9f-4b13-a38b-2d6a8834cfea\windows6.1-kb2729452-x64.cab.	SMS_OFFLINE_SERVICING_MANAGER	1/22/2013 3:59:12 PM	12784 (0x31F0)
    Applying update with ID 16809922 on image at index 1.	SMS_OFFLINE_SERVICING_MANAGER	1/22/2013 3:59:12 PM	12784 (0x31F0)
    Failed to install update with error code -2146498512	SMS_OFFLINE_SERVICING_MANAGER	1/22/2013 3:59:15 PM	12784 (0x31F0)
    InstallUpdate returned code 0x800f0830	SMS_OFFLINE_SERVICING_MANAGER	1/22/2013 3:59:15 PM	12784 (0x31F0)
    STATMSG: ID=7911 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=ISTSCCM03.isllc.local SITE=P01 PID=2476 TID=12784 GMTDATE=Tue Jan 22 22:59:15.944 2013 ISTR0="16809922" ISTR1="P0100024" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_OFFLINE_SERVICING_MANAGER	1/22/2013 3:59:15 PM	12784 (0x31F0)
    Failed to install update with ID 16809922 on the image. ErrorCode = 2096	SMS_OFFLINE_SERVICING_MANAGER	1/22/2013 3:59:15 PM	12784 (0x31F0)
    Checking if update (38 of 56) with ID 16809966 needs to be applied on the image. 1 content binarie(s) are associated with the update.	SMS_OFFLINE_SERVICING_MANAGER	1/22/2013 3:59:15 PM	12784 (0x31F0)
    Applicability State = APPLICABLE, Update Binary = E:\ConfigMgr_OfflineImageServicing\bd82024e-319d-4755-8346-36acc9bd4953\windows6.1-kb2727528-x64.cab.	SMS_OFFLINE_SERVICING_MANAGER	1/22/2013 3:59:18 PM	12784 (0x31F0)
    Applying update with ID 16809966 on image at index 1.	SMS_OFFLINE_SERVICING_MANAGER	1/22/2013 3:59:18 PM	12784 (0x31F0)
    Failed to install update with error code -2146498512	SMS_OFFLINE_SERVICING_MANAGER	1/22/2013 3:59:21 PM	12784 (0x31F0)
    InstallUpdate returned code 0x800f0830	SMS_OFFLINE_SERVICING_MANAGER	1/22/2013 3:59:21 PM	12784 (0x31F0)
    STATMSG: ID=7911 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=ISTSCCM03.isllc.local SITE=P01 PID=2476 TID=12784 GMTDATE=Tue Jan 22 22:59:21.610 2013 ISTR0="16809966" ISTR1="P0100024" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_OFFLINE_SERVICING_MANAGER	1/22/2013 3:59:21 PM	12784 (0x31F0)
    Failed to install update with ID 16809966 on the image. ErrorCode = 2096	SMS_OFFLINE_SERVICING_MANAGER	1/22/2013 3:59:21 PM	12784 (0x31F0)
    Checking if update (39 of 56) with ID 16810048 needs to be applied on the image. 1 content binarie(s) are associated with the update.	SMS_OFFLINE_SERVICING_MANAGER	1/22/2013 3:59:21 PM	12784 (0x31F0)
    Applicability State = APPLICABLE, Update Binary = E:\ConfigMgr_OfflineImageServicing\6aa9ce87-75f9-4504-93e0-b3cad061020d\windows6.1-kb2706045-x64.cab.	SMS_OFFLINE_SERVICING_MANAGER	1/22/2013 3:59:24 PM	12784 (0x31F0)
    Applying update with ID 16810048 on image at index 1.	SMS_OFFLINE_SERVICING_MANAGER	1/22/2013 3:59:24 PM	12784 (0x31F0)
    Failed to install update with error code -2146498512	SMS_OFFLINE_SERVICING_MANAGER	1/22/2013 3:59:27 PM	12784 (0x31F0)
    InstallUpdate returned code 0x800f0830	SMS_OFFLINE_SERVICING_MANAGER	1/22/2013 3:59:27 PM	12784 (0x31F0)
    STATMSG: ID=7911 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=ISTSCCM03.isllc.local SITE=P01 PID=2476 TID=12784 GMTDATE=Tue Jan 22 22:59:27.430 2013 ISTR0="16810048" ISTR1="P0100024" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_OFFLINE_SERVICING_MANAGER	1/22/2013 3:59:27 PM	12784 (0x31F0)
    Failed to install update with ID 16810048 on the image. ErrorCode = 2096	SMS_OFFLINE_SERVICING_MANAGER	1/22/2013 3:59:27 PM	12784 (0x31F0)
    

    Wednesday, January 23, 2013 10:23 PM
  • did you uninstall the WAIK before starting the SP1 upgrade?

    because in one case, I didn't and had similar errors.

    so after I installed SP1 in that same case, I removed waik, restarted server, then ran a repair of the adk

    then it started working


    Wednesday, January 23, 2013 10:35 PM
  • did you uninstall the WAIK before starting the SP1 upgrade?

    because in one case, I didn't and had similar errors.

    so after I installed SP1 in that same case, I removed waik, restarted server, then ran a repair of the adk

    then it started working


    I'm having the issue with fresh installation of SCCM 2012 with SP1. Reinstalled ADK multiple times, no luck at.
    Thursday, January 24, 2013 1:19 AM
  • i have tried to solve this in the past couple of days, but with no luck. even with SCEP turned off, some updates won't install, with an error code 5.

    at first it seemed to always be KB2726353, but now i just got KB2773072 with this error. all subsequent updates after the first failure then result in other failures (e.g error code -2146498512)

    Applicability State = APPLICABLE, Update Binary = C:\ConfigMgr_OfflineImageServicing\6c7de9ff-eee3-4083-9f85-b7093fefeecf\windows6.1-kb2773072-x64.cab.	25.01.2013 12:23:28	8500 (0x2134)
    Applying update with ID 16810305 on image at index 1.	25.01.2013 12:23:28	8500 (0x2134)
    Failed to install update with error code 5	25.01.2013 12:32:38	8500 (0x2134)
    InstallUpdate returned code 0x80070005	25.01.2013 12:32:38	8500 (0x2134)
    STATMSG: ID=7911 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=EGLOSCCM01.eglo.eu SITE=WTF PID=2284 TID=8500 GMTDATE=Fr Jän 25 11:32:38.324 2013 ISTR0="16810305" ISTR1="WTF000C9" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	25.01.2013 12:32:38	8500 (0x2134)
    Failed to install update with ID 16810305 on the image. ErrorCode = 5	25.01.2013 12:32:38	8500 (0x2134)
    Checking if update (76 of 79) with ID 16810309 needs to be applied on the image. 1 content binarie(s) are associated with the update.	25.01.2013 12:32:38	8500 (0x2134)
    Applicability State = APPLICABLE, Update Binary = C:\ConfigMgr_OfflineImageServicing\5772613d-4285-45ab-b453-29c96d48c0a5\windows6.1-kb2786400-x64.cab.	25.01.2013 12:32:50	8500 (0x2134)
    Applying update with ID 16810309 on image at index 1.	25.01.2013 12:32:50	8500 (0x2134)
    Failed to install update with error code -2146498512	25.01.2013 12:32:59	8500 (0x2134)
    InstallUpdate returned code 0x800f0830	25.01.2013 12:32:59	8500 (0x2134)
    STATMSG: ID=7911 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=EGLOSCCM01.eglo.eu SITE=WTF PID=2284 TID=8500 GMTDATE=Fr Jän 25 11:32:59.502 2013 ISTR0="16810309" ISTR1="WTF000C9" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	25.01.2013 12:32:59	8500 (0x2134)
    Failed to install update with ID 16810309 on the image. ErrorCode = 2096	25.01.2013 12:32:59	8500 (0x2134)
    

    i will have to test this with different wim files next week, or with applying single updates step by step.

    Friday, January 25, 2013 11:48 AM
  • I am going to join in and say I am seeing the exact same issue after upgrading to SP1.  I am having a couple of other issues after the upgrade but am working on those separately.  To resolve the other issues I need to be able to service my reference image.

    The early bird gets the worm. The second mouse gets the cheese.

    Monday, January 28, 2013 7:33 PM
  • i have tried for 2 weeks now to find the exact reason for these problems, but i failed. even our server 2008R2 and windows 8 WIM files fail to inject the patches through sccm, even though the endpoint protection scanner is completely turned off. is there anyone who successfully uses the offline servicing feature in SP1 ?
    Thursday, January 31, 2013 9:15 AM
  • I am working with David on this issue and I have ticket open with MS, just waiting for a call back.  Once I have a solution I will post it here.
    Thursday, January 31, 2013 5:55 PM
  • We are experiencing the exact same problem too....
    Friday, February 01, 2013 4:27 PM
  • Robert,

    I'm having the same issue, but with Server 2008 R2 image only. It's good to hear that it's working after you disable SCEP. By default SCEP "Real-time Protection" is disabled on Configuration Servers. I'm wondering how it's causing...


    I also had this problem with 2008 R2 image, that over 50% updates were failing. I have to try disabling online protect in SCEP, see of that helps. Report you guys back.
    Friday, February 01, 2013 10:07 PM
  • Did you get anywhere with MS on this issue?

    Using SCCM SP1 RTM - So far on the same image (win 7 ent x64) I get different updates failing each time I try using the Offline Servicing. The image is then corrupted. I then revert back to the original image and try again and a different set of updates will fail. Seems to be a random issue. I have SCEP installed but realtime protection is disabled.

    Anyone got this to work since sp1?

    Cheers,


    Sam

    Monday, February 04, 2013 9:47 AM
  • Yep, turning OFF SCEP´s online scanner worked for me, the same image is now 100% patched without single error.
    Monday, February 04, 2013 9:48 AM
  • what exactly did you turn off? "real time protection" scanner? or more?

    because for me, this definitely does not help.

    Monday, February 04, 2013 9:51 AM
  • what exactly did you turn off? "real time protection" scanner? or more?

    because for me, this definitely does not help.


    I turned off entire "real-time protection"
    Monday, February 04, 2013 12:06 PM
  • what exactly did you turn off? "real time protection" scanner? or more?

    because for me, this definitely does not help.


    I turned off entire "real-time protection"
    er... I am pretty sure this is turned off by default on Site servers isnt it? I checked SCEP on our Site Server (we only have the one) and realtime protection is definitely turned off already.
    Monday, February 04, 2013 3:07 PM
  • that solely depends what kind of SCEP policy you deploy to the servers.

    Monday, February 04, 2013 3:09 PM
  • that solely depends what kind of SCEP policy you deploy to the servers.

    just for arguments sake I completely uninstalled SCEP, rebooted and still get the same problem.....
    Monday, February 04, 2013 4:23 PM
  • Ok... After a bit more searching I realised I still had WAIK installed - I uninstalled WAIK rebooted. Did a repair on ADK, rebooted and now it appears to work so long as I only select 50 or less updates at a time !!

    Just so I can rule out disk space (still has 13Gb spare space at the lowest whilst its installing updates) does anyone know how to make it do the offline servicing on a drive other than c:?

    Cheers,


    Sam

    Monday, February 04, 2013 5:35 PM
  • Exactly the same issue here! SCCM 2012 SP1 offline servicing fails on W7x86SP1 image. We are using McAfee as antivirus solution, it's completely turned off but all updates fail to install during offline servicing.
    Tuesday, February 05, 2013 8:48 AM
  • @samlw,

    i checked my primary site server and noticed, we also still have WAIK installed. so i followed your instructions, removed waik, repaired ADK, but still offline servicing fails:

    Checking if update (2 of 28) with ID 16793951 needs to be applied on the image. 1 content binarie(s) are associated with the update.	05.02.2013 09:45:19	3424 (0x0D60)
    Applicability State = APPLICABLE, Update Binary = C:\ConfigMgr_OfflineImageServicing\66405cb0-706e-4d54-abe6-cc67c7148998\windows8-rt-kb2768703-x64.cab.	05.02.2013 09:45:26	3424 (0x0D60)
    Applying update with ID 16793951 on image at index 1.	05.02.2013 09:45:26	3424 (0x0D60)
    Failed to install update with error code -2146498512	05.02.2013 09:45:37	3424 (0x0D60)
    InstallUpdate returned code 0x800f0830	05.02.2013 09:45:37	3424 (0x0D60)
    

    this is with SCEP completely uninstalled from the server and no other antivirus product active.

    Tuesday, February 05, 2013 8:51 AM
  • Exactly the same issue here! SCCM 2012 SP1 offline servicing fails on W7x86SP1 image. We are using McAfee as antivirus solution, it's completely turned off but all updates fail to install during offline servicing.
    We had no end of problems with McAffee - try uninstalling the mcaffe framework  - frminst.exe /remove I think it was. Even if you have disable everything in Mcafee or even remove the antivirus components completely - the framework component still interferes with SCCM (as well as lots of other things!) 
    Tuesday, February 05, 2013 8:53 AM
  • @samlw,

    i checked my primary site server and noticed, we also still have WAIK installed. so i followed your instructions, removed waik, repaired ADK, but still offline servicing fails:

    Checking if update (2 of 28) with ID 16793951 needs to be applied on the image. 1 content binarie(s) are associated with the update.	05.02.2013 09:45:19	3424 (0x0D60)
    Applicability State = APPLICABLE, Update Binary = C:\ConfigMgr_OfflineImageServicing\66405cb0-706e-4d54-abe6-cc67c7148998\windows8-rt-kb2768703-x64.cab.	05.02.2013 09:45:26	3424 (0x0D60)
    Applying update with ID 16793951 on image at index 1.	05.02.2013 09:45:26	3424 (0x0D60)
    Failed to install update with error code -2146498512	05.02.2013 09:45:37	3424 (0x0D60)
    InstallUpdate returned code 0x800f0830	05.02.2013 09:45:37	3424 (0x0D60)

    this is with SCEP completely uninstalled from the server and no other antivirus product active.

    Are you getting all updates failing?

    I found after uninstalling WAIK and repairing ADK the first x updates would apply successfully, then at some point (usually after 80 or so updates) it would start failing. I found that if I re-ran it  and only selected the first x updates it would complete successfully. Running it again with the remaining updates.. it would process y updates then start failing. Selecting the first y updates on a third run and it would complete successfully. - in this way it took 4-5 runs to successfully apply/process all 192 updates for windows 7 x64 w sp1. 

    A couple of points to note - always un-tick the option to continue on error - if you dont the image seems to get corrupted when you get failed updates (you get an offline servicing error when you try to apply the failed image to a machine)

    If you have not unticked the 'continue on error' option then you will need to remove the os image, rename the BAK file it created and re-add it to sccm - you will need to update any task sequences that use it too.

    There are two updates I cannot get it to apply at all - they keep failing: KB2799329 and KB2726535

    I still dont know why we are having so many problems with this... but at least its now kinda working.... Hope this helps.

    Tuesday, February 05, 2013 9:04 AM
  • Are you getting all updates failing?
    hard to answer. in the win8 image that i tested now, the first 2 updates are "not need to apply because its already installed", the 3rd update tries to apply but then fails.
    in the win7 image that i tested last week, it could apply some updates, but then fails.

    continue on error:
    yes, thanks for mentioning, but i always have this unticked.

    updates that are failing:

    2726535 update for windows 7  <- interesting, this one fails for you too. i tried this in my win7 image and in my 2008r2 image, it failed on both.....

    2773072 update for windows 7

    2736422 .net 3.5

    2742599 .net 3.5

    2756921 .net 3.5

    i will uninstall ADK now and retry from scratch with a fresh w7 image. but i have my doubts that it will help.

    Tuesday, February 05, 2013 9:09 AM
  • i uninstalled / fresh installed ADK, used a fresh win7 wim, no change in situation.
    Tuesday, February 05, 2013 12:18 PM
  • Hmm... There is definitely something else going on but I am stumped too....

    ... The same updates will install/process fine on some of my images and not others.  The only Consistent failures are:

    KB2799329

    KB2726535

    I also had the same updates as you mentioned fail on our laptop build image - but not our workstation images, yet both are Win 7 Enterprise x64.

    Also I have noted that: once an update fails it never recovers for the rest of that run, yet if you run in two or more batches - each time deselecting the first update that failed in the previous batch then it will work.(9/10 times)... for some random number of updates then start failing again. Very annoying indeed!

    Sorry I cannot be much more help but I have no more time to spend on this problem!



    Tuesday, February 05, 2013 2:11 PM
  • Also I have noted that: once an update fails it never recovers for the rest of that run, yet if you run in two or more batches - each time deselecting the first update that failed in the previous batch then it will work.(9/10 times)... for some random number of updates then start failing again. Very annoying indeed!




    thanks for your time, just quoting this as i see same behaviour here. guess i will convert this to a support ticket.
    Tuesday, February 05, 2013 2:41 PM
  • My ticket with Microsoft is now closed.  The resolution to get the offline image updated was to reinstall the Win 7 AIK which was uninstalled as part of our steps in upgrading to SP1.  Once reinstalled the offline image update worked without an issue.  MS said it was because the AIK contains the Deployment Image Servicing & Management (DISM) which was missing from SCCM after un-installing the AIK.
    • Proposed as answer by JimGSox Monday, February 11, 2013 5:09 PM
    Monday, February 11, 2013 5:08 PM
  • i am confused.

    the microsoft docs say:

    http://support.microsoft.com/kb/2801416/en-us

    Step 2: Uninstall Windows Automated Installation Kit (AIK)

    We recommend that you uninstall Windows AIK. This is because Windows Assessment and Deployment Kit (ADK) and Windows AIK should not coexist on the same computer.

    so, what is correct now?

    • Proposed as answer by PWinstanley Tuesday, October 29, 2013 4:30 PM
    • Unproposed as answer by PWinstanley Tuesday, October 29, 2013 4:30 PM
    Monday, February 11, 2013 5:20 PM
  • I understand what the docs say and the confustion as MS will say having both on same server is unsupported, but from what the engineer I worked with stated the ADK doesn't contain the DISM for Win 7 which is why the AIK needed to be reinstalled.

    MS has got to release a hotfix on this to rid the issue of having to run both.

    Monday, February 11, 2013 7:04 PM
  • Posed this concern to MS in the following question:

    The offline reference image is now able to be updated.  The concern I have is having the AIK and ADK installed on the same system is against MS best practices and is documented as being unsupported.   Has this changed?  If so, is there documentation confirming this change?  Will MS be releasing a hotfix on this?

    Microsoft Response:

    We can uninstall WAIK and can install Dism.exe within ADK itself and that should solve our purpose.

    I will be testing this later today.

    Jim


    Tuesday, February 12, 2013 2:14 PM
  • In my testing yesterday after uninstalling the AIK, I found two things.  First was the Windows Management Framework 3.0 had not installed correctly so PowerShell was only at 2.0.  Reapplied WMF 3.0.  Second, I found that when looking at the ADK in Programs and Features the "Deployment Tools" box was checked and thus the DISM.exe was installed.  After getting PowerShell to 3.0 I was still able to update offline image.  So please make sure of the following:

    1.  Confirm PowerShell version is at 3.0 (Launch PowerShell and run $host)

    2.  If at 2.0,  install WMF 3.0 (verify your OS version to determine your download) http://www.microsoft.com/en-us/download/details.aspx?id=34595

    3.  Go to ADK in Programs and Features and click Change.  Ensure that you have Deployment Tools selected which contains the DISM.

    Jim

    • Proposed as answer by Rahul Argade Tuesday, March 12, 2013 8:07 PM
    Wednesday, February 13, 2013 2:48 PM
  • I have this problem too. Hope Microsoft brings a Hotfix for this.

    I have checked that ADK with DISM is installed, Powershell 3.0 and WMF 3.0, additionally uninstalled the AV-Scanner.

    Failed to install update with error code -2146498512	SMS_OFFLINE_SERVICING_MANAGER	14.02.2013 20:01:24	3440 (0x0D70)
    
    Failed to install update with ID 16797366 on the image. ErrorCode = 2096
    After the patchig is failed the wim is corrupt and couln´t deployed anymore...

    Thursday, February 14, 2013 8:03 PM
  • I have the same problem too.  I have a case open with Microsoft and they are telling me that these errors are because Microsoft does not support Offline Servicing Feature with Windows 8 and Windows Server 2012 (even with SP1 applied) (we have both Windows 7 and Windows 8 images in place).  This seems absurd to me that this could not be supported, even with SP1, can anyone confirm this?
    Wednesday, February 20, 2013 4:33 PM
  • MS has just provided this fix.  As far as I can tell so far, this resolves the issue.

    http://support.microsoft.com/kb/2793237?goback=%2Egde_2760491_member_216952476&wa=wsignin1.0

    Monday, February 25, 2013 7:16 PM
  • This hotfix looks like it only resolves a problem with Server 2012 images... not the problems highlighted with applying updates to windows 7 images at the start of this thread - anyone tried it out yet? Does it also fix the problems with offline servicing and Win7 images?

    Cheers,

    Sam

    Tuesday, February 26, 2013 9:03 AM
  • win8:

    same results as before. one update fails with error code 5, all following updates with erro code -2146something.

    edit: trying win7 now.....
    edit: same situation with win7.

    first update that fails:

    Applicability State = APPLICABLE, Update Binary = C:\ConfigMgr_OfflineImageServicing\1a01a6bf-724a-4f65-b68f-74750dec9746\windows6.1-kb2574819-x64.cab. 26.02.2013 11:13:07 6596 (0x19C4)

    then subsequent updates fail with

    Failed to install update with ID 16795403 on the image. ErrorCode = 2096 26.02.2013 11:15:20 6596 (0x19C4)
    Failed to install update with error code -2146498512 26.02.2013 11:15:47 6596 (0x19C4)

    Tuesday, February 26, 2013 9:18 AM
  • When I applied the hotfix, I was then able to Service all my Windows 7 and Windows 8 images without issue (before I was getting the same error as you). However, I am beginning to think that the issue is just intermittent and not directly related to new hotfix.  I won't be able to test this theory until more MS patches released, but I have a hunch based on this thread that some could fail next time I try.
    Tuesday, February 26, 2013 1:18 PM
  • Can anybody confirm that, when this hotfix is applied, the offlince servicing for Windows 7 Images is probably working again?
    Wednesday, March 06, 2013 8:52 AM
  • I'm having the same problems with updating Server 2012 and Windows 8. After installing the update I was able to update the Server 2012 image. But windows 8 is still having the same problems. I also had WAIK installed so I removed it. Repaired ADK and rebooted the server. But this didn't resolved the problem of updating Windows 8. Does anybody have the same problem?
    Tuesday, March 12, 2013 3:47 PM
  • Confirming Jim Glore's note.

    Essentially, I didn't install the AIK. I used the ADK from the beginning and ensured that DISM and tools were placed as part of the base installation from ADK.

    I had a clean install with Win2k8r2sp1 on SQL2012 with Systems Center 2012.  No matter what I could not update Windows 7 Enterprise Media.  Windows 8, Server 2012 all functioned fine for offline servicing.

    Distribution Points and Software update Site Roles continued to not function properly. Ensured BPA ... kept WSUS db off the system volume and ensured shares were setup properly in my reminst folder with my images.

    Applied kb2793237 (no effect.. still failed)

    Backed out all Update Services in CM and WSUS in server manager.

    Ensured WSUS3.0SP2 was installed correctly (essentially added the role in server and it applied KB972455-x64)

    Updated and applied KB2720211-x64

    Updated and applied KB2734608-x64

    Added Site Role for Software Update Point.

    Install Windows6.1-kb2506143-x64 (management tools 3.0 and verified powershell 3.0 using $host)

    Ensured Synchronization of CMS/Primary against Windows Update.

    Started with a New Image off the Enterprise Media.  Ensured that once added distmgr.log reported successful adding the image to DB.  Waiting for this to sync to my distribution points after I deployed.

    Scheduled updates to Image.  Ran through exactly the way it was supposed to... take a while for 126 updates, but worked well.

    Thanks all.


    Architect, Microsoft Services

    Tuesday, March 12, 2013 8:45 PM
  • For me I noticed that certain updated required other updates which always lead to problem.  What I did was I would do a few updates without automatically updating the distribution point.  After let's say 20 good updates I would manually update the distribution point then apply more updates.  Eventually it took all the updates.  It's a long tedious process that I would hope to only do once.  Anyone care to try this to see if it's a consistent strategy?
    Thursday, March 14, 2013 6:26 AM
  • I´m starting to have -2146498512 and ErrorCode = 2096 again, when I tried to update my wim image for the second period.

    - ADK installed and DISM is included
    - Some updates are injected but not all
    - Problem is with Windows 7 x64 SP1 image
    - There is no AV client existing

    Tuesday, April 02, 2013 11:21 AM
  • The end result of offline servicing. I can´t tell, is this specific patch cousing this, or is this because of unsuccsessfull offline patching process.

    Tuesday, April 02, 2013 12:41 PM
  • yannara, I have seen this, best I can tell, whenever offline servicing fails, you end up with a corrupted image and get the errors above.  Only solution I found is, use the bak WIM file that the offline servicing process to rollback.  Then you can retry offline servicing until it finally works without errors.  Then your WIM should work again.
    Tuesday, April 02, 2013 12:45 PM
  • Agree with bcehr.. only way back is to restore the .bak image.

    I have found its best to not tick the "Continue on error" box on the second page of the schedule updates wizard.. ticking it (I think its ticked by default) seems to always corrupt the image if an update fails to apply properly.

    Tuesday, April 02, 2013 12:52 PM
  • as this problem is still unsolved, i decided to patch the wim files manually

    "Dism.exe" /mount-wim /wimfile:C:\ManualOfflineServicing\install.wim /index:1 /mountdir:c:\ManualOfflineServicing\mount\
    
    "Dism.exe" /Image:c:\ManualOfflineServicing\mount\ /Add-Package /PackagePath:"C:\ManualOfflineServicing\patches"
    
    "Dism.exe" /Unmount-WIM /MountDir:c:\ManualOfflineServicing\Mount\ /commit
    
    

    create a folder C:\ManualOfflineServicing and put the install.wim tile in there (this could be batchscripted too for further automation).
    then just copy all the cab files to \patches and run the script above.

    works without any error for win7, win8 and server 2012, and the resulting WIM file is NOT broken no matter if the patches can be applied or not. definitely not a solution, but a workaround for now.

    • Proposed as answer by Roel Janssens Tuesday, April 02, 2013 1:09 PM
    Tuesday, April 02, 2013 1:03 PM
  • yannara, I have seen this, best I can tell, whenever offline servicing fails, you end up with a corrupted image and get the errors above.  Only solution I found is, use the bak WIM file that the offline servicing process to rollback.  Then you can retry offline servicing until it finally works without errors.  Then your WIM should work again.

    Heh, same story happened to another Win7 image I had. I think if I select not to continue if errors occure, I can forget about Offline Servicing, because there are occuring lot of errors during the update. I had this issue before, that during update there are some updates failing, but still the image was then patched with some ratio and it was working ok.

    I can´t even boot up to safe mode to find out, what patch cousing this.

    Maybe I should open a case to MS, this seems to be common error.
    Tuesday, April 02, 2013 5:36 PM
  • I also have this issue with a Windows 8 image that has had the patches applied via SCCM 2012 SP1 offline servicing.

    Error logs have not shown a specific update. The logs just suggest that the image is damaged by offline servicing.

    Have updated the DP and going to attempt to repatch 


    Lee Bowman MCITP MCTS

    Wednesday, April 03, 2013 11:02 AM
  • I also have this issue with a Windows 8 image that has had the patches applied via SCCM 2012 SP1 offline servicing.

    Error logs have not shown a specific update. The logs just suggest that the image is damaged by offline servicing.

    Have updated the DP and going to attempt to repatch 


    Lee Bowman MCITP MCTS

    I solved this problem by doing the following:

    First select all the 'update' updates. After the wizard has ended do it again for all the critical and security updates. Now your image can be deployed. 

    • Proposed as answer by yannara Wednesday, April 03, 2013 6:09 PM
    Wednesday, April 03, 2013 11:59 AM
  • I solved this problem by doing the following:

    First select all the 'update' updates. After the wizard has ended do it again for all the critical and security updates. Now your image can be deployed. 


    It seems that this I managed to recover my image by doing this. After it got corrupted by installing All updates, I did another update install scheduling by selecting only critical and important updates. Now I can apply that image.
    Wednesday, April 03, 2013 6:09 PM
  • Correct me if I´m wrong, but beside the fact that there is high chance to brake your image with offline patching, there is another thing which doesn´t make the use of offline servicing so handy - as I have read in some topics here, when you inject patches with offline servicing, it only gets injected, not installed. It will really get installed during the first OS boot. So as more patches have you injectes, as long the first boot will take.

    Overall, I think I will continue using "install software updates" step and capture my image once or twice a year again with installing updates offline. What do you think?

    Saturday, April 06, 2013 8:44 AM
  • We too have fallen victim to this issue and had to restore our images from the .bak image files.

    Has Microsoft acknowledged this issue?

    Wednesday, May 29, 2013 6:41 PM
  • The solution for me was first doing regular updates then updating the distribution point and then selecting the critical updates.
    Wednesday, May 29, 2013 8:59 PM
  • Hi all. I had the same issues as everyone here roughly two months ago. Opened a support case with MS and had it confirmed as a bug but no current ETA for a fix.
    • Proposed as answer by yannara Monday, June 03, 2013 5:12 AM
    Saturday, June 01, 2013 1:33 AM
  • Hi all

    I just want to tell what worked for me. I played around with nearly every sugguestions mentioned in different forums. I don't have any anti-virus software installed and scep is also not installed at all.

    I totally ignored any update with a severity like low, moderate, important and critical for offline servicing.  I installed only updates without any severity. I had to run the scheduled updates multiple times. At the end only a few critical updates were outstanding which were applied in the last update cycle.

    There were no errors in the log and the final image isn't corrupt.

    BTW: WAIK wasn't installed..

    Tuesday, June 04, 2013 12:42 PM
  • EDIT: wrong post, sorry,

    • Edited by yannara Thursday, June 06, 2013 5:06 AM
    Wednesday, June 05, 2013 8:46 AM
  • Hello all,

    I've read all your posts, checking Powershell version, WDM... WAIK not installed, WDK repaired... Always the same issue.

    Sorting updates (regular, critical, security) returning same result. I have 52 updates to inject with offline servicing, logs show me that the three first were successfully processed, all other returned error.

    So I start injecting updates two or three at a time (take long time) without sorting anything and it seems working.

    Can the error be caused by a "large" amount of updates to process ?

    I don't have try to deploy the image yet, don't know if it is corrupted.

    I will give feedback as soon as I do.


    • Edited by SylvainNCT Thursday, June 06, 2013 9:43 AM
    Thursday, June 06, 2013 9:42 AM
  • Same thing here i'm now hoping it didnt corrupt my image as well... i will have to look up how to revert back to the bak file but here is my log


    Image package file with ID <Site>0001C contains 2 image(s)  $$<SMS_OFFLINE_SERVICING_MANAGER><06-10-2013 23:41:13.228+300><thread=3252 (0xCB4)>
    Processing image at index 1  $$<SMS_OFFLINE_SERVICING_MANAGER><06-10-2013 23:41:13.229+300><thread=3252 (0xCB4)>
    Mounting image at index 1. Image file='C:\ConfigMgr_OfflineImageServicing\<Site>0001C\windows7x64Ent.wim', MountDirectory='C:\ConfigMgr_OfflineImageServicing\<Site>0001C\ImageMountDir', ImageFileType='WIM', Mode='ReadWrite'  $$<SMS_OFFLINE_SERVICING_MANAGER><06-10-2013 23:41:13.229+300><thread=3252 (0xCB4)>
    Image OS information : MajorVersionMS = 6, MinorVersionMS = 1, MajorVersionLS = 7601, MinorVersionLS = 17965~  $$<SMS_OFFLINE_SERVICING_MANAGER><06-10-2013 23:43:31.574+300><thread=3252 (0xCB4)>
    Checking if update (1 of 5) with ID 16849187 needs to be applied on the image. 1 content binarie(s) are associated with the update.  $$<SMS_OFFLINE_SERVICING_MANAGER><06-10-2013 23:43:31.921+300><thread=3252 (0xCB4)>
    Applicability State = INSTALLED, Update Binary = C:\ConfigMgr_OfflineImageServicing\fae63ba1-5e58-40f3-abd2-bfbee8df7faa\ie9-windows6.1-kb2829530-x64.cab.  $$<SMS_OFFLINE_SERVICING_MANAGER><06-10-2013 23:43:40.560+300><thread=3252 (0xCB4)>
    No need to apply this update binary since its already installed.  $$<SMS_OFFLINE_SERVICING_MANAGER><06-10-2013 23:43:40.561+300><thread=3252 (0xCB4)>
    Checking if update (2 of 5) with ID 16849579 needs to be applied on the image. 1 content binarie(s) are associated with the update.  $$<SMS_OFFLINE_SERVICING_MANAGER><06-10-2013 23:43:40.671+300><thread=3252 (0xCB4)>
    Applicability State = APPLICABLE, Update Binary = C:\ConfigMgr_OfflineImageServicing\e30ee4ea-b0ea-457e-b374-efbf6df00064\windows6.1-kb2830290-x64.cab.  $$<SMS_OFFLINE_SERVICING_MANAGER><06-10-2013 23:43:44.469+300><thread=3252 (0xCB4)>
    Applying update with ID 16849579 on image at index 1.  $$<SMS_OFFLINE_SERVICING_MANAGER><06-10-2013 23:43:44.469+300><thread=3252 (0xCB4)>
    Failed to install update with error code -2146498512~  $$<SMS_OFFLINE_SERVICING_MANAGER><06-10-2013 23:43:48.164+300><thread=3252 (0xCB4)>
    InstallUpdate returned code 0x800f0830~  $$<SMS_OFFLINE_SERVICING_MANAGER><06-10-2013 23:43:48.164+300><thread=3252 (0xCB4)>
    STATMSG: ID=7911 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=<Server>SITE=<Site> PID=5128 TID=3252 GMTDATE=Tue Jun 11 04:43:48.164 2013 ISTR0="16849579" ISTR1="<Site>0001C" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_OFFLINE_SERVICING_MANAGER><06-10-2013 23:43:48.171+300><thread=3252 (0xCB4)>
    Failed to install update with ID 16849579 on the image. ErrorCode = 2096  $$<SMS_OFFLINE_SERVICING_MANAGER><06-10-2013 23:43:48.172+300><thread=3252 (0xCB4)>
    Checking if update (3 of 5) with ID 16849585 needs to be applied on the image. 1 content binarie(s) are associated with the update.  $$<SMS_OFFLINE_SERVICING_MANAGER><06-10-2013 23:43:48.296+300><thread=3252 (0xCB4)>
    Applicability State = APPLICABLE, Update Binary = C:\ConfigMgr_OfflineImageServicing\40dcfc2e-cfbd-4698-a38e-bc766ccae669\windows6.1-kb2829361-x64.cab.  $$<SMS_OFFLINE_SERVICING_MANAGER><06-10-2013 23:43:51.630+300><thread=3252 (0xCB4)>
    Applying update with ID 16849585 on image at index 1.  $$<SMS_OFFLINE_SERVICING_MANAGER><06-10-2013 23:43:51.630+300><thread=3252 (0xCB4)>
    Failed to install update with error code -2146498512~  $$<SMS_OFFLINE_SERVICING_MANAGER><06-10-2013 23:43:54.444+300><thread=3252 (0xCB4)>
    InstallUpdate returned code 0x800f0830~  $$<SMS_OFFLINE_SERVICING_MANAGER><06-10-2013 23:43:54.444+300><thread=3252 (0xCB4)>
    STATMSG: ID=7911 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=<Server>SITE=<Site> PID=5128 TID=3252 GMTDATE=Tue Jun 11 04:43:54.444 2013 ISTR0="16849585" ISTR1="<Site>0001C" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_OFFLINE_SERVICING_MANAGER><06-10-2013 23:43:54.445+300><thread=3252 (0xCB4)>
    Failed to install update with ID 16849585 on the image. ErrorCode = 2096  $$<SMS_OFFLINE_SERVICING_MANAGER><06-10-2013 23:43:54.445+300><thread=3252 (0xCB4)>
    Checking if update (4 of 5) with ID 16849699 needs to be applied on the image. 1 content binarie(s) are associated with the update.  $$<SMS_OFFLINE_SERVICING_MANAGER><06-10-2013 23:43:54.560+300><thread=3252 (0xCB4)>
    Applicability State = APPLICABLE, Update Binary = C:\ConfigMgr_OfflineImageServicing\f6bdaff2-c4c4-4085-a9fd-a91cd1ab085e\windows6.1-kb2847204-x64.cab.  $$<SMS_OFFLINE_SERVICING_MANAGER><06-10-2013 23:43:57.845+300><thread=3252 (0xCB4)>
    Applying update with ID 16849699 on image at index 1.  $$<SMS_OFFLINE_SERVICING_MANAGER><06-10-2013 23:43:57.845+300><thread=3252 (0xCB4)>
    Failed to install update with error code -2146498512~  $$<SMS_OFFLINE_SERVICING_MANAGER><06-10-2013 23:44:01.159+300><thread=3252 (0xCB4)>
    InstallUpdate returned code 0x800f0830~  $$<SMS_OFFLINE_SERVICING_MANAGER><06-10-2013 23:44:01.159+300><thread=3252 (0xCB4)>
    STATMSG: ID=7911 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=<Server>SITE=<Site> PID=5128 TID=3252 GMTDATE=Tue Jun 11 04:44:01.160 2013 ISTR0="16849699" ISTR1="<Site>0001C" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_OFFLINE_SERVICING_MANAGER><06-10-2013 23:44:01.160+300><thread=3252 (0xCB4)>
    Failed to install update with ID 16849699 on the image. ErrorCode = 2096  $$<SMS_OFFLINE_SERVICING_MANAGER><06-10-2013 23:44:01.160+300><thread=3252 (0xCB4)>
    Checking if update (5 of 5) with ID 16850130 needs to be applied on the image. 1 content binarie(s) are associated with the update.  $$<SMS_OFFLINE_SERVICING_MANAGER><06-10-2013 23:44:01.334+300><thread=3252 (0xCB4)>
    Applicability State = APPLICABLE, Update Binary = C:\ConfigMgr_OfflineImageServicing\139a912e-b464-45a5-9362-eeeb88819a06\ie9-windows6.1-kb2847204-x64.cab.  $$<SMS_OFFLINE_SERVICING_MANAGER><06-10-2013 23:44:04.209+300><thread=3252 (0xCB4)>
    Applying update with ID 16850130 on image at index 1.  $$<SMS_OFFLINE_SERVICING_MANAGER><06-10-2013 23:44:04.209+300><thread=3252 (0xCB4)>
    Failed to install update with error code -2146498512~  $$<SMS_OFFLINE_SERVICING_MANAGER><06-10-2013 23:44:07.644+300><thread=3252 (0xCB4)>
    InstallUpdate returned code 0x800f0830~  $$<SMS_OFFLINE_SERVICING_MANAGER><06-10-2013 23:44:07.644+300><thread=3252 (0xCB4)>
    STATMSG: ID=7911 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=<Server>SITE=<Site> PID=5128 TID=3252 GMTDATE=Tue Jun 11 04:44:07.644 2013 ISTR0="16850130" ISTR1="<Site>0001C" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_OFFLINE_SERVICING_MANAGER><06-10-2013 23:44:07.645+300><thread=3252 (0xCB4)>
    Failed to install update with ID 16850130 on the image. ErrorCode = 2096  $$<SMS_OFFLINE_SERVICING_MANAGER><06-10-2013 23:44:07.645+300><thread=3252 (0xCB4)>
    Total number of updates that have been successfully applied on the mounted image is 0  $$<SMS_OFFLINE_SERVICING_MANAGER><06-10-2013 23:44:07.645+300><thread=3252 (0xCB4)>
    UnMounting Image (Commit Changes = 0) ...  $$<SMS_OFFLINE_SERVICING_MANAGER><06-10-2013 23:44:07.645+300><thread=3252 (0xCB4)>
    For image with package ID <Site>0001C  and index 1 one or more updates failed to be installed. However processing of updates continued on error per selected by user option.  $$<SMS_OFFLINE_SERVICING_MANAGER><06-10-2013 23:45:12.494+300><thread=3252 (0xCB4)>
    STATMSG: ID=7919 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=<Server>SITE=<Site> PID=5128 TID=3252 GMTDATE=Tue Jun 11 04:45:12.495 2013 ISTR0="<Site>0001C" ISTR1="1" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_OFFLINE_SERVICING_MANAGER><06-10-2013 23:45:12.495+300><thread=3252 (0xCB4)>
    STATMSG: ID=7907 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=<Server>SITE=<Site> PID=5128 TID=3252 GMTDATE=Tue Jun 11 04:45:12.496 2013 ISTR0="<Site>0001C" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_OFFLINE_SERVICING_MANAGER><06-10-2013 23:45:12.496+300><thread=3252 (0xCB4)>
    Completed processing image package <Site>0001C. Status = Success  $$<SMS_OFFLINE_SERVICING_MANAGER><06-10-2013 23:45:12.522+300><thread=3252 (0xCB4)>
    Updated history for image package <Site>0001C in the database  $$<SMS_OFFLINE_SERVICING_MANAGER><06-10-2013 23:45:12.572+300><thread=3252 (0xCB4)>
    Schedule processing succeeded  $$<SMS_OFFLINE_SERVICING_MANAGER><06-10-2013 23:45:12.572+300><thread=3252 (0xCB4)>

    And it broke the image!! Glad they do make that .bak file, back up and in business for the moment but now ill have to wait for microsoft to patch this bug!!!


    Tuesday, June 11, 2013 5:05 AM

  • I have found  a solution to some of these failing updates. I've discovered that some large updates fails because the default Max Run Time for windows updates is only 5 minutes. If you increase the Max Run Time then the updates will no longer time out and fail after 5 minutes during the Offline Servicing, however this does not work for all updates.

    Go to All Software updates and select the updates you want to change and right click+Properties, now you can change the Maximum Run Time for all selected updates. I changed the failing updates to 10 minutes and they no longer failed in Offline Servicing.

    Wednesday, June 12, 2013 12:37 PM
  • I would love an official response on how to handle this or when a fix might be coming. Can anyone from MS comment?
    Wednesday, July 03, 2013 7:24 PM
  • Just so I can rule out disk space (still has 13Gb spare space at the lowest whilst its installing updates) does anyone know how to make it do the offline servicing on a drive other than c:?

    Cheers,


    Sam

    Is it possible to configure the offline servicing feature so that it will use the specified drive of the site server instead of the drive where Configuration Manager site has been installed?

    The short answer is yes, use WMI query “select * from SMS_SCI_Component where SiteCode='CCP' and ItemName like 'SMS_OFFLINE_SERVICING_MANAGER%' “ to do that.

    The long answer (when using wbemtest tool) is below.

    Let us say you want to specify the drive for offline servicing to stage and mount OS image and store software updates files to be “F”:

    -  Launch wbemtest.exe tool

    -  Connect to Configuration Manager namespace on the site server: if the site code of site where you do that is “CCP”, connect to namespace “root\sms\site_CCP”

    -          Then if “CCP” is site code of the site where you want to do offline servicing then do the query:

    SELECT * FROM SMS_SCI_Component WHERE SiteCode='CCP' AND ItemName LIKE 'SMS_OFFLINE_SERVICING_MANAGER%'

    -          Double Click on the entry that was returned;

    -          Double Click on “Props” property in the list;

    -          Click “View Embedded” button;

    -          There will be four entries returned in the list: find the one where PropertyName field is “StagingDrive” by double clicking on each of the four entries one by one;

    -          Change Value1 in the list to “F:” (or whatever is your desired drive);

    -          Click “Save Object” button;

    -          Click “Close” button;

    -          Click “Save Property” button;

    -          Click “Save Object” button;

    -          Click “Close” button;

    Next time offline servicing is run, it will stage all its files in the folder F:\ConfigMgr_OfflineImageServicing.

    Monday, July 08, 2013 8:47 PM
  • This hotfix looks like it only resolves a problem with Server 2012 images... not the problems highlighted with applying updates to windows 7 images at the start of this thread - anyone tried it out yet? Does it also fix the problems with offline servicing and Win7 images?

    Cheers,

    Sam


         The hotfix addresses ONLY a problem with listing Server 2012 updates
    Tuesday, July 09, 2013 12:26 AM
  • I tried the method suggested here of doing non security updates (i.e. ones without any severity rating) first followed by security updates and it is still failing. A few updates install correctly, then they all start failing. The failures extend to all subsequent attempts too.

    It's looking like SylvainNCT's workaround above of installing 2-3 updates at a time may be the only safe way to do this.

    Tuesday, July 09, 2013 7:10 PM
  • The first image I tried the "2 at a time" method on went ok. The second though started getting the 2096 errors on the 3rd cycle, and from there on it was hopeless.

    I don't feel I should have to burn a support call on this issue, but without MS acknowledging it I have little recourse.... Does anyone have any advice? I am quite frustrated.
    Thursday, July 11, 2013 12:29 PM
  • Hi all. I had the same issues as everyone here roughly two months ago. Opened a support case with MS and had it confirmed as a bug but no current ETA for a fix.

    I also contacted MS about this to fallow the case. Today I was told there is no real investigation work done, so this issue still flows as unsolved.
    Monday, August 05, 2013 7:59 AM
  • I have also tried all the steps listed here and have opened a support case with the Premier support team. I have been working with them for around 3 weeks and have a setup engineer looking into the issue but nothing has come of it yet. They are focusing on specific updates however looking at the others that are having the same issue I don't think that's the issue. I will update this if I get a response from microsoft that fixes the issue.
    Wednesday, August 14, 2013 4:07 PM
  • I had the same as a lot of you and this fixed it for me, not 100% which one as I havn't had time to undo it and work through it.

    SCEP is on the server but not enabled, but added the following exclusions anyway:

    %windir%\TEMP\ and subfolders ( *.* after Temp for those asking)

    <driveletter>\ConfigMgr_OfflineImageServicing and subfolders

    The Offline servicing folder only gets created when offline servicing starts and then gets removed once completed. I kicked off a patch cycle , checked what drive it was been cretaed on, then stopped it. I manually created the folder and applied the relevant permissions to it.

    I also excluded the following processes as it made sense to include them.

    dism.exe

    dismhost.exe

    Once I had done above offline patching started working straight away. Hope it helps someone else.

    DF

    Sunday, August 18, 2013 7:34 PM
  • Windows Server 2012 - ConfigMgr 2012 SP1 CU2 on Hyper-V 2012.

    installed Configmgr2012-sp1-kb2793237-x64-enu.msi

    All classifications have been selected in the Software Update Point.

    Automatic deployment Rule was configured to download 'Product = Windows 7 and Superceded = No'

    Started with a base Windows 7 Enterprise SP1 x64 install.wim. 

    I added the AV exclusions which did not help.

    I opened the OfflineSerfviceMgr.log in cmtrace and monitored the process and found it failed at the same place a few times in a row.  Update 77 was failing.

    First few times looking for a trend:
    ...
    Checking if update (76 of 226) with ID 16779368 needs to be applied on the image. 2 content binarie(s) are associated with the update. SMS_OFFLINE_SERVICING_MANAGER 8/27/2013 10:24:59 PM 7708 (0x1E1C)
    Applicability State = APPLICABILITY_CHECK_NOT_SUPPORTED, Update Binary = D:\ConfigMgr_OfflineImageServicing\f0085f58-6390-43f1-8829-8eeeef6d2a53\MSIPatchRegFix-AMD64.exe. SMS_OFFLINE_SERVICING_MANAGER 8/27/2013 10:24:59 PM 7708 (0x1E1C)
    STATMSG: ID=7917 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=server.domain.com SITE=PRI PID=2500 TID=7708 GMTDATE=Wed Aug 28 03:24:59.067 2013 ISTR0="D:\ConfigMgr_OfflineImageServicing\f0085f58-6390-43f1-8829-8eeeef6d2a53\MSIPatchRegFix-AMD64.exe" ISTR1="16779368" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_OFFLINE_SERVICING_MANAGER 8/27/2013 10:24:59 PM 7708 (0x1E1C)
    Not applying this update binary, it is not supported. SMS_OFFLINE_SERVICING_MANAGER 8/27/2013 10:24:59 PM 7708 (0x1E1C)
    Applicability State = APPLICABILITY_CHECK_NOT_SUPPORTED, Update Binary = D:\ConfigMgr_OfflineImageServicing\185b4c5e-a80e-4d7e-ad97-af35cd92e2bf\NDP40-KB2487367-x64.exe. SMS_OFFLINE_SERVICING_MANAGER 8/27/2013 10:24:59 PM 7708 (0x1E1C)
    STATMSG: ID=7917 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=server.domain.com SITE=PRI PID=2500 TID=7708 GMTDATE=Wed Aug 28 03:24:59.069 2013 ISTR0="D:\ConfigMgr_OfflineImageServicing\185b4c5e-a80e-4d7e-ad97-af35cd92e2bf\NDP40-KB2487367-x64.exe" ISTR1="16779368" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_OFFLINE_SERVICING_MANAGER 8/27/2013 10:24:59 PM 7708 (0x1E1C)
    Not applying this update binary, it is not supported. SMS_OFFLINE_SERVICING_MANAGER 8/27/2013 10:24:59 PM 7708 (0x1E1C)
    Content '55ebc8cb-74aa-4e40-9152-92af8d603c13' not found in content library on this site. Software updates should be distributed to this site. SMS_OFFLINE_SERVICING_MANAGER 8/27/2013 10:24:59 PM 7708 (0x1E1C)
    UnMounting Image (Commit Changes = 0) ... SMS_OFFLINE_SERVICING_MANAGER 8/27/2013 10:24:59 PM 7708 (0x1E1C)
    Completed processing image package PRI0000B. Status = Failed SMS_OFFLINE_SERVICING_MANAGER 8/27/2013 10:25:57 PM 7708 (0x1E1C)
    Updated history for image package PRI0000B in the database SMS_OFFLINE_SERVICING_MANAGER 8/27/2013 10:25:57 PM 7708 (0x1E1C)
    Schedule processing failed SMS_OFFLINE_SERVICING_MANAGER 8/27/2013 10:25:57 PM 7708 (0x1E1C)
    ...

    Note:  I looked in the 55ebc8cb-74aa-4e40-9152-92af8d603c13 folder and the cab was actually in there.  I also looked in the original WindowsUpdates folder and found the update.

    Actual update:
    ...\55ebc8cb-74aa-4e40-9152-92af8d603c13\windows6.1-kb2563227-x64.cab"
    http://support.microsoft.com/kb/2563227:
    "An SVG graphic that has attributes that use large values may not be parsed correctly"


    This time around I only added the first 76:
    ...
    Total number of updates that have been successfully applied on the mounted image is 25 SMS_OFFLINE_SERVICING_MANAGER 8/27/2013 10:47:31 PM 6740 (0x1A54)
    UnMounting Image (Commit Changes = 1) ... SMS_OFFLINE_SERVICING_MANAGER 8/27/2013 10:47:31 PM 6740 (0x1A54)
    STATMSG: ID=7907 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=server.domain.com SITE=PRI PID=2500 TID=6740 GMTDATE=Wed Aug 28 03:48:58.417 2013 ISTR0="PRI0000B" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_OFFLINE_SERVICING_MANAGER 8/27/2013 10:48:58 PM 6740 (0x1A54)
    Completed processing image package PRI0000B. Status = Success SMS_OFFLINE_SERVICING_MANAGER 8/27/2013 10:48:58 PM 6740 (0x1A54)
    STATMSG: ID=7904 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=server.domain.com SITE=PRI PID=2500 TID=6740 GMTDATE=Wed Aug 28 03:48:58.444 2013 ISTR0="PRI0000B" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_OFFLINE_SERVICING_MANAGER 8/27/2013 10:48:58 PM 6740 (0x1A54)
    Create backup copy for image PRI0000B SMS_OFFLINE_SERVICING_MANAGER 8/27/2013 10:48:58 PM 6740 (0x1A54)
    copying image file '\\server\share$\folder\sources\install.wim' to '\\server\share$\folder\sources\install.wim.bak' ... SMS_OFFLINE_SERVICING_MANAGER 8/27/2013 10:48:58 PM 6740 (0x1A54)
    Copy image ( ID PRI0000B, size 2688 MB ) SMS_OFFLINE_SERVICING_MANAGER 8/27/2013 10:48:58 PM 6740 (0x1A54)
    copying file from 'D:\ConfigMgr_OfflineImageServicing\PRI0000B\install.wim' SMS_OFFLINE_SERVICING_MANAGER 8/27/2013 10:48:58 PM 6740 (0x1A54)
          to '\\server\share$\folder\sources\install.wim' .... SMS_OFFLINE_SERVICING_MANAGER 8/27/2013 10:48:58 PM 6740 (0x1A54)
    Copying (25% complete)... SMS_OFFLINE_SERVICING_MANAGER 8/27/2013 10:49:39 PM 6740 (0x1A54)
    Copying (50% complete)... SMS_OFFLINE_SERVICING_MANAGER 8/27/2013 10:50:20 PM 6740 (0x1A54)
    Copying (75% complete)... SMS_OFFLINE_SERVICING_MANAGER 8/27/2013 10:50:59 PM 6740 (0x1A54)
    Copying (100% complete)... SMS_OFFLINE_SERVICING_MANAGER 8/27/2013 10:51:42 PM 6740 (0x1A54)
    Original image '\\server\share$\folder\sources\install.wim' is backed up at '\\server\share$\folder\sources\install.wim.bak' SMS_OFFLINE_SERVICING_MANAGER 8/27/2013 10:51:42 PM 6740 (0x1A54)
    Successfully requested image PRI0000B to be updated from its source. SMS_OFFLINE_SERVICING_MANAGER 8/27/2013 10:51:42 PM 6740 (0x1A54)
    STATMSG: ID=7905 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=server.domain.com SITE=PRI PID=2500 TID=6740 GMTDATE=Wed Aug 28 03:51:42.482 2013 ISTR0="PRI0000B" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_OFFLINE_SERVICING_MANAGER 8/27/2013 10:51:42 PM 6740 (0x1A54)
    Updated history for image package PRI0000B in the database SMS_OFFLINE_SERVICING_MANAGER 8/27/2013 10:51:42 PM 6740 (0x1A54)
    Schedule processing succeeded SMS_OFFLINE_SERVICING_MANAGER 8/27/2013 10:51:42 PM 6740 (0x1A54)
    Processing completed for Schedule with ID 16777222 SMS_OFFLINE_SERVICING_MANAGER 8/27/2013 10:51:42 PM 6740 (0x1A54)
    ...

    Note:  The Operating System Image shows a "Scheduled Updates Status" of Successful and the new WIM was distributed to the DP.  Once the WIM was on the DP I started with the next batch skipping kb2563227.

    149 updates this go round:

    ...
    Total number of updates that have been successfully applied on the mounted image is 104 SMS_OFFLINE_SERVICING_MANAGER 8/27/2013 11:54:33 PM 10136 (0x2798)
    UnMounting Image (Commit Changes = 1) ... SMS_OFFLINE_SERVICING_MANAGER 8/27/2013 11:54:33 PM 10136 (0x2798)
    STATMSG: ID=7907 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=server.domain.com SITE=PRI PID=2500 TID=10136 GMTDATE=Wed Aug 28 04:57:57.061 2013 ISTR0="PRI0000B" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_OFFLINE_SERVICING_MANAGER 8/27/2013 11:57:57 PM 10136 (0x2798)
    Completed processing image package PRI0000B. Status = Success SMS_OFFLINE_SERVICING_MANAGER 8/27/2013 11:57:57 PM 10136 (0x2798)
    STATMSG: ID=7904 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=server.domain.com SITE=PRI PID=2500 TID=10136 GMTDATE=Wed Aug 28 04:57:57.089 2013 ISTR0="PRI0000B" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_OFFLINE_SERVICING_MANAGER 8/27/2013 11:57:57 PM 10136 (0x2798)
    Create backup copy for image PRI0000B SMS_OFFLINE_SERVICING_MANAGER 8/27/2013 11:57:57 PM 10136 (0x2798)
    copying image file '\\server\share$\folder\sources\install.wim' to '\\server\share$\folder\sources\install.wim.bak' ... SMS_OFFLINE_SERVICING_MANAGER 8/27/2013 11:57:57 PM 10136 (0x2798)
    Copy image ( ID PRI0000B, size 2776 MB ) SMS_OFFLINE_SERVICING_MANAGER 8/27/2013 11:57:57 PM 10136 (0x2798)
    copying file from 'D:\ConfigMgr_OfflineImageServicing\PRI0000B\install.wim' SMS_OFFLINE_SERVICING_MANAGER 8/27/2013 11:57:57 PM 10136 (0x2798)
          to '\\server\share$\folder\sources\install.wim' .... SMS_OFFLINE_SERVICING_MANAGER 8/27/2013 11:57:57 PM 10136 (0x2798)
    Copying (25% complete)... SMS_OFFLINE_SERVICING_MANAGER 8/27/2013 11:58:49 PM 10136 (0x2798)
    Copying (50% complete)... SMS_OFFLINE_SERVICING_MANAGER 8/27/2013 11:59:40 PM 10136 (0x2798)
    Copying (75% complete)... SMS_OFFLINE_SERVICING_MANAGER 8/28/2013 12:00:33 AM 10136 (0x2798)
    Copying (100% complete)... SMS_OFFLINE_SERVICING_MANAGER 8/28/2013 12:01:25 AM 10136 (0x2798)
    Original image '\\server\share$\folder\sources\install.wim' is backed up at '\\server\share$\folder\sources\install.wim.bak' SMS_OFFLINE_SERVICING_MANAGER 8/28/2013 12:01:25 AM 10136 (0x2798)
    Successfully requested image PRI0000B to be updated from its source. SMS_OFFLINE_SERVICING_MANAGER 8/28/2013 12:01:25 AM 10136 (0x2798)
    STATMSG: ID=7905 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=server.domain.com SITE=PRI PID=2500 TID=10136 GMTDATE=Wed Aug 28 05:01:25.716 2013 ISTR0="PRI0000B" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_OFFLINE_SERVICING_MANAGER 8/28/2013 12:01:25 AM 10136 (0x2798)
    Successfully deleted entry from database for schedule ID=16777217 Name="" assigned to ImageID=PRI0000B SMS_OFFLINE_SERVICING_MANAGER 8/28/2013 12:01:26 AM 10136 (0x2798)
    Updated history for image package PRI0000B in the database SMS_OFFLINE_SERVICING_MANAGER 8/28/2013 12:01:26 AM 10136 (0x2798)
    Schedule processing succeeded SMS_OFFLINE_SERVICING_MANAGER 8/28/2013 12:01:26 AM 10136 (0x2798)
    Processing completed for Schedule with ID 16777223 SMS_OFFLINE_SERVICING_MANAGER 8/28/2013 12:01:26 AM 10136 (0x2798)
    ...

    Note:  The Operating System Image shows a "Scheduled Updates Status" of Successful and the new WIM was distributed to the DP.  Once the WIM was on the DP I started with kb2563227.

    Just kb2563227:

    ...
    Total number of individual updates to be installed is 1. SMS_OFFLINE_SERVICING_MANAGER 8/28/2013 12:13:56 AM 3740 (0x0E9C)
    STATMSG: ID=7903 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=server.domain.com SITE=PRI PID=2500 TID=3740 GMTDATE=Wed Aug 28 05:13:56.497 2013 ISTR0="PRI0000B" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_OFFLINE_SERVICING_MANAGER 8/28/2013 12:13:56 AM 3740 (0x0E9C)
    Copy image ( ID PRI0000B, size 3345 MB ) SMS_OFFLINE_SERVICING_MANAGER 8/28/2013 12:13:56 AM 3740 (0x0E9C)
    copying file from '\\server\share$\folder\sources\install.wim' SMS_OFFLINE_SERVICING_MANAGER 8/28/2013 12:13:56 AM 3740 (0x0E9C)
          to 'D:\ConfigMgr_OfflineImageServicing\PRI0000B\install.wim' .... SMS_OFFLINE_SERVICING_MANAGER 8/28/2013 12:13:56 AM 3740 (0x0E9C)
    Copying (25% complete)... SMS_OFFLINE_SERVICING_MANAGER 8/28/2013 12:14:46 AM 3740 (0x0E9C)
    Copying (50% complete)... SMS_OFFLINE_SERVICING_MANAGER 8/28/2013 12:15:36 AM 3740 (0x0E9C)
    Copying (75% complete)... SMS_OFFLINE_SERVICING_MANAGER 8/28/2013 12:16:26 AM 3740 (0x0E9C)
    Copying (100% complete)... SMS_OFFLINE_SERVICING_MANAGER 8/28/2013 12:17:18 AM 3740 (0x0E9C)
    STATMSG: ID=7905 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=server.domain.com SITE=PRI PID=2500 TID=3740 GMTDATE=Wed Aug 28 05:17:18.305 2013 ISTR0="PRI0000B" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_OFFLINE_SERVICING_MANAGER 8/28/2013 12:17:18 AM 3740 (0x0E9C)
    [Schedule ID 16777224] Started processing image package with ID PRI0000B SMS_OFFLINE_SERVICING_MANAGER 8/28/2013 12:17:18 AM 3740 (0x0E9C)
    STATMSG: ID=7906 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=server.domain.com SITE=PRI PID=2500 TID=3740 GMTDATE=Wed Aug 28 05:17:18.307 2013 ISTR0="PRI0000B" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_OFFLINE_SERVICING_MANAGER 8/28/2013 12:17:18 AM 3740 (0x0E9C)
    Image package file with ID PRI0000B contains 1 image(s) SMS_OFFLINE_SERVICING_MANAGER 8/28/2013 12:17:18 AM 3740 (0x0E9C)
    Processing image at index 1 SMS_OFFLINE_SERVICING_MANAGER 8/28/2013 12:17:18 AM 3740 (0x0E9C)
    Mounting image at index 1. Image file='D:\ConfigMgr_OfflineImageServicing\PRI0000B\install.wim', MountDirectory='D:\ConfigMgr_OfflineImageServicing\PRI0000B\ImageMountDir', ImageFileType='WIM', Mode='ReadWrite' SMS_OFFLINE_SERVICING_MANAGER 8/28/2013 12:17:18 AM 3740 (0x0E9C)
    Image OS information : MajorVersionMS = 6, MinorVersionMS = 1, MajorVersionLS = 7601, MinorVersionLS = 18015 SMS_OFFLINE_SERVICING_MANAGER 8/28/2013 12:18:53 AM 3740 (0x0E9C)
    Content '55ebc8cb-74aa-4e40-9152-92af8d603c13' not found in content library on this site. Software updates should be distributed to this site. SMS_OFFLINE_SERVICING_MANAGER 8/28/2013 12:18:53 AM 3740 (0x0E9C)
    UnMounting Image (Commit Changes = 0) ... SMS_OFFLINE_SERVICING_MANAGER 8/28/2013 12:18:53 AM 3740 (0x0E9C)
    Completed processing image package PRI0000B. Status = Failed SMS_OFFLINE_SERVICING_MANAGER 8/28/2013 12:19:55 AM 3740 (0x0E9C)
    Successfully deleted entry from database for schedule ID=16777218 Name="" assigned to ImageID=PRI0000B SMS_OFFLINE_SERVICING_MANAGER 8/28/2013 12:19:55 AM 3740 (0x0E9C)
    Updated history for image package PRI0000B in the database SMS_OFFLINE_SERVICING_MANAGER 8/28/2013 12:19:55 AM 3740 (0x0E9C)
    Schedule processing failed SMS_OFFLINE_SERVICING_MANAGER 8/28/2013 12:19:55 AM 3740 (0x0E9C)
    ...

    129 Updates in two passes.  I assume they would have all worked together if I would have excluded the bad one.

    Well it looks like in my particular situation that kb2563227 was the only bad update.

    After it's all said and done I would probably stick with quarterly Build and Captures with the newest updates included.

    Two hours of my life I can never get back.

    Mike Niccum






    • Edited by mniccum Wednesday, August 28, 2013 5:32 AM
    Wednesday, August 28, 2013 5:27 AM
  • I had the same as a lot of you and this fixed it for me, not 100% which one as I havn't had time to undo it and work through it.

    SCEP is on the server but not enabled, but added the following exclusions anyway:

    %windir%\TEMP\ and subfolders ( *.* after Temp for those asking)

    <driveletter>\ConfigMgr_OfflineImageServicing and subfolders

    The Offline servicing folder only gets created when offline servicing starts and then gets removed once completed. I kicked off a patch cycle , checked what drive it was been cretaed on, then stopped it. I manually created the folder and applied the relevant permissions to it.

    I also excluded the following processes as it made sense to include them.

    dism.exe

    dismhost.exe

    Once I had done above offline patching started working straight away. Hope it helps someone else.

    DF


    I followed these steps but left my SCEP installed and running. These steps resolved my issue. Patching 100% now unless it finds a bad download.
    • Proposed as answer by fritschetom Thursday, September 05, 2013 4:04 PM
    Thursday, September 05, 2013 4:04 PM
  • I also tried those exact steps and it did not solve the issue for me.  If I retry enough times or select a smaller number of updates, I can get it to eventually finish/succeed, just takes forever doing 75 updates like 5 at a time...
    Thursday, September 05, 2013 4:24 PM
  • I had the same as a lot of you and this fixed it for me, not 100% which one as I havn't had time to undo it and work through it.

    SCEP is on the server but not enabled, but added the following exclusions anyway:

    %windir%\TEMP\ and subfolders ( *.* after Temp for those asking)

    <driveletter>\ConfigMgr_OfflineImageServicing and subfolders

    The Offline servicing folder only gets created when offline servicing starts and then gets removed once completed. I kicked off a patch cycle , checked what drive it was been cretaed on, then stopped it. I manually created the folder and applied the relevant permissions to it.

    I also excluded the following processes as it made sense to include them.

    dism.exe

    dismhost.exe

    Once I had done above offline patching started working straight away. Hope it helps someone else.

    DF

    worked for me too. Thanks a lot guys..
    • Proposed as answer by Thyum Vyt Friday, November 08, 2013 7:45 AM
    • Unproposed as answer by Thyum Vyt Friday, November 08, 2013 7:45 AM
    Wednesday, September 18, 2013 11:44 AM
  • Has anyone tried offline servicing with CU3 applied?

    http://blogs.technet.com/b/configurationmgr/archive/2013/09/24/kb-cumulative-update-3-for-system-center-2012-configuration-manager-service-pack-1.aspx

    Thursday, October 03, 2013 4:29 PM
  • I have and it still fails.  From what I gather there are certain updates that actually require a restart.  So what I do is when this happens I do a capture from a VM then use that image for future offline servicing.  This will work fine for a few months till Microsoft pushes out a update that really requires a restart.
    Thursday, October 03, 2013 5:33 PM
  • So offline servicing fails to handle updates that require a restart? At least now we know why it doesn't work.

    This feature is billed as an automated way to keep WIM images up to date, but as of September 2013 it is quite simply broken.

    I hope others find this post before wasting hours trying to get it to work.

    • Proposed as answer by oxfordtom Friday, October 04, 2013 11:10 AM
    Friday, October 04, 2013 11:10 AM
  • What is problematic for me is prior to SP1 this worked without issue.
    Friday, October 04, 2013 11:34 AM
  • I have heard that the problem is caused by a bug in dism.exe (which is used to inject the updates), but I haven't got any details ...

    Torsten Meringer | http://www.mssccmfaq.de

    Friday, October 04, 2013 11:53 AM
  • Same issue here :-(
    Saturday, October 05, 2013 3:19 PM
  • Anyone tried this with 2012 R2?
    Monday, October 28, 2013 5:48 PM
  • I did with both a Windows 8 and Windows 8.1 image and it ran fine.  However,  I need a bigger set of updates to get a better feel if they fixed anything.  Let's see in two weeks.
    Tuesday, October 29, 2013 4:49 PM
  • My existing images still fail on Configuration Manager 2012 R2. I am attempting to re-capture all my images and see if that makes a difference.  I will post back when have enough info to say.
    Monday, November 04, 2013 9:20 PM
  • FYI, I recaptured all my images and have not seen the issue since. I'm crossing my figures that with new images the issue is resolved.
    Thursday, December 05, 2013 2:05 PM
  • Just spent 4 days on the phone support with Microsoft Support, They confirmed this is an issue that they know about and have an internal Hotfix that is being worked on as I type this but it is not for general public yet. I will find out more information on 12-9-2013 when they will get back to me. The Hotfix states more then 10 updates but i have had it fail after 2 updates. So to me this is miss information but it is the exact problem since im getting a error code 5 which is an access denied issue. 

    Plus the Hotfix is at this point install at your own risk, and i dont want to have issues in my production environment so im waiting since my test cluster is filled up with other projects at the moment.

    Hope this helps you guys!

    Here is the message i got back in email from Microsoft on their internal beta test of this hotfix:

    Description of the Hotfix

     

    Customer is using System Center 2012 Config Manager and uses this to patch their wim's. In doing so they get an error sometimes when they are applying more than 10 patches at a time, failing with the error "Failed to install update with error code 5"


    Paul

    Thursday, December 05, 2013 2:59 PM
  • Hmm, I upgraded my site server to R2, and I tried to patch same image I had troubles previously. I also shut down Anti-Virus monitoring during the process. I did select only Windows 7 updates, no Framework or other updates. With this, I got 0 errors and the image is installable fine.
    Monday, December 16, 2013 8:58 AM
  • The computer account of the site server is the local computer's SYSTEM account, correct ?  Thanks

    Tuesday, January 14, 2014 6:13 PM
  • Any further update on this hotfix?  I am experiencing the same issue as most on this sight.  No AV and no AIK installed.
    Tuesday, January 14, 2014 9:35 PM
  • Just an update on my other post. Upgrading to R2 AND recapturing all my images did fix the issue. I have ran some servicing processes that contained 30+ updates and all completed without issue. I also can confirm using images that I serviced in 2012 SP1, remained broken after R2 upgrade; recapturing and starting over was the only way to fix.
    Friday, January 17, 2014 5:17 PM
  • So what's special about images captured by SCCM 2012 R2 versus an image captured by MDT 2012 ?
    Friday, January 17, 2014 6:51 PM
  • I'm not sure of all the details, but I know ConfigMgr 2012 and Configmgr 2012 SP1 use a different version of WAIK then ConfigMgr 2012 R2. I had heard that there was a bug in the WAIK that ConfigMgr2012 SP1 uses. My guess is that bug must carry over into after things are captured? (Or once it fails using the buggy version of dism.exe that image is altered to where it will always have an issue?).
    Friday, January 17, 2014 7:38 PM
  • It might be a good idea to recapture images after R2 upgrade. With Windows 8.1, I use original install.wim, but with Windows 7 it´s a bad idea, because there is hell of a lot updates coming.
    Sunday, January 19, 2014 3:06 PM
  • http://social.technet.microsoft.com/Forums/en-US/0e474b3e-67e4-409c-acb9-c0db81c17784/sccm-2012-sp1-offline-servicing-failed-errorinstallupdate-returned-code-0x800f082f?forum=configmanagerosd

    See if it helps.

    Wednesday, February 26, 2014 3:40 PM