[SOLVED] x86_microsoft-windows-d..omerfeedbackmanager_31bf3856ad364e35_10.0.14393.447_none_b9ef218c73bc935a\imecfmui.exe Repair failed: Missing replacement pay

javiert

javiert

Well-known member
Joined
Aug 18, 2022
Posts
61
Hello all.

On W2016 STD.

DISM /online /cleanup-image /restorehealth

Checking System Update Readiness.

(p) CSI Payload Corrupt x86_microsoft-windows-d..omerfeedbackmanager_31bf3856ad364e35_10.0.14393.447_none_b9ef218c73bc935a\imecfmui.exe
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt x86_microsoft-windows-d..omerfeedbackmanager_31bf3856ad364e35_10.0.14393.447_none_b9ef218c73bc935a\imecfmps.dll
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt x86_microsoft-windows-d..omerfeedbackmanager_31bf3856ad364e35_10.0.14393.447_none_b9ef218c73bc935a\imecfm.dll
Repair failed: Missing replacement payload.

Summary:
Operation: Detect and Repair
Operation result: 0x800f081f
Last Successful Step: Entire operation completes.
Total Detected Corruption: 3
CBS Manifest Corruption: 0
CBS Metadata Corruption: 0
CSI Manifest Corruption: 0
CSI Metadata Corruption: 0
CSI Payload Corruption: 3
Total Repaired Corruption: 0
CBS Manifest Repaired: 0
CSI Manifest Repaired: 0
CSI Payload Repaired: 0
CSI Store Metadata refreshed: True


I need help.

Thank you in advance.
 

Attachments

  • Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
  • Please copy this file to your desktop.
  • Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
  • Right-click on this file on your desktop and select Send To...Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
  • The file will likely be too large to upload here, if so please upload to a file sharing service.
  • Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline

Please post me the link to the file
 
Thanks. Looking over things now, will get back to you ASAP.
 
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

  • Download SFCFix.exe and save it to your desktop.
  • Download the attachment SFCFix.zip and also save it on your desktop.
  • Save any work you have open, and close all programs.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
1p8eDnI.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt
  • Open the file, then copy and paste its content in your next reply.

Next ...

  • Click Search button and type Command Prompt
  • From the results, right click on the Command Prompt icon, and select Run as administrator
  • A Command Window will open.
  • Copy paste the command below into it, then press Enter
  • Dism /Online /Cleanup-Image /RestoreHealth
  • Once DISM has finished running ...
    • Please attach your ... C:\Windows\Logs\CBS\cbs.log ... to your next reply.
  • If the file is too large, upload it to a file sharing service, and post me the link.
  • Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline
 

Attachments

Hello again.

"DISM /online /cleanup-image /restorehealth" completes sucessfully but now server wants to install "KB5023788: Servicing stack update for Windows Server 2016: March 14, 2023" and it asks for a reboot, but it do not install.

All recent cumulative updates ase installed.

Thank you.
 
Please post me your SFCFix.txt and your CBS.log as I requested in my last post.
 
Your SFCFix.txt shows that you ran the fix at ... Start time: 2023-05-08 07:31:33

However, the latest entry in the CBS.log you've posted is dated ... 2023-05-08 07:30:14 ... which is before you ran the fix.

I need to see a CBS.log generated after the fix was run

  • Click Search button and type Command Prompt
  • From the results, right click on the Command Prompt icon, and select Run as administrator
  • A Command Window will open.
  • Copy paste the command below into it, then press Enter
  • Dism /Online /Cleanup-Image /RestoreHealth
  • Once DISM has finished running ...
    • Please attach your ... C:\Windows\Logs\CBS\cbs.log ... to your next reply.
  • If the file is too large, upload it to a file sharing service, and post me the link.
  • Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline
 
Hello again.

I've applied KB5017095 sucessfully. I've rebooted and KB5023788 fails to install at reboot time all times.

Thank you.

I post new CBS.
 

Attachments

  • Download the attachment SFCFixScript.txt and save it on your desktop.
  • Save any work you have open, and close all programs.
  • Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.
1p8eDnI.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt
  • Open the file, then copy and paste its content in your next reply.
 

Attachments

Hello.

-----
SFCFix version 3.0.2.1 by niemiro.
Start time: 2023-05-09 12:21:52.940
Microsoft Windows Server 10 Build 14393 (Updates Deferred) - amd64
Using .txt script file at XXXX\SFCFixScript.txt [0]




RegistryExport::
Successfully exported registry key HKEY_LOCAL_MACHINE\COMPONENTS\ServicingStackVersions.



