dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
5076
share rss forum feed


plencnerb
Premium
join:2000-09-25
Carpentersville, IL
kudos:3

Issue installing MS13-054


Picture #1
Click for full size
Picture #2
Click for full size
Picture #3

Picture #4

Picture #5
 

Picture #6
Click for full size
Picture #7
As the title says, I am having an issue installing Microsoft Security Bulletin MS13-054: Vulnerability in GDI+ Could Allow Remote Code Execution (2848295).

When I would install it from Windows Update, I would get the error message and information shown in Picture #1.

I went ahead and found the web page for the actual bulletin, which, for reference is
https://technet.microsoft.com/en-us/security/bulletin/ms13-054

Looking at the list of Operating Systems, Programs, and so on, I find the area's that apply to my system. I'm running Windows 8 Pro x64, and I do have Office 2010 x64 with Service Pack 1 installed. So, the actual patches that apply to me are the ones that are in the red boxes in Picture #2 and Picture #3.

I then went ahead and downloaded the three patch files. The files I downloaded are listed below. We have the full name of the patch, and then the install file associated with the patch.

  • Security Update for Microsoft Office 2010 (KB2687276) 64-Bit Edition --> ogl2010-kb2687276-fullfile-x64-glb.exe
  • Security Update for Windows 8 for x64-based Systems (KB2835361) --> Windows8-RT-KB2835361-x64.msu
  • Security Update for Windows 8 for x64-based Systems (KB2835364) --> Windows8-RT-KB2835364-x64.msu

    I first tried to install the patch for Office 2010. When I do, Windows tells me that the patch has already been installed (see Picture #4).

    I then went and installed the patch for KB2835361. When I do, Windows tells me that the patch has already been installed (see Picture #5).

    Finally, I went and installed the patch for KB2835364. When I do, Windows asks if I want to install the update. I answer "Yes", and it starts to install. At the end, I get a message says that it was not installed, as shown in Picture #6.

    So, I then stopped the Windows Update Service, cleared my event logs, and finally deleted the file C:\Windows\WindowsUpdate.log.

    I then re-started the Windows Update Service. Once things were up and running, I went ahead and ran the install again for KB2835364. Again, it failed, and I see the event log as shown in Picture #7.

    I then went and looked at the WindowsUpdate.log, and here is the full section of the log for the install of this bulletin.

    2013-07-1714:43:39:859885223ccMisc===========  Logging initialized (build: 7.8.9200.16604, tz: -0500)  ===========
    2013-07-1714:43:39:859885223ccMisc  = Process: C:\Windows\system32\wusa.exe
    2013-07-1714:43:39:859885223ccMisc  = Module: C:\Windows\System32\wuapi.dll
    2013-07-1714:43:39:859885223ccCOMAPI-----------  COMAPI: IUpdateServiceManager::AddScanPackageService  -----------
    2013-07-1714:43:39:859885223ccCOMAPI  - ServiceName = Windows Update Standalone Installer
    2013-07-1714:43:39:859885223ccCOMAPI  - ScanFileLocation = C:\990d4bdfdc5da34bc3d2\wsusscan.cab
    2013-07-1714:43:39:957885223ccCOMAPI  - Added scan package service, ServiceID = {96BDC7B6-31F4-4465-AC83-A4CE69C46030} Third party service
    2013-07-1714:43:39:958885223ccCOMAPI-------------
    2013-07-1714:43:39:958885223ccCOMAPI-- START --  COMAPI: Init Search [ClientId = wusa]
    2013-07-1714:43:39:958885223ccCOMAPI---------
    2013-07-1714:43:39:958885223ccCOMAPI-------------
    2013-07-1714:43:39:958885223ccCOMAPI-- START --  COMAPI: Search [ClientId = wusa]
    2013-07-1714:43:39:958885223ccCOMAPI---------
    2013-07-1714:43:39:874 98012e0MiscValidating signature for C:\Windows\SoftwareDistribution\ScanFile\96bdc7b6-31f4-4465-ac83-a4ce69c46030\Source.cab:
    2013-07-1714:43:39:874 98012e0Misc Microsoft signed: Yes
    2013-07-1714:43:39:957 98012e0DtaStorDefault service for AU is {7971F918-A847-4430-9279-4A52D1EFE18D}
    2013-07-1714:43:39:962 9801600Agent*************
    2013-07-1714:43:39:962 9801600Agent** START **  Agent: Finding updates [CallerId = wusa]
    2013-07-1714:43:39:962 9801600Agent*********
    2013-07-1714:43:39:962 9801600Agent  * Online = Yes; Ignore download priority = No
    2013-07-1714:43:39:962 9801600Agent  * Criteria = "DeploymentAction='Installation'"
    2013-07-1714:43:39:962 9801600Agent  * ServiceID = {96BDC7B6-31F4-4465-AC83-A4CE69C46030} Third party service
    2013-07-1714:43:39:962 9801600Agent  * Search Scope = {Machine}
    2013-07-1714:43:39:963 9801600Agent  * Caller SID for Applicability: S-1-5-21-220463232-175254338-3496687295-1001
    2013-07-1714:43:39:963885223ccCOMAPI<<-- SUBMITTED -- COMAPI: Search [ClientId = wusa]
    2013-07-1714:43:40:124 9801600PT+++++++++++  PT: Synchronizing server updates  +++++++++++
    2013-07-1714:43:40:124 9801600PT  + Offline serviceId = {96BDC7B6-31F4-4465-AC83-A4CE69C46030}
    2013-07-1714:43:40:124 9801600PTWARNING: Cached cookie has expired or new PID is available
    2013-07-1714:43:41:590 9801600PT+++++++++++  PT: Synchronizing extended update info  +++++++++++
    2013-07-1714:43:41:591 9801600PT  + Offline serviceId = {96BDC7B6-31F4-4465-AC83-A4CE69C46030}
    2013-07-1714:43:41:630 9801600DnldMgrAdding revision ID 501 for update 2109E27A-B050-46C4-9123-8F241C065E29 to the lock revision cache.
    2013-07-1714:43:41:645 9801600Agent  * Added update {8CD69D56-B07C-48F2-8614-961989C20297}.501 to search result
    2013-07-1714:43:41:645 9801600Agent  * Found 1 updates and 57 categories in search; evaluated appl. rules of 126 out of 242 deployed entities
    2013-07-1714:43:41:646 9801600Agent*********
    2013-07-1714:43:41:646 9801600Agent**  END  **  Agent: Finding updates [CallerId = wusa]
    2013-07-1714:43:41:646 9801600Agent*************
    2013-07-1714:43:41:6478852230cCOMAPI>>--  RESUMED  -- COMAPI: Search [ClientId = wusa]
    2013-07-1714:43:41:6508852230cCOMAPI  - Updates found = 1
    2013-07-1714:43:41:6508852230cCOMAPI---------
    2013-07-1714:43:41:6508852230cCOMAPI--  END  --  COMAPI: Search [ClientId = wusa]
    2013-07-1714:43:41:6508852230cCOMAPI-------------
    2013-07-1714:43:43:639885223ccCOMAPI-------------
    2013-07-1714:43:43:639885223ccCOMAPI-- START --  COMAPI: Install [ClientId = wusa]
    2013-07-1714:43:43:639885223ccCOMAPI---------
    2013-07-1714:43:43:639885223ccCOMAPI  - Allow source prompts: Yes; Forced: No; Force quiet: No; Attempt close apps if necessary: No
    2013-07-1714:43:43:639885223ccCOMAPI  - Updates in request: 1
    2013-07-1714:43:43:639885223ccCOMAPI  - ServiceID = {96BDC7B6-31F4-4465-AC83-A4CE69C46030} Third party service
    2013-07-1714:43:43:390 9801b90DnldMgr***********  DnldMgr: Copy update to cache [UpdateId = {2109E27A-B050-46C4-9123-8F241C065E29}.501]  ***********
    2013-07-1714:43:43:390 9801b90DnldMgrAsking handler to generate non-range requests.
    2013-07-1714:43:43:390 9801b90HandlerGenerating request for CBS update 2109E27A-B050-46C4-9123-8F241C065E29 in sandbox C:\Windows\SoftwareDistribution\Download\9590584bcf0059b63e16dfffdb72de2e_ctc
    2013-07-1714:43:43:390 9801b90HandlerSelecting self-contained because update does not have express payload.
    2013-07-1714:43:43:390 9801b90HandlerSelected payload type is ptSelfContained
    2013-07-1714:43:43:390 9801b90HandlerDetected download state is dsStart
    2013-07-1714:43:43:390 9801b90HandlerAdding windows8-rt-kb2835364-x64.cab (entire file) to request list.
    2013-07-1714:43:43:390 9801b90HandlerRequest generation for CBS update complete with hr=0x0 and pfResetSandbox=0 
    2013-07-1714:43:43:515 9801b90MiscValidating signature for C:\Windows\SoftwareDistribution\Download\9590584bcf0059b63e16dfffdb72de2e_ctc\windows8-rt-kb2835364-x64.cab:
    2013-07-1714:43:43:546 9801b90Misc Microsoft signed: Yes
    2013-07-1714:43:43:546 9801b90DnldMgrAsking handler to generate non-range requests.
    2013-07-1714:43:43:546 9801b90HandlerGenerating request for CBS update 2109E27A-B050-46C4-9123-8F241C065E29 in sandbox C:\Windows\SoftwareDistribution\Download\9590584bcf0059b63e16dfffdb72de2e_ctc
    2013-07-1714:43:43:546 9801b90HandlerSelecting self-contained because update does not have express payload.
    2013-07-1714:43:43:546 9801b90HandlerSelected payload type is ptSelfContained
    2013-07-1714:43:43:546 9801b90HandlerDetected download state is dsHavePackage
    2013-07-1714:43:43:593 9801b90HandlerRequest generation for CBS update complete with hr=0x0 and pfResetSandbox=0 
    2013-07-1714:43:43:655 9801b90AgentBeginning install of conventional work item
    2013-07-1714:43:43:655885223ccCOMAPI  - Updates to install = 1
    2013-07-1714:43:43:655885223ccCOMAPI<<-- SUBMITTED -- COMAPI: Install [ClientId = wusa]
    2013-07-1714:43:43:655 9801078Agent*************
    2013-07-1714:43:43:655 9801078Agent** START **  Agent: Installing updates [CallerId = wusa]
    2013-07-1714:43:43:655 9801078Agent*********
    2013-07-1714:43:43:655 9801078Agent  * Updates to install = 1
    2013-07-1714:43:43:671 9801078Agent  *   Title = Security Update for Windows (KB2835364)
    2013-07-1714:43:43:671 9801078Agent  *   UpdateId = {8CD69D56-B07C-48F2-8614-961989C20297}.501
    2013-07-1714:43:43:671 9801078Agent  *     Bundles 1 updates:
    2013-07-1714:43:43:671 9801078Agent  *       {2109E27A-B050-46C4-9123-8F241C065E29}.501
    2013-07-1714:43:43:768 9801078HandlerAttempting to create remote handler process as BRIAN-DESKTOP\Brian A. Plencner in session 1
    2013-07-1714:43:43:803 9801078DnldMgrPreparing update for install, updateId = {2109E27A-B050-46C4-9123-8F241C065E29}.501.
    2013-07-1714:43:43:8063316924Misc===========  Logging initialized (build: 7.8.9200.16604, tz: -0500)  ===========
    2013-07-1714:43:43:8063316924Misc  = Process: C:\Windows\system32\wuauclt.exe
    2013-07-1714:43:43:8063316924Misc  = Module: C:\Windows\SYSTEM32\wuaueng.dll
    2013-07-1714:43:43:8043316924Handler:::::::::::::
    2013-07-1714:43:43:8063316924Handler:: START ::  Handler: CBS Install
    2013-07-1714:43:43:8063316924Handler:::::::::
    2013-07-1714:43:43:8093316924HandlerStarting install of CBS update 2109E27A-B050-46C4-9123-8F241C065E29
    2013-07-1714:43:43:8103316924HandlerCBS session identity: 30311205_4060751051
    2013-07-1714:43:43:8133316924HandlerCBS package identity: Package_for_KB2835364~31bf3856ad364e35~amd64~~6.2.1.1
    2013-07-1714:43:43:8143316924HandlerInstalling self-contained with source=C:\Windows\SoftwareDistribution\Download\9590584bcf0059b63e16dfffdb72de2e\windows8-rt-kb2835364-x64.cab, workingdir=C:\Windows\SoftwareDistribution\Download\9590584bcf0059b63e16dfffdb72de2e\inst
    2013-07-1714:43:52:8723316 48HandlerFATAL: CBS called Error with 0x80073712, 
    2013-07-1714:43:53:2123316924HandlerFATAL: Completed install of CBS update with type=0, requiresReboot=0, installerError=1, hr=0x80073712
    2013-07-1714:43:53:4843316924Handler:::::::::
    2013-07-1714:43:53:4843316924Handler::  END  ::  Handler: CBS Install
    2013-07-1714:43:53:4843316924Handler:::::::::::::
    2013-07-1714:43:53:530 9801078Agent*********
    2013-07-1714:43:53:530 9801078Agent**  END  **  Agent: Installing updates [CallerId = wusa]
    2013-07-1714:43:53:530 9801078Agent*************
    2013-07-1714:43:53:5308852230cCOMAPI>>--  RESUMED  -- COMAPI: Install [ClientId = wusa]
    2013-07-1714:43:53:5308852230cCOMAPI  - Install call complete (succeeded = 0, succeeded with errors = 0, failed = 1, unaccounted = 0)
    2013-07-1714:43:53:5308852230cCOMAPI  - Reboot required = No
    2013-07-1714:43:53:5308852230cCOMAPI  - WARNING: Exit code = 0x00000000; Call error code = 0x80240022
    2013-07-1714:43:53:5308852230cCOMAPI---------
    2013-07-1714:43:53:5308852230cCOMAPI--  END  --  COMAPI: Install [ClientId = wusa]
    2013-07-1714:43:53:5308852230cCOMAPI-------------
    2013-07-1714:44:01:907885223ccCOMAPI-----------  COMAPI: IUpdateServiceManager::RemoveService  -----------
    2013-07-1714:44:01:907885223ccCOMAPI  - ServiceId = {96bdc7b6-31f4-4465-ac83-a4ce69c46030}
    2013-07-1714:44:02:000885223ccCOMAPIIUpdateService removing volatile scan package service, serviceID = {96BDC7B6-31F4-4465-AC83-A4CE69C46030}
    2013-07-1714:44:02:000885223ccCOMAPIWARNING: ISusInternal::RemoveService failed, hr=80248014
     
    

    These lines looked to be related to the issue
    2013-07-1714:43:43:8143316924HandlerInstalling self-contained with source=C:\Windows\SoftwareDistribution\Download\9590584bcf0059b63e16dfffdb72de2e\windows8-rt-kb2835364-x64.cab, workingdir=C:\Windows\SoftwareDistribution\Download\9590584bcf0059b63e16dfffdb72de2e\inst
    2013-07-1714:43:52:8723316 48HandlerFATAL: CBS called Error with 0x80073712, 
    2013-07-1714:43:53:2123316924HandlerFATAL: Completed install of CBS update with type=0, requiresReboot=0, installerError=1, hr=0x80073712
     
     
    

    So, I stopped the Windows Update service, deleted the WindowsUpdate.log file, as well as the directory "9590584bcf0059b63e16dfffdb72de2e", as well as all the files in it.

    I re-started the service, and tried again, but I got the same error.

    So, my question is, what do I try next to resolve this issue?

    Thanks in advance for any help that can be offered.

    --Brian

    --
    ============================
    --Brian Plencner

    E-Mail: CoasterBrian72Cancer@gmail.com
    Note: Kill Cancer to Reply via e-mail

  • rfnut
    Premium
    join:2002-04-27
    Fisher, IL
    kudos:2

    did you try the steps suggested by MS for the error 0x80073712?

    »support.microsoft.com/kb/957310



    plencnerb
    Premium
    join:2000-09-25
    Carpentersville, IL
    kudos:3

    said by rfnut:

    did you try the steps suggested by MS for the error 0x80073712?

    »support.microsoft.com/kb/957310

    I have not run that yet. I will do so, and then report back if the issue has been resolved or not.

    --Brian
    --
    ============================
    --Brian Plencner

    E-Mail: CoasterBrian72Cancer@gmail.com
    Note: Kill Cancer to Reply via e-mail


    plencnerb
    Premium
    join:2000-09-25
    Carpentersville, IL
    kudos:3

    Ok. I went ahead and ran the two commands that were listed on the page.

    Below are the results.

    Microsoft Windows [Version 6.2.9200]
    (c) 2012 Microsoft Corporation. All rights reserved.
     
    C:\Windows\system32>DISM.exe /Online /Cleanup-image /Scanhealth
     
    Deployment Image Servicing and Management tool
    Version: 6.2.9200.16384
     
    Image Version: 6.2.9200.16384
     
    [==========================100.0%==========================]
    The component store is repairable.
    The operation completed successfully.
     
    C:\Windows\system32>DISM.exe /Online /Cleanup-image /Restorehealth
     
    Deployment Image Servicing and Management tool
    Version: 6.2.9200.16384
     
    Image Version: 6.2.9200.16384
     
    [==========================100.0%==========================]
    The restore operation completed successfully. The component store corruption was
     repaired.
    The operation completed successfully.
     
    C:\Windows\system32>
     
     
    

    Did not do a reboot, but I deleted the WindowsUpdate.log file, as well as the events in Event Viewer.

    I ran the update again, and it still failed. This time, the error code is 0x80070003.

    So, looks like one problem solved, and it created another.

    Here is the WindowsUpdate.log file

    2013-07-1717:01:48:19491681850Misc===========  Logging initialized (build: 7.8.9200.16604, tz: -0500)  ===========
    2013-07-1717:01:48:19491681850Misc  = Process: C:\Windows\system32\wusa.exe
    2013-07-1717:01:48:19491681850Misc  = Module: C:\Windows\System32\wuapi.dll
    2013-07-1717:01:48:19391681850COMAPI-----------  COMAPI: IUpdateServiceManager::AddScanPackageService  -----------
    2013-07-1717:01:48:19491681850COMAPI  - ServiceName = Windows Update Standalone Installer
    2013-07-1717:01:48:19491681850COMAPI  - ScanFileLocation = C:\e43978d9085fd8fff38ffc0887\wsusscan.cab
    2013-07-1717:01:48:23191681850COMAPI  - Added scan package service, ServiceID = {2779B287-8033-4585-982D-D61C2B74633E} Third party service
    2013-07-1717:01:48:23191681850COMAPI-------------
    2013-07-1717:01:48:23191681850COMAPI-- START --  COMAPI: Init Search [ClientId = wusa]
    2013-07-1717:01:48:23191681850COMAPI---------
    2013-07-1717:01:48:23191681850COMAPI-------------
    2013-07-1717:01:48:23191681850COMAPI-- START --  COMAPI: Search [ClientId = wusa]
    2013-07-1717:01:48:23191681850COMAPI---------
    2013-07-1717:01:48:201 98010bcMiscValidating signature for C:\Windows\SoftwareDistribution\ScanFile\2779b287-8033-4585-982d-d61c2b74633e\Source.cab:
    2013-07-1717:01:48:211 98010bcMisc Microsoft signed: Yes
    2013-07-1717:01:48:230 98010bcDtaStorDefault service for AU is {7971F918-A847-4430-9279-4A52D1EFE18D}
    2013-07-1717:01:48:23591681850COMAPI<<-- SUBMITTED -- COMAPI: Search [ClientId = wusa]
    2013-07-1717:01:48:236 9801210Agent*************
    2013-07-1717:01:48:236 9801210Agent** START **  Agent: Finding updates [CallerId = wusa]
    2013-07-1717:01:48:236 9801210Agent*********
    2013-07-1717:01:48:236 9801210Agent  * Online = Yes; Ignore download priority = No
    2013-07-1717:01:48:236 9801210Agent  * Criteria = "DeploymentAction='Installation'"
    2013-07-1717:01:48:236 9801210Agent  * ServiceID = {2779B287-8033-4585-982D-D61C2B74633E} Third party service
    2013-07-1717:01:48:236 9801210Agent  * Search Scope = {Machine}
    2013-07-1717:01:48:236 9801210Agent  * Caller SID for Applicability: S-1-5-21-220463232-175254338-3496687295-1001
    2013-07-1717:01:48:378 9801210PT+++++++++++  PT: Synchronizing server updates  +++++++++++
    2013-07-1717:01:48:378 9801210PT  + Offline serviceId = {2779B287-8033-4585-982D-D61C2B74633E}
    2013-07-1717:01:48:379 9801210PTWARNING: Cached cookie has expired or new PID is available
    2013-07-1717:01:49:379 9801210PT+++++++++++  PT: Synchronizing extended update info  +++++++++++
    2013-07-1717:01:49:379 9801210PT  + Offline serviceId = {2779B287-8033-4585-982D-D61C2B74633E}
    2013-07-1717:01:49:414 9801210DnldMgrAdding revision ID 501 for update 2109E27A-B050-46C4-9123-8F241C065E29 to the lock revision cache.
    2013-07-1717:01:49:429 9801210Agent  * Added update {8CD69D56-B07C-48F2-8614-961989C20297}.501 to search result
    2013-07-1717:01:49:429 9801210Agent  * Found 1 updates and 57 categories in search; evaluated appl. rules of 126 out of 242 deployed entities
    2013-07-1717:01:49:430 9801210Agent*********
    2013-07-1717:01:49:430 9801210Agent**  END  **  Agent: Finding updates [CallerId = wusa]
    2013-07-1717:01:49:430 9801210Agent*************
    2013-07-1717:01:49:43191681d4cCOMAPI>>--  RESUMED  -- COMAPI: Search [ClientId = wusa]
    2013-07-1717:01:49:43391681d4cCOMAPI  - Updates found = 1
    2013-07-1717:01:49:43391681d4cCOMAPI---------
    2013-07-1717:01:49:43391681d4cCOMAPI--  END  --  COMAPI: Search [ClientId = wusa]
    2013-07-1717:01:49:43391681d4cCOMAPI-------------
    2013-07-1717:01:53:28091681850COMAPI-------------
    2013-07-1717:01:53:28091681850COMAPI-- START --  COMAPI: Install [ClientId = wusa]
    2013-07-1717:01:53:28091681850COMAPI---------
    2013-07-1717:01:53:28091681850COMAPI  - Allow source prompts: Yes; Forced: No; Force quiet: No; Attempt close apps if necessary: No
    2013-07-1717:01:53:28091681850COMAPI  - Updates in request: 1
    2013-07-1717:01:53:28091681850COMAPI  - ServiceID = {2779B287-8033-4585-982D-D61C2B74633E} Third party service
    2013-07-1717:01:52:979 98010bcDnldMgr***********  DnldMgr: Copy update to cache [UpdateId = {2109E27A-B050-46C4-9123-8F241C065E29}.501]  ***********
    2013-07-1717:01:52:980 98010bcDnldMgrAsking handler to generate non-range requests.
    2013-07-1717:01:52:980 98010bcHandlerGenerating request for CBS update 2109E27A-B050-46C4-9123-8F241C065E29 in sandbox C:\Windows\SoftwareDistribution\Download\9590584bcf0059b63e16dfffdb72de2e_ctc
    2013-07-1717:01:52:981 98010bcHandlerSelecting self-contained because update does not have express payload.
    2013-07-1717:01:52:981 98010bcHandlerSelected payload type is ptSelfContained
    2013-07-1717:01:52:981 98010bcHandlerDetected download state is dsStart
    2013-07-1717:01:52:981 98010bcHandlerAdding windows8-rt-kb2835364-x64.cab (entire file) to request list.
    2013-07-1717:01:52:982 98010bcHandlerRequest generation for CBS update complete with hr=0x0 and pfResetSandbox=0 
    2013-07-1717:01:53:083 98010bcMiscValidating signature for C:\Windows\SoftwareDistribution\Download\9590584bcf0059b63e16dfffdb72de2e_ctc\windows8-rt-kb2835364-x64.cab:
    2013-07-1717:01:53:116 98010bcMisc Microsoft signed: Yes
    2013-07-1717:01:53:116 98010bcDnldMgrAsking handler to generate non-range requests.
    2013-07-1717:01:53:120 98010bcHandlerGenerating request for CBS update 2109E27A-B050-46C4-9123-8F241C065E29 in sandbox C:\Windows\SoftwareDistribution\Download\9590584bcf0059b63e16dfffdb72de2e_ctc
    2013-07-1717:01:53:120 98010bcHandlerSelecting self-contained because update does not have express payload.
    2013-07-1717:01:53:120 98010bcHandlerSelected payload type is ptSelfContained
    2013-07-1717:01:53:121 98010bcHandlerDetected download state is dsHavePackage
    2013-07-1717:01:53:167 98010bcHandlerRequest generation for CBS update complete with hr=0x0 and pfResetSandbox=0 
    2013-07-1717:01:53:287 98010bcAgentBeginning install of conventional work item
    2013-07-1717:01:53:28791681850COMAPI  - Updates to install = 1
    2013-07-1717:01:53:28891681850COMAPI<<-- SUBMITTED -- COMAPI: Install [ClientId = wusa]
    2013-07-1717:01:53:288 9801694Agent*************
    2013-07-1717:01:53:288 9801694Agent** START **  Agent: Installing updates [CallerId = wusa]
    2013-07-1717:01:53:288 9801694Agent*********
    2013-07-1717:01:53:288 9801694Agent  * Updates to install = 1
    2013-07-1717:01:53:289 9801694Agent  *   Title = Security Update for Windows (KB2835364)
    2013-07-1717:01:53:289 9801694Agent  *   UpdateId = {8CD69D56-B07C-48F2-8614-961989C20297}.501
    2013-07-1717:01:53:289 9801694Agent  *     Bundles 1 updates:
    2013-07-1717:01:53:289 9801694Agent  *       {2109E27A-B050-46C4-9123-8F241C065E29}.501
    2013-07-1717:01:53:434 9801694HandlerAttempting to create remote handler process as BRIAN-DESKTOP\Brian A. Plencner in session 1
    2013-07-1717:01:53:474 9801694DnldMgrPreparing update for install, updateId = {2109E27A-B050-46C4-9123-8F241C065E29}.501.
    2013-07-1717:01:53:4764260aa4Misc===========  Logging initialized (build: 7.8.9200.16604, tz: -0500)  ===========
    2013-07-1717:01:53:4764260aa4Misc  = Process: C:\Windows\system32\wuauclt.exe
    2013-07-1717:01:53:4764260aa4Misc  = Module: C:\Windows\SYSTEM32\wuaueng.dll
    2013-07-1717:01:53:4754260aa4Handler:::::::::::::
    2013-07-1717:01:53:4764260aa4Handler:: START ::  Handler: CBS Install
    2013-07-1717:01:53:4764260aa4Handler:::::::::
    2013-07-1717:01:53:4794260aa4HandlerStarting install of CBS update 2109E27A-B050-46C4-9123-8F241C065E29
    2013-07-1717:01:53:4814260aa4HandlerCBS session identity: 30311225_1058112121
    2013-07-1717:01:53:4824260aa4HandlerCBS package identity: Package_for_KB2835364~31bf3856ad364e35~amd64~~6.2.1.1
    2013-07-1717:01:53:4834260aa4HandlerInstalling self-contained with source=C:\Windows\SoftwareDistribution\Download\9590584bcf0059b63e16dfffdb72de2e\windows8-rt-kb2835364-x64.cab, workingdir=C:\Windows\SoftwareDistribution\Download\9590584bcf0059b63e16dfffdb72de2e\inst
    2013-07-1717:02:02:134426015c0HandlerFATAL: CBS called Error with 0x80070003, 
    2013-07-1717:02:02:6974260aa4HandlerFATAL: Completed install of CBS update with type=0, requiresReboot=0, installerError=1, hr=0x80070003
    2013-07-1717:02:02:7644260aa4Handler:::::::::
    2013-07-1717:02:02:7644260aa4Handler::  END  ::  Handler: CBS Install
    2013-07-1717:02:02:7644260aa4Handler:::::::::::::
    2013-07-1717:02:02:769 9801694Agent*********
    2013-07-1717:02:02:769 9801694Agent**  END  **  Agent: Installing updates [CallerId = wusa]
    2013-07-1717:02:02:769 9801694Agent*************
    2013-07-1717:02:02:76991681d4cCOMAPI>>--  RESUMED  -- COMAPI: Install [ClientId = wusa]
    2013-07-1717:02:02:76991681d4cCOMAPI  - Install call complete (succeeded = 0, succeeded with errors = 0, failed = 1, unaccounted = 0)
    2013-07-1717:02:02:76991681d4cCOMAPI  - Reboot required = No
    2013-07-1717:02:02:76991681d4cCOMAPI  - WARNING: Exit code = 0x00000000; Call error code = 0x80240022
    2013-07-1717:02:02:76991681d4cCOMAPI---------
    2013-07-1717:02:02:76991681d4cCOMAPI--  END  --  COMAPI: Install [ClientId = wusa]
    2013-07-1717:02:02:76991681d4cCOMAPI-------------
    2013-07-1717:02:06:73291681850COMAPI-----------  COMAPI: IUpdateServiceManager::RemoveService  -----------
    2013-07-1717:02:06:73291681850COMAPI  - ServiceId = {2779b287-8033-4585-982d-d61c2b74633e}
    2013-07-1717:02:06:75991681850COMAPIIUpdateService removing volatile scan package service, serviceID = {2779B287-8033-4585-982D-D61C2B74633E}
    2013-07-1717:02:06:76191681850COMAPIWARNING: ISusInternal::RemoveService failed, hr=80248014
     
    

    --Brian

    --
    ============================
    --Brian Plencner

    E-Mail: CoasterBrian72Cancer@gmail.com
    Note: Kill Cancer to Reply via e-mail

    rfnut
    Premium
    join:2002-04-27
    Fisher, IL
    kudos:2

    When you have update issues you usually have to remove more than just the update log. Especially if you have manually downloaded anything:
    »support.microsoft.com/kb/910336



    Dustyn
    Premium
    join:2003-02-26
    Ontario, CAN
    kudos:11
    reply to plencnerb

    Do you have Auto Updates enabled? (Auto download and install?)
    What does your Windows Update installed update history look like?



    Steve Mehs
    Gun Control Is Using A Steady Hand
    Premium
    join:2005-07-16
    kudos:1
    reply to plencnerb

    I thought that KB# looked familiar. I'm having the exact same issue here, but with Office 2013 installed. The update installed fine on my laptop with Windows 7/Office 2013, but failed and keeps failing on my desktop with Windows 8. I tried installing the update manually, but like you I also get the message that the update is already installed. That's as far as I went. I have the update hidden right now.
    --
    4/17/13 - A Beautiful Day For Freedom, Thank You United States Senate!
    Message to Anti-Gun Liberals: HA HA!
    Hussein Obama 0 – American Public 1
    “the right of the people to keep and bear arms shall not be infringed”
    Repeal Obamacare Now!



    plencnerb
    Premium
    join:2000-09-25
    Carpentersville, IL
    kudos:3
    reply to rfnut

    Click for full size
    said by rfnut:

    When you have update issues you usually have to remove more than just the update log. Especially if you have manually downloaded anything:
    »support.microsoft.com/kb/910336

    Will look at that next. I'll report back once I've done the steps in that item.

    said by Dustyn:

    Do you have Auto Updates enabled? (Auto download and install?)
    What does your Windows Update installed update history look like?

    I do not have Auto Updates enabled. I have it set to "Never check for updates (not recommended).

    As far as my Windows Update installed history look like, see the above picture.

    --Brian
    --
    ============================
    --Brian Plencner

    E-Mail: CoasterBrian72Cancer@gmail.com
    Note: Kill Cancer to Reply via e-mail


    plencnerb
    Premium
    join:2000-09-25
    Carpentersville, IL
    kudos:3
    reply to plencnerb

    Well, I did the steps in that kb article, and I got the same issue. Same error code returned (0x80070003).

    --Brian


    rfnut
    Premium
    join:2002-04-27
    Fisher, IL
    kudos:2
    Reviews:
    ·Mediacom

    A quick google of KB2835364 failed win8 has many in the same boat. At overclockers, a suggestion was made that changes to the start menu could cause this. ( like using start8 and customizing menus shortcuts). This was based on a solution of running sfc /scannow to repair from MS
    Link:
    »forums.overclockers.co.uk/showth···24618796



    plencnerb
    Premium
    join:2000-09-25
    Carpentersville, IL
    kudos:3

    said by rfnut:

    A quick google of KB2835364 failed win8 has many in the same boat. At overclockers, a suggestion was made that changes to the start menu could cause this. ( like using start8 and customizing menus shortcuts). This was based on a solution of running sfc /scannow to repair from MS
    Link:
    »forums.overclockers.co.uk/showth···24618796

    Well, with that, I think we can call this problem solved. I know that I make a LOT of modifications to the layout / organization of this directory

    C:\ProgramData\Microsoft\Windows\Start Menu\Programs

    when I install Windows 8. In fact, this would be the 2nd patch that will not install if you "modify" the start screen items.

    As I have made reference to in a few posts, I have this text file that contains the steps that I follow to install, configure, and setup Windows 8. It is 80 steps long!

    I had to modify my process a bit to account for that first patch, as one of my steps was to take every file / folder out of that location (minus the "Administrative Tools" and "Startup" folders), and move them to the desktop. Doing that caused a patch (don't remember which one at this point), not to install. Not doing that step, the patch installs without issue.

    At this point, I know I'm not able to "put things back the way they are on install", so I'm just going to ignore the failure until I rebuild my system. Since I install the first set of patches before any modifications are made to the start screen, this patch (MS13-054), and whatever the other one was, will be installed at that time, and life will then be good.

    I would also like to say, that as far as I know, these two (MS13-054, and whatever the other one is), are the first patches that I can think of, under Windows 8, that will not install if a given shortcut is not in the proper place. This has never been the case for Windows XP, or Windows 7. I cannot speak for Windows Vista, as I have never run it. However, I do know that in both XP and Windows 7, I have made many modifications to the start menu just like I do to the start screen in Windows 8. I hope that this is not a trend that Microsoft is starting to move towards.

    Speaking of Microsoft, it makes me wonder why a patch requires that a given shortcut be in a specific location on your system. Most times, these patches update DLL's or EXE's. We'll probably never know, but I wonder what logic or reason Microsoft has for doing it that way. If they are trying to figure out if a program is installed (to see if said patch is applicable), even if it is installed by default in the OS, I would think it would be better to verify the executable that the shortcut points to, rather then the shortcut itself. The whole point behind shortcuts is to allow the end user to modify them (change their name, where they are stored, and so on), and not have to worry about where the application is at.

    --Brian
    --
    ============================
    --Brian Plencner

    E-Mail: CoasterBrian72Cancer@gmail.com
    Note: Kill Cancer to Reply via e-mail


    Steve Mehs
    Gun Control Is Using A Steady Hand
    Premium
    join:2005-07-16
    kudos:1
    reply to plencnerb

    well what do ya know, it worked! I uninstalled Classic Shell, ran sfc /scannow, KB2835364 installed successfully, reinstalled Classic Shell and all good to go. Thanks for the link Rfnut!


    rfnut
    Premium
    join:2002-04-27
    Fisher, IL
    kudos:2

    You're welcome. Glad it worked.



    plencnerb
    Premium
    join:2000-09-25
    Carpentersville, IL
    kudos:3
    reply to Steve Mehs

    said by Steve Mehs:

    well what do ya know, it worked! I uninstalled Classic Shell, ran sfc /scannow, KB2835364 installed successfully, reinstalled Classic Shell and all good to go. Thanks for the link Rfnut!

    Knowing that fixed your issue, then that just adds more proof that is why it is also not installing for me (outside of what I said above).

    As I said, I do make a ton of changes to the default folders / shortcuts. I don't rename any of the shortcuts, I just rename the folders that are there, and move the shortcuts around to different folders.

    --Brian
    --
    ============================
    --Brian Plencner

    E-Mail: CoasterBrian72Cancer@gmail.com
    Note: Kill Cancer to Reply via e-mail


    Steve Mehs
    Gun Control Is Using A Steady Hand
    Premium
    join:2005-07-16
    kudos:1
    reply to plencnerb

    Click for full size
    Yep same here. I didn’t rename shortcuts but customized the names and content of the folders that contain those shortcuts. Running the sfc /scannow command (it does take a long time to complete) and rebooting afterword should allow you to download the update without a problem, and then just reapply your customizations. The problem must have been specific to Windows 8, because on my two Windows 7 machines I have Classic Shell installed and things renamed and no issue there.

    Just a heads up, maybe it was my system, but the first time I tried to install the update, after going through the whole process, and even after rebooting, it did fail one more time, rebooted and tried again, and it was a success! I’m extremely anal and OCD about my computers and I hate having failed updates, and this is one of the only ones that has ever given me a problem. After getting it installed I now know what it feels like to win the Super Bowl, Stanley Cup and World Series all in the same day.

    Mele20
    Premium
    join:2001-06-05
    Hilo, HI
    kudos:5
    reply to plencnerb

    I have Start 8 and Decor and use Windows Blinds with LOTS of modifications of Windows 8. But I didn't move files about like I recall reading in other threads that you did. I had no difficulty installing those two patches. I use Open Office on Win 8 so did not need the Office patch.

    I can't help but wonder if you had not used WU, but did a direct download of the patches from Microsoft Download site, if you could have installed them. I don't use WU and I had no problems with direct downloads to disk of all patches this month and then installing a few....then using the computer for awhile to make sure things were ok, then installing a few more...rinse and repeat. I was so surprised that I had zero problems installing a huge bunch of .NET patches and each installed very quickly too.
    --
    When governments fear people, there is liberty. When the people fear the government, there is tyranny. Thomas Jefferson



    plencnerb
    Premium
    join:2000-09-25
    Carpentersville, IL
    kudos:3

    said by Mele20:

    I can't help but wonder if you had not used WU, but did a direct download of the patches from Microsoft Download site, if you could have installed them. I don't use WU and I had no problems with direct downloads to disk of all patches this month and then installing a few....then using the computer for awhile to make sure things were ok, then installing a few more...rinse and repeat. I was so surprised that I had zero problems installing a huge bunch of .NET patches and each installed very quickly too.

    Well, that is what is interesting. The problem first showed up when I was using WU, but it continued when I actually downloaded the patch files directly, and ran them on my system.

    This tells me that somewhere in the coding of the patch, there is some check that is done before the patch runs / installs. Its like the checks that were built into games or other software years ago, that would check to verify that you had enough disk space to install the application, or that your CPU was fast enough, or that you had enough Ram. If you have ever tried to install something like that on a computer from Today, running the older OS, it won't install. In fact, you may get some strange or odd message, and may not know why it won't install.

    The same appears to be true with this patch. If the patch is actually looking for the shortcut to Calculator (as an example...I don't know what specific shortcut it is looking for) to be in a specific place, for verification that you have it installed, and the patch installer does not find it, it returns some generic error message and code. Yet, if it said something like "This patch could not be installed because the shortcut for the calculator application could not be found in C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Accessories. Please correct the issue, and try to install the patch again".

    If it said that, it would make things like this a whole lot easier!

    Not to mention, I don't get why Microsoft feels it is so important to verify the location of a shortcut. I know there are other checks that are done when your computer is doing the "Scanning for patches" part, and whatever it did, it determined that my system had the files installed that needed to be patched (Exe's or DLL's come to mind here), which is why it offered me the patch to begin with. So, why would the actual install of the patch look for a shortcut? I could see it doing one final check for specific DLL's, or EXE's, but a shortcut? That is what I don't get.

    --Brian
    --
    ============================
    --Brian Plencner

    E-Mail: CoasterBrian72Cancer@gmail.com
    Note: Kill Cancer to Reply via e-mail


    plencnerb
    Premium
    join:2000-09-25
    Carpentersville, IL
    kudos:3
    reply to plencnerb

    Click for full size
    I just wanted to update this thread to indicate that I now have MS13-054 installed. I rebuilt my machine yesterday. As I indicated in this thread, I do make a ton of changes to the folder structure at the following locations

    • C:\ProgramData\Microsoft\Windows\Start Menu\Programs
    • C:\Users\Administrator\AppData\Roaming\Microsoft\Windows\Start Menu\Programs
    • C:\Users\Brian A. Plencner\AppData\Roaming\Microsoft\Windows\Start Menu\Programs

    Since during my process of installing Windows 8, I apply the first set of patches before any changes are done to the above directories, it installed without issue, as everything was in place as Microsoft "thinks" it should be.

    I did some research on why this would be the case. Here is a link that has all the information on this KB article that did not install for me

    »support.microsoft.com/kb/2835364

    If you open up all the sections, you will get A LOT of information, including all the files that are updated for every version of the OS that is supported by this patch.

    I've been able to determine that this update has to do with Windows Journal. By default on Windows 8 x64, Windows Journal is installed (meaning the exe physically resides at) the following location: C:\Program Files\Windows Journal\Journal.exe

    The shortcut on my system is now at this location: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Windows Accessories\Windows Journal.lnk

    I *think* that is not where the shortcut is at by default. I believe it is in a folder called "Tablet PC" or something. I know in my process, I take that one shortcut (Journal) out of that folder, move it with the other "Windows Accessories", and then delete the Tablet PC folder. I do this to help reduce the number of folders, and to clean things up a bit.

    It appears then to me that the patch does some directory verifications to see if the shortcut is in the "proper" place (as far as Microsoft goes, based on where it was installed by default inside of the OS). If it does not find it, it throws an error.

    What's interesting is that I did not move (and would have no reason to do so) the actual EXE.

    Again, this is why I made the comment before about doing verifications of installed software based on the LOCATION of a shortcut, and why its a bad idea. The whole reason for a shortcut is to allow you to move that shortcut to anyplace on your system. It makes it easier for the end user to launch the given application, without having to know where the actual EXE is at. To use the shortcut as a means to verify that an application is installed, right down to where the shortcut must be located, seems a bit odd to me.

    In any case, problem has been solved.

    --Brian
    --
    ============================
    --Brian Plencner

    E-Mail: CoasterBrian72Cancer@gmail.com
    Note: Kill Cancer to Reply via e-mail

    Mele20
    Premium
    join:2001-06-05
    Hilo, HI
    kudos:5

    By default it resides here: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Accessories\Tablet PC
    The only thing in the folder is the shortcut

    Did you call Microsoft about this? You should because I agree that a shortcut exists for the user to put wherever they want it. For Microsoft to be using a shortcut to determine whether or not a security patch should be installed is absurd. Microsoft should be made aware of this problem.
    --
    When governments fear people, there is liberty. When the people fear the government, there is tyranny. Thomas Jefferson



    Sherlocc

    @174.127.228.x
    reply to plencnerb

    I tried the suggestions from this forum and others for the installation of KB2835364 and KB2822241 including sfc /scannow - reboots and all. No joy. I really can't believe that even Microsoft would be dumb enough to need shortcuts to remain in a fixed location. And by the way I have Start 8 installed on 3 Windows8 systems and had different results on the three. One installed one of the updates, another both, and the third neither!

    I finally did the one tried and true approach I should have started with - disable the antivirus software during the updates! After the requisite reboot the problem was solved on the 2 failing systems.

    KB2835364 and KB2822241 are now both installed successfully on all three. I would suggest anyone finding this post should disable the antivirus software as a first step in this process. No guarantees, but it sure worked for me.



    CarlS

    @charter.com

    "Tried and true"? Disabling Anti-virus?

    In as much as the only A-V and firewall I am using (at the moment) is Microsoft's own Win8 built-in MS Defender, I had assumed Microsoft engineers were smart enough to factor their own updates into the protection schema.

    I'll disable Defender. If it works, I'll accept that MS is - again - wrong.

    (and now you see why MS has so far failed to provide a "Snark Font".)



    Hall
    Premium,MVM
    join:2000-04-28
    Germantown, OH
    kudos:2
    reply to plencnerb

    Having trouble installing the same KB2835364 and I noticed in the Windows Update screen that it says it's for Window x64 systems. This is happening on my wife's laptop running Windows 7 32-bit though. Is the text in WU just generic ?

    MS says to do a few different things: Run checksur (when I download it and try to run it, it says it's not for this system), sfc /scannow but that completes with no errors, something else that I can't recall at the moment, and finally, run an in-place Windows upgrade using the Windows CD/DVD. We're in the process of moving and I can't locate the discs, besides the fact that they're recovery discs from ACER, not Microsoft discs. I think all I can do is restore Windows, not do an in-place upgrade.

    I did try downloading the KB update manually (»www.microsoft.com/en-us/download···id=39459) vs using WU and I get an error: "This update is not applicable to your computer"

    I also saw the reference to changing Start Menu items - how in the world do you reset them to stock ?



    plencnerb
    Premium
    join:2000-09-25
    Carpentersville, IL
    kudos:3


    #1
     
    Click for full size
    #2
    said by Hall:

    Having trouble installing the same KB2835364 and I noticed in the Windows Update screen that it says it's for Window x64 systems. This is happening on my wife's laptop running Windows 7 32-bit though. Is the text in WU just generic ?

    That's interesting. I know in my screen shots, it will show for Window x64 system, as I am running Windows 8 x64 Pro. However, that patch does apply to the following Operating Systems:

    • Windows XP Tablet PC Edition 2005 only (Windows XP Service Pack 3)
    • Windows Vista Service Pack 2 (32-bit)
    • Windows Vista Service Pack 2 (64-bit)
    • Windows Server 2008 Service Pack 2 (32-bit)
    • Windows Server 2008 Service Pack 2 (64-bit)
    • Windows 7 Service Pack 1 (32-bit)
    • Windows 7 Service Pack 1 (64-bit)
    • Windows Server 2008 R2 (64-bit)
    • Windows 8 (32-bit)
    • Windows 8 (64-bit)
    • Windows Server 2012

    I would think that when you look at the screen of your wife's system it probably does say for Windows 7 Service Pack 1 (32-bit), and not Windows 7 Service Pack 1 (64-bit).

    By the way, that list comes from this page
    »support.microsoft.com/kb/2835364

    said by Hall:

    I also saw the reference to changing Start Menu items - how in the world do you reset them to stock ?

    I don't know a magical way to "reset your start menu back to default", short of doing a re-install of windows. However, I have done some research and limited testing on this. The research that I have done indicates that the shortcut in question is the Windows Journal Viewer. On Windows 8, that shortcut by default is located at C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Accessories\Tablet PC (btw, Thanks Mele20 See Profile for posting this ).

    I'm currently looking at my girlfriends Windows 7 x64 system, and the default location of that icon on the start menu is shown in Picture #1 above. Which, would put the shortcut at this location: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Accessories\Tablet PC (see picture #2).

    So, I'm thinking for Windows 7, if you moved or renamed that "Tablet PC" folder, or the icons contained in it, that could be why it is not installing for you. I would think then if you put it back to to that location, the update may install.

    --Brian
    --
    ============================
    --Brian Plencner

    E-Mail: CoasterBrian72Cancer@gmail.com
    Note: Kill Cancer to Reply via e-mail


    Hall
    Premium,MVM
    join:2000-04-28
    Germantown, OH
    kudos:2

    I didn't think much of the wording saying "x64", just figured it was 'generic' text as there really is a proper version of this update for 32-bit systems. Here's a screenshot, in case anyone's interested (or doesn't believe me !! ):




    The shortcut for Tablet PC stuff is in the proper location also.




    plencnerb
    Premium
    join:2000-09-25
    Carpentersville, IL
    kudos:3

    Click for full size
    Interesting.

    Do you also have this folder?

    C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Tablet PC

    On my girlfriends windows 7 x64 system, she has that too, but its empty (see above)
    --
    ============================
    --Brian Plencner

    E-Mail: CoasterBrian72Cancer@gmail.com
    Note: Kill Cancer to Reply via e-mail


    Hall
    Premium,MVM
    join:2000-04-28
    Germantown, OH
    kudos:2

    Have it and it's NOT empty. It has the same (3) shortcuts that appear in the Start menu.

    I just moved the (3) items out of that folder and let's see if it let's this update apply.... Nope, it immediately fails with the same error # from above.