Ver # after 2004 upgrade?

I just did the patch Tuesday updates and got a few updates but nothing that indicated 2004 update/upgrade. A cumulative update and Adobe fix.

IF I did get it, what would the VER command show?

Al

Big Al wrote:

IF I did get it, what would the VER command show?

10.0.19041.329

Big Al wrote:
I just did the patch Tuesday updates and got a few updates but nothing
that indicated 2004 update/upgrade. A cumulative update and Adobe fix.

IF I did get it, what would the VER command show?

Al

I got a surprise recently. Connected my "daily driver" version of
Win10 1909 on an SSD, and expected to see the offer of
2004 (with *no* blockers) in Windows Update.

And to my surprise, my 18363.xxx OS did *not* offer me 2004 19041.xxx!
There was no offer at all.

Either some servicing stack file is magically missing, or now
I'm "really blocked" for some reason, without a dialog box
stating I'm blocked. I don't know what's going on there.
I have force-installed 2004 on another disk drive's 18363.xxx
and no issues of note resulted. I even (by accident), installed
it on a 32GB partition that I'd forgotten to expand again before
kickoff. The installer did a fine job of surviving with only
the 32GB partition to work with. I guess I paid for
my mistake, with extra time wasted compressing stuff.

It added another System Reserved partition, which I don't
appreciate, but I can see the logic and logistics of
doing so. It makes reversion capability easier to do,
if the user seeks to revert, or the installer does a Safe OS
stage revert. There's probably two BCD files involved,
one points to the old System Reserved, the other file
points to the new System Reserved. I'm not aware of
Microsoft ever cleaning up this crap afterwards
(like, at the point in time they remove Windows.old).

Paul

On 6/10/20 7:08 AM, Paul wrote:
Big Al wrote:
I just did the patch Tuesday updates and got a few updates but nothing
that indicated 2004 update/upgrade.Â*Â* A cumulative update and Adobe fix.

IF I did get it, what would the VER command show?

Al

I got a surprise recently. Connected my "daily driver" version of
Win10 1909 on an SSD, and expected to see the offer of
2004 (with *no* blockers) in Windows Update.

And to my surprise, my 18363.xxx OS did *not* offer me 2004 19041.xxx!
There was no offer at all.

Either some servicing stack file is magically missing, or now
I'm "really blocked" for some reason, without a dialog box
stating I'm blocked. I don't know what's going on there.
I have force-installed 2004 on another disk drive's 18363.xxx
and no issues of note resulted. I even (by accident), installed
it on a 32GB partition that I'd forgotten to expand again before
kickoff. The installer did a fine job of surviving with only
the 32GB partition to work with. I guess I paid for
my mistake, with extra time wasted compressing stuff.

It added another System Reserved partition, which I don't
appreciate, but I can see the logic and logistics of
doing so. It makes reversion capability easier to do,
if the user seeks to revert, or the installer does a Safe OS
stage revert. There's probably two BCD files involved,
one points to the old System Reserved, the other file
points to the new System Reserved. I'm not aware of
Microsoft ever cleaning up this crap afterwards
(like, at the point in time they remove Windows.old).

Â*Â* Paul



Counting my spare machines, I have nine, Win10 machines here. Only on a
few of them was the upgrade to 2004 offered.

I just put the upgrade on a DVD to do the rest of the machines

On Wed, 10 Jun 2020 08:53:46 -0500, philo wrote:

On 6/10/20 7:08 AM, Paul wrote:
Big Al wrote:
I just did the patch Tuesday updates and got a few updates but nothing
that indicated 2004 update/upgrade.** A cumulative update and Adobe fix.

IF I did get it, what would the VER command show?

Al

I got a surprise recently. Connected my "daily driver" version of
Win10 1909 on an SSD, and expected to see the offer of
2004 (with *no* blockers) in Windows Update.

And to my surprise, my 18363.xxx OS did *not* offer me 2004 19041.xxx!
There was no offer at all.

Either some servicing stack file is magically missing, or now
I'm "really blocked" for some reason, without a dialog box
stating I'm blocked. I don't know what's going on there.
I have force-installed 2004 on another disk drive's 18363.xxx
and no issues of note resulted. I even (by accident), installed
it on a 32GB partition that I'd forgotten to expand again before
kickoff. The installer did a fine job of surviving with only
the 32GB partition to work with. I guess I paid for
my mistake, with extra time wasted compressing stuff.

It added another System Reserved partition, which I don't
appreciate, but I can see the logic and logistics of
doing so. It makes reversion capability easier to do,
if the user seeks to revert, or the installer does a Safe OS
stage revert. There's probably two BCD files involved,
one points to the old System Reserved, the other file
points to the new System Reserved. I'm not aware of
Microsoft ever cleaning up this crap afterwards
(like, at the point in time they remove Windows.old).

** Paul



Counting my spare machines, I have nine, Win10 machines here. Only on a
few of them was the upgrade to 2004 offered.

I just put the upgrade on a DVD to do the rest of the machines

