BIOS and Firmware Update Issue

A.KH · Feb 28, 2025

Guys, Thank you for helping always
I have problem with couple machine when try to run BIOS update give this error linked to dbutil_2_3.sys driver.

the Error Message as the attach pic

Help how to fix it or bypass.

I had tried with these steps,
stop endpoint security
stop the firewall
run tool from dell to remove the driver if already installed

but nothing works

A.KH · Feb 28, 2025

The machine is Dell OptiPlex 390 Core i5 Mini Tower,

antspants · Feb 28, 2025

Temporarily disable driver checks. May fix it?:

Press Windows key + X and select "Command Prompt (Admin)".
Type (or click this command to copy for pasting): bcdedit /set loadoptions DISABLE_INTEGRITY_CHECKS and press Enter.
Restart your computer to temporarily bypass driver signature enforcement.
Important: Remember to re-enable driver signature enforcement after installing the driver by typing (or click this command to copy for pasting) bcdedit /set loadoptions ENABLE_INTEGRITY_CHECKS.
Restart your computer to re-enable driver signature enforcement

pseymour · Feb 28, 2025

This is a vulnerable driver from a few years ago. You should be using more recent versions of Dell utiliities.

DSA-2021-088: Dell Client Platform Security Update for an Insufficient Access Control Vulnerability in the Dell dbutil Driver | Dell US

Edit: Oh, I see... the 390 is ancient. No wonder I didn't know what it was.
Edit Again: If you're using a BIOS flash .exe, you might try putting the BIOS flash .exe on a USB drive and updating from the BIOS interface itself. Not sure if the 390 had this option like models from this decade.

bobkn · Feb 28, 2025

Just to be clear: you've downloaded the BIOS update? Support for OptiPlex 390 | Drivers & Downloads | Dell US

The download is O390-A14.exe. If it's like Dell BIOS updates I used to see, when you run it, it'll reboot the PC and finish the update outside of Windows.

pseymour · Feb 28, 2025

Yep, that's true @bobkn, but it's from 2018, before the vulnerable driver was revoked. If running it inside Windows, it may be trying to load that driver, and Windows is complaining.

Berton · Feb 28, 2025

Just a note, I have the Dell Support Assist program on my Windows machines, 7, 10, 11, and no issues with the updates it does for me.

bobkn · Feb 28, 2025

pseymour said:
Yep, that's true @bobkn, but it's from 2018, before the vulnerable driver was revoked. If running it inside Windows, it may be trying to load that driver, and Windows is complaining.

I have no idea about that.

The .exe is not an archive that can be opened with 7Zip.

antspants · Mar 1, 2025

Berton said:
Just a note, I have the Dell Support Assist program on my Windows machines, 7, 10, 11, and no issues with the updates it does for me.

The Dell Optiplex 390 core i5 was released in 2011. To be honest, I am surprised Eleven even runs on it. Ten did so obviously it’s OK?

You can buy a new Optiplex 390 i5 in Australia (also surprising) for AU$150 which is probably equivalent to 1 buck fiddy in US$

Just try post number 2 above, it should work.

Berton · Mar 1, 2025

I have an Optiplex 3020 SFF with Win10, no issues.

A.KH · Mar 3, 2025

Guys the problem is I need to update all the environment, not just one PC or two. and I can't stop by each station to boot from USB.

pseymour · Mar 3, 2025

You said, "I have problem with couple machine..."

A.KH · Mar 3, 2025

pseymour said:
You said, "I have problem with couple machine..."

yeah But not one

PerpetualCycle · Mar 3, 2025

I maybe should not mention thiss, ut if you have confidence that the .exe is from DELL, you could temporarily disable the Vulnerable Driver Blocklist. This comes with a risk. The reason the driver is on the vulnerable list is that hackers have exploited it in the past. It either has a vulnerability or hacked versions were posted somewhere. You can disable the list from the security panel -> Device Security -> Core Isolation -> Microsoft Vulnerable Driver Blocklist. At your own risk though, and make sure it is temporary because it opens up all the vulnerable drivers on the list.

A.KH · Mar 3, 2025

antspants said:
Temporarily disable driver checks. May fix it?:

Press Windows key + X and select "Command Prompt (Admin)".

Type (or click this command to copy for pasting): bcdedit /set loadoptions DISABLE_INTEGRITY_CHECKS and press Enter.

Restart your computer to temporarily bypass driver signature enforcement.

Important: Remember to re-enable driver signature enforcement after installing the driver by typing (or click this command to copy for pasting) bcdedit /set loadoptions ENABLE_INTEGRITY_CHECKS.

Restart your computer to re-enable driver signature enforcement

This one does not work, after running the command and the result successfully, and reboot the machine to re install the BIOS update, the same message show up again

A.KH · Mar 3, 2025

PerpetualCycle said:
I maybe should not mention thiss, ut if you have confidence that the .exe is from DELL, you could temporarily disable the Vulnerable Driver Blocklist. This comes with a risk. The reason the driver is on the vulnerable list is that hackers have exploited it in the past. It either has a vulnerability or hacked versions were posted somewhere. You can disable the list from the security panel -> Device Security -> Core Isolation -> Microsoft Vulnerable Driver Blocklist. At your own risk though, and make sure it is temporary because it opens up all the vulnerable drivers on the list.

do you have the steps for this method or just i can find the driver in Core Isolation ?

A.KH · Mar 3, 2025

PerpetualCycle said:
I maybe should not mention thiss, ut if you have confidence that the .exe is from DELL, you could temporarily disable the Vulnerable Driver Blocklist. This comes with a risk. The reason the driver is on the vulnerable list is that hackers have exploited it in the past. It either has a vulnerability or hacked versions were posted somewhere. You can disable the list from the security panel -> Device Security -> Core Isolation -> Microsoft Vulnerable Driver Blocklist. At your own risk though, and make sure it is temporary because it opens up all the vulnerable drivers on the list.

I think when disable all the device security such as integrity and blocklist, will work fine
I try now and I see its work fine

BIOS and Firmware Update Issue

Member

Attachments

My Computer

Member

My Computer

Like a rolling drone.

My Computers

enjoying a tall glass of Tang

My Computer

Well-known member

My Computers

enjoying a tall glass of Tang

My Computer

Ret. ATC

My Computers

Well-known member

My Computers

Like a rolling drone.

My Computers

Ret. ATC

My Computers

Member

My Computer

enjoying a tall glass of Tang

My Computer

Member

My Computer

Syzygy

My Computers

Member

My Computer

Member

My Computer

Member

My Computer

Similar threads