none
Server 2016 - Unable to Add RSAT Role - The Referenced Assembly could not be found. Error: 0x80073701 RRS feed

  • Question

  • Hi there, 

    After some outside opinion on this one as i'm finding lots of resources online but none are a close enough fit for the solutions to work. 

    In short we have a Server 2016 template which is working fine, we can deploy VMs from it add roles, apply windows updates and everything is fine. If we then revisit and try and add new roles we have issues and get the error: The Referenced Assembly could not be found. Error: 0x80073701. 

    Now in the case of my current server i've narrowed it down to just being the Remote Server Administration Tools > DNS Server Tools that is the problem role. 

    Other instances i've found online mention checking the language packs of files that have been installed and see if these are both installed, being reported in error logs (CBS.log) and even look to removing from registry. 

    I've tried running the following commands (that both complete without issue):

    DISM.exe /Online /Cleanup-image /Restorehealth

    sfc /scannow

    Another solution suggested checking the following location in the registry (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect) for language packs referenced in the CBS.log, however i only seem to fine 'Native' rather than a specific region referenced. 

    I've attempted to install via GUI, Powershell and Command line, all of which fail with the same (or a variation of) error code.

    Section in the CBS log that i believe relates to the issue is below:

    2019-02-28 11:39:43, Error                 CSI    00001a8e (F) STATUS_SXS_ASSEMBLY_MISSING #5012934# from CCSDirectTransaction::OperateEnding at index 0 of 1 operations, disposition 2[gle=0xd015000c]
    2019-02-28 11:39:43, Error                 CSI    00001a8f (F) HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_MISSING) #5008383# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_PinDeployment(Flags = 0, a = 8d9d8d12592c2db7420f8ca8682e1c85, version 10.0.14393.953, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}, cb = (null), s = (null), rid = 'Package_4458_for_KB4088787~31bf3856ad364e35~amd64~~10.0.1.2.4088787-8692_neutral', rah = '2', manpath = (null), catpath = (null), ed = 0, disp = 0)[gle=0x80073701]
    2019-02-28 11:39:43, Info                  CBS    Failed to pin deployment while resolving Update: Package_4458_for_KB4088787~31bf3856ad364e35~amd64~~10.0.1.2.4088787-8692_neutral from file: (null) [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
    2019-02-28 11:39:43, Info                  CBS    Failed to bulk stage deployment manifest and pin deployment for package:Package_4967_for_KB4480961~31bf3856ad364e35~amd64~~10.0.1.3 [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
    2019-02-28 11:39:43, Info                  CBS    CommitPackagesState: Started persisting state of packages
    2019-02-28 11:39:43, Info                  CBS    CommitPackagesState: Completed persisting state of packages
    2019-02-28 11:39:43, Info                  CSI    00001a90@2019/2/28:11:39:43.480 CSI Transaction @0x187ea4cd930 destroyed

    I attempted to start uninstalling the KB packages referenced (with a view to manually reinstall) but after 4 packages removed and not being able to directly install them again manually (only WSUS package being shown) i haven't removed any more as yet.

    I have been able to add the 'DNS Server' role without issue so at the moment its purely the RSAT tools, again i've tried looking for a manual download/install/source file for these specifically for Server 2016 to no avail. 

    Any help would be greatly appreciated as most of the links i'm now finding in Google are purple. Let me know if any more logs / info is needed for information / troubleshooting. 

    Thanks, Wayne

    Monday, March 4, 2019 9:05 AM

All replies

  • Fuller output from CBS.log following an attempted role install below in case that's needed too:

    2019-03-04 10:24:07, Info                  CBS    Exec: Resolving Package: Package_4458_for_KB4088787~31bf3856ad364e35~amd64~~10.0.1.2, Update: 4088787-8692_neutral
    2019-03-04 10:24:07, Info                  CBS    Exec: Resolving component from existing package; passing NULL manifest path to PinDeployment and hoping things haven't been scavenged.
    2019-03-04 10:24:07, Info                  CBS    Exec: Resolving Package: Package_4458_for_KB4088787~31bf3856ad364e35~amd64~~10.0.1.2, Update: 4088787-8692_neutral, PinDeployment: amd64_8d9d8d12592c2db7420f8ca8682e1c85_31bf3856ad364e35_10.0.14393.953_none_e337f7f5d24ab68f
    2019-03-04 10:24:07, Info                  CBS    Exec: 1 deployments need bulk staging
    2019-03-04 10:24:07, Error                 CSI    00000008@2019/3/4:10:24:07.553 (F) onecore\base\wcp\componentstore\csd_locking.cpp(200): Error STATUS_SXS_ASSEMBLY_MISSING originated in function CCSDirectTransaction::LockComponent expression: (null)
    [gle=0x80004005]
    2019-03-04 10:24:07, Info                  CBS    Added C:\Windows\Logs\CBS\CBS.log to WER report.
    2019-03-04 10:24:07, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20190301154849.log to WER report.
    2019-03-04 10:24:07, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20190228150032.log to WER report.
    2019-03-04 10:24:07, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20190228135706.log to WER report.
    2019-03-04 10:24:07, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20190228130501.log to WER report.
    2019-03-04 10:24:07, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20190228104651.cab to WER report.
    2019-03-04 10:24:07, Info                  CBS    Not able to add pending.xml to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2019-03-04 10:24:07, Info                  CBS    Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2019-03-04 10:24:07, Info                  CBS    Not able to add SCM.EVM to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2019-03-04 10:24:07, Error                 CSI    00000009 (F) STATUS_SXS_ASSEMBLY_MISSING #8683# from CCSDirectTransaction::OperateEnding at index 0 of 1 operations, disposition 2[gle=0xd015000c]
    2019-03-04 10:24:07, Error                 CSI    0000000a (F) HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_MISSING) #8531# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_PinDeployment(Flags = 0, a = 8d9d8d12592c2db7420f8ca8682e1c85, version 10.0.14393.953, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}, cb = (null), s = (null), rid = 'Package_4458_for_KB4088787~31bf3856ad364e35~amd64~~10.0.1.2.4088787-8692_neutral', rah = '2', manpath = (null), catpath = (null), ed = 0, disp = 0)[gle=0x80073701]
    2019-03-04 10:24:07, Info                  CBS    Failed to pin deployment while resolving Update: Package_4458_for_KB4088787~31bf3856ad364e35~amd64~~10.0.1.2.4088787-8692_neutral from file: (null) [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
    2019-03-04 10:24:07, Info                  CBS    Failed to bulk stage deployment manifest and pin deployment for package:Package_4590_for_KB4103723~31bf3856ad364e35~amd64~~10.0.1.5 [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
    2019-03-04 10:24:07, Info                  CBS    CommitPackagesState: Started persisting state of packages
    2019-03-04 10:24:07, Info                  CBS    CommitPackagesState: Completed persisting state of packages
    2019-03-04 10:24:07, Info                  CSI    0000000b@2019/3/4:10:24:07.637 CSI Transaction @0x146b08e5fc0 destroyed
    2019-03-04 10:24:07, Info                  CBS    Perf: Resolve chain complete.
    2019-03-04 10:24:07, Info                  CBS    Failed to resolve execution chain. [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
    2019-03-04 10:24:07, Error                 CBS    Failed to process single phase execution. [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
    2019-03-04 10:24:07, Info                  CBS    WER: Generating failure report for package: Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~10.0.14393.0, status: 0x80073701, failure source: Resolve, start state: Installed, target state: Installed, client id: DISM Package Manager Provider
    2019-03-04 10:24:07, Info                  CBS    Not able to query DisableWerReporting flag.  Assuming not set... [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2019-03-04 10:24:07, Info                  CBS    Added C:\Windows\Logs\CBS\CBS.log to WER report.
    2019-03-04 10:24:07, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20190301154849.log to WER report.
    2019-03-04 10:24:07, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20190228150032.log to WER report.
    2019-03-04 10:24:07, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20190228135706.log to WER report.
    2019-03-04 10:24:07, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20190228130501.log to WER report.
    2019-03-04 10:24:07, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20190228104651.cab to WER report.
    2019-03-04 10:24:07, Info                  CBS    Not able to add %windir%\winsxs\pending.xml to WER report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2019-03-04 10:24:07, Info                  CBS    Not able to add %windir%\winsxs\pending.xml.bad to WER report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2019-03-04 10:24:07, Info                  CBS    Reboot mark cleared
    2019-03-04 10:24:07, Info                  CBS    Winlogon: Simplifying Winlogon CreateSession notifications
    2019-03-04 10:24:07, Info                  CBS    Winlogon: Deregistering for CreateSession notifications
    2019-03-04 10:24:07, Info                  CBS    FinalCommitPackagesState: Started persisting state of packages
    2019-03-04 10:24:07, Info                  CBS    FinalCommitPackagesState: Completed persisting state of packages
    2019-03-04 10:24:07, Info                  CBS    Enabling LKG boot option
    2019-03-04 10:24:07, Info                  CBS    Exec: Processing complete.  Session: 30724724_1632902317, Package: Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~10.0.14393.0 [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
    2019-03-04 10:24:07, Error                 CBS    Failed to perform operation.  [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
    2019-03-04 10:24:07, Info                  CBS    Session: 30724724_1632902317 finalized. Reboot required: no [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
    2019-03-04 10:24:07, Info                  CBS    Failed to FinalizeEx using worker session [HRESULT = 0x80073701]
    2019-03-04 10:24:23, Info                  CBS    Session: 30724724_1874874644 initialized by client DISM Package Manager Provider, external staging directory: (null), external registry directory: (null
    2019-03-04 10:24:23, Info                  CBS    Enumerating Foundation package: Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~10.0.14393.0, this could be slow


    Monday, March 4, 2019 10:29 AM
  • 0x80073701 = ERROR_SXS_ASSEMBLY_MISSING which means there are some system files are missing, which caused the update installation failure. You can also try a repair install by running setup.exe from the root of the install.

    I wouldn't hold much hope for this, better time may be spent standing up a new one, patch it fully and migrate the roles or applications over to it.

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Monday, March 4, 2019 1:41 PM
  • The problem with wiping out and starting again is, that this seems to be affected a number of our VM's. But only once we have deployed them, added roles and once they have had Windows Updates we then seem to be unable to add further roles. 

    So something during the windows updates is replacing or corrupting something on the base install (i think i tracked it down to Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~10.0.14393.0).

    So although starting again might be quicker for the VM i have (annoyingly 2 of them are Domain Controllers) longer term we could have this popping up more and more. 

    Its already on the back of my mind that we need to redo our VM template as i suspect the corruption is rooted there 'somewhere', unless its something during the Windows update process.

    Tuesday, March 5, 2019 8:27 AM
  • Then you might also try some different install media. If a download then try from another location to avoid the same copy stored on ISP's caching equipment.

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Tuesday, March 5, 2019 1:23 PM
  • Hi,
    Was your issue solved?
    If yes, would you like to share your solution in order that other community members could find the helpful reply quickly.
    If no, please reply and tell us the current situation in order to provide further help.
    Best Regards,

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, March 19, 2019 2:34 AM
    Moderator
  • Disclaimer: Use this solution at your own risk!  Have a good backup or use as a last resort before an OS reload!  Testing has been limited to two Windows Server 2016 systems running RDS and SCCM which are now in production with no issues.

    The C:\Windows\Logs\CBS\CBS.log file will have an entry for the missing assembly that say '(ERROR_SXS_ASSEMBLY_MISSING)'.  In this same line, you will find the package assembly name that it is unable to find.  If you delete the associated registry values from HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect and Packages keys, the problem will go away. 

    I wrote a quick PowerShell script to scan the CBS.log file for me and delete the registry keys.  As this was a last ditch effort before re-installing the OS, I didn't worry about backing up any keys.  You might want to backup the entire key listed above first.  

    Again, use at your own risk!

    #Read CBS log file contents into memory
    try {$Contents = [System.IO.File]::ReadLines('C:\Windows\Logs\CBS\CBS.log')} catch {"File is currently in use.  Re-run script in 2 minutes.";return}
    
    #Parse log file for missing assemblies
    $InterestingLines = $Contents | Select-String -SimpleMatch '(ERROR_SXS_ASSEMBLY_MISSING)'
    
    #Retrieve unique Package names from error messages
    $Packages = @()
    foreach ($Line in $InterestingLines) {
        $Package  = $(($Line -split("'") )[1]).Substring(0,$Package.Length - ($Package.split(".")[4]).Length - 1)
        if ($Packages -notcontains $Package) { $Packages += $Package }
    }
    
    $AllKeys = @('HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect', 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages')
    
    foreach ($RegRoot in $AllKeys) {
        $Keys = Get-ChildItem $RegRoot | where {$_.PSIsContainer}
        foreach ($Key in $Keys) {
        #write-host "Checking $($Key.name)" -ForegroundColor Blue
            foreach ($Package in $Packages) {
                foreach ($Property in $Key.Property) {
                    #write-Host "$Property ? $Package" -ForegroundColor blue
                    if ($Property -match $Package) {
                        $ShortTarget = $($Key.Name).Substring(87) 
                        write-host "Found $Package in $ShortTarget...  " -ForegroundColor Yellow -NoNewline
                        $Target = $($Key.Name).TrimStart("HKEY_LOCAL_MACHINE\\")
                        try {
                            # Attempt to give Admins full control of key and delete key.
                            $key = [Microsoft.Win32.Registry]::LocalMachine.OpenSubKey($Target,[Microsoft.Win32.RegistryKeyPermissionCheck]::ReadWriteSubTree,[System.Security.AccessControl.RegistryRights]::ChangePermissions)
                            $acl = $key.GetAccessControl()
                            $rule = New-Object System.Security.AccessControl.RegistryAccessRule ("BUILTIN\Administrators","FullControl","Allow")
                            $acl.SetAccessRule($rule)
                            $key.SetAccessControl($acl)
                            Remove-ItemProperty -Path "HKLM:\$Target" -Name $Package -Force
                            Write-Host "delete successful." -ForegroundColor Green
                        } catch {
                            Write-Host "delete failed.  Delete manually." -ForegroundColor Red
                        }
                    }
                }
            }
        }
    }

    Thursday, May 30, 2019 2:27 PM