Bootloop after trying Installing KB4493473

[Wisdome]

Ok, I try the Normal WIndows update Reboot => Rebootloop

After that I startet Windows repair and try KB4520724 manuelly => Rebootloop :-(

 

[Sysnative Windows Update]

Please run a fresh FRST scan:

Bootloop after trying Installing KB4493473

 

[Wisdome]

Done.

 

[Sysnative Windows Update]

Okay, can I get the full CBS folder export as well.

This is very interesting.

Is there anything connected to the VMs via USB or any other ports?

 

[Wisdome]

Yes, there are to USB connected. One ist RDX-Tandberg-Backupdrive, which I just removed and one "Wibu-KEY-Dongle" for a special license-key from Customed.

I can remove the Wibu-Key-Dongle his Afternoon.

I attached both files.

 

[Sysnative Windows Update]

It looks like there is a driver operation causing the issue:

2020-01-02 08:42:22, Info                  CBS    Failed reading session id for driver operation sequenceID 121 [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2020-01-02 08:42:22, Info                  CBS    Failed loading a driver operation [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2020-01-02 08:42:22, Error                 CBS    Doqi: Failed loading driver operations queue. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2020-01-02 08:42:22, Info                  CBS    Failed loading driver operation queue [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2020-01-02 08:42:22, Info                  CBS    Failed initializing driver operation queue [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2020-01-02 08:42:22, Info                  CBS    Perf: InstallUninstallChain complete.
2020-01-02 08:42:22, Info                  CSI    00001641@2020/1/2:07:42:22.042 CSI Transaction @0x1fd96b97370 destroyed
2020-01-02 08:42:22, Info                  CBS    Failed to execute execution chain. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2020-01-02 08:42:22, Error                 CBS    Failed to process single phase execution. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2020-01-02 08:42:22, Info                  CBS    WER: Generating failure report for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~14393.2941.1.10, status: 0x80070490, failure source: Execute, start state: Staged, target state: Installed, client id: WindowsUpdateAgent
2020-01-02 08:42:22, Info                  CBS    Not able to query DisableWerReporting flag.  Assuming not set... [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2020-01-02 08:42:22, Info                  CBS    Added C:\Windows\Logs\CBS\CBS.log to WER report.

Please provide a fresh copy of this file: c:\Windows\inf\setupapi.dev.log

Can QuincyUpdater be removed as a test as well?

As the first test, you may want to run the Server in Clean Boot Mode to eliminate any interference and retry the update from there:

https://support.microsoft.com/en-us/help/929135/how-to-perform-a-clean-boot-in-windows

 

[Wisdome]

Here the File.

 

[Wisdome]

the Update does not work, Bootloop

 

[Sysnative Windows Update]

Which steps have you taken thus far?

 

[Wisdome]

1 Step done: As the first test, you may want to run the Server in Clean Boot Mode to eliminate any interference and retry the update from there:
https://support.microsoft.com/en-us/help/929135/how-to-perform-a-clean-boot-in-windows
Bootloop

2. Step: Uninstall QuincyUpdater. And Try Update again.
Bootloop

:-(

 

[Wisdome]

One Question: Is it possible that 1 Driver or Software on Hyper-V-Server could cause the Problem and is there a way to check it?

 

[Sysnative Windows Update]

Yes, it is. I would need to see what drivers are loaded on the hypervisor via FRST logs.

 

[Wisdome]

Here they are.

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 erfolgreich
repariert. 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.

 

[Wisdome]

C:\Users\Administrator>Dism.exe /Online /Cleanup-Image /RestoreHealth

Tool zur Imageverwaltung für die Bereitstellung
Version: 10.0.14393.3241

Abbildversion: 10.0.14393.3241

[==========================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".

 

[Sysnative Windows Update]

Hi!

This is merely a bug and has no real effect on your issue, but let's address it:

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
3. Save any open documents and close all open windows.
4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
6. SFCFix will now process the script.
7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

Step#2 - DISM /RestoreHealth Scan
Warning:this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

1. Right-click on the Start button and select Command Prompt (Admin)
2. When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter
   Dism /Online /Cleanup-Image /RestoreHealth
3. Once it finishes, copy and paste the following into the command-prompt window and press Enter. If prompted to overwrite the existing file go ahead.
   copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
   
4. Once this has completed please go to your Desktop and you will find CBS.txt => Please zip/upload to this thread.
   Please Note:: if the file is too big (over 7MB) to upload to your next post, please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.

 

[Wisdome]

SFCFix version 3.0.2.1 by niemiro.
Start time: 2020-01-04 07:21:36.150
Microsoft Windows Server 10 Build 14393 - amd64
Using .zip script file at C:\Users\Administrator\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\Defender.psd1
Successfully took permissions for file or folder C:\windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpComputerStatus.cdxml
Successfully took permissions for file or folder C:\windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpPreference.cdxml
Successfully took permissions for file or folder C:\windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpScan.cdxml
Successfully took permissions for file or folder C:\windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpSignature.cdxml
Successfully took permissions for file or folder C:\windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpThreat.cdxml
Successfully took permissions for file or folder C:\windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpThreatCatalog.cdxml
Successfully took permissions for file or folder C:\windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpThreatDetection.cdxml
Successfully took permissions for file or folder C:\windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpWDOScan.cdxml

Successfully copied file C:\Users\Administrator\AppData\Local\niemiro\Archive\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\Defender.psd1 to C:\windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\Defender.psd1.
Successfully copied file C:\Users\Administrator\AppData\Local\niemiro\Archive\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpComputerStatus.cdxml to C:\windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpComputerStatus.cdxml.
Successfully copied file C:\Users\Administrator\AppData\Local\niemiro\Archive\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpPreference.cdxml to C:\windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpPreference.cdxml.
Successfully copied file C:\Users\Administrator\AppData\Local\niemiro\Archive\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpScan.cdxml to C:\windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpScan.cdxml.
Successfully copied file C:\Users\Administrator\AppData\Local\niemiro\Archive\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpSignature.cdxml to C:\windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpSignature.cdxml.
Successfully copied file C:\Users\Administrator\AppData\Local\niemiro\Archive\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpThreat.cdxml to C:\windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpThreat.cdxml.
Successfully copied file C:\Users\Administrator\AppData\Local\niemiro\Archive\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpThreatCatalog.cdxml to C:\windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpThreatCatalog.cdxml.
Successfully copied file C:\Users\Administrator\AppData\Local\niemiro\Archive\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpThreatDetection.cdxml to C:\windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpThreatDetection.cdxml.
Successfully copied file C:\Users\Administrator\AppData\Local\niemiro\Archive\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpWDOScan.cdxml to C:\windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpWDOScan.cdxml.

Successfully restored ownership for C:\windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\Defender.psd1
Successfully restored permissions on C:\windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\Defender.psd1
Successfully restored ownership for C:\windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpComputerStatus.cdxml
Successfully restored permissions on C:\windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpComputerStatus.cdxml
Successfully restored ownership for C:\windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpPreference.cdxml
Successfully restored permissions on C:\windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpPreference.cdxml
Successfully restored ownership for C:\windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpScan.cdxml
Successfully restored permissions on C:\windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpScan.cdxml
Successfully restored ownership for C:\windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpSignature.cdxml
Successfully restored permissions on C:\windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpSignature.cdxml
Successfully restored ownership for C:\windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpThreat.cdxml
Successfully restored permissions on C:\windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpThreat.cdxml
Successfully restored ownership for C:\windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpThreatCatalog.cdxml
Successfully restored permissions on C:\windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpThreatCatalog.cdxml
Successfully restored ownership for C:\windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpThreatDetection.cdxml
Successfully restored permissions on C:\windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpThreatDetection.cdxml
Successfully restored ownership for C:\windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpWDOScan.cdxml
Successfully restored permissions on C:\windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpWDOScan.cdxml
PowerCopy:: directive completed successfully.




Successfully processed all directives.



Failed to generate a complete zip file. Upload aborted.


SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 9 datablocks.
Finish time: 2020-01-04 07:27:07.912
Script hash: 8ThLOTwS1f6O7EMg/3Zw8mFupY7gKoIDKOKMDkxB+/Q=
----------------------EOF----------------------

 

[Sysnative Windows Update]

Can you try choosing the Disable Driver Signature Enforcement option and see if the install goes through: Disable Driver Signature Enforcement on Windows 2016 Server

 

[Wisdome]

Are you talking about the Hyper-V server or the VM Fileserver?

 

[Sysnative Windows Update]

VM.

 

[Wisdome]

C:\Users\Administrator>bcdedit /set testsigning on
Fehler beim Festlegen der Elementdaten.
Der Wert wird durch die Richtlinie für sicheres Starten geschützt und kann nicht geändert oder gelöscht werden.

C:\Users\Administrator>bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
Der Vorgang wurde erfolgreich beendet.

C:\Users\Administrator>bcdedit.exe -set TESTSIGNING ON
Fehler beim Festlegen der Elementdaten.
Der Wert wird durch die Richtlinie für sicheres Starten geschützt und kann nicht geändert oder gelöscht werden.


I found the option "sicheres Starten" in Hyper-V-Option and switch it off and will try it again.
too be continued...