Stuck on Dell Logo after updates

Hi

In the company I work for we have several Latitude laptops. They are all slightly different models but all have Windows 10 and very similar spec. We use Bitlocker on them all. Reasonably frequently on any one of these laptops after windows updates have been installed and the system reboots it will not reboot successfully into Windows.

After we choose to update and restart (or update and shut down) the following is what happens when the laptop restarts

Bitlocker screen appears - We enter code and thats fine

Then we get the Dell Logo screen and it doesnt get past this screen. It just stays with the Dell Logo and a spinning icon forever.

To get past this I have to turn the laptop off an on 3 times and then go through the advanced options screens and either choose system restore or safe mode and let it undo changes and then restart laptop and everything is fine. However this is very time consuming as it happens multiple times and for end users it is very frustrating as they might be reliant on me or somebody else to talk them through it.

This doesnt happen with any specifc update or on any specfic build of Windows. Drivers on the laptops are up to date and this can also happen with no peripherals plugged in. Also as soon as I restore Windows and get logged in I can just do the updates again and it will restart no problem. The laptops are not losing power during the update process. Any one laptop can have no errors during updates today and the next few times and then suddenly it will happen again in a few months time. The opposite can be the case with any other laptop.

I am really not sure what is causing this. Maybe it is something to do with Bitlocker but I need this to be on permanently. If there was a way of automatically disabling this during reboots for windows updates only this might help.I have tried remporarily disabling it a few times on different laptops just before rebooting for updates and the laptops had no issues. However this might just be coincidence as these laptops might have rebooted fine on these occasions anyway.

If anybody here has any ideas I would really appreciate it.

Thanks

Brian