Recent content by Akeo

Rufus does that dynamically. But we "clamp" the max SVN to the version that was last released as retail ISO (which currently is 25H2 v2), which means 7.0 instead of the actual current 8.0. This is because, with many, many people using the retail ISOs for install, which Microsoft doesn't update...

So this: Cannot be construed as a veiled insinuation that, because most people aren't experts on crypto, they may want to be cautious about using Mosby? Please try to re-read the quote objectively, in context, because sentences like "you always have to ask if your tools are secure" are very...

Yes. And what I'm seeing is that every time that happens, you invent some bullshit about it, such as strongly insinuating as you have done here, that maybe the tool is not as secure as yours. There are not many way to interpret what you tried to aim at here, with your allegation that somehow my...

Seriously? WTF dude. So a long PowerShell script is not equally cryptic to laymen as C code now? And it's also SUPER TRANSPARENT in Mosby: Mosby/src/gen_data.sh at main · pbatard/Mosby We apply the same approach, so, again, I would appreciate if you stopped trying to disparage Mosby at any...

@garlin, it might be of interest to you to know that the SVN has been updated by Microsoft to v8.0 in their official repository.

This is because you were using an old version of Mosby. This is evidenced by Mosby not reporting its version from the log, whereas all the latest versions do (precisely so that we can tell if you are not using the latest). As you have seen, once you used the latest version your results...

No, that is incorrect. Using the Windows OEM signed certs only means that you can install the KEK without enabling Setup Mode, since, outside of Setup Mode, you must use signed packages to update the Secure Boot databases. But the end result will be EXACTLY THE SAME, as the signed "wrapper" is...

There you go. Mosby was successful and your PK was installed without errors.

From what I can tell, you are still using an old version of Mosby, since your log entry should have the Mosby version reported (this reporting was added in newer versions precisely so we can tell if someone is not using an up to date Mosby), which entirely explains your issue. Please download...

There's no way it shouldn't work if we have the same BIOS. Can you please create an issue in pbatard/Mosby and post your full Mosby.log there (you'll find the Mosby.log at the root of the USB). Again, I extensively tested Mosby on that machine (and I am positive I have the exact same T460 model...

v1.45. Actually, the whole reason why I purchased a secondhand T460 is because I saw your original report in the other thread, where you mentioned the failure with Mosby (and I believe you also piggybacked on an issue on the GitHub issue tracker), and I wanted to investigate it. See PK...

I have a T460, and I extensively validated Mosby on it. It should work fine, as long as you do use the latest version.

It seems to me like you're not using an official ISO downloaded from Microsoft (at Download Windows 11 for instance). You are also mentioning 26H1 which is not an official consumer Windows release. Therefore, I would strongly suggest that you only use the official 25H2 from Microsoft (and just...

Maybe run a bad blocks check of your USB stick (which Rufus can do, under advanced format options) or try a different one. It would also help if you provided the exact error message you get then. Note that, if you have the 2023 certs installed, and haven't revoked the 2011 PCA one, then either...

More specialist than a dedicated issue tracker for the software? Look, I know it's easy for people who spend a lot of time in a few places to have their visions skewed into believing that, because they wander there, these places somehow happen to be the most relevant places in the world. But...