Datablocks:
RegistryExport:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 4 datablocks.
Finish time: 2023-05-09 12:21:53.018
Script hash: pmwa3ohT7d5eagnWVUZ7LxBJK0YXRXRIVG8sCqNXiso=
----------------------EOF-----------------------

Thanks.
 
OK, that didn't do what I expected it to do, so let's try to do it a different way ....

Download FRST64 to your Desktop.

Next ....

  • Start FRST.
  • Hit your Windows Key + R to open a Run window
  • Type Notepad then click OK
  • This will open an empty Notepad document
  • Copy/Paste the following into it (Don't include Code: ) .....
Code: 
cmd: reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
ExportKey: HKey_Local_Machine\COMPONENTS\ServicingStackVersions
  • Save it as fixlist.txt to the same location as FRST (must be in this location)
  • NOTICE: This script was written specifically for this user. Running it on another machine may cause damage to your operating system
  • Now press the Fix button once and wait.
  • FRST will process fixlist.txt
  • When finished, it will produce a log fixlog.txt in the same folder/directory as FRST64.exe
  • Please post me the log
 
Hello:

The fixlog.txt content:

Modo de Inicio: Normal
==============================================

fixlist contenido:
*****************
cmd: reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
ExportKey: HKey_Local_Machine\COMPONENTS\ServicingStackVersions

*****************


========= reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS =========

La operación se completó correctamente.


========= Final de CMD: =========

================== ExportKey: ===================

[HKey_Local_Machine\COMPONENTS\ServicingStackVersions]
"LastWCPVersionToAccessStore"="10.0.14393.2963 (rs1_release.190408-1827)"
"10.0.14325.1000 (rs1_onecore_ens_oss.160416-1700)"="2016/7/16:6:4:38.506 10.0.14325.1000 (rs1_onecore_ens_oss.160416-1700)"
"10.0.14393.0 (rs1_release.160715-1616)"="2016/11/20:21:15:31.701 10.0.14393.0 (rs1_release.160715-1616)"
"10.0.14393.350 (rs1_release.161013-1725)"="2018/3/9:14:6:11.320 10.0.14393.350 (rs1_release.161013-1725)"
"10.0.14393.1883 (rs1_release_sec.171025-0700)"="2018/4/6:7:57:45.17 10.0.14393.1883 (rs1_release_sec.171025-0700)"
"10.0.14393.2151 (rs1_release_1.180220-1730)"="2018/4/26:11:28:18.444 10.0.14393.2151 (rs1_release_1.180220-1730)"
"10.0.14393.2182 (rs1_release.180318-1045)"="2018/7/10:6:9:9.494 10.0.14393.2182 (rs1_release.180318-1045)"
"10.0.14393.2272 (rs1_release_1.180423-1805)"="2018/11/25:8:26:58.539 10.0.14393.2272 (rs1_release_1.180423-1805)"
"10.0.14393.2602 (rs1_release.181015-1821)"="2019/2/13:4:21:33.462 10.0.14393.2602 (rs1_release.181015-1821)"
"10.0.14393.2782 (rs1_release.190111-1811)"="2019/6/4:11:17:17.172 10.0.14393.2782 (rs1_release.190111-1811)"
"10.0.14393.2963 (rs1_release.190408-1827)"="2023/5/9:11:16:16.950 10.0.14393.2963 (rs1_release.190408-1827)"

=== Final de ExportKey ===

==== Final de Fixlog 19:15:57 ====

Thank you.
 
Going to have to consult with my colleagues about what this latest log shows.

Clearly there's some problem installing SSUs since despite you saying that KB5017095 had installed, that does not appear to be the case.

May take a while. I'll get back to you as soon as I can though.
 
Hello again and thank you for your help.

I think that KB5017095 is not really installed because it seems completes sucessfully but I can not see on updates history.
 
It should have installed SSU ... 10.0.14393.5285 ... but as that is not showing in your ServicingStackVersions key, then it does not appear to have done so.

We can run a further check to see whether it's part installed by doing the following ....

  • Click Search and type CMD
  • Right click the CMD App from the search results and select Run as Administrator
  • With the App open ...
    • Copy/Paste the following Command into it ...
    • reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
      • This loads your COMPONENT hive.
    • You can now close the Command window.
  • Next ...
  • Right-click on FRST64.exe and choose Run as administrator
    • Copy and paste ... KB5017095 ... into the Search box.
    • Click the Search Registry button.
    • When the scan is complete ...
      • A log will open on your Desktop ... SearchReg.txt
    • Attach the file ... SearchReg.txt ... to your next reply.
  • You may close any remaining open windows now.
 
You must log in or register to reply here.

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

Back
Top