Windows 10 version 2004 "Your Device is not ready"

Download the  windows update assistant and update your OS. Here's the link: https://support.microsoft.com/en-ca/help/3159635/windows-10-update-assistant

This worked for me.

Guess what?   When Setup said my PC was not ready, it apparently wasn't ready.

I tried the Windows 10 Update Assistant work around.   Yes, it allowed me to start the update to 2004.    However, in the end, it finally failed.   I'll give kudos to Microsoft, in that the Update Assistant was able to return me back to 1909 with no ill effects.

I am still left wondering why, even after all these many months since 2004 was officially released, 2004 isn't yet ready for my PC.   I have done many feature updates over the years, without delays or problems.   So, I would say, my PC is rather standard.  No odd or unusual hardware and with that, no odd or unusual drivers (ie, I have all Win 10 drivers).

As others have said, it would be great if Setup also gave a REASON for not being ready.  The Update Assistant also left not a clue as to why if failed.  And Microsoft should at least tell me WHEN 2004 will be ready.

I have four old (vintage 2008/2009) desktop computers and an old (vintage 2009) laptop.  Three of the desktops and the laptop are running Windows 10 Home Edition, and all took the Windows 10 Version 2004 feature update without any issues.  The remaining desktop is running Windows 10 Pro and it keeps getting the "not ready" message - I check it every day.

Based on this small sample, my guess is that the Version 2004 feature update isn't yet available for computers that are running Windows 10 Pro.

No, my Windows 10 Pro machines are running great.

Thanks for the info.

Great! Worked for me as well. Thanks for the clue. But poor stuff from Microsoft. Works via the Update Assistant and not via the Windows Update?? Why?

My problem is with Conexant. I went to the Device Manager and upgraded their drivers which seemed to take a little longer than usual on that function then restarted and the same "not ready" box still comes up. Guess I'll just have to wait a bit for them to clear the issue up.