Windows Cumulative Update - Black Screen Spinning Circle Pre-Login

[Guest Hicksteruk]

Hi all,

 

Looking for some help with an issue with Cumulative Updates on Windows 10 for a random selection of machines.

 

Basically we have a selection of 100s out of 1000s of Windows 10 machines with different hardware models and OS versions that black screen on reboot when installing cumulative updates.

 

There are recent reports of black screen issues with cumulative updates which can be resolved with a ctrl+alt+del but this is not the same issue. We are unable to get to a login screen at all.

 

If we run a Cumulative Update on an affected machine, it runs and then asks for a reboot. Upon reboot the UEFI screen loads and then leaves us with a spinning circle of dots. The machine then sits there indefinitely with the spinning circle. The only way to work around this is to boot into safe mode, enter the bit locker key, and reboot. However, upon doing this the update rolls back and then lets you login. The problem is, if you run the update again, the same things happen. There doesn’t appear to be anything useful in the logs. The event logs are pretty empty, presumably because the point where it fails is pre logging?

 

The ntbtlog form a machne looks like this and appears to loop around on in that cycle:

 

…..

 

BOOTLOG_NOT_LOADED @kdnic.inf,%kdnic.devicedesc%;Microsoft Kernel Debug Network Adapter

 

BOOTLOG_NOT_LOADED @oem27.inf,%iskldtgt2%;Intel® HD Graphics 530

 

BOOTLOG_NOT_LOADED @oem33.inf,%rtl8168.devicedesc%;Realtek PCIe GBE Family Controller

 

BOOTLOG_NOT_LOADED @msports.inf,%*pnp0400.devicedesc%;Printer Port

 

BOOTLOG_NOT_LOADED @msports.inf,%*pnp0501.devicedesc%;Communications Port

 

BOOTLOG_NOT_LOADED @cpu.inf,%intelppm.devicedesc%;Intel Processor

 

BOOTLOG_NOT_LOADED @cpu.inf,%intelppm.devicedesc%;Intel Processor

 

BOOTLOG_NOT_LOADED @cpu.inf,%intelppm.devicedesc%;Intel Processor

 

BOOTLOG_NOT_LOADED @cpu.inf,%intelppm.devicedesc%;Intel Processor

 

BOOTLOG_NOT_LOADED @kdnic.inf,%kdnic.devicedesc%;Microsoft Kernel Debug Network Adapter

 

BOOTLOG_NOT_LOADED @oem27.inf,%iskldtgt2%;Intel® HD Graphics 530

 

BOOTLOG_NOT_LOADED @oem33.inf,%rtl8168.devicedesc%;Realtek PCIe GBE Family Controller

 

BOOTLOG_NOT_LOADED @msports.inf,%*pnp0400.devicedesc%;Printer Port

 

BOOTLOG_NOT_LOADED @msports.inf,%*pnp0501.devicedesc%;Communications Port

 

BOOTLOG_NOT_LOADED @cpu.inf,%intelppm.devicedesc%;Intel Processor

 

BOOTLOG_NOT_LOADED @cpu.inf,%intelppm.devicedesc%;Intel Processor

 

BOOTLOG_NOT_LOADED @cpu.inf,%intelppm.devicedesc%;Intel Processor

 

BOOTLOG_NOT_LOADED @cpu.inf,%intelppm.devicedesc%;Intel Processor

 

BOOTLOG_NOT_LOADED @kdnic.inf,%kdnic.devicedesc%;Microsoft Kernel Debug Network Adapter

 

BOOTLOG_NOT_LOADED @oem27.inf,%iskldtgt2%;Intel® HD Graphics 530

 

BOOTLOG_NOT_LOADED @oem33.inf,%rtl8168.devicedesc%;Realtek PCIe GBE Family Controller

 

BOOTLOG_NOT_LOADED @msports.inf,%*pnp0400.devicedesc%;Printer Port

 

BOOTLOG_NOT_LOADED @msports.inf,%*pnp0501.devicedesc%;Communications Port

 

BOOTLOG_NOT_LOADED @cpu.inf,%intelppm.devicedesc%;Intel Processor

 

BOOTLOG_NOT_LOADED @cpu.inf,%intelppm.devicedesc%;Intel Processor

 

BOOTLOG_NOT_LOADED @cpu.inf,%intelppm.devicedesc%;Intel Processor

 

BOOTLOG_NOT_LOADED @cpu.inf,%intelppm.devicedesc%;Intel Processor

 

BOOTLOG_NOT_LOADED @kdnic.inf,%kdnic.devicedesc%;Microsoft Kernel Debug Network Adapter

 

BOOTLOG_NOT_LOADED @oem27.inf,%iskldtgt2%;Intel® HD Graphics 530

 

BOOTLOG_NOT_LOADED @oem33.inf,%rtl8168.devicedesc%;Realtek PCIe GBE Family Controller

 

BOOTLOG_NOT_LOADED @msports.inf,%*pnp0400.devicedesc%;Printer Port

 

BOOTLOG_NOT_LOADED @msports.inf,%*pnp0501.devicedesc%;Communications Port

 

BOOTLOG_NOT_LOADED @cpu.inf,%intelppm.devicedesc%;Intel Processor

 

BOOTLOG_NOT_LOADED @cpu.inf,%intelppm.devicedesc%;Intel Processor

 

BOOTLOG_NOT_LOADED @cpu.inf,%intelppm.devicedesc%;Intel Processor

 

BOOTLOG_NOT_LOADED @cpu.inf,%intelppm.devicedesc%;Intel Processor

 

……

 

The issues has happened now for the past 2 months cumulative updates ( we pulled last months because of the issue). We are unable to find any link between the machine affected, drivers, software, OS versions etc. Annoyingly when trying to fix the issue, machines will randomly succeed their update and then work fine. But it has no correlation so the fix that has been tried at the time. We have tried updating as many drivers as possible, but nothing shifts it.

 

Does anyone have any tips or insight into resolving this type of issue? Is there any more aggressive logging which can be enabled to help identify where the issue is?

 

Any help offered would be very much appreciated.

 

Cheers

 

PJ

 

More...