I have two computers one is an HP laptop, and the other is an HP
desktop. The two computers have had all of the updates applied as they
were offered.

When 21h1 was offered for the Laptop I installed, it went with no problems.

After several days and 21H1 was not offered to the desktop, I went to
The MS Update Assistant Web page and installed 21H1 with no apparent
problems. (Yes I am impatient but want to get the updates over with.)

On the command line "winver" and in Setting, System, About on both
computers the is Windows Build 19043.985.

On the laptop in the Settings, Update and Security, Windows Update, when
I look at Update history, it shows I up date to 20H2 in Oct 20 and 21H1
in May 21.

However on the desktop Settings, Settings, Update and Security, Windows
Update, when I look at Update history it does not show the 21H1 update
or the 20h2 update.

Is this a function of the way I updated the two computers or do I have a
problem

knuttle wrote:
> I have two computers one is an HP laptop, and the other is an HP
> desktop. The two computers have had all of the updates applied as they
> were offered.
>
> When 21h1 was offered for the Laptop I installed, it went with no
> problems.
>
> After several days and 21H1 was not offered to the desktop, I went to
> The MS Update Assistant Web page and installed 21H1 with no apparent
> problems. (Yes I am impatient but want to get the updates over with.)
>
> On the command line "winver" and in Setting, System, About on both
> computers the is Windows Build 19043.985.
>
> On the laptop in the Settings, Update and Security, Windows Update, when
> I look at Update history, it shows I up date to 20H2 in Oct 20 and 21H1
> in May 21.
>
> However on the desktop Settings, Settings, Update and Security, Windows
> Update, when I look at Update history it does not show the 21H1 update
> or the 20h2 update.
>
> Is this a function of the way I updated the two computers or do I have a
> problem
>

When you install using an ISO or a DVD, in the usual way,
that "wipes out the install history".

When you use "enabler" installs, those show in the history
and don't wipe the installer state.

I think what's happened to you is "normal" :-)
Whatever "normal" means now.

I hope you realize, that we're reaching a point now,
where it is no longer possible to answer questions about
Windows 10. We are entering the era of containerization,
multiple kernels, and we will have less and less
ability to debug things, or offer comments about them.
When something "goes slow", will it be your hard drive ?
Would a more expensive CPU bring the performance back ?
We won't know, because the things that matter are now
hidden from us.

Just skim read this, and see how many terms you don't
recognize, and how the author throws stuff around like
the audience knows just as much as he does. Sure, I know
we're not the intended audience. But, I want you to get
some idea of the scale of the opportunities for confusion,
and how none of the model or the if/then/else that
controls it, is visible anywhere.

https://www.techrepublic.com/article/windows-10-containers-are-the-future-and-heres-what-you-need-to-know/

"With two use cases for its containers, and
five different container models, it would seem
that Microsoft's container strategy is ripe for confusion.
But that's not the case. Windows' own application isolation
technologies are managed automatically by the installer..."

What of the users ? Do they matter any more ? Guess not.

What's wrong with the Microsoft model, is some parts of the
model are not scaling. NTFS is just as slow as it always was.
Larding on a more expensive model that requires loading
more stuff from disk, this cannot end well, as NTFS is a
bottleneck, and buying an NVMe won't help you. If it
takes 60 seconds to open a .docx, how many foreign
swear words will you be able to say in those 60 seconds ???
The Swear Jar will be overflowing with quarters.

Paul