Hekate: failed to launch hos because exfat - Caused by missing FS hashes
i faced this issue after i update system to 10.2.0
sd card is exfat and installed hos driver only supports fat32 failed to launch hos
i check that i may need a fs driver to support exfat.
where can i get it?
zsw12abc
All 7 comments
Having the same issue, I tried to update Hekate and Atmosphere to latest but I'm still getting this issue. The OFW boots just fine though, and also the Fusee.
FezVrasta
on 15 Sep 2020
This is a message that normally checks if your HOS update is the FAT32 only or the FAT32 + exFAT one.
In this case though, it's a bug because FS kip hashes are not yet in and hekate thinks you have the fat32-only update.
Will be rectified later this day.
CTCaer
on 15 Sep 2020
I have same issue, will i just need to download the release to get this fix? thanks
aceadamuk
on 15 Sep 2020
You will see a release in a couple of hours.
CTCaer
on 15 Sep 2020
Fixed in https://github.com/CTCaer/hekate/commit/8f7bdd45b15cca7c20ffaf6e27e0ab2665ad040d
Please download the new release: https://github.com/CTCaer/hekate/releases/latest
CTCaer
on 15 Sep 2020
hi I have same issue, can guide how to fix? thanks
kenson96
on 3 Oct 2020
hi I have same issue, can guide how to fix? thanks
Update everything, Atmosphere and bootloader
aceadamuk
on 3 Oct 2020
Related issues
coffeeken
路
4Comments
Real96
路
10Comments
tegutistgut
路
3Comments
noahc3
路
3Comments
aveao
路
6Comments
Most helpful comment
This is a message that normally checks if your HOS update is the FAT32 only or the FAT32 + exFAT one.
In this case though, it's a bug because FS kip hashes are not yet in and hekate thinks you have the fat32-only update.
Will be rectified later this day.