CU Update error 0x8000ffff -2016 - 1607 Build 14393.2828

[admmpat]

Hello together,

i got some Problems on one of my 2016 Servers.
Server got 14393.2828 Build.

All Updates Work, but when i try to Install an CU (anyone) it errors with 0x8000ffff

Get-Packages shows Version 10.0.14393.2457

Paketidentität : Package_for_RollupFix~31bf3856ad364e35~amd64~~14393.2828.1.11
Status : Teilweise installiert
Versionstyp : Update
Installationszeit : 26.02.2019 15:30

SFC /Scannow shows following:

sfc /scannow

Systemsuche wird gestartet. Dieser Vorgang kann einige Zeit dauern.

Überprüfungsphase der Systemsuche wird gestartet.
Überprüfung 100 % abgeschlossen.

Vom Windows-Ressourcenschutz wurden beschädigte Dateien gefunden, und
einige davon konnten nicht repariert werden. Weitere Informationen finden Sie in der Datei "CBS.Log" unter "windir\Logs\CBS\CBS.log",
z.B. "C:\Windows\Logs\CBS\CBS.log".
Hinweis: Bei der Offlinewartung wird die Protokollierung derzeit nicht unterstützt.

Dism shows following:

Dism /Online /Cleanup-Image /CheckHealth

Tool zur Imageverwaltung für die Bereitstellung
Version: 10.0.14393.0

Abbildversion: 10.0.14393.2457

Der Komponentenspeicher kann repariert werden.
Der Vorgang wurde erfolgreich beendet.

Already tried to do online / Offline Dism Restore Health with RTM and newest CU Iso of 2016, as the Old CU is no longer Avaible on Windows Update Catalog

Dism /Restorehealth:

Dism /Online /Cleanup-Image /RestoreHealth /Source:d:\sources /LimitAccess

Tool zur Imageverwaltung für die Bereitstellung
Version: 10.0.14393.0

Abbildversion: 10.0.14393.2457

[==========================100.0%==========================]
Fehler: 0x800f081f

Die Quelldateien wurden nicht gefunden.
Geben Sie mit der Option "Quelle" den Ort der Dateien an, die zum Wiederherstellen des Features erforderlich sind. Weitere Informationen zum Angeben eines Quellorts finden Sie unter "Configure a Windows Repair Source".

Die DISM-Protokolldatei befindet sich unter "C:\Windows\Logs\DISM\dism.log".

Tried upgrade Installation endet in Bluescreen cycle.


Anyone got some Idea to fix this?

Will add .zip with logfiles of each Step.

Kind Regards
Martin

 

[axe0]

Hi admmpat,

Please do the following.

WARNING! The following fix is specific to admmpat's system in this thread only. No one else should follow these instructions, as it could damage your system.

• Download the attachment SFCFix.zip and 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.
  
  
• SFCFix will launch, let it complete.
• Once done, a file will appear on your desktop, called SFCFix.txt.
• Copy and paste the content of SFCFix.txt in your next post please.

After the fix, run the command SFC /scannow again and let me know what it returns.

 

[admmpat]

Hello and thank you for Supply.

Here is the Sfc /scannow output and attached the 3 Log Files.

sfc /scannow

Systemsuche wird gestartet. Dieser Vorgang kann einige Zeit dauern.

Überprüfungsphase der Systemsuche wird gestartet.
Überprüfung 100 % abgeschlossen.

Vom Windows-Ressourcenschutz wurden beschädigte Dateien gefunden, und
einige davon konnten nicht repariert werden. Weitere Informationen finden Sie in der Datei "CBS.Log" unter "windir\Logs\CBS\CBS.log",
z.B. "C:\Windows\Logs\CBS\CBS.log".
Hinweis: Bei der Offlinewartung wird die Protokollierung derzeit nicht unterstützt.

Kind Regards,

Martin

 

[axe0]

Can you try DISM /Online /Cleanup-Image /RestoreHealth without any local source?

 

[admmpat]

DISM /Online /Cleanup-Image /RestoreHealth

Tool zur Imageverwaltung für die Bereitstellung
Version: 10.0.14393.0

Abbildversion: 10.0.14393.2457

[==========================100.0%==========================]
Fehler: 0x800f081f

Die Quelldateien wurden nicht gefunden.
Geben Sie mit der Option "Quelle" den Ort der Dateien an, die zum Wiederherstellen des Features erforderlich sind. Weitere Informationen zum Angeben eines Quellorts finden Sie unter "Configure a Windows Repair Source".

Die DISM-Protokolldatei befindet sich unter "C:\Windows\Logs\DISM\dism.log".

 

[axe0]

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-win32 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.
  
  

 

[admmpat]

Hi Axe0,

just tried, tells Unsupported.

I Assume, as it is an PXE Streamed citrix vdisk running in Memory , SMART won't Work here.

 

[axe0]

I would like to have a look at your Components hive.

Retrieve Components Hive
1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
2. Please copy this file to your desktop.
3. 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.
4. The file may be too large to upload here, if so, please upload to OneDrive or Dropbox and just provide the link in your next post.

 

[admmpat]

Hello together,

just finaly fixed it.

There was an Reg Key ([HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-comdlg32.resources_31bf3856ad364e35_0.0.0.0_nb-no_25bb658cf851887a]) with chinese Letters wich had to be replaced.

After Replacing it, i took the install.wim with the exact same Version as installed (Provided by MS Premier Case becouse the Archive is only avaible MS Internal) and let it restorehealth 3 times in a row till all errors where fixed.

Then i installed the partly Installed KB 4478877 and 4487006 i got from dism /online /get-packages.

After those 3 Steps i was able to install the current CU Update.

Sadly, Microsoft removes all old CU Files from update catalog so i had to create the Premier case.

 

[axe0]

That's good news!

Are the errors with SFC and DISM also gone?

 

[admmpat]

Yes, the Chinese Reg Key just lead to not being able to repair. And becouse of the old CU only Microsoft was able to provide the file to fix the SFC and DISM errors.