Start a Conversation

Unsolved

D

1 Message

595

February 25th, 2022 19:00

Just FYI, SA fails to install drivers

Firstly, having read a bunch of posts, I see that SA (SupportAssist) is a unattended train wreck. That said, this is just FYI for anyone with an Aurora R12. SupportAssist pushed two updates, BIOS and a wifi driver update. Neither worked. Manual BIOS update worked, but was scary--asked for reboot, didn't come back, powerbutton force off rendered machine unable to boot, powering off for 60 seconds seemed to restore ability to boot

Secondly, the driver QCA61x4A-QCA9377-Wi-Fi-and-Bluetooth-Driver_2K5GJ_WIN_11.0.0.779_A11_01 install just locked up with support assist. With manual installation, at least there was an error log that revealed that the R12 isn't a supported system. 

Too bad I can't get my hour with tech support and troubleshooting back.

 

[Fri Feb 25 22:22:44 2022] Update Package Execution Started
[Fri Feb 25 22:22:44 2022] Original command line: "C:\Users\daver\Downloads\Qualcomm-QCA61x4A-QCA9377-Wi-Fi-and-Bluetooth-Driver_2K5GJ_WIN_11.0.0.779_A11_01.EXE"
[Fri Feb 25 22:22:44 2022] DUP Framework EXE Version: 4.4.5.44
[Fri Feb 25 22:22:44 2022] DUP Release: 2K5GJA11
[Fri Feb 25 22:22:44 2022] Initializing framework...
[Fri Feb 25 22:22:44 2022] Data in smbios table is (hex)value = 3 , Chasis type (hex)value = 3 , System type is : Client
[Fri Feb 25 22:22:45 2022] logo.png
[Fri Feb 25 22:22:48 2022] User Command: attended
[Fri Feb 25 22:22:48 2022] DUP Capabilities Value: 35651583 (0x21FFFFF)
[Fri Feb 25 22:22:48 2022] DUP Vendor Software Version: 11.0.0.779
[Fri Feb 25 22:22:48 2022] Local System/Model Compatible with this Package? Yes
[Fri Feb 25 22:22:48 2022] Local System OS Version: 10.0.0.0
[Fri Feb 25 22:22:48 2022] OS Compatible with this Package? Unknown
[Fri Feb 25 22:22:48 2022] Local System OS Language: Unknown
[Fri Feb 25 22:22:48 2022] Language Compatible with this Package? Unknown
[Fri Feb 25 22:22:48 2022] Identified Behavior : attended
[Fri Feb 25 22:22:48 2022] Extraction-miniunz path: c:\PROGRA~3\dell\drivers\C53CD3~1\miniunz.exe
[Fri Feb 25 22:22:48 2022] Extraction-arguments: -x C:\Users\daver\DOWNLO~1\QUALCO~1.EXE -o -d c:\PROGRA~3\dell\drivers\C53CD3~1
[Fri Feb 25 22:22:49 2022] Extraction-GetExitCode: 0
[Fri Feb 25 22:22:49 2022] Temporary payload log file name: C:\ProgramData\dell\drivers\c53cd3e7-e6f9-472e-8112-b28c58a7ff02\DUP7B0E.tmp
[Fri Feb 25 22:22:49 2022] payloadExe: Setup_MUP.exe
[Fri Feb 25 22:22:49 2022] payloadArgs: /LOG"C:\ProgramData\dell\drivers\c53cd3e7-e6f9-472e-8112-b28c58a7ff02\DUP7B0E.tmp"
[Fri Feb 25 22:22:49 2022] payloadDir: C:\ProgramData\dell\drivers\c53cd3e7-e6f9-472e-8112-b28c58a7ff02
[Fri Feb 25 22:22:49 2022] MUP Spec version is less than 3 or Not a DCH Package.
[Fri Feb 25 22:22:49 2022] Legacy installation is selected. Calling Vendor Installer...
[Fri Feb 25 22:22:50 2022] Appending Vendor Software Log.
[Fri Feb 25 22:22:50 2022]
--- Start of Vendor Software Log ---

[Fri Feb 25 22:22:50 2022] ASCII payload log file detected:
[Fri Feb 25 22:22:50 2022] Log File Name: DUP7B0E.tmp
[Fri Feb 25 22:22:50 2022] [2022-2-25 22:22:50] Setup start up.
[2022-2-25 22:22:50] CommandLine is:[/LOG"C:\ProgramData\dell\drivers\c53cd3e7-e6f9-472e-8112-b28c58a7ff02\DUP7B0E.tmp"]
[2022-2-25 22:22:50] The current system isn`t supported.
[2022-2-25 22:22:50] Setup end.(1150)

[Fri Feb 25 22:22:50 2022]
--- End of Vendor Software Log ---

[Fri Feb 25 22:22:50 2022] Vendor Software Return Code: 1150
[Fri Feb 25 22:22:50 2022] logo.png
[Fri Feb 25 22:22:50 2022] Name of Exit Code: ERROR
[Fri Feb 25 22:22:50 2022] Exit Code set to: 1 (0x1)
[Fri Feb 25 22:22:50 2022] Result: FAILURE
[Fri Feb 25 22:22:53 2022] Open file: C:\ProgramData\Dell\UpdatePackage\Log\Qualcomm-QCA61x4A-QCA9377-Wi-Fi-and-Bluetooth-Driver_2K5GJ_WIN_11.0.0.779_A11_01.txt

 

8 Wizard

 • 

17K Posts

February 25th, 2022 22:00


@dr_adams wrote:

1. I see that support assist is a unattended train wreck.

2. Manual BIOS update worked, but was scary--asked for reboot, didn't come back, powerbutton force off rendered machine unable to boot, powering off for 60 seconds seemed to restore ability to boot

 


Thanks for the report.

 

1. Yeah, pretty much. I uninstalled it from my Aurora-R6 long ago.

I get everything I need from Windows-Update and Nvidia.com . 

I'll get (and apply) my own BIOS updates from Dell.com (if having a specific problem) on MY schedule.

https://www.dell.com/community/Alienware-Desktops/My-Aurora-R6-The-Adventure-Continues/m-p/6095405/highlight/true#M3971

2. Interesting. As you know (what should happen) is it write the file to special queue in the UEFI Partition. On next boot, it should see it and apply it (just after Post) while still in UEFI-Environment. It helps to watch what is actually happening with the various sub-firmwares, and what it says at the very-end.

Yes, it might shut-down when done. You simply turn it back on. There should not be any error-code light-flashings. After one successful boot (and a look with msinfo32), I usually shut-down, reboot, and quickly F12 to go view BIOS options.

On many machines, BIOS updates are downloading/installing from Windows-Update now-days.

 

No Events found!

Top