I've been checking several Dell Pro 14 Plus laptops using Dell Command Update and noticed something odd. The System Information only shows a driver version for the ControlVault3, specifically version 6.2.25.24, while I found version 6.2.26.36 after manually downloading the update from Dell's website. We set up DCU via Intune policy to handle firmware and driver updates automatically, but this particular firmware update seems to be skipped. Is anyone else having this issue? Also, is there an alternative method to verify the actual firmware version of ControlVault? I'd appreciate any insights!
5 Answers
Last week I had a similar situation. Maybe check your Device Manager? If you see a warning on Dell Control Guard, try uninstalling it and then run the Command Update again. That might do the trick!
I can confirm the same behavior—Device Manager shows 5.15.9.9, while the Control Panel shows 5.15.10.14. It’s confusing, as I thought I had the update installed. This was from the package they emailed out recently.
I'm having the same issue! It seems Dell Command Update isn't detecting the latest drivers either. Even the standard Windows Update doesn't find anything. They really lack good documentation for rolling out software silently, which doesn't help at all. I've tried everything, but no luck!
I was curious about that too because installing the update didn't change my Device Manager list. Then I found out that Dell messed up their advisory page! The listed installer version isn't the actual driver or firmware version. For instance, they said version 5.15.10.14 was patched, but that's the installer version, not the driver. The real driver I have is 5.15.9.9 based on updates from April and May. Crazy, right?
Yeah, I noticed the same thing! The driver from G7K77_WIN64_5.15.10.14_A31_01.EXE gives you 5.15.9.9 when installed. Uninstalling the driver and running the Command Update flagged the correct driver. It's quite the mess.
We're experiencing this too! Even when we manually install the updates, the driver version doesn't change at all. It's frustrating!
I managed to run it quietly by extracting CVHCI64.exe from the downloaded package and using the command /v/qn without any space. That worked for me!