I've given it to you twice. Please follow post #1310Hello, what command line should I use to update Windows Bootmgr SVN from 7.0 to 8.1? Thank you for your help.
Regards
My Computer
At a glance
Windows 7
- OS
- Windows 7
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
I've given it to you twice. Please follow post #1310Hello, what command line should I use to update Windows Bootmgr SVN from 7.0 to 8.1? Thank you for your help.
Regards
Get-Partition: C:\Users\RYSZARD\Desktop\ksas\Check_UEFI-CA2023.ps1:1447
Line |
1447 | $GUID = (Get-Partition -DiskNumber $SystemDisk | Where-Object { $ …
| ~~~~~~~~~~~
| Cannot validate argument on parameter 'DiskNumber'. The argument is null. Provide a valid value for the
| argument, and then try running the command again.
Get-Volume_DevicePath: C:\Users\RYSZARD\Desktop\ksas\Check_UEFI-CA2023.ps1:1449
Line |
1449 | $EFI_Path = '{0}EFI' -f (Get-Volume_DevicePath $GUID)
| ~~~~~
| Cannot bind argument to parameter 'VolumeGUID' because it is an empty string.
Get-Disk | Where-Object {$_.IsSystem -eq $true}
Starting from April 2025, W10 or W11 Monthly Updates will push changes to C:\Windows\System32\SecureBootUpdates.Regarding SkuSiPolicy.p7b policy, what is the Microsoft source for its update? I used this page to apply the policy on a computer, and the last update to this page is December 17, 2025:
OK, thanks, I'll probably use your script to update it.Starting from April 2025, W10 or W11 Monthly Updates will push changes to C:\Windows\System32\SecureBootUpdates.
This may include new versions of the DBXupdate.bin, DBXUpdateSVN.bin and SkuSiPolicy.p7b files.
Prior to Secure Boot getting more attention, SkuSiPolicy.p7b was updated once a year when a new Windows was released in October. Now, it's refreshed every time a new security fix is added to the boot manager file. There doesn't appear to be explicit messaging from MS when the policy file changes, so we need to periodically compare the reference copy from SecureBootUpdates.
If you don't bother updating your Windows, your SkuSiPolicy.p7b might be woefully out of date. There isn't a single reference page like for Defender which lists the latest policy version number. SkuSiPolicy.p7b is a signed, binary encoded version of a XML policy file. Without a special function to decode the contents, you can't know what version you have unless someone publishes the file size or checksum.
I'm using a shortened Get-CIPolicyParser function from Matthew Graeber to extract the version number.
This part is unclear. Setting AvailableUpdates = 0x20 will force the Secure Boot update task to refresh SkuSiPolicy.p7b.If I don't use your script and I update Windows, SkuSiPolicy.p7b will be updated, right?
Yeah, if Microsoft updates it automatically.This part is unclear. Setting AvailableUpdates = 0x20 will force the Secure Boot update task to refresh SkuSiPolicy.p7b.
Now is that something you're supposed to do, or should Windows do this for you? I get the feeling that it's a future goal to have the Secure Boot task silently take care of this after a recent update. MS has all of the puzzle pieces, but they might not be ready to turn on automatic updates.
For now, it wouldn't hurt to run the check script after Patch Tuesday's just to confirm there wasn't a recent change.
I've noticed a problem with the April 2026 version of the files. Run these commands instead of the update script.
Code:reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Secureboot /v AvailableUpdates /t REG_DWORD /d 0x200 /f powershell Start-ScheduledTask -TaskName "\Microsoft\Windows\PI\Secure-Boot-Update"
Wait a few seconds. Then run the check script again.

MS should hire you for, let's say 6 months
MS has enough folks working on different Secure Boot features. High-level coordination and public messaging is my concern.MS should hire you for, let's say 6 months
I think you could help them get it all working as it should be, like you explained in this thread
Then, again, maybe you already work for MS... ?![]()
use updated script from this post #1,304I've searched the forum for instructions but can't seem to find the correct info to update my USB media, which has been working up til updating the machines for SkuSiPolicy.p7b. I apologize for not being able to find the right instructions here as I'm sure they are here . . . .
Use the update script as mentioned above.On my unsupported machines I've been running fine after adding the 2023 certs (see output below.) But I've updated the policy SkuSiPolicy.p7b to 8.0 and now can't boot Macrium media without getting the violation notice that it wants to see v 8 but finds v. 7 on the USB stick. I've tried updating the USB media using Make2023BootableMedia.ps1 and UpdateMyBootFile.ps1 but that hasn't been successful. I've searched the forum for instructions but can't seem to find the correct info to update my USB media, which has been working up til updating the machines for SkuSiPolicy.p7b. I apologize for not being able to find the right instructions here as I'm sure
I don't know if you used this newer version of the script.I ran the script Update_UEFI-CA2023.ps1 -BootMedia from the post mentioned and it reported success. When I tried to boot from the USB stick I got this blue screen:
I didn't get any output after running that command:What's the output from this PS command? Do you have zero or multiple drives reported?
Code:Get-Disk | Where-Object {$_.IsSystem -eq $true}
