Dell Update or Support with Windows Reliability Viewer W11. XPS8940 problem?

Question

BIOS update, is it Dell or MS???

I've got the Nvidia/BIOS 2.4.0 problem.

I've manually installed BIOS 2.3.0 and running fine? However a few times each day for the past few days, my system has been somewhat unresponsive for a short period of time? Usually I'll notice this if using a browser or opening or closing windows. The browser didn't respond to clicks on a link and icons and opened windows did not open or close. Then for the rest of the day, no problems as it clears rather fast and everything works.

Well, today I looked at my Reliability Viewer (hope this screen captures appear soon):

6/2

The BT error I know is caused by disconnecting my phone from Dell Mobile Connect, doesn't bother me.

6/3

6/4

OK, the USBIEUpdate, from prior threads it appears to be Dell has the wrong date in the file... and since it tried quite often, it was probably 'eating the CPU' which I did see in Task Manager as 100% for System Services but couldn't find out 'who'.

It is the LAST one that bothers me more...

The BIOS UPDATE!!!!

It had been sitting in Windows Update as an OPTIONAL UPDATE! I just left t there.

Now yesterday I guess DELL diid me in!!!

How, I decided to check via the SUPPORT page for my 8940 under my correct Service Tag, if I had any new files.

It came back I had TWO, a Killer update and the BIOS 2.6.0 update...

I did UNCHECK the BIOS and then started the Install. That kicked of Dell Update I recall and I did SEE the Killer Install. Never saw the BIOS install... but I was told I needed to reboot to complete the install which I did. Never saw a BIOS install happen?

Ran SYSINFO, it was NOT it seems, BIOS Version/Date Dell Inc. 2.3.0, 10/7/2021???

So I went back to the Support page and had it check for updates.... and it basically reached 100% and stopped there? Opened Support Assist, and it shows the BIOS was available today, but somehow that never got back to browser Support page.

But this is what Support Assist shows:

So why wasn't the Killer file shown? Why did RM think the BIOS was updated?

Hmm, I reloaded the Support web page and it shows the same as Support Assist, the BIOS file is available?

However, now on WU Optional drivers, BIOS 2.6.0 is GONE!!!

The PC was rebooted yesterday after the Killer s/w was installed, no sign of a BIOS being installed, and again this morning?

I'm going to reboot now, and if I see the BIOS being installed, I'll post it. I would NOT expect it to be though?

I wonder where RM really gets it data and could there have been a Registry entry made by Support Assist or Dell Update with BIOS 2.6.0 that RM read?

ispalten · Answer

OK, BOOT did not show BIOS update in progress and entered into the BIOS and it is STILL V2.3.0?

Searched the Registry for BIOSVersion:

All entries show 2.3.0 and updated to today as I entered and closed the BIOS.

So where is RM getting the data?

tolduso · Answer

Check Device Manager and look under firmware to see which version it says. It maybe just updated that.

ispalten · Answer

RIGHT ON!!!

Does indeed show in Device Manager...

Here is the Status:

==============

Currently, this hardware device is not connected to the computer. (Code 45)

To fix this problem, reconnect this hardware device to the computer.

----------

So how is 'broke' and why? I 'assume' that a later BIOS when I load it will fix DM though?

Insane that this should happen but 'who' really did it? Odds on I suspect Support Assist who found both the Killer and BIOS update. I UNCHECKED the BIOS update, and it appears it DID NOT install it, but I 'bet' it made the prerequisite change for it and then would have installed it but I told it not to... BUG!!!

ispalten · Answer

Wait, I now recall that was always there, I never deleted the EXE from the PC so I could re-install it at any time if I needed to. False alarm.

RoHe · Answer

Those 8 errors in a row you see in Reliability Monitor are the bug in latest SupportAssist update which was released at end of May. It's causing exact same errors on many different PC models, running Win 10 or Win 11. Long thread about this over in the Inspiron forum. You'll see 8 of them in a row every time SupportAssist launches itself automatically (or when user manually launches it) to look for updates.

