Hello,
we have three users so far with a slow boot performance, where the device got stuck before the login screen. All reported with the EliteBook 840 G1
Some device informations:
OS: Windows 7 x64 Enterprise
- joined into our company domain
- Bitlocker enabled
BIOS: v1.20
What is the issue?
The users reported, that when they use the device at home it is getting stuck during the boot process. The login screens is not appearing or comes with a huge delay of >15min. If the login screen is there with the huge delay, then the notebook is not usable since it is very slow (CPU with high load), but we had cases where a user left it running over night and even after 12h the login screen was not there.
The strange thing is, that it releases the lock immediatly when the user plugs in our company network cable, so it looks that something is waiting for a response, but without or a random timeout. If no network cable is plugged in and all network cards disabled, then the issue can happen.
We had some early devices, which have been delivered with BIOS 1.08 at that time and none of these devices has the same issue. The affected devices have been all delivered with BIOS 1.20. Early this year we have seen that HP removed the version 1.20 from the website and only 1.12 was available until last week, where HP released 1.30A.
Of course we tried that BIOS version, but it did not resolve the issue.
A call had been created with Microsoft and we provided them with a lot of system logs, boot trace logs, ... but we could not resolve it.
What we tried so far:
- BIOS update to latest 1.30A
- latest network card drivers from Intel
- latest Windows Updates
- specific Windows hotfixes
We though, that it could be linked to our Build Process, but we have different models and especially the 820 G1, which should be very similar than the 840 G1, but no other different model reported this issue.
No user reported this issue so far with the early purchased 840 G1's (running more than one year), but they run with BIOS 1.08. Except the BIOS the rest of the hardware should be the same. The devices with issue have been purchased in June/July 2014, but delivery started about September/October to the users, where we had as well the first report of a user.