My organization recently purchased several HP ProBook 4 G1a 16 laptops, model BP7Y7UA. We normally wipe every new device and install a clean copy of Windows 11 from installation media. The installation itself completes normally, but halfway through the first Windows Update run, the machines become severely unstable. Task Manager stops refreshing, wired networking disconnects even though the adapter remains visible, some applications will not open or close, and pressing the Windows key can crash Explorer. After restarting, the laptop often boots to a black screen with only the mouse cursor visible.
I have tried downloading the ISO again, using the Media Creation Tool, and using different USB drives, so the installation media does not seem to be the issue. The problem appears to start when Windows Update installs drivers or patches. We also have similar ProBook units with a different configuration that do not show the problem. Has anyone seen this on the BP7Y7UA model or found a reliable workaround?
5 Answers
Before wiping the factory installation, boot it once and use HP Image Assistant to install only the BIOS and firmware updates. Reboot and let those finish completely, then perform the clean Windows installation. A firmware or BIOS update may be required before Windows Update can correctly handle the newer hardware.
The configuration difference may be important. The affected BP7Y7UA uses a Ryzen 7 250 with Radeon 780M graphics and a touchscreen, while the working BP7Y2UA uses a Ryzen 5 230 with Radeon 760M. This sounds more like Windows Update replacing the graphics or chipset driver with a bad version than a problem with the Windows image itself. Try keeping the machine offline, booting Safe Mode, removing the AMD display package with AMD Cleanup Utility, and then installing the current driver manually from AMD or HP before reconnecting it.
I would avoid allowing Windows Update to install everything immediately. Install Windows while disconnected from the network, apply the model-specific BIOS, chipset, graphics, and network drivers manually, then reconnect and test updates in smaller groups. Check Windows Update history and Event Viewer after each reboot so you can identify which driver or update triggers the failure.
We have seen similar behavior on other HP systems after driver deployment: networking disappears even though the adapters still show as working in Device Manager, and the only recovery is reloading the machine. That points strongly to a faulty driver package rather than a defective USB installer. If you use HP Image Assistant, verify exactly which drivers it selects instead of accepting every recommended package automatically.
Compare the installed driver versions before and after the update, especially the AMD display, chipset, Wi-Fi, and Ethernet drivers. If the issue can be reproduced, capture the update history and Event Viewer logs from a failed machine. That evidence should help determine whether a particular Windows patch or HP driver is responsible and gives HP or Microsoft something concrete to investigate.
That matches what we are seeing: the hardware remains visible, but networking and the desktop stop functioning after the update cycle. We are testing a driver-controlled deployment with the affected models kept offline until the required drivers are installed.