I have an old Windows 10 computer that is formatted MBR. No recovery. It
is not going to ever be used on the internet but I decided to update it
using the cumulative updates. So I figured out what the next update would
be and downloaded the updates and started installing them. Everything went
fine until that last 2 cumulative updates. Has somebody successfully
installed the last 2 updates to MBR with no recovery? Yes, I know I have
way to much time on my hands.
--
<Bill>

Brought to you from Anchorage, Alaska

On 1/17/24 03:59 PM, Bill Bradshaw wrote:
> I have an old Windows 10 computer that is formatted MBR. No recovery. It
> is not going to ever be used on the internet but I decided to update it
> using the cumulative updates. So I figured out what the next update would
> be and downloaded the updates and started installing them. Everything went
> fine until that last 2 cumulative updates. Has somebody successfully
> installed the last 2 updates to MBR with no recovery? Yes, I know I have
> way to much time on my hands.
Search for 0x in this group. There have been a lot of discussions on
KB....4441 if that's what you're talking about. Otherwise post the KB#
--
Linux Mint 21.2 Cinnamon
Al

Big Al wrote:
> On 1/17/24 03:59 PM, Bill Bradshaw wrote:
>> I have an old Windows 10 computer that is formatted MBR. No
>> recovery. It is not going to ever be used on the internet but I
>> decided to update it using the cumulative updates. So I figured out
>> what the next update would be and downloaded the updates and started
>> installing them. Everything went fine until that last 2 cumulative
>> updates. Has somebody successfully installed the last 2 updates to
>> MBR with no recovery? Yes, I know I have way to much time on my
>> hands.
> Search for 0x in this group. There have been a lot of discussions on
> KB....4441 if that's what you're talking about. Otherwise post the
> KB#

I am also looking at the update 1 before that. I wonder if Microsoft is
trying to force us to at least have Win 10 computers that can be upgraded to
11?

<Bill>

On 1/17/24 04:50 PM, Bill Bradshaw wrote:
> Big Al wrote:
>> On 1/17/24 03:59 PM, Bill Bradshaw wrote:
>>> I have an old Windows 10 computer that is formatted MBR. No
>>> recovery. It is not going to ever be used on the internet but I
>>> decided to update it using the cumulative updates. So I figured out
>>> what the next update would be and downloaded the updates and started
>>> installing them. Everything went fine until that last 2 cumulative
>>> updates. Has somebody successfully installed the last 2 updates to
>>> MBR with no recovery? Yes, I know I have way to much time on my
>>> hands.
>> Search for 0x in this group. There have been a lot of discussions on
>> KB....4441 if that's what you're talking about. Otherwise post the
>> KB#
>
> I am also looking at the update 1 before that. I wonder if Microsoft is
> trying to force us to at least have Win 10 computers that can be upgraded to
> 11?
>
> <Bill>
>
>
Need KB #s. We can't see your screen.
--
Linux Mint 21.2 Cinnamon
Al

On 1/17/24 05:16 PM, Big Al wrote:
> On 1/17/24 04:50 PM, Bill Bradshaw wrote:
>> Big Al wrote:
>>> On 1/17/24 03:59 PM, Bill Bradshaw wrote:
>>>> I have an old Windows 10 computer that is formatted MBR.  No
>>>> recovery.  It is not going to ever be used on the internet but I
>>>> decided to update it using the cumulative updates.  So I figured out
>>>> what the next update would be and downloaded the updates and started
>>>> installing them.  Everything went fine until that last 2 cumulative
>>>> updates.  Has somebody successfully installed the last 2 updates to
>>>> MBR with no recovery?  Yes, I know I have way to much time on my
>>>> hands.
>>> Search for 0x in this group.  There have been a lot of discussions on
>>> KB....4441 if that's what you're talking about.  Otherwise post the
>>> KB#
>>
>> I am also looking at the update 1 before that.  I wonder if Microsoft is
>> trying to force us to at least have Win 10 computers that can be
>> upgraded to
>> 11?
>>
>> <Bill>
>>
>>
> Need KB #s.  We can't see your screen.
Search for "Status: Download error - 0x80070643"
--
Linux Mint 21.2 Cinnamon
Al

Bill Bradshaw wrote on 1/17/24 1:59 PM:
> I have an old Windows 10 computer that is formatted MBR. No recovery. It
> is not going to ever be used on the internet but I decided to update it
> using the cumulative updates. So I figured out what the next update would
> be and downloaded the updates and started installing them. Everything went
> fine until that last 2 cumulative updates. Has somebody successfully
> installed the last 2 updates to MBR with no recovery? Yes, I know I have
> way to much time on my hands.
>

