Free Zomb

Found a somewhat "hacky" solution to prevent further writes to a PreviousBoot file by setting a read-only attribute on the said file. Thank you

Hello, first of all, thank you for this great tool. Use of NVRAM for storing variables is discouraged because it wears flash storage. On the other hand, writes to the filesystem frequently cause issues on my machines (I understand that this is the fault of the buggy UEFI implementations): sometimes the PreviousBoot gets corrupted/unreadable which causes rEFInd to stall on the next boot, sometimes the timestamps gets messed up (i.e. Windows "chkdsk" always finds something to complain about). So I...

Hello, first of all, thank you for this great tool. Use of NVRAM for storing variables is discouraged because it wears flash storage. On the other hand, writes to the filesystem frequently cause issues on my machines (I understand that this is the fault of the buggy UEFI implementations): sometimes the PreviousBoot gets corrupted/unreadable which causes rEFInd to stall on the next boot, sometimes the timestamps gets messed up (i.e. Windows "chkdsk" always finds something to complain about). So I...

Hello, first of all, thank you for this great tool. Use of NVRAM for storing variables is discouraged because it wears flash storage. On the other hand, writes to the filesystem frequently cause issues on my machines (I understand that this is the fault of the buggy UEFI implementations): sometimes the PreviousBoot gets corrupted/unreadable which causes rEFInd to stall on the next boot, sometimes the timestamps gets messed up (i.e. Windows "chkdsk" always finds something to complain about). So I...

Hello, first of all, thank you for this great tool. Use of NVRAM for storing variables is discouraged because it wears flash storage. On the other hand, writes to the filesystem frequently cause issues on my machines (I understand that this is the fault of the buggy UEFI implementations): sometimes the PreviousBoot gets corrupted/unreadable which causes rEFInd to stall on the next boot, sometimes the timestamps gets messed up (i.e. Windows "chkdsk" always finds something to complain about). So I...

Hello, first of all, thank you for this great tool. Use of NVRAM for storing variables is discouraged because it wears flash storage. On the other hand, writes to the filesystem frequently cause issues on my machines (I understand that this is the fault of the buggy UEFI implementations): sometimes the PreviousBoot gets corrupted/unreadable which causes rEFInd to stall on the next boot, sometimes the timestamps gets messed up ("chkdsk" always finds some issue). So I was wondering, is there a way...

Hello, first of all, thank you for this great tool. Use of NVRAM for storing variables is discouraged because it wears flash storage. On the other hand, writes to the filesystem frequently cause issues on my machines (I understand that this is the fault of the buggy UEFI implementations): sometimes the PreviousBoot gets corrupted/unreadable which causes rEFInd to stall on the next boot, sometimes the timestamps gets messed up ("chkdsk" always finds some issue). So I was wondering, is there a way...

Hello, first of all, thank you for this great tool. Use of NVRAM for storing variables is discouraged because it wears flash storage. On the other hand, writes to the filesystem frequently causes issues on my machines (I understand that this is the fault of the buggy UEFI implementations): sometimes the PreviousBoot gets corrupted/unreadable which causes rEFInd to stall on the next boot, sometimes the timestamps gets messed up ("chkdsk" always finds some issue). So I was wondering, is there a way...