How to get the Windows 10 May 2019 Update version 1903

Compumind · 23 May 2019

Compumind said:

This is nuts...

Still have two systems on 503 (intermediate build) - anyone else not being offered this?
Is 503 required before 1903 (I think so)?

One other item -

Can I use the 1903 ADK binaries on 1809 to update them or do I have to wait for 1903?

Thanks!

Anybody?

f14tomcat · 23 May 2019

Caledon Ken said:

If we are keeping score, Apps is broken on one machine but good on the other.

Wow somebody wanted this Feature Update pushed out the door.

Wish there was some insight as to number of conversions and some sort of issue grouping.

I posted this over in Known Issues, if you want to give it a try. For the Apps crashing.......

Known issues for Windows 10 May 2019 Update version 1903

kado897 · 23 May 2019

rezpower said:

Thanks. I don't have "background apps" totally disabled. ( I mean the main option) But I have disabled few individual apps. Are there any that I should particularly enable?

Never did track that down. I had all disabled at the time.

babyblue · 23 May 2019

Compumind said:

Anybody?

I think you need 529 not 503 before 1903 upgrade

ignatzatsonic · 23 May 2019

Samuria said:

Any one done the update and noticed disk space? I ran disk clean before insyallin 1903 and had 29 gig free after the update I now have 40 gig free?

Yep:

45 gb occupied before update.

31 gb occupied after update, after I did a "free up space now".

OldOzzie · 23 May 2019

Caledon Ken said:

If we are keeping score, Apps is broken on one machine but good on the other.

Wow somebody wanted this Feature Update pushed out the door.

Wish there was some insight as to number of conversions and some sort of issue grouping.

Tried not to laugh with your response, but I reckon you're right.
Let's face it, they aren't going to capture everything, but after the 1809 data loss saga, basic installation issues that people have been having doesn't give a great vibe to it all, and it's not as though there wasn't alot of testing either.

Some decision maker in an MS office will be dropping his pants and getting bent over for this shitstorm.
This update seems great right about now.

Caledon Ken · 23 May 2019

Yes with the number of possible permutations of hardware, software and customizations maybe this is as good as it gets.

OldOzzie · 23 May 2019

The average point & clicker out there who has no idea would be wondering what hit them when it all turns pear shaped.
Point, click and crash.

alkaufmann · 23 May 2019

Caledon Ken said:

Of course some of the known quick fixes might apply.

Attachment 234766

from this doc.

Thanks for those suggestions. My system has all the latest updates and I am running Windows 10 PRO version 1809 build 17763.529 so I am surprised my system has been rejected for now. I removed some hardware I don't use and some beta software but got the same results. I am way overdue doing a clean install so I may backup, format drive c: and close the curtains for 3 or 4 days.

Ak

rezpower · 23 May 2019

LEOPEVA64 said:

The build in which this bug was fixed belongs to the insider program (version 20H1), this bug has not yet been fixed in the May 2019 update (version 19H1, 1903), Microsoft first test these fixes in the insider builds and then back-port them to the stable build, this particular fix has not been back-ported to the stable build (18362.116).

Thanks a lot. good to know as I am really not in the mood of spending few hours doing a clean install just to see it happen again.
I can live with that for now and will wait to see if the issue is addressed my MS anytime soon.