How to get the Windows 10 May 2019 Update version 1903

IronZorg89 said:

@Geosammy,

My dear mate, all I know is that that my CPU is waiting for a patch and this is definitely one of the many reasons why MS is not offering me 1903. For the other reasons that I don't know of, I will have to wait after MS's learning machine based on AI. I am pretty sure even if I knew the other reasons, there wouldn't be anything I could do, for as far as I know my machine is really up-to-date regarding the latest graphic driver, my major apps, Windows updates, brand new Canon printer bought two weeks ago etc...

I know it is sometimes nerve-racking with the way MS is doing things and we are left in a guess work about what could be wrong. Your approach is the best right now, meaning to wait and that's exactly what I am doing also.

Lastly, in post #1067 the message has well stipulated that "There is nothing to do at this time". I take it that MS will fix whatever is wrong and they will advise me in due time.

Right, you're speculating and don't have any way of confirming what you think.
Why don't you use the Windows Update Assistant, as has been suggested to me by many in this thread?
Then, if you successfully get the 1903 update, how would you explain this and would you still make the same presumptions if it fails?
Why don't you face what is right in front of you, instead of presuming what the cause is, based on faulty assumptions, that you have little to no evidence for.
Any one of us here on this forum, can guess at what the cause might be.
This doesn't mean, that these guesses are what is actually causing the issue.
Correlation does not imply causation.
At this point, it's all speculation.

IronZorg89 said:

I can tell that you haven't read my previous posts. I did try the Update Assistant already and upgraded to 1903 twice. I had to roll back to 1809 because of two main issues: Edge could not be launched in my admin account, despite having tried to fix it with "Repair" & "Reset" and all the other tricks in the book that I know of. And the other issue is that one of my headphones couldn't get paired.

Now, with regard to speculation, I wouldn't call it that way in my case, because it is a fact that would be fixed sooner or later. You want me to be sure about that. I wish I could be part of Redmond's inner circle. We would like MS to give us the main reason(s) why our machine is not ready for the upgrade, but the fact is they just don't. Sometimes, to have the answer, we rely on others' experiences.

The other thing worth noting is that, installing 1903 successfully doesn't mean everything is OK. One has to use the machine for a while to see if there are no bugs. I can definitely relate to that because that was my case. On the other hand, in some other forums, 1903 is considered as being in a Beta-like state and some MVPs won't even advise to install it right now. That 's why I am not in a hurry.

Finally so far you are very reluctant to try 1903, preferring to wait. Like I said I don't blame you for that, but at least you can give it a try and that could be of some benefit to other members in this forum, according to what comes out of your experience.

I apologies.
However, I have fully read your previous posts, but failed to take into account, your attempts at installing 1903.
At this time, I feel, that the best course of action, would be to take no action.
I also would like to mention, that my frustration, is turning into anger. Which is not helping the issue at hand.
For this I also apologies.
Thanks for not suggesting, that I "go jump in a lake".

IronZorg89 said:

There you go "At this time, I feel, that the best course of action, would be to take no action.". And that is the best thing to do right now. I can tell you that you are not missing out on anything so far. So no need to be angry! We had the same message and that explains why we are having this discussion. Remember the message said "There is nothing to do at this time". In a way, MS is saying "Trust me on this". Let's just do that and see what comes next.

Agreed.

IronZorg89 said:

That is probably why "A long time ago" as you mentioned. This seems very recent with TrendMicro (ESET):

Support for Windows 10 compatibility - OfficeScan / Apex One

As far as I know, Trend Micro doesn't own Eset. I've looked over the Eset site and don't find any mention of Trend Micro.

ESET Antivirus, Antimalware & Internet Security Solutions | ESET

babyblue said:

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

Exactly, BabyBlue! I knew they were different, but had to prove it to myself before I spoke!

Geosammy said:

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.

Attachment 237791