Recent content by krzemien

@garlin, your 'Update-UEFI.bat' - dated 21/12/25 - in the latest ZIP file (downloaded it just now) incorrectly refers to Update_UEFI-CA2023.ps rather than Update_UEFI-CA2023.ps1. Small error, but rather important one for those uninitiated.

I did use the previous version of your script unfortunately, and only downloaded latter (latest) version once I moved these files manually myself. Will keep an eye on this 1796 event as I'm just not keen in seeing it...

Was supposed to chime in quite earlier - few weeks' back - but always had to postpone due to some other pending tasks. First of all: Many thanks for your good job, @garlin. Cut the long story short: was using others' (notably: GitHub - cjee21/Check-UEFISecureBootVariables: PowerShell scripts...

...and on the next day, upon launching: Update check now also works:

Ditto...

It is, but when one downloads it, one gets previous version:

Hmm? Download link gets me the previous version, has it been pulled for some reason?

Many thanks for all above, and also others's contributors input. Just executed the above commands on my partially (in Secure Boot sense) patched Windows 11 PC - driven by annoying 1796 errors in Event Log that started appearing once I deployed October CU - with the expected (I hope!) results...

Same here.

Same here. Thanks for this, thought it was a one-off when I tried to get onto BIOS from OS rather than via F10 keys when booting. The other thing worth adding is that I started seeing this after each restart: For some reason AvailableUpdates key value under...

Just gave it a go out of interest and am moved to 25H2 (Version 10.0.26200.6584). With the exception of post-restart installation of KB5066613 (and another restart...), it was rather uneventful, I must add...

Same here, also with another error message popping up (0x8007139f). This was after other components in the CU (namely: NET updates) were deployed and PC restarted in no time. Needless to say, download suddenly started trickling in, and update installation followed. And am up to date. Please...

All good and truly appreciate the effort, but I got this PC only mid-May and frankly speaking this was the first CU that got deployed on top of the usual 22H2/22H3/22H4 staged migrations that were taking place since original factory image from HP recovery media was used.

Decided to bite potential bullet and just installed it today - all good and rather smooth, although a wee lengthy (>30 minutes?).

It got invariably installed on my afresh PC straight from greenfield HP Recovery state and past upgrade to 22H2 and migration to 23H2 on its way, and on the same day - as it's all been happening in a jiffy. Nothing to report really (early days - or hours even), no problems and side-efffects...