WIN 10 Update - device not ready

Windows Update screen says "The Windows 10 May 2020 Update is on its
way. We’re offering this update to compatible devices, but your device
isn’t quite ready for it. Once your device is ready, you’ll see the
update available on this page. There’s nothing you need to do at this
time."

Why would my PC be not quite ready? I've never had to make changes to
my device before receiving an update in the past.

Currently on 1909 build 18363.836, on what was originally a WIN 7
machine, and has been through all the ugrades/updates for WIN 10.

In article , Davidm
wrote:

Windows Update screen says "The Windows 10 May 2020 Update is on its
way. We’re offering this update to compatible devices, but your device
isn’t quite ready for it. Once your device is ready, you’ll see the
update available on this page. There’s nothing you need to do at this
time."

Why would my PC be not quite ready? I've never had to make changes to
my device before receiving an update in the past.

because microsoft is still working on it.

https://www.computerworld.com/articl...e-road-to-the-
win10-version-2004-rollout.html
What¹s painfully obvious: (1) If you see that message, you won¹t be
offered the version 2004 upgrade through Windows Update just yet;
and (2) the message isn¹t related to a specific set of deficiencies
on your machine. Indeed, the message should say, ³Windows isn¹t
ready for your computer,² instead of putting the shoe on the other,
erroneous foot.

nospam wrote:
In article , Davidm
wrote:

Windows Update screen says "The Windows 10 May 2020 Update is on its
way. We’re offering this update to compatible devices, but your device
isn’t quite ready for it. Once your device is ready, you’ll see the
update available on this page. There’s nothing you need to do at this
time."

Why would my PC be not quite ready? I've never had to make changes to
my device before receiving an update in the past.

because microsoft is still working on it.

https://www.computerworld.com/articl...e-road-to-the-
win10-version-2004-rollout.html
What¹s painfully obvious: (1) If you see that message, you won¹t be
offered the version 2004 upgrade through Windows Update just yet;
and (2) the message isn¹t related to a specific set of deficiencies
on your machine. Indeed, the message should say, ³Windows isn¹t
ready for your computer,² instead of putting the shoe on the other,
erroneous foot.


Or another way to put it: "Consider yourself lucky that we haven't
foisted this update on you right now possibly f'ing your system as we
beta test this...."

--
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com

On Sat, 06 Jun 2020 14:15:47 +0100, Davidm wrote:

Windows Update screen says "The Windows 10 May 2020 Update is on its
way. We’re offering this update to compatible devices, but your device
isn’t quite ready for it. Once your device is ready, you’ll see the
update available on this page. There’s nothing you need to do at this
time."

There is also a button "Learn more" underneath this.

Why would my PC be not quite ready? I've never had to make changes to
my device before receiving an update in the past.

If you click that "Learn more" button, it will open your web browser on
a page with a list of 'Known issues' which Microsoft is still working on.

In other words, Microsoft is still working on getting it ready. It may be
OK for some devices where these issues do not apply, but otherwise see
Jonathan N. Little's reply in this thread.


--
Kind regards
Ralph

Jonathan N. Little wrote:
nospam wrote:
In article , Davidm
wrote:

Windows Update screen says "The Windows 10 May 2020 Update is on its
way. We’re offering this update to compatible devices, but your device
isn’t quite ready for it. Once your device is ready, you’ll see the
update available on this page. There’s nothing you need to do at this
time."

Why would my PC be not quite ready? I've never had to make changes to
my device before receiving an update in the past.
because microsoft is still working on it.

https://www.computerworld.com/articl...e-road-to-the-
win10-version-2004-rollout.html
What¹s painfully obvious: (1) If you see that message, you won¹t be
offered the version 2004 upgrade through Windows Update just yet;
and (2) the message isn¹t related to a specific set of deficiencies
on your machine. Indeed, the message should say, ³Windows isn¹t
ready for your computer,² instead of putting the shoe on the other,
erroneous foot.


Or another way to put it: "Consider yourself lucky that we haven't
foisted this update on you right now possibly f'ing your system as we
beta test this...."


This is what comes of "what we test is not what we release".

Drop-dead issues would require the ISO to be repaired. You
are using the customers to test, so the "list of issues"
grows within the first few days, creating "blockers" for the
slower Upgrade situations.

I've noticed this sort of divergence in previous Upgrades, so
this behavior isn't a brand new one. They never seem to release
what they've been testing (whether testing for weeks, or testing
for months, doesn't matter, same issue).

Less crucial issues will be fixed via the "first patch" which
is installed soon after the ISO is installed. Presumably the
time gap between ISO (19041.1) and patch (19041.248 or whatever),
is pretty short. And may even be pulled in during the installation
for all I know. I don't know if the time stamp history of
Windows Update tracks this adequately or not. If the machine is
network-connected, the Upgrade can communicate with home base
during the install (at certain points in the install). Figuring out
what has gone on, would involve some hard-to-read logfiles. The GUI
Windows Update History, doesn't give the level of detail I want.

The DVD is stamped this way, so .248 is not the release level
of the DVD

10.0.19041.1

If there was something wrong with the DVD, preventing usage,
they'd spin a new one and bump the release.

10.0.19041.xxx

