Unsolved
This post is more than 5 years old
3 Posts
0
6501
February 26th, 2017 12:00
E6440 – unable to update control vault firmware
E6440 – unable to update control vault firmware
Hi, I am unable to update the control vault firmware on my e6440
The update program appears to work ok. But on reboot the update dose not complete
how can I fix this?
here is the contents of C:\Windows\System32\CVFirmwareUpgradeLog.txt
Thursday December 29, 2016 17:47:17: Command - FWUpgrade
Thursday December 29, 2016 17:47:17: There is no FW upgrade count reg key
Thursday December 29, 2016 17:47:17: Event: SUCCESS creating FW Upgrade events. Return code: 0
Thursday December 29, 2016 17:47:17: Event: eventIndx: 0, Handle: 248
Thursday December 29, 2016 17:47:17: Event: eventIndx: 1, Handle: 5c
Thursday December 29, 2016 17:47:17: Event: eventIndx: 2, Handle: 6c
Thursday December 29, 2016 17:47:17: Event: eventIndx: 3, Handle: 70
Thursday December 29, 2016 17:47:17: Event: eventIndx: 4, Handle: 60
Thursday December 29, 2016 17:47:22: cvif_IsUsh (0x0)
Thursday December 29, 2016 17:47:22: Updating ControlVault firmware from 3.0.405.0 to 4.5.13.0
Thursday December 29, 2016 17:47:22: Event: FwUpgradeStarted: 1, Handle: 5c
Thursday December 29, 2016 17:47:22: Control Vault getting chip type
Thursday December 29, 2016 17:47:22: Could not determine chip type
Thursday December 29, 2016 17:47:22: Failed. Return code: 15 Set number of failed FW upgrades to 1
Thursday December 29, 2016 17:47:22: Event: FwUpgradeError: 4, Handle: 60
Thursday December 29, 2016 17:54:46: Command - FWUpgrade
Thursday December 29, 2016 17:54:46: Event: SUCCESS creating FW Upgrade events. Return code: 0
Thursday December 29, 2016 17:54:46: Event: eventIndx: 0, Handle: 4e0
Thursday December 29, 2016 17:54:46: Event: eventIndx: 1, Handle: 468
Thursday December 29, 2016 17:54:46: Event: eventIndx: 2, Handle: 1f4
Thursday December 29, 2016 17:54:46: Event: eventIndx: 3, Handle: 4e8
Thursday December 29, 2016 17:54:46: Event: eventIndx: 4, Handle: 4e4
Thursday December 29, 2016 17:54:51: cvif_IsUsh (0x0)
Thursday December 29, 2016 17:54:51: Updating ControlVault firmware from 3.0.405.0 to 4.5.13.0
Thursday December 29, 2016 17:54:51: Event: FwUpgradeStarted: 1, Handle: 468
Thursday December 29, 2016 17:54:51: Control Vault getting chip type
Thursday December 29, 2016 17:54:51: Could not determine chip type
Thursday December 29, 2016 17:54:51: Failed. Return code: 15 Set number of failed FW upgrades to 2
Thursday December 29, 2016 17:54:51: Event: FwUpgradeError: 4, Handle: 4e4
Thursday December 29, 2016 17:54:54: Command - FWUpgrade
Thursday December 29, 2016 17:54:54: Event: SUCCESS creating FW Upgrade events. Return code: 0
Thursday December 29, 2016 17:54:54: Event: eventIndx: 0, Handle: 520
Thursday December 29, 2016 17:54:54: Event: eventIndx: 1, Handle: 524
Thursday December 29, 2016 17:54:54: Event: eventIndx: 2, Handle: 528
Thursday December 29, 2016 17:54:54: Event: eventIndx: 3, Handle: 52c
Thursday December 29, 2016 17:54:54: Event: eventIndx: 4, Handle: 530
Thursday December 29, 2016 17:55:00: cvif_IsUsh (0x0)
Thursday December 29, 2016 17:55:00: Updating ControlVault firmware from 3.0.405.0 to 4.5.13.0
Thursday December 29, 2016 17:55:00: Event: FwUpgradeStarted: 1, Handle: 524
Thursday December 29, 2016 17:55:00: Control Vault getting chip type
Thursday December 29, 2016 17:55:00: Could not determine chip type
Thursday December 29, 2016 17:55:00: Failed. Return code: 15 Set number of failed FW upgrades to 3
Thursday December 29, 2016 17:55:00: Event: FwUpgradeError: 4, Handle: 530
Thursday December 29, 2016 18:09:43: Command - FWUpgrade
Thursday December 29, 2016 18:09:43: Event: SUCCESS creating FW Upgrade events. Return code: 0
Thursday December 29, 2016 18:09:43: Event: eventIndx: 0, Handle: 208
Thursday December 29, 2016 18:09:43: Event: eventIndx: 1, Handle: 1c4
Thursday December 29, 2016 18:09:43: Event: eventIndx: 2, Handle: 1c8
Thursday December 29, 2016 18:09:43: Event: eventIndx: 3, Handle: 1dc
Thursday December 29, 2016 18:09:43: Event: eventIndx: 4, Handle: 20c
Thursday December 29, 2016 18:09:49: cvif_IsUsh (0x0)
Thursday December 29, 2016 18:09:49: Updating ControlVault firmware from 3.0.405.0 to 4.5.13.0
Thursday December 29, 2016 18:09:49: Event: FwUpgradeStarted: 1, Handle: 1c4
Thursday December 29, 2016 18:09:49: Control Vault getting chip type
Thursday December 29, 2016 18:09:49: Could not determine chip type
Thursday December 29, 2016 18:09:49: Failed. Return code: 15 Set number of failed FW upgrades to 4
Thursday December 29, 2016 18:09:49: Event: FwUpgradeError: 4, Handle: 20c
Sunday February 12, 2017 15:22:11: Command - FWUpgrade
Sunday February 12, 2017 15:22:11: Event: SUCCESS creating FW Upgrade events. Return code: 0
Sunday February 12, 2017 15:22:11: Event: eventIndx: 0, Handle: 50
Sunday February 12, 2017 15:22:11: Event: eventIndx: 1, Handle: 54
Sunday February 12, 2017 15:22:11: Event: eventIndx: 2, Handle: 44
Sunday February 12, 2017 15:22:11: Event: eventIndx: 3, Handle: 20c
Sunday February 12, 2017 15:22:11: Event: eventIndx: 4, Handle: 1ec
Sunday February 12, 2017 15:22:16: cvif_IsUsh (0x0)
Sunday February 12, 2017 15:22:16: Updating ControlVault firmware from 3.4.10.0 to 4.5.13.0
Sunday February 12, 2017 15:22:16: Event: FwUpgradeStarted: 1, Handle: 54
Sunday February 12, 2017 15:22:16: Control Vault getting chip type
Sunday February 12, 2017 15:22:16: Could not determine chip type
Sunday February 12, 2017 15:22:16: Failed. Return code: 15 Set number of failed FW upgrades to 5
Sunday February 12, 2017 15:22:16: Event: FwUpgradeError: 4, Handle: 1ec
Sunday February 12, 2017 15:45:51: Command - FWUpgrade
Sunday February 12, 2017 15:45:51: Event: SUCCESS creating FW Upgrade events. Return code: 0
Sunday February 12, 2017 15:45:51: Event: eventIndx: 0, Handle: 214
Sunday February 12, 2017 15:45:51: Event: eventIndx: 1, Handle: 21c
Sunday February 12, 2017 15:45:51: Event: eventIndx: 2, Handle: 220
Sunday February 12, 2017 15:45:51: Event: eventIndx: 3, Handle: 224
Sunday February 12, 2017 15:45:51: Event: eventIndx: 4, Handle: 228
Sunday February 12, 2017 15:45:57: cvif_IsUsh (0x0)
Sunday February 12, 2017 15:45:57: Updating ControlVault firmware from 3.4.10.0 to 4.5.13.0
Sunday February 12, 2017 15:45:57: Event: FwUpgradeStarted: 1, Handle: 21c
Sunday February 12, 2017 15:45:57: Control Vault getting chip type
Sunday February 12, 2017 15:45:57: Could not determine chip type
Sunday February 12, 2017 15:45:57: Failed. Return code: 15 Set number of failed FW upgrades to 6
Sunday February 12, 2017 15:45:57: Event: FwUpgradeError: 4, Handle: 228
Sunday February 12, 2017 15:51:28: Command - FWUpgrade
Sunday February 12, 2017 15:51:28: Event: SUCCESS creating FW Upgrade events. Return code: 0
Sunday February 12, 2017 15:51:28: Event: eventIndx: 0, Handle: 1dc
Sunday February 12, 2017 15:51:28: Event: eventIndx: 1, Handle: 1e0
Sunday February 12, 2017 15:51:28: Event: eventIndx: 2, Handle: 204
Sunday February 12, 2017 15:51:28: Event: eventIndx: 3, Handle: 218
Sunday February 12, 2017 15:51:28: Event: eventIndx: 4, Handle: 21c
Sunday February 12, 2017 15:51:33: cvif_IsUsh (0x0)
Sunday February 12, 2017 15:51:33: Updating ControlVault firmware from 3.4.10.0 to 4.5.13.0
Sunday February 12, 2017 15:51:33: Event: FwUpgradeStarted: 1, Handle: 1e0
Sunday February 12, 2017 15:51:33: Control Vault getting chip type
Sunday February 12, 2017 15:51:34: Could not determine chip type
Sunday February 12, 2017 15:51:34: Failed. Return code: 15 Set number of failed FW upgrades to 7
Sunday February 12, 2017 15:51:34: Event: FwUpgradeError: 4, Handle: 21c
Sunday February 12, 2017 16:20:48: Command - FWUpgrade
Sunday February 12, 2017 16:20:48: Event: SUCCESS creating FW Upgrade events. Return code: 0
Sunday February 12, 2017 16:20:48: Event: eventIndx: 0, Handle: 1c4
Sunday February 12, 2017 16:20:48: Event: eventIndx: 1, Handle: 1c8
Sunday February 12, 2017 16:20:48: Event: eventIndx: 2, Handle: 1e4
Sunday February 12, 2017 16:20:48: Event: eventIndx: 3, Handle: 210
Sunday February 12, 2017 16:20:48: Event: eventIndx: 4, Handle: 214
Sunday February 12, 2017 16:20:53: cvif_IsUsh (0x0)
Sunday February 12, 2017 16:20:53: Updating ControlVault firmware from 3.4.10.0 to 4.5.13.0
Sunday February 12, 2017 16:20:53: Event: FwUpgradeStarted: 1, Handle: 1c8
Sunday February 12, 2017 16:20:53: Control Vault getting chip type
Sunday February 12, 2017 16:20:53: Could not determine chip type
Sunday February 12, 2017 16:20:53: Failed. Return code: 15 Set number of failed FW upgrades to 8
Sunday February 12, 2017 16:20:53: Event: FwUpgradeError: 4, Handle: 214
Sunday February 12, 2017 16:31:23: Command - FWUpgrade
Sunday February 12, 2017 16:31:23: Event: SUCCESS creating FW Upgrade events. Return code: 0
Sunday February 12, 2017 16:31:23: Event: eventIndx: 0, Handle: 210
Sunday February 12, 2017 16:31:23: Event: eventIndx: 1, Handle: 214
Sunday February 12, 2017 16:31:23: Event: eventIndx: 2, Handle: 218
Sunday February 12, 2017 16:31:23: Event: eventIndx: 3, Handle: 21c
Sunday February 12, 2017 16:31:23: Event: eventIndx: 4, Handle: 220
Sunday February 12, 2017 16:31:28: cvif_IsUsh (0x0)
Sunday February 12, 2017 16:31:28: Updating ControlVault firmware from 3.4.10.0 to 4.5.13.0
Sunday February 12, 2017 16:31:28: Event: FwUpgradeStarted: 1, Handle: 214
Sunday February 12, 2017 16:31:28: Control Vault getting chip type
Sunday February 12, 2017 16:31:28: Could not determine chip type
Sunday February 12, 2017 16:31:28: Failed. Return code: 15 Set number of failed FW upgrades to 9
Sunday February 12, 2017 16:31:28: Event: FwUpgradeError: 4, Handle: 220
Saturday February 18, 2017 10:09:12: Command - FWUpgrade
Saturday February 18, 2017 10:09:12: Event: SUCCESS creating FW Upgrade events. Return code: 0
Saturday February 18, 2017 10:09:12: Event: eventIndx: 0, Handle: 4c
Saturday February 18, 2017 10:09:12: Event: eventIndx: 1, Handle: 50
Saturday February 18, 2017 10:09:12: Event: eventIndx: 2, Handle: 48
Saturday February 18, 2017 10:09:12: Event: eventIndx: 3, Handle: 204
Saturday February 18, 2017 10:09:12: Event: eventIndx: 4, Handle: 1fc
Saturday February 18, 2017 10:09:17: cvif_IsUsh (0x0)
Saturday February 18, 2017 10:09:17: Updating ControlVault firmware from 3.4.10.0 to 4.5.13.0
Saturday February 18, 2017 10:09:17: Event: FwUpgradeStarted: 1, Handle: 50
Saturday February 18, 2017 10:09:18: Control Vault getting chip type
Saturday February 18, 2017 10:09:18: Could not determine chip type
Saturday February 18, 2017 10:09:18: Failed. Return code: 15 Set number of failed FW upgrades to 10
Saturday February 18, 2017 10:09:18: Event: FwUpgradeError: 4, Handle: 1fc
Tuesday February 21, 2017 18:32:25: Command - FWUpgrade
Tuesday February 21, 2017 18:32:25: Event: SUCCESS creating FW Upgrade events. Return code: 0
Tuesday February 21, 2017 18:32:25: Event: eventIndx: 0, Handle: 210
Tuesday February 21, 2017 18:32:25: Event: eventIndx: 1, Handle: 218
Tuesday February 21, 2017 18:32:25: Event: eventIndx: 2, Handle: 1c4
Tuesday February 21, 2017 18:32:25: Event: eventIndx: 3, Handle: 1c8
Tuesday February 21, 2017 18:32:25: Event: eventIndx: 4, Handle: 208
Tuesday February 21, 2017 18:32:30: cvif_IsUsh (0x0)
Tuesday February 21, 2017 18:32:30: Updating ControlVault firmware from 3.4.10.0 to 4.5.13.0
Tuesday February 21, 2017 18:32:30: Event: FwUpgradeStarted: 1, Handle: 218
Tuesday February 21, 2017 18:32:30: Control Vault getting chip type
Tuesday February 21, 2017 18:32:30: Could not determine chip type
Tuesday February 21, 2017 18:32:30: Failed. Return code: 15 Set number of failed FW upgrades to 11
Tuesday February 21, 2017 18:32:30: Event: FwUpgradeError: 4, Handle: 208
Tuesday February 21, 2017 20:36:12: Command - FWUpgrade
Tuesday February 21, 2017 20:36:12: Event: SUCCESS creating FW Upgrade events. Return code: 0
Tuesday February 21, 2017 20:36:12: Event: eventIndx: 0, Handle: 1d8
Tuesday February 21, 2017 20:36:12: Event: eventIndx: 1, Handle: 1dc
Tuesday February 21, 2017 20:36:12: Event: eventIndx: 2, Handle: 220
Tuesday February 21, 2017 20:36:12: Event: eventIndx: 3, Handle: 228
Tuesday February 21, 2017 20:36:12: Event: eventIndx: 4, Handle: 22c
Tuesday February 21, 2017 20:36:17: cvif_IsUsh (0x0)
Tuesday February 21, 2017 20:36:17: Updating ControlVault firmware from 3.4.10.0 to 4.5.13.0
Tuesday February 21, 2017 20:36:17: Event: FwUpgradeStarted: 1, Handle: 1dc
Tuesday February 21, 2017 20:36:17: Control Vault getting chip type
Tuesday February 21, 2017 20:36:17: Could not determine chip type
Tuesday February 21, 2017 20:36:17: Failed. Return code: 15 Set number of failed FW upgrades to 12
Tuesday February 21, 2017 20:36:17: Event: FwUpgradeError: 4, Handle: 22c
Tuesday February 21, 2017 21:53:18: Command - FWUpgrade
Tuesday February 21, 2017 21:53:18: Event: SUCCESS creating FW Upgrade events. Return code: 0
Tuesday February 21, 2017 21:53:18: Event: eventIndx: 0, Handle: 210
Tuesday February 21, 2017 21:53:18: Event: eventIndx: 1, Handle: 214
Tuesday February 21, 2017 21:53:18: Event: eventIndx: 2, Handle: 218
Tuesday February 21, 2017 21:53:18: Event: eventIndx: 3, Handle: 21c
Tuesday February 21, 2017 21:53:18: Event: eventIndx: 4, Handle: 220
Tuesday February 21, 2017 21:53:23: cvif_IsUsh (0x0)
Tuesday February 21, 2017 21:53:23: Updating ControlVault firmware from 3.4.10.0 to 4.5.13.0
Tuesday February 21, 2017 21:53:23: Event: FwUpgradeStarted: 1, Handle: 214
Tuesday February 21, 2017 21:53:23: Control Vault getting chip type
Tuesday February 21, 2017 21:53:23: Could not determine chip type
Tuesday February 21, 2017 21:53:23: Failed. Return code: 15 Set number of failed FW upgrades to 13
Tuesday February 21, 2017 21:53:23: Event: FwUpgradeError: 4, Handle: 220
Saturday February 25, 2017 11:04:00: Command - FWUpgrade
Saturday February 25, 2017 11:04:00: Event: SUCCESS creating FW Upgrade events. Return code: 0
Saturday February 25, 2017 11:04:00: Event: eventIndx: 0, Handle: 210
Saturday February 25, 2017 11:04:00: Event: eventIndx: 1, Handle: 214
Saturday February 25, 2017 11:04:00: Event: eventIndx: 2, Handle: 218
Saturday February 25, 2017 11:04:00: Event: eventIndx: 3, Handle: 21c
Saturday February 25, 2017 11:04:00: Event: eventIndx: 4, Handle: 220
Saturday February 25, 2017 11:04:05: cvif_IsUsh (0x0)
Saturday February 25, 2017 11:04:05: Updating ControlVault firmware from 3.4.10.0 to 4.5.13.0
Saturday February 25, 2017 11:04:05: Event: FwUpgradeStarted: 1, Handle: 214
Saturday February 25, 2017 11:04:05: Control Vault getting chip type
Saturday February 25, 2017 11:04:05: Could not determine chip type
Saturday February 25, 2017 11:04:05: Failed. Return code: 15 Set number of failed FW upgrades to 14
Saturday February 25, 2017 11:04:05: Event: FwUpgradeError: 4, Handle: 220
Saturday February 25, 2017 15:44:15: Command - FWUpgrade
Saturday February 25, 2017 15:44:15: Event: SUCCESS creating FW Upgrade events. Return code: 0
Saturday February 25, 2017 15:44:15: Event: eventIndx: 0, Handle: 210
Saturday February 25, 2017 15:44:15: Event: eventIndx: 1, Handle: 214
Saturday February 25, 2017 15:44:15: Event: eventIndx: 2, Handle: 218
Saturday February 25, 2017 15:44:15: Event: eventIndx: 3, Handle: 21c
Saturday February 25, 2017 15:44:15: Event: eventIndx: 4, Handle: 220
Saturday February 25, 2017 15:44:20: cvif_IsUsh (0x0)
Saturday February 25, 2017 15:44:20: Updating ControlVault firmware from 3.4.10.0 to 4.5.13.0
Saturday February 25, 2017 15:44:20: Event: FwUpgradeStarted: 1, Handle: 214
Saturday February 25, 2017 15:44:20: Control Vault getting chip type
Saturday February 25, 2017 15:44:20: Could not determine chip type
Saturday February 25, 2017 15:44:20: Failed. Return code: 15 Set number of failed FW upgrades to 15
Saturday February 25, 2017 15:44:20: Event: FwUpgradeError: 4, Handle: 220
Saturday February 25, 2017 17:56:37: Command - FWUpgrade
Saturday February 25, 2017 17:56:37: Event: SUCCESS creating FW Upgrade events. Return code: 0
Saturday February 25, 2017 17:56:37: Event: eventIndx: 0, Handle: 1f0
Saturday February 25, 2017 17:56:37: Event: eventIndx: 1, Handle: 218
Saturday February 25, 2017 17:56:37: Event: eventIndx: 2, Handle: 21c
Saturday February 25, 2017 17:56:37: Event: eventIndx: 3, Handle: 220
Saturday February 25, 2017 17:56:37: Event: eventIndx: 4, Handle: 224
Saturday February 25, 2017 17:56:43: cvif_IsUsh (0x0)
Saturday February 25, 2017 17:56:43: Updating ControlVault firmware from 3.4.10.0 to 4.5.13.0
Saturday February 25, 2017 17:56:43: Event: FwUpgradeStarted: 1, Handle: 218
Saturday February 25, 2017 17:56:43: Control Vault getting chip type
Saturday February 25, 2017 17:56:43: Could not determine chip type
Saturday February 25, 2017 17:56:43: Failed. Return code: 15 Set number of failed FW upgrades to 16
Saturday February 25, 2017 17:56:43: Event: FwUpgradeError: 4, Handle: 224
Sunday February 26, 2017 15:15:48: Command - FWUpgrade
Sunday February 26, 2017 15:15:48: Event: SUCCESS creating FW Upgrade events. Return code: 0
Sunday February 26, 2017 15:15:48: Event: eventIndx: 0, Handle: 1dc
Sunday February 26, 2017 15:15:48: Event: eventIndx: 1, Handle: 208
Sunday February 26, 2017 15:15:48: Event: eventIndx: 2, Handle: 1c0
Sunday February 26, 2017 15:15:48: Event: eventIndx: 3, Handle: 1c4
Sunday February 26, 2017 15:15:48: Event: eventIndx: 4, Handle: 1e8
Sunday February 26, 2017 15:16:43: Command - FWUpgrade
Sunday February 26, 2017 15:16:43: Event: SUCCESS creating FW Upgrade events. Return code: 0
Sunday February 26, 2017 15:16:43: Event: eventIndx: 0, Handle: 210
Sunday February 26, 2017 15:16:43: Event: eventIndx: 1, Handle: 54
Sunday February 26, 2017 15:16:43: Event: eventIndx: 2, Handle: 48
Sunday February 26, 2017 15:16:43: Event: eventIndx: 3, Handle: 20c
Sunday February 26, 2017 15:16:43: Event: eventIndx: 4, Handle: 220
Sunday February 26, 2017 15:16:48: cvif_IsUsh (0x0)
Sunday February 26, 2017 15:16:48: Updating ControlVault firmware from 3.4.10.0 to 4.5.13.0
Sunday February 26, 2017 15:16:48: Event: FwUpgradeStarted: 1, Handle: 54
Sunday February 26, 2017 15:16:48: Control Vault getting chip type
Sunday February 26, 2017 15:16:49: Could not determine chip type
Sunday February 26, 2017 15:16:49: Failed. Return code: 15 Set number of failed FW upgrades to 17
Sunday February 26, 2017 15:16:49: Event: FwUpgradeError: 4, Handle: 220
Sunday February 26, 2017 16:48:10: Command - FWUpgrade
Sunday February 26, 2017 16:48:10: Event: SUCCESS creating FW Upgrade events. Return code: 0
Sunday February 26, 2017 16:48:10: Event: eventIndx: 0, Handle: 44
Sunday February 26, 2017 16:48:10: Event: eventIndx: 1, Handle: 1fc
Sunday February 26, 2017 16:48:10: Event: eventIndx: 2, Handle: 1f8
Sunday February 26, 2017 16:48:10: Event: eventIndx: 3, Handle: 200
Sunday February 26, 2017 16:48:10: Event: eventIndx: 4, Handle: 204
Sunday February 26, 2017 16:48:15: cvif_IsUsh (0x0)
Sunday February 26, 2017 16:48:15: Updating ControlVault firmware from 3.4.10.0 to 4.5.13.0
Sunday February 26, 2017 16:48:15: Event: FwUpgradeStarted: 1, Handle: 1fc
Sunday February 26, 2017 16:48:15: Control Vault getting chip type
Sunday February 26, 2017 16:48:16: Could not determine chip type
Sunday February 26, 2017 16:48:16: Failed. Return code: 15 Set number of failed FW upgrades to 18
Sunday February 26, 2017 16:48:16: Event: FwUpgradeError: 4, Handle: 204
robert p
4 Operator
•
9.4K Posts
0
March 1st, 2017 03:00
Hi mre6,
Thanks for posting.
Which OS are you running? Here is some information that may be helpful:
http://dell.to/2mcTtp3
mre6
3 Posts
0
March 5th, 2017 10:00
Hello, thank you for your reply
I was attempting to update the controlvault firmware in windows 10 64bit, which I now see is unsupported
So i have now reinstalled win7 pro 64bit
When I attempt to install the latest firmware it asks me for a password - which I don't recall setting, the laptop was from the outlet
I have cleared the tpm, but each time it still asks for a password
If i enter any random text for the password the update will start regardless,
but I then get the CV User Prompt "Please insert smart card", my e6440 dose not have a smart card reader
if I ignore this prompt for a minute or two i then get this:
error: controlvault admin authorization failure.
The ControlVaultAdmin Password was incorrect
Rerun the utility with the correct ControlVault Admin Password.
a search found this pdf latitude-e6230_white papers115_en-us.pdf
it states
3.1.2 ControlVault Firmware Installer Prompts for Owner Password
On older generation platforms, the Dell ControlVault Firmware installer may also prompt for an "owner
password" (prompt will be in English only).
If this prompt is displayed, enter the TPM owner password for the installation to proceed.
If the TPM owner password is not known, clear the TPM owner password
using BIOS Setup (this clears the password) and re- try the Dell ControlVault update
3.1.3 ControlVault Firmware Installed Displays Error Code 0x00000008
On older generation platforms, the ControlVault firmware installer may fail with error 0x00000008. This is a result of the current ControlVault firmware on the system being very old to allow proper communication during the update.
To resolve the issue, follow the steps below:
1.Go to dell.com/support
2.Download and install the ControlVault Driver, version 2.3.309.1625, followed by the ControlVault Firmware update package, version 23.7.009.0A.
3.After the intermediate driver and firmware are updated, you may use this Dell ControlVault Software update package to upgrade to the latest ControlVault driver and firmware.
If I try the older firmware mentioned above I don't get a password prompt, but I still get the prompt to "Please insert smart card" followed by:
error: controlvault admin authorization failure.
The ControlVaultAdmin Password was incorrect
Rerun the utility with the correct ControlVault Admin Password.
Here is the contents of the upgrade utility:
This program will update the ControlVault firmware
from 23.7.405.0 to 23.7.303.0.
Once started, do not interrupt process.
Going to stop Host Services.
Credential Vault Host Control Service ... stopped.
Credential Vault Host Storage ... stopped.
WbioSrvc ... stopped.
Going to stop Host and DCP tasks.
Checking current ControlVault status.
Found ControlVault Chip Type: 5882 B0 CustID 7
Going to update the SBI.
Going to clear SCD.
Going to reset ControlVault.
Waiting for ControlVault to come up. (~5 seconds)
Going to update the BCM. (~40 seconds)
Going to reset ControlVault.
Waiting for ControlVault to come up. (~5 seconds)
Going to update the PBA. (~5 seconds)
ERROR(00000008): Could not update the PBA.
ERROR: Could not update ControlVault firmware.
Restart the system and try again.
Do you know what the issue might be?
robert p
4 Operator
•
9.4K Posts
0
March 6th, 2017 07:00
Thanks for the information. I'll move the post over to the software forum for more experts advice.
mre6
3 Posts
0
March 9th, 2017 10:00
Hi,
Is it possible to raise this issue with the guys that write the update tools?