How to get the Windows 10 May 2019 Update version 1903

Bree · 19 Jun 2019

Comp Cmndo said:

Patch Tuesday, 6/18/19
MCT has now been updated to 18362.175

Thanks for the 'heads up', downloading now.

HRPuffnstuff · 19 Jun 2019

Yes thank you and I'm also updating my ISO's.

Brink · 19 Jun 2019

Microsoft auto-updating Windows 10 version 1803 and earlier to 1903

ThrashZone · 19 Jun 2019

Hi,
Skippy 1809 at current working order it sucks anyway

IronZorg89 · 19 Jun 2019

babyblue said:

Just to point out the obvious - TrendMicro and ESET are different AV products!

Thanks for pointing this out. In my mind those two were from the same company because most of the time they are always mentioned in the same breath; but after a little bit of research, I realize that this was not the case.

LOL!

Geosammy · 19 Jun 2019

Murphcid said:

I had to update the BIOS on two machines (my wife's Ryzen 7 HP laptop, my youngest daughter's HP Spectre x360 15) before I could get the update to install on their laptops. Make sure you have the latest and greatest BIOS. YMMV.

See This Post: How to get the Windows 10 May 2019 Update version 1903

IronZorg89 · 19 Jun 2019

Well, Well, last night while doing a routine check for updates, I found out that I was in the same boat as @Geosammy:

How to get the Windows 10 May 2019 Update version 1903-notice-window-update-1903.png

In my case, I think I have a good idea about what is keeping MS from offering me 1903. It has to do probably with the µcode patch for my CPUID (306C3) which has not been out yet. I will wait since I am not in any hurry...

Geosammy · 19 Jun 2019

IronZorg89 said:

Well, Well, last night while doing a routine check for updates, I found out that I was in the same boat as @Geosammy:

In my case, I think I have a good idea about what is keeping MS from offering me 1903. It has to do probably with the µcode patch for my CPUID (306C3) which has not been out yet. I will wait since I am not in any hurry...

That's odd?
How did you determine, that it was CPUID causing this issue, and how did you rule out any other cause?
Is this simply your best guess?

IronZorg89 · 19 Jun 2019

Geosammy said:

That's odd?
How did you determine, that it was CPUID causing this issue, and how did you rule out any other cause?
Is this simply your best guess?

Because the last PS script run for CPU info showed that my µcode revision was at 0x25 (see screenshot red square). I think after the upcoming patch it should sit at 0x27. Besides, I don't have any issue with 1809 on which I am running right now. Everything is very smooth compared to the last time I tried to upgrade to 1903 and had to roll back because of Edge not launching in my admin account, and the pairing of one my headphones (Sony) couldn't work. I don't have any of the latter on 1809.

How to get the Windows 10 May 2019 Update version 1903-cpu-infob.ps1-result-new-version.png

Geosammy · 19 Jun 2019

IronZorg89 said:

Because the last PS script run for CPU info showed that my µcode revision was at 0x25 (see screenshot red square). I think after the upcoming patch it should sit at 0x27. Besides, I don't have any issue with 1809 on which I am running right now. Everything is very smooth compared to the last time I tried to upgrade to 1903 and had to roll back because of Edge not launching in my admin account, and the pairing of one my headphones (Sony) couldn't work. I don't have any of the latter on 1809.

Everything on my system is running smoothly as well and I don't use CPUID.
My best guess is, that it has something to do with Microsoft's AI and nothing to do with my system not being ready.
However, I have no way of confirming this, other then using one of the alternative methods to install 1903, to see if it is successful installed. Which is something I shouldn't need to do.
Do you have any way of confirming, that it is indeed CPUID, which is causing this issue for you?
If not, you're guessing.
Since you haven't shown, that you've ruled out any other potential causes, this can only be speculation on your part.
Which doesn't determine what the exact cause of this issue is.
What you're doing, is know as The Texas Sharpshooter Fallacy.