All of my Win10 VMs start off as clones of one another, and most of them
stay that way. That said, some of them were offered the 2004 upgrade more
than two weeks ahead of some others, and no amount of manually checking for
updates had any effect on that behavior. Eventually, all of them got
offered the upgrade via WU.

On Wed, 10 Jun 2020 08:53:46 -0500, philo wrote:

Counting my spare machines, I have nine, Win10 machines here. Only on a
few of them was the upgrade to 2004 offered.

I just put the upgrade on a DVD to do the rest of the machines

Exactly my experience also.
o Only I don't have nine, but a bit less than half that.

The newest laptops are already upgraded.
o The older desktops aren't being offered.
--
One desktop is still dead (bad Windows boot, unrelated to v2004).

On 6/10/2020 11:12 AM, Arlen Holder wrote:
On Wed, 10 Jun 2020 08:53:46 -0500, philo wrote:

Counting my spare machines, I have nine, Win10 machines here. Only on a
few of them was the upgrade to 2004 offered.

I just put the upgrade on a DVD to do the rest of the machines

Exactly my experience also.
o Only I don't have nine, but a bit less than half that.

The newest laptops are already upgraded.
o The older desktops aren't being offered.

It is my experience that there was a late upgrade to 1909. Then I waited
for the 2004 update to be offered. I got tired waiting and went to the
Microsoft site and updated from their.

On 10/06/2020 17:01, knuttle wrote:
Â*I got tired waiting and went to the Microsoft site and updated from
their.


So now you can tell us what did you achieve by forcing the upgrade? Also
tell us what can can you now do on your system that you weren't able to
do before the upgrade?



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

Big Al wrote:

I just did the patch Tuesday updates and got a few updates but nothing
that indicated 2004 update/upgrade. A cumulative update and Adobe
fix. IF I did get it, what would the VER command show?

Use winver.exe which will show:

Windows 10
Microsoft Windows
Version version (OS Build buildnumber)

You can also go into Settings - System - About, and scroll down the
right panel to the "Windows specifications" section.

You can also click on the Search taskbar button and search on "update
history". Select "View update history". The latest feature update is
listed at the top of the right panel.

Andy already showed what you should see when you run ver.exe in a
command shell. He showed build 10.0.19041.329. When it came out on May
20, it was 10.0.19041.207 for the Insider ring. The sub-sub-sub-minor
version could be different for you.

So, what do those show for you? When you check for updates, you may not
be prompted to install a feature update. After checking for updates,
look to see if it is offered rather than relying on a prompt to tell you
it is available. That is, the feature update is not automatically
pushed. The user must seek the update by manually checking for updates.

For me, and with updates paused, checking for updates 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.

They never detail why they believe a host is not compatible. Possibly
some drivers are older than they want. Another reason for pending a
feature update is that you still have prior dependent updates to
install. Because I paused updates, I have 2 pending download and 1
pending restart updates that may be required before the 2004 feature
update becomes available. I did a manual check, and because I have a
recent backup (scheduled to run everyday), the updates changed status to
pending restart. If I'm not back soon to note if 2004 was offered to
me, it's because I had to restore from backup. Unsettling to add more
code, especially with known defects (which may not affect you in
particular), turn on the blender, and see if the OS, apps, and all
hardware still work afterward.

After seeing the above message, click on the "Learn more" link. That
goes to:

https://docs.microsoft.com/en-us/win...indows-10-2004

to show some further information along with known defects and whether
there are mitigations yet (as subsequent updates or revisions to the
2004 update), or if Microsoft is investigating a problem (which means
not yet fixed).

Make sure to have a recent image backup before installing ANY updates
from Microsoft. Some have had very nasty results. Even for the few
users that have encounted the known, investigating, or even unknown bugs
in an update, when it hits you the few them become all you.

VanguardLH wrote:

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.

Nope, after installing 3 pending updates, and a subsequent update that
showed up, I'm still told my "device" is not compatible with the 2004
feature update.

https://www.zdnet.com/article/window...ays-microsoft/
""To safeguard your update experience, we have applied a compatibility
hold on Windows 10 devices ..."

Regarding the reported issues listed the
- My onboard audio uses Realtek, not Conexant or Synaptics.
- Integrated graphics is on many Intel CPUs. I have an Intel Core i7
8700 Coffee Lake, and that has integrated graphics. However, it is
NOT enabled in BIOS. Instead I am using an AMD video card.
- Nothing Thunderbolt in my hardware config.
- My video games are really old (Thief 1 to 3, fan missions, Hitman).
They won't be using the GameInput redistributable libs.
- aksfridge.sys and aksdf.sys are for Aladdin HASP (Hardware Against
Software Piracy). I know of nothing in my setup that uses Aladdin's
DRM crap. It is for use with specialized external hardware; i.e.,
security dongles. I don't have any.
- I have an AMD video card, not nVidia.

Windows 10, version 2004 and Windows Server, version 2004
Known issues and notifications
https://docs.microsoft.com/en-us/win...indows-10-2004

Lot of **** to wade through there trying to figure out why Microsoft
thinks they need a compatibility hold on the 2004 feature update on my
hardware setup.

https://docs.microsoft.com/en-us/win...indows-10-2004