Bootloop after trying Installing KB4493473

[Wisdome]

How often does this Update Reboot?

 

[Sysnative Windows Update]

A reboot will be required after installation. It should happen only once, two times tops.

 

[Wisdome]

I Think now is the 10x reboot. Should i Stop it? One Question, does a Virtuall machine on a HyperV needs more Reboots?

 

[Sysnative Windows Update]

It can take a while. Please leave it for another half an hour.

 

[Wisdome]

I asked me one Question, why do we install
2019-05 Servicing Stack Update für Windows Server 2016 für x64-basierte Systeme (KB4498947) instead of
2019-04 Kumulatives Update für Windows Server 2016 für x64-basierte Systeme (KB4493473) which was before and does not work.

Ok, I let it running this Night and report tomorrow morning. Again thank you for your gorgeous help so far.
Good night

 

[Sysnative Windows Update]

Because your system reported that this one was missing and necessary to be installed.

 

[Wisdome]

Good moring,
the System was still in Update modus und restarts the hole night.

SFC scannow : After Sfc /scannow, I get the Error: There is a system repair pending which requires reboot to complete. Restart Windows and run SFC scan again. Reboot does not cause anything.

attached the new cbs.txt

 

[Sysnative Windows Update]

Okay, fix it by running this again: Bootloop after trying Installing KB4493473

Is it an option to temporarily disable Hyper-V while we troubleshoot this? I've had a similar issue recently and it was the root cause.

 

[Wisdome]

Version: 10.0.14393.0

Abbildversion: 10.0.14393.0

[==========================100.0%==========================] Der Wiederherstellungsvorgang wurde erfolgreich abgeschlossen.
Der Vorgang wurde erfolgreich beendet.

Now I am at that point again.
I try Sfc scannow again an get
Error: There is a system repair pending which requires reboot to complete. Restart Windows and run SFC scan again.

In German: "Es steht eine Systemreparatur aus, deren Abschluss einen Neustart erfordert"

Attached new cbs.zip

 

[Sysnative Windows Update]

You need to run Windows Repair Tool that I linked.

 

[Wisdome]

Windows Repair tool and sfc scannow done with Result:
Windows Resource Protection did not find any integrity violations." / "Der Windows-Ressourcenschutz hat keine Integritätsverletzungen gefunden. "

Should I start Dism /Online /Cleanup-Image /RestoreHealth again?

 

[Sysnative Windows Update]

No, I suspect this is a Hyper-V issue.

 

[Wisdome]

The Thing is, we have 4 VM on the Hyper V. This one is the only VM who was problems.

After the Reboot the Windows Updates wants to Install
2019-11 Servicing Stack Update für Windows Server 2016 für x64-basierte Systeme (KB4520724)
and
2019-04 Kumulatives Update für Windows Server 2016 für x64-basierte Systeme (KB4493473)

why does the Updates doesn't want to install KB4498947



About for Question above:
"Is it an option to temporarily disable Hyper-V while we troubleshoot this? I've had a similar issue recently and it was the root cause. "

this is possible.

 

[Wisdome]

After auto-Download from the Windows-Update without Installation, the SFC scannow, says again Error: There is a system repair pending which requires reboot to complete. Restart Windows and run SFC scan again.

 

[Sysnative Windows Update]

What did you try from Windows Update?

 

[Wisdome]

I don't try anything. It was the auto Windows Update Download.

 

[Sysnative Windows Update]

Please remove hyper V and then try installing only the update I linked, so the Servicing Stack 2019-04 and then reboot and retry updates.

Do not restore Hyper-V until you hear back from me.

I am off to bed now.

Good night.

 

[Wisdome]

Do not understand, how can I Access a virtuelle Hyper-V-Maschine, when I remove Hyper-V-Server?

Good Night

 

[Sysnative Windows Update]

Oh, you need it for the machine to work. Okay. In that case, I would recommend trying to install the latest Servicing Stack:

http://download.windowsupdate.com/c..._97604f0b532d6da814b4120fc43b2d9f6fd0b356.msu

If it fails, attach CBS.log and C:\Windows\Inf\setupapi.dev.log.

 

[Wisdome]

Hello again and happy new year,

Just that you understand me: We have 1 physically Server-Hardware Windows 2016 Server which works as Hyper-V-Server.
One the Hyper-V-Server we installed 4 Virtuelle Windows 2016 Server: 2 DC, 1 Terminalsever and 1 Fileserver.
The Fileserver has the problems with the Rebootloops, like i showed in the Video before.

I Try what unrecommend above, but I get the same Problem. The SFc-Scan before installation was OK.

Attached the file.