Windows 10 Home 64 bit 1803 Update OS Build
 

Tried to update Windows 10 Home 64 bit from the cumulative catalog file.
Got an error that my version could not be updated. Could somebody that has
successfully updated the 64 bit version of Windows 10 Home post their 1803
OS Build number?
--
Bill

Brought to you from Anchorage, Alaska

Windows 10 Home 64 bit 1803 Update OS Build
 

Bill Bradshaw wrote:
Tried to update Windows 10 Home 64 bit from the cumulative catalog file.
Got an error that my version could not be updated. Could somebody that has
successfully updated the 64 bit version of Windows 10 Home post their 1803
OS Build number?

What does your "winver" command report ?

Run it from Start : Run or enter it in a
Command Prompt or Powershell window.

Then post the number.

A "Cumulative" would be a Windows Update security update,
which will raise the patch number "y" on the x.y
format of Winver. The "x" corresponds to the OS release.

If the "x" value is old enough, it's out of support.
And downloading a current DVD image and running the
Setup.exe on it, will get you the current release.

Paul

Windows 10 Home 64 bit 1803 Update OS Build
 

Bill Bradshaw wrote:

Could somebody that has successfully updated the 64 bit version of
Windows 10 Home post their 1803 OS Build number?

17134.285

Windows 10 Home 64 bit 1803 Update OS Build
 

Thanks. It gave a message it could not update my version so I rebooted and
somethings happened and I ended up with the same OS Build number you have so
it must have updated in spite of the message. Love windows update.

Bill

Andy Burns wrote:
Bill Bradshaw wrote:

Could somebody that has successfully updated the 64 bit version of
Windows 10 Home post their 1803 OS Build number?

17134.285

Windows 10 Home 64 bit 1803 Update OS Build
 

See my response to Andy's message. I use the cumulative updates every month
to try to avoid these issues. It appears based on the OS Build number it
did update.

Bill

Paul wrote:
Bill Bradshaw wrote:
Tried to update Windows 10 Home 64 bit from the cumulative catalog
file. Got an error that my version could not be updated. Could
somebody that has successfully updated the 64 bit version of Windows
10 Home post their 1803 OS Build number?

What does your "winver" command report ?

Run it from Start : Run or enter it in a
Command Prompt or Powershell window.

Then post the number.

A "Cumulative" would be a Windows Update security update,
which will raise the patch number "y" on the x.y
format of Winver. The "x" corresponds to the OS release.

If the "x" value is old enough, it's out of support.
And downloading a current DVD image and running the
Setup.exe on it, will get you the current release.

Paul

Windows 10 Home 64 bit 1803 Update OS Build
 

Bill Bradshaw wrote:
Thanks. It gave a message it could not update my version so I rebooted and
somethings happened and I ended up with the same OS Build number you have so
it must have updated in spite of the message. Love windows update.

Bill

Are you telling us, you attempted a "race condition" ???

Your machine had downloaded and queued up the Cumulative for the month.

Then, you went to catalog.update.microsoft.com and downloaded
a 700MB Cumulative .msu, double clicked it and it said
the update "was not appropriate" or the like. Because it
was blocked by the pending status of the very same update
already queued for you to reboot. And yet there was absolutely
no notification a reboot was required ?

Or something like that.

Shirely the machine provided feedback while all this was happening.

Were you looking in the Windows Update panel
at the time, for inspiration ?

What did it say ?

There's a lot missing from your story of daring-do.
Did you nudge it with your hip, trying to get a
free game ? Did you lose your quarter ? Enquiring minds...

Paul

Windows 10 Home 64 bit 1803 Update OS Build
 

On 2018-09-16, Paul wrote:
Bill Bradshaw wrote:
Thanks. It gave a message it could not update my version so I rebooted and
somethings happened and I ended up with the same OS Build number you have so
it must have updated in spite of the message. Love windows update.

Bill

Are you telling us, you attempted a "race condition" ???

Your machine had downloaded and queued up the Cumulative for the month.

Then, you went to catalog.update.microsoft.com and downloaded
a 700MB Cumulative .msu, double clicked it and it said
the update "was not appropriate" or the like. Because it
was blocked by the pending status of the very same update
already queued for you to reboot. And yet there was absolutely
no notification a reboot was required ?

Or something like that.

Shirely the machine provided feedback while all this was happening.

Were you looking in the Windows Update panel
at the time, for inspiration ?

What did it say ?