When the Upgrade to 2004 comes in via Windows Update, it's
a series of a thousand small packages. That's how it is downloaded.
But I think it still has the notion of curation, as all the
files have been stamped with 19041.1 individually, and it's
just the curious way of building the thing to be installed
that involves the thousand small packages and slow download.
The server also has a mode of operation, where it will deliver
part of the Windows Update Upgrade as a 2.5GB blob (still followed
by more small files of course). You can trigger that sort of delivery,
by modifying BITS or DoSVC max download threads to a lower number.

HTH,
Paul

On Sat, 06 Jun 2020 14:15:47 +0100, Davidm
wrote:

Windows Update screen says "The Windows 10 May 2020 Update is on its
way. We’re offering this update to compatible devices, but your device
isn’t quite ready for it. Once your device is ready, you’ll see the
update available on this page. There’s nothing you need to do at this
time."

Why would my PC be not quite ready? I've never had to make changes to
my device before receiving an update in the past.

Currently on 1909 build 18363.836, on what was originally a WIN 7
machine, and has been through all the ugrades/updates for WIN 10.
Thanks all, I think I'll just delay the update for a month (or 3) to
let it settle down.

Davidm wrote:
On Sat, 06 Jun 2020 14:15:47 +0100, Davidm
wrote:

Windows Update screen says "The Windows 10 May 2020 Update is on its
way. We’re offering this update to compatible devices, but your device
isn’t quite ready for it. Once your device is ready, you’ll see the
update available on this page. There’s nothing you need to do at this
time."

Why would my PC be not quite ready? I've never had to make changes to
my device before receiving an update in the past.

Currently on 1909 build 18363.836, on what was originally a WIN 7
machine, and has been through all the ugrades/updates for WIN 10.
Thanks all, I think I'll just delay the update for a month (or 3) to
let it settle down.

I fired up a Win10 disk here a couple hours ago,
and the Upgrade dialog didn't even appear at all.
I was neither Enabled nor Blocked :-) The 18363.xxx computer
claimed I was "Up to Date", when I clicked the
button to verify. I'm hoping that the updates
on the thing aren't broken.

At least computers are predictable. You know exactly
what they'll do next (whatever you don't want them to do).

Paul

On 06/06/2020 14:15, Davidm wrote:

Why would my PC be not quite ready? I've never had to make changes to
my device before receiving an update in the past.

Just because you were getting updates on your device doesn't mean it
will continue getting in the foreseeable future.Â* Technology changes at
the speed of thought so your device may not be compatible with something
new.

However, Windows has a "Trouble Shooter".Â* Try running it to see if it
throws any light into this.

[ Trouble Shooter Window ] https://i.imgur.com/WaFtdcv.png


This window has got trouble shooter for most things that could give some
people sleepless nights!!Â* Network, Bluetooth etc etc can all be
corrected automatically.

Some people here are discouraging users from using this feature but they
are not the brightest bulbs on this planet!!Â* they are "con-artists2"
who should all be executed for defrauding old people.

Are you the same nm-shifter who used to go by the name of David_B?Â* Most
people here have kill-filed that individual but your message came thrugh
so you must have done something to by-pass my filter system.

Path: aioe.org!peer01.ams4!peer.am4.highwinds-media.com!news.highwinds-media.com!fx28.am4.POSTED!not-for-mail
From: Davidm
Newsgroups: alt.comp.os.windows-10
Subject: WIN 10 Update - device not ready
Message-ID:
User-Agent: ForteAgent/7.00.32.1200
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Lines: 11
X-Complaints-To: http://netreport.virginmedia.com
NNTP-Posting-Date: Sat, 06 Jun 2020 13:15:47 UTC
Organization: virginmedia.com
Date: Sat, 06 Jun 2020 14:15:47 +0100
X-Received-Bytes: 1102
X-Received-Body-CRC: 3611160738
Xref: aioe.org alt.comp.os.windows-10:115253


--
With over 1.2 billion devices now running Windows 10, customer
satisfaction is higher than any previous version of windows.

On 6/6/2020 8:15 AM, Davidm wrote:
Windows Update screen says "The Windows 10 May 2020 Update is on its
way. We’re offering this update to compatible devices, but your device
isn’t quite ready for it. Once your device is ready, you’ll see the
update available on this page. There’s nothing you need to do at this
time."

Why would my PC be not quite ready? I've never had to make changes to
my device before receiving an update in the past.

Currently on 1909 build 18363.836, on what was originally a WIN 7
machine, and has been through all the ugrades/updates for WIN 10.


I had the same thing on my laptop, so I just went online and downloaded
the 2004 Media Creation Tool and installed it that way. Just did that
earlier today and so far there haven't been any problems. My laptop is a
HP 15 (N5Y09UA#ABA) which is using AMD chips and I noticed that most of
the problems MS listed were with Intel chips. So that's why I decided to
update manually. I'll post back if I do run into any problems.

--


Wednesday, June 10, 2020 1:40 PM
Thunderbird 68.9.0

Roy Smith wrote:

Davidm wrote:

Currently on 1909 build 18363.836

I had the same thing on my laptop, so I just went online and downloaded
the 2004 Media Creation Tool and installed it that way.

Usually I do use the MCT to jump the gun, but this time my work PC got
2004 very early (and I postponed the install/reboot until the weekend)
my home PC which I normally test first didn't pick up 2004 straight
away, then it got the latest cumulative update and immediately after
offered the upgrade this morning ... no problem with either of them