There are reports of Windows failing to boot on the Dell Pro 16 Plus PB16250 after BIOS 2.19.0 and recent Intel driver updates. Which updates should I watch for, and what can I try if a laptop gets stuck?
Could Dell Pro 16 Plus updates stop Windows from booting?
Answers
The reported combination is BIOS 2.19.0 with Intel Ethernet 20.0.3.35, Bluetooth 24.70.0.4, and the Intel extension or NPU driver 32.0.100.4841. The report describes the BIOS flash completing, followed by Windows hanging or crashing early in startup.
For now, I'd hold off on installing that combination together, or exclude those drivers while testing. The report doesn't establish which driver is responsible, or whether one driver alone causes the problem.
Reply to this answer
If you're already in a boot loop, try getting into Windows Recovery Environment. Interrupting startup with a forced shutdown three times may bring it up. From there, go to Troubleshoot, Advanced options, Startup Settings, then Restart and press 4 or F4 for Safe Mode.
In Device Manager, check the recently updated Intel Ethernet, Bluetooth, and Intel AI Boost devices. Their Driver tabs may offer a Roll Back Driver option. Restart normally afterward and check that Dell Update won't automatically reinstall the same versions. Rollback may not be available for every device.
Reply to this answer
Don't assume every PB16250 on BIOS 2.19.0 is affected. Some reported systems with Ultra 5 processors have had no issue, and an Ultra 7 system was also reported running the listed configuration without a crash. That doesn't rule out a compatibility problem, but it makes the conditions unclear.
Reply to this answer
There are also reports of similar boot loops clearing after resetting BIOS settings to defaults, and one report mentioning BIOS and Wi-Fi driver changes. Those aren't confirmed fixes for this particular driver combination. If you try a BIOS reset, check and record any settings your setup depends on first.
Reply to this answer
Add your answer
Answers are reviewed before publication.
6a~plovergauge_493:
Safe Mode and driver rollback are recovery options to try, not proof that all three drivers are faulty. The specific trigger hasn't been isolated.