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

Thanks. May take me a while to go through it, but will get back to you ASAP.
 
  • Download: https://catalog.s.download.windowsu..._70c6d50fa9b65aa7f7a1202145185f244f8425c7.msu
  • Copy the MSU file to your desktop.
  • Click on 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 commands into it, press enter after each
    • cd %userprofile%\Desktop
    • expand windows10.0-kb4512574-x64_70c6d50fa9b65aa7f7a1202145185f244f8425c7.msu -f:* %userprofile%\Desktop
    • DISM.exe /Online /Add-Package /PackagePath:%userprofile%\Desktop\windows10.0-kb4512574-x64.cab
  • You should receive the message: The operation completed successfully.
  • Make sure to allow the computer to restart if prompted.
  • If you receive any other message:
    • Post a screenshot of the Command Prompt window.
    • Zip and attach the file C:\Windows\\Logs\CBS\CBS.log
 
Hello.

I´ve applied patch sucessfully, rebooted and search for new updates.

KB5023788 installs and ask for reboot, but it is not installed.

1684263428289.png

Thanks.
 

Attachments

Need to check whether your SSU has actually been updated, so please do the following ...

  • 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:

----------------------
Perfiles cargados:
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/16:15:54:40.358 10.0.14393.2963 (rs1_release.190408-1827)"

=== Final de ExportKey ===

==== Final de Fixlog 06:57:48 ====
 
Sadly it does not appear that KB4512574 has installed, otherwise there would be an entry for SSU 10.0.14393.3200, and clearly there is not.

Your problem appears to be being caused by an update KB5012170 which caused a lot of problems for a lot of machines, but quite what we need to do to resolve it, I'm not quite sure at this point, as we searched for it earlier, and the search returned no results.

Going to have to consult, to see if any of my colleagues have a solution.
 
Can you please send me updated copies of your COMPONENTS hive, and your CBS hive ...

For Components Hive ...

  • 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


For CBS Hive ...

  • Click on the Start button and in the search box, type regedit
    • When you see regedit on the list, right-click on it and select Run as administrator
  • When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing

  • Once selected, click File > Export....
    • Change the Save as type: to Registry Hive Files (.)
    • Name this file ComponentBasedServicing (with no file extension) and save it to your Desktop.
  • Right-click on the saved file and choose Send To -> Compressed (zipped) Folder.
  • Attach the .ZIP file to your next post.
  • If the file is too large to upload here, please upload to a file sharing service.
  • Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline
 
Thanks. Got a lot to look through, so may be a while before I get back to you.

Can you please try the following for me ...

  • 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 commands below into it, one at a time, pressing Enter after each.
  • DISM /online /cleanup-image /AnalyzeComponentStore
    DISM /online /cleanup-image /StartComponentCleanup
  • Once DISM has finished running try updating again ...
  • If unsuccessful ...
  • 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
 
Last edited:
Hello.

The first command:

DISM /online /cleanup-image /AnalyzeComponentStore

Herramienta Administración y mantenimiento de imágenes de implementación
Versión: 10.0.14393.0

Versión de imagen: 10.0.14393.2457

[===========================99.9%========================= ]

Información del almacén de componentes (WinSxS):

Tamaño declarado en Windows Explorer del almacén de componentes : 41.86 GB

Tamaño real del almacén de componentes : 38.17 GB

Compartido con Windows : 7.75 GB
Copias de seguridad y características deshabilitadas : 23.78 GB
Caché y datos temporales : 6.63 GB

Fecha de última limpieza : 2018-08-02 14:38:19

Número de paquetes reclamables : 29
Se recomienda limpiar el almacén de componentes : Sí

La operación se completó correctamente.
Reinicie Windows para completar esta operación.
¿Desea reiniciar el equipo ahora? (Y/N)

I reboot now and launch the second command ASAP.
 
Yes, reboot and try the 2nd command.
 
Hello again

DISM /online /cleanup-image /startcomponentcleanup

Herramienta Administración y mantenimiento de imágenes de implementación
Versión: 10.0.14393.0

Versión de imagen: 10.0.14393.2457



Error: 0x800f0806

No se pudo completar la operación debido a operaciones pendientes.

El archivo de registro de DISM se encuentra en C:\Windows\Logs\DISM\dism.log

----------------------

On every reboot server is pending for a reboot.

I attack cbs.log
 

Attachments

Can you try running those two commands again please.

DISM /online /cleanup-image /AnalyzeComponentStore
DISM /online /cleanup-image /StartComponentCleanup

The first one only ran to 99.9% and did not complete, so I'd like to know if it does the same again, or runs to the full 100% this time, in which case the second one may complete as well.
 
Hello.

DISM /online /cleanup-image /AnalyzeComponentStore

Herramienta Administración y mantenimiento de imágenes de implementación
Versión: 10.0.14393.0

Versión de imagen: 10.0.14393.2457

[===========================99.9%========================= ]

Información del almacén de componentes (WinSxS):

Tamaño declarado en Windows Explorer del almacén de componentes : 41.86 GB

Tamaño real del almacén de componentes : 38.17 GB

Compartido con Windows : 7.75 GB
Copias de seguridad y características deshabilitadas : 23.78 GB
Caché y datos temporales : 6.63 GB

Fecha de última limpieza : 2018-08-02 14:38:19

Número de paquetes reclamables : 29
Se recomienda limpiar el almacén de componentes : Sí

La operación se completó correctamente.
Reinicie Windows para completar esta operación.
¿Desea reiniciar el equipo ahora? (Y/N)
------------------------------------------------
DISM /online /cleanup-image /startcomponentcleanup

Herramienta Administración y mantenimiento de imágenes de implementación
Versión: 10.0.14393.0

Versión de imagen: 10.0.14393.2457



Error: 0x800f0806

No se pudo completar la operación debido a operaciones pendientes.

El archivo de registro de DISM se encuentra en C:\Windows\Logs\DISM\dism.log


Thanks.
 

Attachments

OK, still failing to complete, thought it might, but it was worth a shot.

Still working on the information provided by your previous CBS.log, may take a while, but I'll get back to you as soon as I can.
 
Question .... are you familiar with how to boot your computer into Recovery Environment ????

Because the next thing we need to do, needs to be run from RE, and it will save me time writing a detailed set of instructions for booting into RE, if you already know how to do it.
 
Hello Gary.

Yes, I am familiar with boot into recovery enviroment.

It's enabled on this server and I know commands:

shutdown /f /r /o /t 0

or

reagentc /boottore

This is a virtuallized server on ESXi and there is not problem to boot on recovery enviroment, but it's a production server and I need to schedule a prolonged stop.

Thank you.
 
OK, in that case, I need you to run the following command when booted into RE.

DISM /Image:C:\ /Cleanup-Image /RevertPendingActions

(you may need to change the C: if that's not the drive letter your system is on)

No problem if you can't do this right away, I understand the need to schedule stops. Will talk to you again once you've had the opportunity to run that command.
 
Hello

I`ve adapted command to my enviroment:

DISM /Image:d:\ /Cleanup-Image /RevertPendingActions /scratchdir:d:\windows\temp

But I have an error with DISM 800706BE "Failed to get de IDismImage instance form the image session"

Thank you.
 
Download and run SetupDiag from Microsoft
  • Download
    60e45c659164d-SetupDiag.png
    SetupDiag to your desktop.
  • Right-click on SetupDiag.exe and select Run as administrator.
  • When completed the following files are created: "Logs.zip, SetupDiag.exe.config and SetupDiagResults.log"
  • Attach SetupDiagResults.log and Logs.zip to your next reply.
 
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