none
windows 2008 r2 sp1 installation error 0x800f081f

    Question

  • I have two servers that are nearly identical running Windows 2008 R2.  Both are Hyper-V hosts.  I have applied SP1 to one of them, but am having problems getting SP1 to install on the 2nd one.  The downloaded installation fails with 0x800f081f. 

    I have found posts that refer to the Remote Server Administration Tools (RSAT) but since this is NOT Windows 7 and I have not installed the RSAT tools, I am at a loss.

    I have also found this thread that seems to be similar to my issue, except the O/S is Windows 7 instead of Windows 2008 R2.

    I can see the failure in the CBS.log file, but don't know how to troubleshoot this problem.

    2011-03-03 21:38:06, Info                  CBS    Calling client to resolve source, cannot find file 'TsUsbGD.sys' at path: \\?\C:\Windows\Servicing\Packages\amd64_tsgenericusbdriver.inf_31bf3856ad364e35_6.1.7601.17514_none_9872c8452ac8f816\TsUsbGD.sys
    2011-03-03 21:38:06, Error                 CBS    Exec: Failed to pre-stage package: Package_for_KB976933~31bf3856ad364e35~amd64~cs-CZ~6.1.7601.17514, file: TsUsbGD.sys, source: \\?\C:\Windows\Servicing\Packages\amd64_tsgenericusbdriver.inf_31bf3856ad364e35_6.1.7601.17514_none_9872c8452ac8f816\TsUsbGD.sys, sandbox: (null) [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
    2011-03-03 21:38:06, Info                  CBS    Failed to gather all required files. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
    2011-03-03 21:38:06, Info                  CBS    Failed to gather all missing files for package: Package_for_KB976932~31bf3856ad364e35~amd64~~6.1.1.17514 [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
    2011-03-03 21:38:06, Info                  CSI    0000000e@2011/3/4:03:38:06.785 CSI Transaction @0x3316be0 destroyed
    2011-03-03 21:38:06, Error                 CBS    Failed to pre- stage package: Package_for_KB976932~31bf3856ad364e35~amd64~~6.1.1.17514 [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
    2011-03-03 21:38:06, Info                  CBS    Perf: Stage chain complete.
    2011-03-03 21:38:06, Info                  CBS    Failed to stage execution chain. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
    2011-03-03 21:38:06, Error                 CBS    Failed to process Multi-phase execution. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
    2011-03-03 21:38:06, Info                  CBS    WER: Generating failure report for package: Package_for_KB976932~31bf3856ad364e35~amd64~~6.1.1.17514, status: 0x800f081f, failure source: Stage, start state: Staged, target state: Staged, client id: SP Coordinater Engine
    2011-03-03 21:38:06, Info                  CBS    Failed to query DisableWerReporting flag.  Assuming not set... [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2011-03-03 21:38:07, Info                  CBS    Failed to add %windir%\winsxs\pending.xml to WER report because it is missing.  Continuing without it...
    2011-03-03 21:38:07, Info                  CBS    Failed to add %windir%\winsxs\pending.xml.bad to WER report because it is missing.  Continuing without it...

    I have also attempted an SP1 installation using Windows Update, but it fails, too.

    I have installed the System Update Readiness Tool with no change in the outcome.

    I have run sfc /scannow with no effect.

    Can anyone assist?

    Thanks...Russ

     

    Friday, March 04, 2011 4:29 PM

Answers

  • Hello,

    I had the same problem. In the system eventlog I found an error entry ID 7 from source Service Pack Installer which informed me about a problem with a package. I used the command

    dism /online /remove-package /packagename:[Package_as_named_in_log]

    to remove this package. After this, installation succeeded without any problems.

     

    Regards
    Andreas

    Monday, March 07, 2011 6:20 AM
  • All--

    I followed Andreas' advice and ran the command for the Deployment Image Services and Management Tool:

    dism /online /remove-package /packagename:Package_for_KB976932~31bf3856ad364e35~amd64~~6.1.1.17514

    and it went through the process of removing the package (took a while), after which I was able to successfully install SP1.  When the server rebooted, it went through another extended period of updates.  I'm putting together a blog post with pictures.

    Yeah!

    Thanks everyone for the assist.  Does anyone know what this actually did and why it was necessary?

    Thanks again.

    Russ

    Wednesday, March 09, 2011 4:08 AM

All replies

  • Hi,

     

    Please run the System Update Readiness Tool again and paste the result in %SYSTEMROOT%\Logs\CBS\CheckSUR.log.

     

    Tim Quan

     

    Monday, March 07, 2011 5:46 AM
    Moderator
  • Hello,

    I had the same problem. In the system eventlog I found an error entry ID 7 from source Service Pack Installer which informed me about a problem with a package. I used the command

    dism /online /remove-package /packagename:[Package_as_named_in_log]

    to remove this package. After this, installation succeeded without any problems.

     

    Regards
    Andreas

    Monday, March 07, 2011 6:20 AM
  • HI Andreas__L,

    Thanks for the hint, worked like a charm for me...

    Monday, March 07, 2011 3:26 PM
  • Tim--

    I actually ran the System Readiness Tool again last night  Here's the result.  No errors, from what I see.
    =================================
    Checking System Update Readiness.
    Binary Version 6.1.7601.21645
    Package Version 11.0
    2011-03-06 18:07

    Checking Windows Servicing Packages

    Checking Package Manifests and Catalogs

    Checking Package Watchlist

    Checking Component Watchlist

    Checking Packages

    Checking Component Store

    Summary:
    Seconds executed: 312
     No errors detected

     

    Tuesday, March 08, 2011 2:16 AM
  • All--

    I followed Andreas' advice and ran the command for the Deployment Image Services and Management Tool:

    dism /online /remove-package /packagename:Package_for_KB976932~31bf3856ad364e35~amd64~~6.1.1.17514

    and it went through the process of removing the package (took a while), after which I was able to successfully install SP1.  When the server rebooted, it went through another extended period of updates.  I'm putting together a blog post with pictures.

    Yeah!

    Thanks everyone for the assist.  Does anyone know what this actually did and why it was necessary?

    Thanks again.

    Russ

    Wednesday, March 09, 2011 4:08 AM
  • Hi,

     

    This indicates the file Package_for_KB976932~31bf3856ad364e35~amd64~~6.1.1.17514 was corrupt. After you removed this file, it worked.

     

    Tim Quan

      

    Wednesday, March 09, 2011 5:24 AM
    Moderator
  • Hi,

     

    I have exact the same problem.

    After installing SP1 Windows 2008 R2 through windows update i can not start server manger..

     

    System Update Readiness Tool

    =================================
    Checking System Update Readiness.
    Binary Version 6.1.7601.21645
    Package Version 11.0
    2011-03-15 12:29

    Checking Windows Servicing Packages

    Checking Package Manifests and Catalogs

    Checking Package Watchlist
    (f)    CBS Watchlist Package Missing    0x80070002    Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~0.0.0.0    Package_7_for_KB2467023~31bf3856ad364e35~amd64~~6.1.1.1    Package registry presence failed, possibly an orphaned package on package watchlist

    Checking Component Watchlist
    (f)    CBS Watchlist Component Missing    0x80070002    amd64_microsoft-windows-upnpcontrolpoint_31bf3856ad364e35_0.0.0.0_none_b2c7ff753148df7e    Package_7_for_KB2467023~31bf3856ad364e35~amd64~~6.1.1.1    Package registry presence failed, possibly an orphaned package on package watchlist
    (f)    CBS Watchlist Component Missing    0x80070002    amd64_microsoft-windows-upnpcontrolpoint_31bf3856ad364e35_0.0.0.0_none_b2c7ff753148df7e    Package_7_for_KB2467023~31bf3856ad364e35~amd64~~6.1.1.1    Package registry presence failed, possibly an orphaned package on package watchlist
    (f)    CBS Watchlist Component Missing    0x80070002    x86_microsoft-windows-upnpcontrolpoint_31bf3856ad364e35_0.0.0.0_none_56a963f178eb6e48    Package_7_for_KB2467023~31bf3856ad364e35~amd64~~6.1.1.1    Package registry presence failed, possibly an orphaned package on package watchlist
    (f)    CBS Watchlist Component Missing    0x80070002    x86_microsoft-windows-upnpcontrolpoint_31bf3856ad364e35_0.0.0.0_none_56a963f178eb6e48    Package_7_for_KB2467023~31bf3856ad364e35~amd64~~6.1.1.1    Package registry presence failed, possibly an orphaned package on package watchlist

    Checking Packages

    Checking Component Store

    Summary:
    Seconds executed: 387
     Found 5 errors
      CBS Watchlist Package Missing Total count: 1
      CBS Watchlist Component Missing Total count: 4

    Wednesday, March 16, 2011 11:44 AM
  • Try this:

    0x8024200D and 0x800f081f error when you are installing Windows 7 or Windows Server 2008 R2 SP1

    http://blogs.technet.com/b/asiasupp/archive/2011/03/14/0x8024200d-and-0x800f081f-error-when-you-are-installing-windows-7-or-windows-server-2008-r2-sp1.aspx

    Monday, March 21, 2011 7:24 AM
  • If got similar error 0x800f081f when executing W7 64bit sp1:

    From the cbs.log file

    2011-04-04 14:06:00, Error                 CBS    Exec: Failed to pre-stage package: Package_for_KB976933~31bf3856ad364e35~amd64~cs-CZ~6.1.7601.17514, file: TsUsbGD.sys, source: \\?\C:\Windows\Servicing\Packages\amd64_tsgenericusbdriver.inf_31bf3856ad364e35_6.1.7601.17514_none_9872c8452ac8f816\TsUsbGD.sys, sandbox: (null) [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]

    Effectively this entry is not in this folder.

     

    The CheckSUR.log file is:


    =================================
    Checking System Update Readiness.
    Binary Version 6.1.7601.21645
    Package Version 11.0
    2011-04-04 11:54

    Checking Windows Servicing Packages

    Checking Package Manifests and Catalogs

    Checking Package Watchlist

    Checking Component Watchlist

    Checking Packages

    Checking Component Store

    Summary:
    Seconds executed: 657
     No errors detected

     

     


    Mario Groleau Ingénieur Université du Québec à Trois-Rivières
    Monday, April 04, 2011 6:58 PM
  • Thanks Andreas_L

    Removing the package and then reinstalling the SP worked for me too.

    Friday, April 06, 2012 2:16 PM
  • WOW, this worked! I have tried every thing else found on the internet, and this is the only thing that worked. I actually had the exact same package highlighted in the service logs. 

    Thanks!

    Friday, June 27, 2014 1:32 PM