Solved Secure Boot update failed to update a Secure boot variable - possible after 24H2 update

Just updated to 24H2 and the computer beeps on start-up. Does not seem to cause a problem as such, but there is an error in the event log

This seems to be due to an incompatible driver. I got the message "A Driver cannot load on this device" earlier, when connecting an external hard Drive to the computer to do a backup. Don't know if this is related. The backup (Nero BackitUP) did work.
Unfortunately, I cannot identify the driver from the event viewer. Most of the information is unintelligible to a novice.
How do I find out what driver is causing this problem and rectify the problem?

Don't know if this is related to 24H2 but did not get the beep before.

Is the Secure Boot enabled in BIOS?

I believe it is. Went in to BIOS and it said
Secure Boot State User
Secure Boot Mode Custom

Not really sure what that means though as not an expert.
Don't really want to fiddle about with the BIOS without knowing what I am doing.
It still beeps on start-up but the computer seems to work correctly otherwise.
Probably end up ignoring the issue unless something goes seriously wrong.

Ok, got more information on this which is beginning to make sense. When I look through Device Manager, all the devices seemed to be ok, but when I attached an external hard drive through USB, a driver showed up with an exclamation mark - relating to my first post I think.


I guess this is the problem, but Microsoft seems to think this is the best driver. I will see if there is a newer driver on the Manufacturers Website, if I can find that. The Hard Drives are several years old now - probably about 7 to 10.
Strangely, the backup works and I can see the device in Windows Explorer and all seems OK. I wonder what driver it is using.

Not sure how to proceed now. Do I disable the device, uninstall the device ? Will that stop it working altogether?
There does not seem to be an option to just uninstall the driver.

Further update.
I believe the single beep on start-up means that all is OK.
I uninstalled the WD Driver using Device Manager, thinking that would stop the system error in the event viewer. It did not. Still get Secure Boot update failed error on start-up, which is surprising. I am pretty certain the error is down to that device though. Does not seem to need a driver.

Secure Boot Custom mode is a feature that allows a user to modify the UEFI database and add or delete Secure Boot keys. This mode is useful when using an "out-of-box driver" and requires the user to add their own keys to the Secure Boot database.

When you click Secure Boot from BIOS what options it shows?

OK, thanks for your replies FreeBooter. Think I have now resolved the issue without fiddling in the BIOS.
I went into Windows Update, Advanced Options and looked at optional drivers available. There was one for WD devices, which I installed.
Now the exclamation mark has gone from the Device Manager and the Driver seems to be ok. Restarting the computer was successful without the Secure Update Boot error message in Event Viewer.
I am going to assume that has fixed the problem.

Would have been nice if this had been part of the automatic update process. Would have saved a lot of time and trouble!

Oops,

Spoke too soon. Still getting the Secure Update Boot error message - came three minutes after start-up.
No I idea if I should bother about this.
The options for Secure Boot Mode were Custom or Standard, by the way.

OK, further news. Looked at Secure Boot State using msinfo32 and it said it was Off.
Had another look in the BIOS at Secure Boot Settings after doing a bit of research. They did not look right, so I changed them to Windows UEIF and Standard from Other and Custom. The computer restarted OK and msinfo32 showed Secure Boot State as ON.
Also, the Event Viewer did not show any Secure Boot error messages, so it looks good.

What I now need to find out is if the BIOS settings were incorrect when I bought the machine - two weeks ago, or whether having an incompatible WD Driver forced the BIOS to change settings to allow the computer to boot. Am getting back to the manufacturer about that.

I'm glad to know you have resolved the problem.