[SOLVED] MSMQ-Server :: referenced assembly could not be found :: 0x80073701

tbj

Member
Joined
Mar 16, 2022
Posts
14
Hello Forum,

I faced a problem that totally drives me crazy and I do not know how to fix it.
But first things first:

I want to install Windows Optional Feature MSMQ-Server on windows Server 2019
Neither GUI, Powershell nor DISM worked to install the feature:

They all fail with message: The referenced assembly could not be found.

Investigating the dism.log I can see the following:
Code:
2022-08-09 09:18:07, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: SetupPlatformManager.
2022-08-09 09:18:07, Info                  DISM   DISM Package Manager: PID=36000 TID=32924 Processing the top level command token(enable-feature). - CPackageManagerCLIHandler::Private_ValidateCmdLine
2022-08-09 09:18:07, Info                  DISM   DISM Package Manager: PID=36000 TID=32924 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine
2022-08-09 09:18:07, Info                  DISM   DISM Package Manager: PID=36000 TID=32924 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine
2022-08-09 09:18:07, Info                  DISM   DISM Package Manager: PID=36000 TID=32924 Encountered the option "featurename" with value "MSMQ-Server" - CPackageManagerCLIHandler::Private_GetPackagesFromCommandLine
2022-08-09 09:18:07, Info                  DISM   DISM Package Manager: PID=36000 TID=32924 Encountered an unknown option "featurename" with value "MSMQ-Server" - CPackageManagerCLIHandler::Private_GetPackagesFromCommandLine
2022-08-09 09:18:10, Info                  DISM   DISM Package Manager: PID=36000 TID=32924 Feature MSMQ-Services with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 7(DISM_INSTALL_STATE_INSTALLED) - CDISMPackageFeature::LogInstallStateMapping
2022-08-09 09:18:10, Info                  DISM   DISM Package Manager: PID=36000 TID=32924 Initiating Changes on Package with values: 5, 7 - CDISMPackage::Internal_ChangePackageState
2022-08-09 09:18:10, Info                  DISM   DISM Package Manager: PID=36000 TID=32924 CBS session options=0x40100! - CDISMPackageManager::Internal_Finalize
2022-08-09 09:18:14, Info                  DISM   DISM Package Manager: PID=36000 TID=27264  Error in operation: (null) (CBS HRESULT=0x80073701) - CCbsConUIHandler::Error
2022-08-09 09:18:14, Error                 DISM   DISM Package Manager: PID=36000 TID=32924 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x80073701)
2022-08-09 09:18:14, Error                 DISM   DISM Package Manager: PID=36000 TID=32924 Failed processing package changes with session options - CDISMPackageManager::ProcessChangesWithOptions(hr:0x80073701)
2022-08-09 09:18:14, Error                 DISM   DISM Package Manager: PID=36000 TID=32924 Failed ProcessChanges. - CPackageManagerCLIHandler::Private_ProcessFeatureChange(hr:0x80073701)
2022-08-09 09:18:14, Error                 DISM   DISM Package Manager: PID=36000 TID=32924 Failed while processing command enable-feature. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x80073701)
2022-08-09 09:18:14, Info                  DISM   DISM Package Manager: PID=36000 TID=32924 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
2022-08-09 09:18:14, Error                 DISM   DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=80073701

sfc /scannow shows me:
Code:
PS C:\Users\service.varonis> sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 68% complete.

Windows Resource Protection found corrupt files but was unable to fix some of them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

