[kb4551762] - 0x800f081f

[lopm46]

Hi,

SFCFix.txt

SFCFix version 3.0.2.1 by niemiro.
Start time: 2020-03-20 17:52:56.356
Microsoft Windows 10 Build 18363 - 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: 2020-03-20 17:53:11.978
----------------------EOF-----------------------

Thanks you :)

 

[lopm46]

Another CBS log with more informations now. Idk why...

 

[lopm46]

2020-03-20 18:22:42, Info                  CBS    Exec: Processing complete.  Session: 30801627_3845215563, Package: Package_for_RollupFix~31bf3856ad364e35~amd64~~18362.720.1.0, Identifier: KB4551762 [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]

Is this the issue ?

 

[lopm46]

PS C:\Windows\system32> DISM.exe /Online /Add-Package /PackagePath:C:\Update\Windows10.0-KB4551762-x64_PSFX.cab

Outil Gestion et maintenance des images de déploiement
Version : 10.0.18362.1

Version de l’image : 10.0.18363.657

Traitement de 1 sur 1 - Ajout du package Package_for_RollupFix~31bf3856ad364e35~amd64~~18362.720.1.0
[==========================100.0%==========================]
Une erreur s’est produite - Package_for_RollupFix Erreur : 0x800f081f

Erreur : 0x800f081f

Échec de DISM. Aucune opération n’a été effectuée.
Pour plus d’informations, consultez le fichier journal.

Le fichier journal DISM se trouve à l’emplacement C:\Windows\Logs\DISM\dism.log
PS C:\Windows\system32>

2020-03-21 20:54:25, Error                 DISM   DISM Package Manager: PID=1240 TID=5616 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f081f)
2020-03-21 20:54:25, Error                 DISM   DISM Package Manager: PID=1240 TID=5616 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg
2020-03-21 20:54:25, Error                 DISM   DISM Package Manager: PID=1240 TID=5616 Failed processing package changes - CDISMPackageManager::ProcessChanges(hr:0x800f081f)
2020-03-21 20:54:25, Error                 DISM   DISM Package Manager: PID=1240 TID=5616 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg
2020-03-21 20:54:25, Info                  DISM   DISM Package Manager: PID=1240 TID=5616 Loaded servicing stack for online use only. - CDISMPackageManager::CreateCbsSession
2020-03-21 20:54:25, Error                 DISM   DISM Package Manager: PID=1240 TID=5616 Failed while processing command add-package. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f081f)
2020-03-21 20:54:25, Info                  DISM   DISM Package Manager: PID=1240 TID=5616 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
2020-03-21 20:54:25, Error                 DISM   DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=800F081F

 

[Sysnative Windows Update]

Hi!

Apologies for the delay!

If this is still an issue, please run DISM with the RestoreHealth parameter as indicated in our Posting instructions and attach CBS.log after that.

 

[lopm46]

Hi

Thanks you.

 

[lopm46]

With wim file source ("fr_windows_10_consumer_editions_version_1909_updated_dec_2019_x64_dvd_28b828a1")

 

[lopm46]

After run the update :

 

[lopm46]

Maybe it can help.

I've follow this guide ("Windows 10 Privacy Guide - October 2018 Update" Section Removing Windows Defender) and i think "install_wim_tweak /o /c Windows-Defender /r" command may have been corrupt the Windows image.

 

[Sysnative Windows Update]

What has been done in between the logs?

 

[lopm46]

Nothing

 

[lopm46]

Yesterday i tried to to run the command "install_wim_tweak /o /c Windows-Defender /r" on fresh windows image in virtual box and i get the same error.
So i try to recover the Windows Defender packages.

