-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center.
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center.
- HP Community
- Notebooks
- Notebook Hardware and Upgrade Questions
- Who Me Too'd this topic

Create an account on the HP Community to personalize your profile and ask a question
07-12-2020 05:48 PM - edited 07-12-2020 05:49 PM
We recently upgraded BIOS on laptops across our fleet using HP SSM. On the whole, it worked fine.
We are however getting incidents reports by dozens of users across our organisation from users that have a HP Zbook 15 G4 laptop.
They are advising that their G2 thunderbolt docks have stopped working after the upgrade bios ran.
This is the BIOS version they are all running:
HP Notebook System BIOS Update (P70) - Version: 01.34 A (SP103803.CVA)
Some troubleshooting already performed:
If we check the secure connect app we can see the user's dock and port is not attached (even though the device has been previously approved).
Thinking that maybe there is another component out of date we proceeded to add further categories to hp ssm which deployed the following:
Intel Thunderbolt 3 FW for HP ZBook 15 G4 - Version: 41.2.5.5.1 A (SP98129.CVA)
Realtek USB Audio Driver for HP Thunderbolt Dock G2 - Version: 6.3.9600.250 A (SP102365.CVA)
Intel Thunderbolt 3 Secure Connect for 2018 - Version: 17.4.78.500 B
none of these additional driver upgrades appear to help.
We really need a solution that we can push out across the fleet. So rolling back bios in my view is not an easy option. We have a bios password enabled.
I should also mention that we have secure connect set up in bios. we have changed to user authorisation and it hasnt really made a difference.
there have been a few minor instances where the docks did come back after performing some of the above steps, however the next day the docks just stopped working again.
it is very likely that dock firmware may not be up to date on our entire fleet. We did however obtain a dock we could firmware upgrade to the latest version. Using this on a pc also did not help.