There's a lot missing from your story of daring-do.
Did you nudge it with your hip, trying to get a
free game ? Did you lose your quarter ? Enquiring minds...

Paul

I checked my update history & see something "funny".

1) 09/12 - cumulative update 1803 = KB4457128) ==========
2) 09/12 - update for flash player 1803 = KB4457146
3) 09/12 - update for 1803 = KB445665
4) 09/13 - cumulative update 1803 = KB4457128 ===========

Guess ms did not think that the cumulative worked??
Or was it a measure twice thinggy?

Windows 10 Home 64 bit 1803 Update OS Build
 

On Sun, 16 Sep 2018 19:55:02 -0000 (UTC), in alt.comp.os.windows-10, lew
wrote:

On 2018-09-16, Paul wrote:
Bill Bradshaw wrote:
Thanks. It gave a message it could not update my version so I rebooted and
somethings happened and I ended up with the same OS Build number you have so
it must have updated in spite of the message. Love windows update.

Bill

Are you telling us, you attempted a "race condition" ???

Your machine had downloaded and queued up the Cumulative for the month.

Then, you went to catalog.update.microsoft.com and downloaded
a 700MB Cumulative .msu, double clicked it and it said
the update "was not appropriate" or the like. Because it
was blocked by the pending status of the very same update
already queued for you to reboot. And yet there was absolutely
no notification a reboot was required ?

Or something like that.

Shirely the machine provided feedback while all this was happening.

Were you looking in the Windows Update panel
at the time, for inspiration ?

What did it say ?

There's a lot missing from your story of daring-do.
Did you nudge it with your hip, trying to get a
free game ? Did you lose your quarter ? Enquiring minds...

Paul

I checked my update history & see something "funny".

1) 09/12 - cumulative update 1803 = KB4457128) ==========
2) 09/12 - update for flash player 1803 = KB4457146
3) 09/12 - update for 1803 = KB445665
4) 09/13 - cumulative update 1803 = KB4457128 ===========

Guess ms did not think that the cumulative worked??
Or was it a measure twice thinggy?

I had KB4457128 go off twice, too. The first time it installed, it was
very brief and didn't require a restart. It didn't upgrade the version
number, which remained at 17134.254.

The second time it took a lot longer, like a cumulative update normally
should, required a restart, and I ended up with 17134.285.

So maybe something is wonky with that update.

On my laptop, the update went off without a hitch, but it didn't have
KB4346783 already installed. It went straight from 228 to 285.

--
Zag

No one ever said on their deathbed, 'Gee, I wish I had
spent more time alone with my computer.' ~Dan(i) Bunten

Windows 10 Home 64 bit 1803 Update OS Build
 

"Paul" wrote in message
...
(Skip)
Did you nudge it with your hip, trying to get a
free game ? Did you lose your quarter ? Enquiring minds...

Paul

That brought back memories of my pinball playing days. :)
Buffalo

Windows 10 Home 64 bit 1803 Update OS Build
 

Zaghadka wrote:
On Sun, 16 Sep 2018 19:55:02 -0000 (UTC), in alt.comp.os.windows-10, lew
wrote:

On 2018-09-16, Paul wrote:
Bill Bradshaw wrote:
Thanks. It gave a message it could not update my version so I rebooted and
somethings happened and I ended up with the same OS Build number you have so
it must have updated in spite of the message. Love windows update.

Bill
Are you telling us, you attempted a "race condition" ???

Your machine had downloaded and queued up the Cumulative for the month.

Then, you went to catalog.update.microsoft.com and downloaded
a 700MB Cumulative .msu, double clicked it and it said
the update "was not appropriate" or the like. Because it
was blocked by the pending status of the very same update
already queued for you to reboot. And yet there was absolutely
no notification a reboot was required ?

Or something like that.

Shirely the machine provided feedback while all this was happening.

Were you looking in the Windows Update panel
at the time, for inspiration ?

What did it say ?

There's a lot missing from your story of daring-do.
Did you nudge it with your hip, trying to get a
free game ? Did you lose your quarter ? Enquiring minds...

Paul
I checked my update history & see something "funny".

1) 09/12 - cumulative update 1803 = KB4457128) ==========
2) 09/12 - update for flash player 1803 = KB4457146
3) 09/12 - update for 1803 = KB445665
4) 09/13 - cumulative update 1803 = KB4457128 ===========

Guess ms did not think that the cumulative worked??
Or was it a measure twice thinggy?

