I also have the same issue. My pc is not good, but everything works and all drivers are installed and on the current version. I would also like to know why my PC is not ready.
Windows 10 version 2004 "Your Device is not ready"
Any idea why this is? l am literally running a very modern £1600 PC with very modern hardware (approx 6 months old).
Windows for home | Windows 10 | Windows update
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
71 answers
Sort by: Newest
-
Anonymous
2020-06-04T18:45:43+00:00 -
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
-
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
-
Anonymous
2020-06-03T01:05:50+00:00 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.
-
Anonymous
2020-06-02T21:51:02+00:00 I think it's a bit disconcerting that we are told that we aren't "ready" without any diagnostic information whatsoever. You aren't ready, but don't worry about it.....
I also am in the "We aren't ready" box, and I'd prefer to know what rule is being applied to me to put me in that bracket - even a code that can be looked up. It could be something I could resolve myself.....
Like the OP I have a high end PC, with all the latest drivers, so to be frank although not allowing me to bork my PC is awesome I'd quite like to know the issue....?
Edit - oh yes, I've already been to the page that lists the known issues and couldn't reconcile any of them, hence why knowing the issue with my build would be MORE than helpful?
Edit 2 - not looking for assistance per-se, rather Microsoft accepting that a "not yet" message isn't enough :o(