According to a recent update thread on the Secure Boot Objects GitHub, MS deliberately rotates through a series of one-year "leaf" certs to sign the boot manager. And this particular one will be the last in that series, since they can't generate another past the Oct 2026 deadline.
From these results, you haven't revoked the PCA 2011 cert. Any boot file version is eligible.
No, nothing from Macrium yet (if ever?). This subject has gone quiet on Macrium forums too.
That's what I was implying by saying it's all gone quiet. Can't help wondering what the fate of LTSC 2024 will be though.....
@Flipmode, I consider this a very unfair rant (and I'm not even a Macrium fanboi). A user of a product needs to know how a product functions... that's called due diligence.
A quick lesson... RDR does not mess with disk blocks that have not been changed by the operating System. Why... because it saves a massive amount of RESTORE time when returning an image to the System. If the contents of a disk block has changed without the operating System's knowledge (your device, your problem, I believe) then there's no way REFLECT or any other application can know that without comparing every single bit on the disk block with its reference image... nobody does that except AX64 (now defunct) and Image For Windows (feature not used very much anymore). If you understood how RDR worked, the first thing you would have tried would have been a non-RDR FULL restore (re-write everything, including all unchanged disk blocks... takes longer but usually eliminates these types of issues. As you found out, it solved your immediate problem (but surely not your longer term issue).
What you described as an issue is, in my eyes, a storage device beginning a longer term failure scenario... better be ready. Normally, the storage device itself would flag, to the OS, this type of DATA failure (based on internal DATA error detection/correction codes)... in your case, it did not, something else to worry about with that SOURCE storage device.
Be gentle with your application developers...
You still need to find out why the resident disk DATA went south on you without either your or Windows knowledge... I'd still worry about that source disk. A fluke... maybe, but it just may happen again.
Currently, the MR UI layout and default behaviour leave significant room for improvement and much to be desired when navigating these primary features and settings!
I agree with this, Hasleo is way easier to use... I just switched some days ago and it even aligns partitions correctly; settings are on sight and intuitive to get to.For most techs, 99% of our workflow is installation, maintenance, and log checking etc. Restore's represent about 1% of our time actually restoring or retrieving data for clients.
Because restoring is so rare (well, until Windows 12, touch wood), "backup" s/w should be designed for the critical 1% moment (restoring), not just the 99% routine (config / monitoring). The interface needs to be completely intuitive in a crisis - especially for SMBs or mid-level techs (me) with a diverse skill set.
It highlights a bigger problem - Macrium should not assume every user is an 'elite special-ops' expert who knows every toggle inside out.
Just saw your reply. Cheers mate. Not having a rant or whinge. I'll be having an 'objective' rant with MR support! hah
Source was Kingston SKC3000 2TB and Gigabyte AG470S1TB (original SSD). Basic disks & all NTFS. 94% & 96% health.
Delta Restore to 26 July 2025 Diff failed. 7th July Full failed. 18th June Full failed. 2nd June (Diff) failed..
Full's were 02/05, 14/06, 18/06, 07/07. Loads of Diff's and Incr's spanning across that.
When I turned off RDR, I tried a dozen in July, 2 in June= BSOD, Only one to work was differetntial on 02/06.