Simplest work-around is to disable Dell SupportAssist and Dell SupportAssist Remediation Service in services.msc while Dell works on an update to fix this.

Click Start>Run>type in: services.msc and click OK. When it opens, scroll down to those entries on the list. Double-click each one and change its Startup type to Disabled. Do not change anything else in services.msc. Just close services.msc and reboot. The errors will stop...

No ETA -so far- for release of a new version of SupportAssist that fixes the bug...

tolduso · Answer

I have a XPS8930 . When windows updated my DM to 0.1.1.18 I already had the bios at 1.1.18. So yeah probably a update to the actual bios will fix that error in DM? Not really sure on that though.

RoHe · Answer

What am I missing here?

When you manually check for updates using your Service Tag, the support page does not look to see what's already installed on the PC. It only shows what updates are available. Since you unchecked the BIOS 2.6.0 update, it wasn't downloaded and installed. That's why you're still on 2.3.0. If 2.6.0 is listed in Device Manager, right-click it and delete it.

I told you in another thread the latest "optional" BIOS update (0.)1.1.23 offered by WU for my XPS 8930 disappeared from WU's optional update list. There's no evidence WU tried to install it. I already had that same version installed and Capsule Updates is disabled. This BIOS update isn't listed as having been installed in the WU History.

I also had BIOS (0.)1.1.18 force-installed on my XPS 8930 by WU, and the WU History logged it as having been successfully installed, even though Capsule Updates was disabled back then too. No telling how that happened, but since that one forced update, WU has offered several optional BIOS updates for this PC model, but none has been force-installed here and none listed in the WU History.

ispalten · Answer

@RoHe

The USB problem is a minor annoyance. Small 'busy' time on the system and I'd not normally notice it.

I'm more concerned about BIOS 2.6.0 and RM thinks it was Installed by WU and it is not longer in my Options WU area? Even with Capsule Update blocked, it happened. Seems it is a false situation though as I'm still on 2.3.0, but if it could be installed or even thought to be installed, that is a problem.

ispalten · Answer

@RoHe

Ron, What you are missing are these points:

Capsule Update is disabled.
Reliability Viewer shows BIOS 2.6.0 has been installed by WU on 6/4
BIOS 2.6.0 no longer appears in Windows Update at all, not even where it was before, as an Optional Update.
Dell Support site runs Dell Support Assist and still thinks I need BIOS 2.6.0, only available d/l found.
Dell Web Site Support drivers page supposedly has installed the Killer S/w, but it doesn't show as installed in RM, nor in Revo Uninstaller or Control Panel as installed? I did SEE it install and a REBOOT was needed to complete install which was done. I did install the latest Killer S/W from the Intel Site on 5/30 though and it shows for that date, not 6/4 when I installed it via the Dell site.

That is the root problem(s).

Something went wrong using the Dell Support Web site to update Killer and reject the BIOS change. RM seems to have the wrong entry, and WU doesn't see that Optional BIOS is needed. BIOS is still 2.3.0, and right now, the Support Page still sees I 'need' 2.6.0, but also I am up to date on the Killer s/w?

RoHe · Answer

Maybe WU attempted to install 2.6.0 and but Capsule Updates was disabled so that failed, but Reliability Monitor didn't notice it failed...

As long as you still have 2.3.0 running, I wouldn't worry about it.

ispalten · Answer

@RoHe

Ron, not worried about it as much as I am 'documenting' a failure.

On the web support driver page, after Support Assist ran, it showed 2 updates, first the BIOS and then the Killer file. I unchecked the BIOS.

Here is where it gets 'murky', who did to who and who didn't?

I'll assume first since neither REVO Uninstaller to the Control Panel Program list sees the Killer s/w installed, it is QUITE possible that Support Assist or Dell Update installed Killer but was passed the application name for the unchecked BIOS. That would explain why RM thought it was installed and not Killer. OK, if you think that is probably it, then where ever that data is on the PC, WU was able to see that the BIOS was installed and then REMOVED it from the OPTIONAL UPDATES.....

