Unsolved

1 Rookie

 • 

2 Posts

380

September 16th, 2023 12:17

XPS 17 7930, failed Windows Update firmware install

XPS 17 9730

XPS 17 9730

New XPS 7930, after first boot up used SupportAssist to update software before running Windows update. Support assist installed Dell Firmware 1.5.0 update. Windows update tried to update to that 1.5.0 firmware as well and failed. 

After some research in the Windows update found that the UEFI hardware id in the Windows update did not match the XPS 7930 UEFI id, causing the Windows Update of its version of the firmware to fail. The pingback line in the log shows the error cause.  Windows Update continues to attempt to install the firmware update and fails every time it runs, resetting the Windows Update Software Distribution folder does not stop the failed install attempts. I disabled Capsule UEFI updates in the firmware just in case after the error appeared.

Excerpt from the WIndows Update log with the error

2023/09/07 18:19:14.9642039 18500 21352 Deployment      Deployment job Id 48A3A559-D38E-4FE6-8623-045FC15B564C : Update 144d2b0b-2ff2-4148-815a-e75dd7bc72fe.1, Top-level update 144d2b0b-2ff2-4148-815a-e75dd7bc72fe.1 deployment data prepared successfully.
2023/09/07 18:19:14.9644367 18500 21352 Deployment      *FAILED* [80004001] file = D:\a\_work\1\s\src\Client\UpdateDeployment\Lib\UpdateDeploymentJob.cpp, line = 3110
2023/09/07 18:19:14.9649086 14360 23396 Handler         * START *   Driver Install
2023/09/07 18:19:14.9649102 14360 23396 Handler         Updates to install = 1
2023/09/07 18:19:14.9649979 14360 23396 Test            AUTest.cab validation: Test keys are not allowed
2023/09/07 18:19:14.9655331 18500 20760 Agent           Deploy call 756F5494-6BF0-41C1-B189-455D3E4DA47E : NotifyClient (20760)(0) called with Deployment callback code = Update progress, reboot status = unspecified
2023/09/07 18:19:14.9655742 18500 20760 Agent           Deploy call 756F5494-6BF0-41C1-B189-455D3E4DA47E : Callback to client with code Update progress and error 0 
2023/09/07 18:19:14.9664282 14360 23396 Handler         CUHDriverHandler: No optional CompatibleProvider
2023/09/07 18:19:15.2485197 14360 23396 Handler         *FAILED* [80070002] file = D:\a\_work\1\s\src\Client\lib\wusyshelper\wusyshelper.cpp, line = 751
2023/09/07 18:19:15.2485260 14360 23396 Handler         *FAILED* [80070002] file = D:\a\_work\1\s\src\Client\Engine\handler\wuuhdrv\lib\drvinst.cpp, line = 1277
2023/09/07 18:19:15.2485415 14360 23396 Driver          *FAILED* [80070002] Error Installing PnP Driver uefi\res_{09619916-52a7-467e-844d-8f8be0ef2b08}
2023/09/07 18:19:15.2722055 14360 23396 Handler         Device id = uefi\res_{09619916-52a7-467e-844d-8f8be0ef2b08} 
2023/09/07 18:19:15.2722088 14360 23396 Handler         DriverPingback=1|1|UEFI\RES_{09619916-52a7-467e-844d-8f8be0ef2b08}&REV_10500|2023-05-31|0.1.3.2|0xff0001|0|0|Dell, Inc.|Dell, Inc.|System Firmware 1.3.2|UEFI\RES_{09619916-52a7-467e-844d-8f8be0ef2b08}
2023/09/07 18:19:15.2722203 14360 23396 Handler         *FAILED* [80070002] Driver Install of {144D2B0B-2FF2-4148-815A-E75DD7BC72FE} on uefi\res_{09619916-52a7-467e-844d-8f8be0ef2b08} (mapping to error 8024200B)
2023/09/07 18:19:15.2723810 18500 24284 Deployment      Deployment job Id 48A3A559-D38E-4FE6-8623-045FC15B564C : Update 144d2b0b-2ff2-4148-815a-e75dd7bc72fe.1 failure delegate invoked.
2023/09/07 18:19:15.2724524 14360 23396 Handler         Exit code = 0x8024200B
2023/09/07 18:19:15.2724538 14360 23396 Handler         * END *   Driver Install

1 Rookie

 • 

2 Posts

September 20th, 2023 00:36

Figured out the problem I believe. Support Assist tried and failed to update the firmware to 1.6.0.  I downloaded the update and ran it manually and got prompted for the BIOS admin password. There's a Dell technote saying you have to install manually if you've set the BIOS admin password. That's probably why Windows Update failed to install the 1.5.0 update.

Both Windows Update and SupportAssist still try to update the firmware after I update to 1.6.0, they don't recognize it is already installed.

1 Rookie

 • 

1 Message

September 24th, 2023 13:53

Same problem. Downgrading to 1.5.0 or 1.3.1 do not solve the problem; the system does not automatically upgrade back.

No Events found!

Top