-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
firmware signature missing or not trusted; #23
Comments
Same issue here on Surface Go |
Seeing the same for SL3 intel |
Same on SL4 intel. |
Same problem on SB2 |
SP6 has this issue. |
Wondered if you managed to solve this? Having the same issue with the Sept '22 updates. |
@mannp no, unfortunately. |
Any updates on this? It seems to still be an issue |
First of all sorry for ignoring this for so long, I was pretty busy and when I had time again I simply forgot this issue existed. The error message about the missing signature comes from fwupd, it has nothing to do with the firmware files you are trying to flash. fwupd is designed to install firmware from LVFS, where the cab files are signed. This script doesn't sign them with a trusted key (not that we would have one, so you would need to generate your own), so fwupd refuses to flash them. The firmware files inside the cab are signed with a Microsoft key and should be checked by the UEFI seperately before they are installed. However, this is just me guessing, so keep that in mind. As long as you only flash what is inside the MSI files you should be fine. Since there doesnt seem to be a commandline option that disables signature verification (except maybe |
I flashed the newest firmware on my Surface Pro 5 without any problems using |
I just wanted to install the latest downloadable files from here.
I ended up with these files.
I am however not able to install it:
Should I really make this setting?
The hell is microsoft doing ?
The text was updated successfully, but these errors were encountered: