Open Crashdummyy opened 2 years ago
Same issue here on Surface Go
Seeing the same for SL3 intel
Same on SL4 intel.
Same problem on SB2
SP6 has this issue.
Same issue here on Surface Go
Wondered if you managed to solve this? Having the same issue with the Sept '22 updates.
@mannp no, unfortunately.
@mannp no, unfortunately.
Okay, thanks for coming back to me @mobedoor
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 --force
?), setting OnlyTrusted=false
like it says in the output is what you should do.
I flashed the newest firmware on my Surface Pro 5 without any problems using OnlyTrusted=false
. Using only --force
did not help. Maybe this should be added to the README?
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 ?