More info needed
Even with MBR Windows 10 has a Recovery partition(not the OEM recovery
which is usually GB in size and at the end of your disk).

Open Disk Management, take a snapshot of the partitioning and post a link
to the picture or report in your response the partitions you see(all or
them) and the size and free space.

--
....w¡ñ§±¤ñ

Big Al wrote:
> On 1/17/24 05:16 PM, Big Al wrote:
>> On 1/17/24 04:50 PM, Bill Bradshaw wrote:
>>> Big Al wrote:
>>>> On 1/17/24 03:59 PM, Bill Bradshaw wrote:
>>>>> I have an old Windows 10 computer that is formatted MBR. No
>>>>> recovery. It is not going to ever be used on the internet but I
>>>>> decided to update it using the cumulative updates. So I figured
>>>>> out what the next update would be and downloaded the updates and
>>>>> started installing them. Everything went fine until that last 2
>>>>> cumulative updates. Has somebody successfully installed the last
>>>>> 2 updates to MBR with no recovery? Yes, I know I have way to much
>>>>> time on my hands.
>>>> Search for 0x in this group. There have been a lot of discussions
>>>> on KB....4441 if that's what you're talking about. Otherwise post
>>>> the KB#
>>>
>>> I am also looking at the update 1 before that. I wonder if
>>> Microsoft is trying to force us to at least have Win 10 computers
>>> that can be upgraded to
>>> 11?
>>>
>>> <Bill>
>>>
>>>
>> Need KB #s. We can't see your screen.
> Search for "Status: Download error - 0x80070643"

The last 2 are kb5033372 and kb50334122. I am not getting an error except
at the end the install process it displays a message update not installed.

I guess an additional question is on MBR do I need a recovery partition?

<Bill>

....w�񧱤� wrote:
> Bill Bradshaw wrote on 1/17/24 1:59 PM:
>> I have an old Windows 10 computer that is formatted MBR. No
>> recovery. It is not going to ever be used on the internet but I
>> decided to update it using the cumulative updates. So I figured out
>> what the next update would be and downloaded the updates and started
>> installing them. Everything went fine until that last 2 cumulative
>> updates. Has somebody successfully installed the last 2 updates to
>> MBR with no recovery? Yes, I know I have way to much time on my
>> hands.
>
> More info needed
> Even with MBR Windows 10 has a Recovery partition(not the OEM recovery
> which is usually GB in size and at the end of your disk).
>
> Open Disk Management, take a snapshot of the partitioning and post a
> link to the picture or report in your response the partitions you
> see(all or them) and the size and free space.

I posted in a message to Al with the KBs. I have instructions for creating
a recovery partition so I will try to create one. I have recoverys on the
other computers and I still not have figured why all the partitions and why
they are where they are at. So the key is to create a recovery. I never
have had a problem in the past with using cumulative updates with no
recovery and was not sure you needed one with MBR. The computer I am
working with I purchased in January 2010 so it has had a lot upgrades and
updates without a problem untll now.

<Bill>

....w�񧱤� wrote:
> Bill Bradshaw wrote on 1/17/24 1:59 PM:
>> I have an old Windows 10 computer that is formatted MBR. No
>> recovery. It is not going to ever be used on the internet but I
>> decided to update it using the cumulative updates. So I figured out
>> what the next update would be and downloaded the updates and started
>> installing them. Everything went fine until that last 2 cumulative
>> updates. Has somebody successfully installed the last 2 updates to
>> MBR with no recovery? Yes, I know I have way to much time on my
>> hands.
>
> More info needed
> Even with MBR Windows 10 has a Recovery partition(not the OEM recovery
> which is usually GB in size and at the end of your disk).
>
> Open Disk Management, take a snapshot of the partitioning and post a
> link to the picture or report in your response the partitions you
> see(all or them) and the size and free space.

I see what appears to be another problem in that I have 4 partitions (C, D,
E, F) and it appears this is probably affecting the creation of the recovery
partition. I have to do some more research.

<Bill>

