Ground Zero installation of W10 - 2 weird things incl KB34441

I installed W10 from scratch (wiped and nuked HDDs) on two elderly Dells this week.
Two strange findings.
1. After the usual raft of W10 Updates with 4 or 5 "Restart now"s I noticed that I was not getting the repeated persistent KB34441 "Failure - Retry" phenomenon. I saw it once; it was (or seemed to be) Accepted. No repeat thereafter though from memory (or was this something else) it is the initial Success that is followed by repeated Failures.
NB There is a new file at the C:\ root directory. It is attribute Hidden, of size 0, named
$WINRE_BACKUP_PARTITION.MARKER
I wondered whether this was a MS-supplied workaround (or fix) for the KB34441 repeated nag in which case Yay!! At Last!!
But .. .. I invented the same file, same attribute, same size on my standard un-refreshed machine - but to no improvemnent, The KB34441 nag persists. (
Any MeToo's or any explanation for any of this?
2. Not so good. On the new installations (importantly, both successfully Activated) I find I am unable to rename the Desktop icon called "This PC" to "Computer" (or anything else). R-click - Rename fails; the opportunity is presented, but the regression to "This PC" is immedate. Grrr!!
(Whereas, there is no difficulty using the indentical procedure to rename "Recycle Bin" to "Wasstebasket", my preferred nomenclature. And no difficulty with either on my standard un-refreshed machine.)
Weird or what. Any ideas?
Thank you!
fergusd
Edition Windows 10 Pro
Version 22H2
Installed on ‎22/‎04/‎2024
OS build 19045.4355
Experience Windows Feature Experience Pack 1000.19056.1000.0

Ghot said:

@fergusd
.. .. It's probably because it was a clean install and KB5034441 had "room" to make a larger recovery partition .. ..

Well: actually I prepared for the clean install by partitioning the HDD into exactly two - p1 being NTFS 80G and p2 being exfat 400G (I don't like MS's decison-making) - and then booting into the W10 installation medium. The net result is two very clean partitions with no complications. Their insufficiency, if that is the primary cause of the persistent 34441 problem, seems in this scenario to raise no problems; or at least to have gone unnoticed. Really very perplexing!

Megahertz said:

Please post a whole window Disk Manager image of ALL your drives.

VolumeList and DiskList both attached.
Also (in text immediately following) output from fdisk and sfdisk demonstrating full and adjacent occupancy of entire HDD drive by two partitions NTFS+exFAT.
Thank you very much for your interest .. ..
fergusd

~> fdisk-l
Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: ST1000LM024 HN-M
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xbba7c6b9
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 131604479 131602432 62.8G 7 HPFS/NTFS/exFAT
/dev/sda2 131604480 1953525167 1821920688 868.8G 7 HPFS/NTFS/exFAT

~> sfdisk-d
label: dos
label-id: 0xbba7c6b9
device: /dev/sda
unit: sectors
/dev/sda1 : start= 2048, size= 131602432, type=7, bootable
/dev/sda2 : start= 131604480, size= 1821920688, type=7

Megahertz said:

There is no Recovery partition on the drive .. .. If you don't have the recovery partition it can't be updated.

You are absolutely correct that there is no Recovery partition on this drive. I dislike Microsoft's management of Setup on a clean drive. From the beginning I set up just two partitions as described and run Setup from there, accepting p1 as the default platform. Which is why I have been nagged since January about KB34441. The entire point of my post (and the only point of it) was to say that in April I made a clean install as usual (two partitions) and on this platform I have NOT been nagged. It apopeared that KB34441 was either successfully installed, or possibly intelligently ignored - I do not know which.
But the lack of any nag about it since the clean install was imposed has been very welcome!
However I do not understand how this happy circumstance has been achieved. That's all.

Megahertz said:

In this case you can't complain against M$.
I hope you disabled the recovery environment on the Recovery partition (reagentc /disable) before you deleted the partition.

I'm not complaining. Did I sound as though I was? On the contrary I'm thrilled to bits. I just hoped some expert might be able to explain the occurrence. (So far, not.)
Also, I didn't disable the recovery envronment on the Recovery partition as there was no Recovery partition on which to do this; and then no Recovery partition to delete.
Thank you very much for your comments and advice. Much appreciated.