How to get the Windows 10 May 2019 Update version 1903

Geosammy said:

What is a "safeguard hold"?
I'm guessing if I need to ask this question, that I don't have this, but how would I know otherwise?

Not certain, but it sounds like a "block" MS has put on your (or any) machine it deems might fail. Nothing tangible on your end. Nothing you could look for and/or modify. Bottom line, nothing you can control.

f14tomcat said:

Not certain, but it sounds like a "block" MS has put on your (or any) machine it deems might fail. Nothing tangible on your end. Nothing you could look for and/or modify. Bottom line, nothing you can control.

That's what I suspected.

I have the latest BIOS and all my drives are recent additions from Samsung.
Except for the WD Black 1TB HDD, but it's just a storage drive.
The motherboard has the Z170 chipset for 2016, which is still a viable chipset.
The OS drive is a Samsung 970 PRO 512GB NVMe SSD, only a few months old.

My system, as a whole, is a modern PC.
All my 1809 updates check out.
No telling what could be causing MS, to claim my PC isn't ready for the 1903 update.
When older and less capable system have already received this update.
This doesn't compute, (pun intended).

Geosammy said:

That's what I suspected.

I have the latest BIOS and all my drives are recent additions from Samsung.
Except for the WD Black 1TB HDD, but it's just a storage drive.
The motherboard has the Z170 chipset for 2016, which is still a viable chipset.
The OS drive is a Samsung 970 PRO 512GB NVMe SSD, only a few months old.

My system, as a whole, is a modern PC.
All my 1809 updates check out.
No telling what could be causing MS, to claim my PC isn't ready for the 1903 update.
When older and less capable system have already received this update.
This doesn't compute, (pun intended).

Your specs and mine are similar , but yours in total blow mine away. Unless you are totally against any method other than WU, do what I did, and others. The Update Assistant does a compatibility check and all that right up front. I used it on mine and a rinky-dink 5 year old i5-2400D lappy that can barely get out of it's own way. Went in smooth and no aftermath. Worse case, you restore back.

banger said:

I would suggest you ARE on a safeguard hold as something on your machine is stopping the update.

Do you know what a "safeguard hold" is, or are you just repeating what others have already mentioned?

f14tomcat said:

Your specs and mine are similar , but yours in total blow mine away. Unless you are totally against any method other than WU, do what I did, and others. The Update Assistant does a compatibility check and all that right up front. I used it on mine and a rinky-dink 5 year old i5-2400D lappy that can barely get out of it's own way. Went in smooth and no aftermath. Worse case, you restore back.

Thanks for the suggestion, but that was the original point, that I was trying to make.

I don't want to force, or use alternative methods, for updating my OS.
Why would I us any of the aforementioned methods, when my system should update on it's own?
This seems like a contradiction to me.

Now I'm just getting upset over this.
Perhaps I should take a brake, form responding to this thread.

Geosammy said:

Thanks for the suggestion, but that was the original point, that I was trying to make.

I don't want to force, or use alternative methods, for updating my OS.
Why would I us any of the aforementioned methods, when my system should update on it's own?
This seems like a contradiction to me.

Now I'm just getting upset over this.
Perhaps I should take a brake, form responding to this thread.

Well, my goof for bringing it up again, no need to upset yourself. I'll let it rest. Time to hit the sack anyway. Give it a rest, come back tomorrow, and maybe something will pop up.

Cheers, and goodnight.

f14tomcat said:

Well, my goof for bringing it up again, no need to upset yourself. I'll let it rest. Time to hit the sack anyway. Give it a rest, come back tomorrow, and maybe something will pop up.

Cheers, and goodnight.

Right. thumbsup

Bree said:

Looks like MS is making up new words for 'blocking issue' as they go along (or perhaps defining subtly different categories of blocking issue). You can find (variously) "safeguard hold", "quality hold" and "compatibility hold" used in the Issue Details section here...

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


Edit: actually, it just appears to be loose use of language. Here they applied a 'quality hold' but removed a 'safeguard hold' when it was resolved

https://docs.microsoft.com/en-us/win...903#491msgdesc

Thanks Bree.
I know that you're only trying to help, but how does this pertain to my issue?
I can't find anything at the link you provided, that might shed some light on this.
It all sounds like double talk to me, even though I consider myself a pretty tech-savvy person.
I'm not about to start manually installing updates, on speculation.
When apparently, MS claims my system is up to date, even though I can't get the 1903 update.