UEFI corruption with HP 17-cp1035cl, F.10 Rev.A firmware

[Mr_Magoo2]

I'd upgraded the UEFI firmware from F.9 Rev.A to F.10 Rev.A recently on my HP 17-cp1035cl laptop in hopes that the USB-C port on the left side of the machine would finally start working (Zorin OS 16.3 Linux recognizes it, but the USB port refuses to accept any resource assignment, so it never powers on).

The new firmware isn't stable... I noticed that the machine sometimes hangs upon reboot, which required that I unplug all the USB devices and just keep trying to reboot until it worked again... it wouldn't pop up any errors or anything, it was just a black screen right as the machine powered on (either cold or warm boot)...

... well, it finally did it in such a way that I figured out what was happening... it just wouldn't reboot No Matter What, so I investigated further... the UEFI had become corrupted. I ended up removing the battery to force it to reset the UEFI to defaults.

After the battery was removed and the machine was powered on, it popped up a dialog box that the UEFI had been corrupted, it sat at that dialog box for a bit, then it rebooted and went into the BIOS settings screen (everything was at defaults), where I could reset everything back the way it's supposed to be.

Just so your UEFI firmware programmers know, there's something screwy with F.10 Rev.A.

* HP 17-cp1035cl laptop

* 64 GB RAM, 3200 MHz

* 500 GB, 7200 RPM, 128 MB cache, internal drive (one drive)

* 500 GB, 7200 RPM, 128 MB cache, external drives (two drives), one drive on each USB port

* Zorin OS Core 16.3 Linux

* ZFS file system

* bpool and rpool on three mirrored drives, giving 820 MB/s maximum data throughput

I will note, however, that under F.10 Rev.A, the battery management from the UEFI kicked in and held the battery at 87% SOC for days, even across warm and cold boots... F.9 Rev.A never did that. So that's progress. Now if it worked reliably, that'd be great. Unplug and replug the power and it'll charge up to 100% and stay there (the UEFI corrupted before it got a chance to lower battery SOC again, so I'm not sure what triggered it to start working in the first place, but it'd be great if it kept battery charge at 87% reliably, even after unplugging and plugging the power).