....w�񧱤� wrote:
> Bill Bradshaw wrote on 1/17/24 1:59 PM:
>> I have an old Windows 10 computer that is formatted MBR. No
>> recovery. It is not going to ever be used on the internet but I
>> decided to update it using the cumulative updates. So I figured out
>> what the next update would be and downloaded the updates and started
>> installing them. Everything went fine until that last 2 cumulative
>> updates. Has somebody successfully installed the last 2 updates to
>> MBR with no recovery? Yes, I know I have way to much time on my
>> hands.
>
> More info needed
> Even with MBR Windows 10 has a Recovery partition(not the OEM recovery
> which is usually GB in size and at the end of your disk).
>
> Open Disk Management, take a snapshot of the partitioning and post a
> link to the picture or report in your response the partitions you
> see(all or them) and the size and free space.

Disk Management shows a healthy recovery behind C of 523MB. But is shows it
as unformatted. I thought it was suppose to formatted to NTFS. So there
could be a problem. I have to leave this issue behind for a while and get
on to things I am suppose to be doing.

<Bill>

On 1/17/2024 3:59 PM, Bill Bradshaw wrote:
> I have an old Windows 10 computer that is formatted MBR. No recovery. It
> is not going to ever be used on the internet but I decided to update it
> using the cumulative updates. So I figured out what the next update would
> be and downloaded the updates and started installing them. Everything went
> fine until that last 2 cumulative updates. Has somebody successfully
> installed the last 2 updates to MBR with no recovery? Yes, I know I have
> way to much time on my hands.
>

I prepared a landing area, for one Windows 10, so the '4441
would work for sure. It is possible some drivers are getting
added here.

[Daily driver, physical install, dual-boot windows]

dir /ah K:\Recovery\WindowsRE [partition 6]

01/14/2024 12:55 PM 517,679,270 winre.wim

*******

[In a VM...]

C:\Recovery\WindowsRE [partition 3]

466,404,365 December 4 Winre.wim

K:\Recovery\WindowsRE [partition 4] reagentc /info points here...

473,452,580 Jan.18 winre.wim

In both cases, '4441 claims to be successfully installed.

I don't see a reason it could not install to
C:\Recovery\WindowsRE if that is where reagentc /info
points to.

reagentc could also be disabled. Check.

reagentc /info

It's not unknown for reagentc fo be disabled.
It is what prevents a Recovery USB stick from being made.

I had to "re-wire" a reagentc one day, just so I could
make one of the (lame) USB recovery sticks. You're better off
just downloading an ISO.

Paul

On 1/18/2024 12:39 PM, Bill Bradshaw wrote:
> ...w¡ñ§±¤ñ wrote:
>> Bill Bradshaw wrote on 1/17/24 1:59 PM:
>>> I have an old Windows 10 computer that is formatted MBR. No
>>> recovery. It is not going to ever be used on the internet but I
>>> decided to update it using the cumulative updates. So I figured out
>>> what the next update would be and downloaded the updates and started
>>> installing them. Everything went fine until that last 2 cumulative
>>> updates. Has somebody successfully installed the last 2 updates to
>>> MBR with no recovery? Yes, I know I have way to much time on my
>>> hands.
>>
>> More info needed
>> Even with MBR Windows 10 has a Recovery partition(not the OEM recovery
>> which is usually GB in size and at the end of your disk).
>>
>> Open Disk Management, take a snapshot of the partitioning and post a
>> link to the picture or report in your response the partitions you
>> see(all or them) and the size and free space.
>
> I see what appears to be another problem in that I have 4 partitions (C, D,
> E, F) and it appears this is probably affecting the creation of the recovery
> partition. I have to do some more research.
>
> <Bill>

Well, you know there is Extended/Logical, as a solution.
(At least the partition that booting starts from, the "Active"
partition, has to be a primary. C: could be in a logical if
you want. But for the trouble that would cause, you might
as well leave the controlling Windows C: as a primary.)

You also know, when you "move some things", you need
a boot repair. Macrium Reflect Rescue CD can do that.
(It has a "Boot Repair" in the menu only on the CD version.)
But it also fouls up some times, and needs a little help.

And while there is MBR2GPT.exe on your C: drive,
that too takes balls and instruction manuals.
You could change from MBR to GPT. There are
restrictions in the instructions, on what is supported.
I think I stopped testing that at some point (tool 1 : Paul 0).

Thwarted on every turn... :-)

I created an MBR VM just to test, and I had to do
one Boot Repair before I was finished there. I even had
to use PTEDIT32.exe and move one row of the partition
table, to clean up the mess. This sort of work is
loads of fun, for some value of loads.

Paul