Thoses keys was missing so i import them from a fresh windows image (same build). And also the catalog files in "C:\Windows\servicing\Packages"

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-AM-Default-Definitions-Package~31bf3856ad364e35~amd64~fr-FR~10.0.18362.1
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-AM-Default-Definitions-Package~31bf3856ad364e35~amd64~~10.0.18362.1
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-AppLayer-Group-Package~31bf3856ad364e35~amd64~fr-FR~10.0.18362.1
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-AppLayer-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-ApplicationGuard-Inbox-Package~31bf3856ad364e35~amd64~fr-FR~10.0.18362.1
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-ApplicationGuard-Inbox-Package~31bf3856ad364e35~amd64~~10.0.18362.1
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Client-Package~31bf3856ad364e35~amd64~fr-FR~10.0.18362.1
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Client-Package~31bf3856ad364e35~amd64~~10.0.18362.449
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Core-Group-amcore-Package~31bf3856ad364e35~amd64~fr-FR~10.0.18362.1
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Core-Group-amcore-Package~31bf3856ad364e35~amd64~~10.0.18362.1
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Core-Group-onecore-Package~31bf3856ad364e35~amd64~fr-FR~10.0.18362.1
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Core-Group-onecore-Package~31bf3856ad364e35~amd64~~10.0.18362.1
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Core-Group-Package~31bf3856ad364e35~amd64~fr-FR~10.0.18362.1
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Core-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Group-Policy-Package~31bf3856ad364e35~amd64~fr-FR~10.0.18362.1
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Group-Policy-Package~31bf3856ad364e35~amd64~~10.0.18362.1
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Management-Group-amcore-Package~31bf3856ad364e35~amd64~fr-FR~10.0.18362.1
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Management-Group-amcore-Package~31bf3856ad364e35~amd64~~10.0.18362.1
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Management-Group-onecore-Package~31bf3856ad364e35~amd64~fr-FR~10.0.18362.1
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Management-Group-onecore-Package~31bf3856ad364e35~amd64~~10.0.18362.1
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Management-Group-Package~31bf3856ad364e35~amd64~fr-FR~10.0.18362.1
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Management-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Management-MDM-Group-Package~31bf3856ad364e35~amd64~fr-FR~10.0.18362.1
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Management-MDM-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~fr-FR~10.0.18362.1
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.449
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Nis-Group-Package~31bf3856ad364e35~amd64~fr-FR~10.0.18362.1
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender-Nis-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1

So now i get the error 0x80073701 ([HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]) instead of 0x800f081f (after run DISM /RestoreHealth and /Cleanup-Image /StartComponentCleanup). See the CBS log.

What did i do wrong ? Is others package are missing from the uninstall of Windows-Defender ?
I export all the packages keys, can you tell me if important packages are missing ? See the package keys log.

Thanks you.

 

[Sysnative Windows Update]

The Component Cleanup command should never be executed. It removes the components that can be of vital importance for the system in need of troubleshooting.

What other issues are you seeing?

 

[lopm46]

I follow the microsoft workaround about 0x80073701 (https://support.microsoft.com/fr-fr...dates-from-windows-update-you-might-receive-u)...

I've not other issues. Other that i can't install kb update related to security.

 

[Sysnative Windows Update]

Please attempt installing one of the updates that failed previously and attach CBS.log.

 

[lopm46]

For : 0x800f081f

After run the update :

You can take this log but here's another one if you want.

Note : it's not kb4551762 anymore but KB4549951 (april update)

 

[Sysnative Windows Update]

Please do the following:

GSmartControl
Follow the instructions below to check your SMART status with GSmartControl:

• Download the portable version of GSmartControl and save it on your Desktop;
• Extract the zip file to your Desktop. Open the folder gsmartcontrol-1.1.3-win64 which should be located on your Desktop and double-click gsmartcontrol.exe to launch the program.
• Identify your drive in the list (if recognized by the tool), and hover your mouse over it.
• You should see something called: SMART status. It will either read: Enabled, in which case you should do the following:
• Double-click on it to bring up its window (usually you'll find your drive by its size or its brand name);
• Go to the Self-Tests tab, then select Extended Self-test in the Test type drop-down list and click on Execute (this test can take a few hours to complete);
• Once the test is over, the results will be displayed at the bottom of the window. Please copy and paste these results in your next reply or take a screenshot;
• Also, go in the Attributes tab and if you have any entries highlighted in red or pink, take a screenshot of the GSmartControl window and attach it in your next reply;
• Please note: If the SMART Status reads: Unsupported, stop and let me know.
  
  

 

[lopm46]

Complete without error.
No red/pink attributes.

 

[Sysnative Windows Update]

Let's try the following:

1. Download the Media Creation Tool and save this to your desktop. Go ahead and run this as well. Note: Click the Download tool now button when you get to this link.
2. Accept the License Agreement
3. Download the ISO file to your desktop.
4. Double-click on the ISO and then run the setup to try and upgrade your machine.

We want to get the ISO so that you don't have to keep downloading which can take hours.

 

[lopm46]

The upgrade will just make an update not delete anything ?