However, in RM if I look at the DETAILS for 2.6.0, I see this:

RM thinks WU installed it?

As for Killer s/w, if I go here, https://www.intel.com/content/www/us/en/support/intel-driver-support-assistant.html I see this:

=====================

Killer® Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW)

Driver DetailsUp to date
ProviderIntel
Version22.130.0.5
Date3/15/2022

Device Details
ManufacturerIntel Corporation
AvailabilityRunning at full power
StatusThis device is working properly.
InstalledTrue
MAC AddressB0:A4:60:71:CB:40
Service NameNetwtw10
Device IdPCI\VEN_8086&DEV_06F0&SUBSYS_16521A56&REV_00\3&11583659&0&A3
Revision00

===================

Which matches what I see in Device Manager...

OK, but the file in the Dell Support page for my specific XPS has this as the version for the Killer s/w, 22.130.0.2, A35.

What I have installed is NEWER!!! So I bet it was NOT installed.

All well and good.

I did see the install go through, no error and got a reboot required popup which I did.... didn't see any files being updated on the reboot.

What I think transpired and was a collection of errors:

When I unchecked the FIRST update on the support page, either the Support page, Support Assist, or Dell Update kept that first file name of the BIOS 2.6.0.
Since only one update was to be installed, it used that name (the 'bug' I guess).
Once the single file (Killer s/w) was d/l'ed it started the install, which I did see.
I would 'think' if it produced an error as essentially it was trying to back-level the s/w, 'someone' should have reported that back and either said it was ending or ask me if I wanted to do that? Another possible bug, but not sure who?
Once the Killer file finished (and it seems did NOT install any s/w) since Dell Support Assist or Update knew it did, and had the FLAG that a reboot was required (would have been for the BIOS file) and posted that (semi-bug if it is due to it thinking it was installing the BIOS which does require a reboot).
Lastly, how does WU know (or think) BIOS 2.6.0 is installed and then removes it from Optional Updates (has to be somewhere on the PC or possibly Dell Update removed it?).
RM thinks the BIOS was installed by WU which I'm pretty sure is wrong too.

Is it 'possible' (and I doubt it though) that Dell Update uses WU to install files? Might explain all this I guess? WU was 'asked' by Dell Update to install the BIOS, but it was blocked by Capsule Update, so it never was, but some data was created so RM then knew it was done by WU?

Anyway, you are correct, I am on 2.3.0 and I'm not worried about it. Wish I had a 'good' way to report this to Dell (if they cared)?

RoHe · Answer

I doubt when using Dell Update it gets WU to install anything. It probably all comes from Dell's servers. And whether or not it asked to reboot doesn't say anything about a BIOS update being run. Lots of routine driver updates require a reboot to complete the installation.

Don't know why your BIOS update disappeared from WU, but mine did too so maybe after a certain time limit WU stops offering these "optional" updates. That info is above my pay grade around here.

You could always do a System Restore and revert back to before RM said the BIOS update was installed. That will likely remove the Killer update, but you can just install it again. But do it manually, not using SupportAssist/Dell Update.

To be honest, don't know why you want any of that Killer stuff. Aside from the driver, IMO, it's useless. I have Killer Ethernet on my PC and I've disable all Killer and xTend services in services.msc and my Ethernet works perfectly, and all that extra stuff isn't using any CPU and RAM time.

ispalten · Answer

I don't think the BIOS update was run at all, just the info passed to Dell Update made it think it got the BIOS one when in reality it was the Killer file.

This is above my pay grade too, and I don't have access to what I'd probably need to figure this out. I have no interest in rolling my system back and trying to see what happens either.

I'm not seeing any performance hit with the Killer s/w and I occasionally look at its control center...

RoHe · Answer

Just do a System Restore and go back in time before this mess happened....

XPS Desktops

Dell Update or Support with Windows Reliability Viewer W11. XPS8940 problem?

Killer® Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW)

Was this post helpful?