I had KB4457128 go off twice, too. The first time it installed, it was
very brief and didn't require a restart. It didn't upgrade the version
number, which remained at 17134.254.

The second time it took a lot longer, like a cumulative update normally
should, required a restart, and I ended up with 17134.285.

So maybe something is wonky with that update.

On my laptop, the update went off without a hitch, but it didn't have
KB4346783 already installed. It went straight from 228 to 285.

A KB can be issued more than once, and they have
revision control on them. I would hope the large
one would come first, and the revision 2 would
be a small one correcting the install status of
the first one. If one of them is intended to be
a Servicing Stack update, it should have its own
number.

Paul

Windows 10 Home 64 bit 1803 Update OS Build
 

On Sun, 16 Sep 2018 20:19:01 -0400, in alt.comp.os.windows-10, Paul
wrote:

Zaghadka wrote:
On Sun, 16 Sep 2018 19:55:02 -0000 (UTC), in alt.comp.os.windows-10, lew
wrote:

On 2018-09-16, Paul wrote:
Bill Bradshaw wrote:
Thanks. It gave a message it could not update my version so I rebooted and
somethings happened and I ended up with the same OS Build number you have so
it must have updated in spite of the message. Love windows update.

Bill
Are you telling us, you attempted a "race condition" ???

Your machine had downloaded and queued up the Cumulative for the month.

Then, you went to catalog.update.microsoft.com and downloaded
a 700MB Cumulative .msu, double clicked it and it said
the update "was not appropriate" or the like. Because it
was blocked by the pending status of the very same update
already queued for you to reboot. And yet there was absolutely
no notification a reboot was required ?

Or something like that.

Shirely the machine provided feedback while all this was happening.

Were you looking in the Windows Update panel
at the time, for inspiration ?

What did it say ?

There's a lot missing from your story of daring-do.
Did you nudge it with your hip, trying to get a
free game ? Did you lose your quarter ? Enquiring minds...

Paul
I checked my update history & see something "funny".

1) 09/12 - cumulative update 1803 = KB4457128) ==========
2) 09/12 - update for flash player 1803 = KB4457146
3) 09/12 - update for 1803 = KB445665
4) 09/13 - cumulative update 1803 = KB4457128 ===========

Guess ms did not think that the cumulative worked??
Or was it a measure twice thinggy?

I had KB4457128 go off twice, too. The first time it installed, it was
very brief and didn't require a restart. It didn't upgrade the version
number, which remained at 17134.254.

The second time it took a lot longer, like a cumulative update normally
should, required a restart, and I ended up with 17134.285.

So maybe something is wonky with that update.

On my laptop, the update went off without a hitch, but it didn't have
KB4346783 already installed. It went straight from 228 to 285.

A KB can be issued more than once, and they have
revision control on them. I would hope the large
one would come first, and the revision 2 would
be a small one correcting the install status of
the first one. If one of them is intended to be
a Servicing Stack update, it should have its own
number.

These two updates were in the space of 10 minutes, and the small one was
the first one.

Something wasn't right with the first install. It didn't install at all.
My build number stayed the same, and didn't increment to from 254 to 285.

--
Zag

No one ever said on their deathbed, 'Gee, I wish I had
spent more time alone with my computer.' ~Dan(i) Bunten

Windows 10 Home 64 bit 1803 Update OS Build
 

All the computers are now fine. I run Windows 10 Pro and have updates
paused so I can do the updates manually using the cumulative updates from
the catalog. This allows me to download and apply the updates to more than
one computer. Plus the updates normally seem to go better.

Bill

Paul wrote:
Bill Bradshaw wrote:
Thanks. It gave a message it could not update my version so I
rebooted and somethings happened and I ended up with the same OS
Build number you have so it must have updated in spite of the
message. Love windows update. Bill

Are you telling us, you attempted a "race condition" ???

Your machine had downloaded and queued up the Cumulative for the
month.
Then, you went to catalog.update.microsoft.com and downloaded
a 700MB Cumulative .msu, double clicked it and it said
the update "was not appropriate" or the like. Because it
was blocked by the pending status of the very same update
already queued for you to reboot. And yet there was absolutely
no notification a reboot was required ?

Or something like that.

Shirely the machine provided feedback while all this was happening.

Were you looking in the Windows Update panel
at the time, for inspiration ?

What did it say ?

There's a lot missing from your story of daring-do.
Did you nudge it with your hip, trying to get a
free game ? Did you lose your quarter ? Enquiring minds...

Paul