AMD Ryzen 7, Should I wait or install 1903 Update?

Hi All,
Just finished putting the final touches on my upgraded rig. The main reason
for the upgrade was because it was a bit long in the tooth.
The main hardware was around 9 years old.
I upgraded to the following hardware:
MSI B450 Pro Carbon MB, Ryzen 7 1700x CPU, RX590-8 GB GPU, 16 GB's DDR4 RAM.
I perched a Windows 7 Pro x 64 retail license from Microsoft when I originally
build the PC, I had no trouble at all when it came to reactivating windows 10
with the new hardware.
Microsoft put me on the holding list on the new update because of the
Ryzen 7 CPU. Today I see that Microsoft addressed the compatibility issue with
the Ryzen 7 because the update is ready for download and installation.
I've been following "Brinks Trend"(Known and Resolved issues for Windows 10 May 2019 Update version 1903),Seems Microsoft is working hard in fixing the issues the New Update caused.
The reason for the post is to get some feed-back from persons running a Ryzen 7 CPU.
Did you have to deal with any major issues after the 1903 update.
My PC is working just fine at this point. If I get negative feed-back, I put off installing
the update for a while since Microsoft is giving me the option. If the feed-back is
positive I'll go ahead and install it today, because I know the update is going to mess
up all my custom settings. Today I have time to set windows 10 back to the feel I like.
Thanks...

I've just built a Ryzen box using 1903 - seems OK, didn't have any problems.

Thanks BaDcrc, Good to hear your install went smoothly...

Your cpu is old now, as is my Ryzen 7 2700X which runs Windows 10 190. flawlessly.
INSTALL 1903, but do a clean install of it. as it has changes for the partition sizes it creates, compared to past Windows 10 versions.

Thanks BRKKAB

BRKKAB said:

Your cpu is old now, as is my Ryzen 7 2700X versions.

Yeah, there old in computer age but in my case I was keeping my 60 hertz Samsung monitor so
when gaming I'm caped at 60 fps, so I went with this one and the price was a lot less then the 2700x.
Well the good new is, if we want to upgrade the CPU, were in good shape because that is all will have to
change. Maybe will upgrade the GPU along with it... LOL... Thanks for the comeback...

I ran into a problem last night. I updated to version 1903 and with a Ryzen 7 3200 on an ASUS X470 Prime Pro. For some reason the PC would not boot up, only powers on and hangs up. Stuck in the back up spare with 1803 and the PC worked fine. Sort of ran out of time last night so I just left it and finished with the OCZ PCIe SSD on another system. I can't say if it is the 1903 CU as the issue or another factor causing the problem. After work today I plan on checking it out and then will add the results. Both drives are the same 2 TB seagate.

Techymike: Are you using a X570 mobo?
If you are AND released new chipset drivers this week, as a lot of people had issues..https://www.amd.com/en/support/chipsets/amd-socket-am4/x570

I just finished the update, with the exception of a few tweaked settings I had made that got reset to default, all in all it went pretty smooth. Well, I did find one thing that I did not like. Seems the update removes "sound shortcut for the sound control panel" from the menu that opens when you right click the speaker icon on system tray. I'll have to see how I can get it back.
Mike, if you look closely at the hardware I upgraded too, you will see that all of it has been
out for a year or more. There are two reasons I do it this way. One, All the stuff is a
lot cheaper. Two, There a lot or reviews on how certain combinations work with each other.
I don't upgrade very often because when something goes wrong it's a pain to figure out
what is causing the problem. If your PC works fine with 1803 version of windows than it's
got to be a software issue on either the motherboard or the GPU...

The board is an X470. The issue is that the MB had to reset the cmos. Really not sure about the details on why but everything appears to be running just fine.

Glad to hear, Your up and running, Mike...