----------------------------------------------------------------------------------
@MSGID: <u5vvvl.i8.1@ID-201911.user.individual.net>
8028f5b8
@REPLY: 1@dont-email.me> ba8e7ee4
@REPLYADDR Frank Slootweg
<this@ddress.is.invalid>
@REPLYTO 2:5075/128 Frank Slootweg
@CHRS: CP866 2
@RFC: 1 0
@RFC-Message-ID:
<u5vvvl.i8.1@ID-201911.user.individual.net>
@RFC-References: 1@dont-email.me>
1@dont-email.me> 3@dont-email.me> 1@dont-email.me>
1@dont-email.me> 1@dont-email.me> 1@dont-email.me>
1@dont-email.me> <u4609h.10s0.1@ID-201911.user.individual.net> 1@dont-email.me>
<u48bqv.c2c.1@ID-201911.user.individual.net> 1@dont-email.me>
@TZUTC: 0000
@PID: tin/1.6.2-20030910 ("Pabbay") (UNIX)
(CYGWIN_NT-10.0-WOW/2.8.0(0.309/5/3) (i686)) Hamster/2.0.2.2
@TID: FIDOGATE-5.12-ge4e8b94
[Context kept because of age. Please skip to the end.]
On May 19, ...winston <
winstonmvp@gmail.com> wrote:
> Frank Slootweg wrote:
> > ...winston <
winstonmvp@gmail.com> wrote:
> >> Frank Slootweg wrote:
> >>> ...winston <
winstonmvp@gmail.com> wrote:
> >>>> Paul wrote:
> >>>>> and I`d already
> >>>>> done my Patch Tuesday ceremonies.
> >>>>>
> >>>>> Paul
> >>>>>
> >>>>
> >>>> p.s.
> >>>>
> >>>> w/r to Patch Tuesday(May updates)
> >>>> Update your boot or Iso media after applying the May updates.
> >>>> Update your backup images
> >>>> - necessary due to staged implementation(May, June, 1st QTR 2024) of
> >>>> Secure Boot mitigation/revocations
> >>>>
> >>>> See CVE-2023-24932 and KB5025885
> >>>>
> >>>> Windows 11 Software Download site for MCT(for creating USB/DVD/ISO) and
> >>>> the optional ISO file option all provide current media with Windows
> >>>> update released on May 9(i.e. May`s Patch Tuesday updates)
> >>>>
> >>>> Once the revocations for Secure Boot mitigation are pushed/deployed,
> >>>> media and images created earlier than the current available(with the May
> >>>> updates) will no longer function.
> >>>
> >>>
> >>>
> >>>> Update your backup images
> >>>
> >>>
> >>>
> >>> "backup images" like those made by Macrium Reflect (Free), etc.?
> >>>
> >>> If so, backup images of *which* partition(s)? C: or the non-C:
> >>> partitions or both? (I have only C:, no other partitions with drive
> >>> letters.)
> >>>
> >>
> >> Yes, images created prior to installing the May 2023 Update on Windows
> >> 11(10) 22H2, 21H2 need to be updated.
> >>
> >> Which partition?
> >> The general rule when backing up Win11/Win10 on UEFI systems with GPT
> >> created partitions:
> >> - Image should contain the Four(4) GPT partitions(System[aka EFI],
> >> MSR, Windows, Recovery)
> >>
> >> All my devices(Win11 Pro 22H2 and Win10 Pro 22H2) use Macrium Reflect
> >> and Acronis 2020(perpetual) for image creation.
> >> e.g. when loading Macrium on a UEFI GPT device, all 4 of the partitions
> >> are shown in the Macrium UI - thus I image all four(4).
> >>
> >> The reason for all 4, especially for this specific case, is once the
> >> revocations are in-place(3rd phase/stage) the final impact will affect
> >> 3 partitions(System(EFI), Windows, and Recovery)
> >> - At this time, only the System and Windows is affected
> >
> > Thanks!
> >
> > I backed up the three non-C: partitions (System, MSR and Recovery)
> > only once, under the assumption they wouldn`t change over time.
> >
> > Apparently that assumption was wrong, so I will back them up again and
> > at the next Full image backup, I will backup all four and keep it that
> > way.
> >
> > BTW, my `Recovery` partition - partition 4, the last one - has no
> > label (like `Recovery`). Is that normal? (Partition 1 has label `SYSTEM`
> > (uppercase), partition 2 has no label because it`s `Unformatted` and
> > Partition 3 has label `Windows`.)
> >
> There have been a couple of changes in the Win10/11 era where the System
> and Recovery Partition were updated....more so with the latter, because
> by design the Recovery partition has a unique characteristic in Windows
> - Windows can increase it`s size by carving out space from the Windows
> partition(Note: this only applies when the Recovery partition is
> right-adjacent to the Windows partition, if not rt-adjacent Windows will
> recreate a new Recovery partition rt adjacent to the Windows partition
> rendering the old Recovery partition useless and still present)
> - Recovery partition is updated with each and every feature upgrade[1]
I finally re-made the (Macrium Reflect Free) Image backup of the three
non-C: partitions.
I noticed that now the (image of the) Recovery Partition is (seems to
be?) completely empty, i.e. I can mount it, but File Explorer, DIR and
ATTRIB show no files or folders.
If my (02AUG2022, i.e pre-MAY2023) notes are correct, it used to
contain a single folder `Recovery` with a single 3-byte file _CNBRP.FLG.
Why the difference and why is the partition empty/nearly-empty?
Should I worry?
FTR, Macrium says this about the partition:
4 - (None) Primary - NTFS 603.5 MB 693.0 MB
The others (non-C:) are:
1 - SYSTEM (None) Primary - FAT (LBA) 71.0 MB 260.0 MB
(Contains folder `EFI` with subfolders.)
2 - (None) Primary - Unformatted 16.0 MB 16.0 MB
[...]
--- tin/1.6.2-20030910 ("Pabbay") (UNIX)
(CYGWIN_NT-10.0-WOW/2.8.0(0.309/5/3) (i686)) Hamster/2.0.2.2
* Origin: NOYB (2:5075/128)
SEEN-BY: 5005/49 5015/255 5019/40 5020/715 848 1042
4441 12000 5030/49 1081
SEEN-BY: 5075/128 6078/80
@PATH: 5075/128 5020/1042 4441