The CBS.log shows me:
Code:
2022-08-09 10:08:38, Info                  CBS    Exec: 6 deployments need bulk staging
2022-08-09 10:08:38, Error                 CSI    00000008@2022/8/9:08:08:38.627 (F) onecore\base\wcp\componentstore\csd_locking.cpp(95): Error STATUS_SXS_ASSEMBLY_MISSING originated in function CCSDirectTransaction::LockComponent expression: (null)
[gle=0x80004005]
2022-08-09 10:08:38, Info                  CBS    Added C:\Windows\Logs\CBS\CBS.log to WER report.
2022-08-09 10:08:38, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20220809080834.log to WER report.
2022-08-09 10:08:38, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20220809071807.log to WER report.
2022-08-09 10:08:38, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20220809060640.log to WER report.
2022-08-09 10:08:38, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20220809012318.log to WER report.
2022-08-09 10:08:38, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20220808212239.log to WER report.
2022-08-09 10:08:38, Info                  CBS    Not able to add pending.xml to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2022-08-09 10:08:38, Info                  CBS    Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2022-08-09 10:08:38, Info                  CBS    Not able to add SCM.EVM to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2022-08-09 10:08:40, Error                 CSI    00000009 (F) STATUS_SXS_ASSEMBLY_MISSING #19351# from CCSDirectTransaction::OperateEnding at index 0 of 1 operations, disposition 2[gle=0xd015000c]
2022-08-09 10:08:40, Error                 CSI    0000000a (F) HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_MISSING) #19193# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_PinDeployment(Flags = 0, a = 69d05075c33bf009307a02c9cba085c4, version 10.0.17763.1817, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}, cb = (null), s = (null), rid = 'Package_3907_for_KB5000822~31bf3856ad364e35~amd64~~10.0.1.5.5000822-7778_neutral', rah = (null), manpath = (null), catpath = (null), ed = 0, disp = 0)[gle=0x80073701]
2022-08-09 10:08:40, Info                  CBS    Failed to pin deployment while resolving Update: Package_3907_for_KB5000822~31bf3856ad364e35~amd64~~10.0.1.5.5000822-7778_neutral from file: (null) [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
2022-08-09 10:08:40, Info                  CBS    Failed to bulk stage deployment manifest and pin deployment for package:Package_4123_for_KB5015811~31bf3856ad364e35~amd64~~10.0.1.8 [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
2022-08-09 10:08:40, Info                  CBS    CommitPackagesState: Started persisting state of packages
2022-08-09 10:08:40, Info                  CBS    CommitPackagesState: Completed persisting state of packages
2022-08-09 10:08:40, Info                  CSI    0000000b@2022/8/9:08:08:40.654 CSI Transaction @0x1f30d37bc20 destroyed
2022-08-09 10:08:40, Info                  CBS    Perf: Resolve chain complete.
2022-08-09 10:08:40, Info                  CBS    Failed to resolve execution chain. [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
2022-08-09 10:08:40, Error                 CBS    Failed to process single phase execution. [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
2022-08-09 10:08:40, Info                  CBS    WER: Generating failure report for package: Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~10.0.17763.1, status: 0x80073701, failure source: Resolve, start state: Installed, target state: Installed, client id: DISM Package Manager Provider
2022-08-09 10:08:40, Info                  CBS    Not able to query DisableWerReporting flag.  Assuming not set... [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2022-08-09 10:08:40, Info                  CBS    Added C:\Windows\Logs\CBS\CBS.log to WER report.


After that I run SFCFix.exe and after some time it told me that there is nothing to fix:
Code:
SFCFix version 3.0.2.1 by niemiro.
Start time: 2022-08-09 09:19:43.484
Microsoft Windows Server 10 Build 17763 - amd64
Not using a script file.




AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2022-08-09 09:57:39.861
----------------------EOF-----------------------

Any idea how to resolve this issue or how to get a step further?
I dont know what to do...

The CBS and DISM Logs are attached.

Best regards,
Toni
 

Attachments

Hi,
  • Open the Start menu of Windows and type the command CMD
  • When you see Command Prompt on the list, right-click on it and select Run as administrator.
  • When command prompt opens, copy and paste the following command into it, then press enter.
Code:
wusa /uninstall /KB:5000822
  • Let me know if it says it was successful or if there are any errors. Or take a screenshot of the command prompt window and paste it into your next reply.
 
  • Thanks
Reactions: tbj
Hi,

Thank you for your response. Here is the output of the CMD/Powershell Command:

1660902830213.png

Best regards,
Toni
 
Hi,

Download the
577bf0efb8088-FRST.png
Farbar Recovery Scan Tool and save it to your Desktop:

Download the 64 bit version: - Farbar Recovery Scan Tool Link
  • Open the startmenu and type the command cmd.
  • After you find the Command Prompt, right click on it and select Run as Administrator.
  • Copy and paste the following into the Command Prompt and press enter.
Code:
reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
Right-click on the file FRST64.exe and choose Run as administrator.
  • Copy and paste the following (code) into the Search box and click the Search Registry button.
Code:
KB5000822
  • When the scan is complete, a message will display that SearchReg.txt is saved in the same folder FRST was started from.
  • Post the logfile SearchReg.txt as attachment in your next reply.
 
Hello & Thank you for your reply.

Attached you will find the SearchReg.txt Logfile.
 

Attachments

Start the
577bf0efb8088-FRST.png
Farbar Recovery Scan Tool again.

Warning: This script was written specifically for this system. Do not run this script on another system.
  • Download the attachment fixlist.txt and save it to your desktop.
  • Right-click on FRST.exe and select "Run as administrator".
  • Press the Fix button.
  • If for some reason the tool needs a restart, please make sure you let the system restart normally.
  • When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  • Post the logfile Fixlog.txt as attachment in your next reply.
 

Attachments

Click the Start button and in the search box, type Command Prompt
When you see Command Prompt on the list, right-click on it and select Run as administrator.
When command prompt opens, copy and paste the following command and press enter.
Code:
DISM /online /cleanup-image /RestoreHealth
Take a screenshot of the commandprompt window and paste it into your next reply.

If it fails attach a new copy of the CBS log into your next post.
 
Rich (BB code):
2022-08-19 15:10:01, Info                  CBS    (p)    CSI Payload Corrupt    (n)            x86_netfx-csc_exe_config_b03f5f7f11d50a3a_10.0.17763.1_none_4395571e31fa16c9\csc.exe.config
2022-08-19 15:10:01, Info                  CBS    Repair failed: Missing replacement payload.
2022-08-19 15:10:01, Info                  CBS    (p)    CSI Payload Corrupt    (n)            msil_system.directoryser..s.accountmanagement_b77a5c561934e089_10.0.17763.1_none_919140669b969904\System.DirectoryServices.AccountManagement.dll
2022-08-19 15:10:01, Info                  CBS    Repair failed: Missing replacement payload.
2022-08-19 15:10:01, Info                  CBS    (p)    CSI Payload Corrupt    (n)            amd64_netfx35linq-microso...entity.build.tasks_31bf3856ad364e35_10.0.17763.1_none_c721dd78a163d466\Microsoft.Data.Entity.Build.Tasks.dll
2022-08-19 15:10:01, Info                  CBS    Repair failed: Missing replacement payload.

Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
  • Save any work you have open, and close all programs.
  • Download the attachment SFCFix.zip and save it to your desktop.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
6190d993a26f3-SFCFix-Zip-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.


Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code:
DISM /online /cleanup-image /RestoreHealth
 

Attachments

Hi Maxstar,

Thank you very much for your advise and help!!!
Finally, the DISM Command finished successfully:
1661161278448.png

I attached the SFCFix.txt file.

The MSMQ-Server Feature now could be installed successfully!!
1661161478639.png

Again, thank you very very much! :)
This saved me a lot of time and work and fixed a very hard problem.

Best regards,
Toni





PS: Is it possible to generate the SFCFix.zip and the fixlist on my own for the future? What do I need (to know) to create them?
 

Attachments

Hi,

You're welcome. Glad to hear you were able to install that feature now without any issues.. (y)
Is it possible to generate the SFCFix.zip and the fixlist on my own for the future? What do I need (to know) to create them?
Personally, I would not recommend that to create scripts for SFCFix or FRST yourself. This makes it more difficult to solve the problem if the script does not work or is incomplete, etc.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top