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(
This is, again, a semantic mishap! Microsoft states "Your machine is not ready" whereas the truth is, their update is not ready yet! They haven´t worked out yet a number of specifics like Realtek, Conexant or Intel Graphics components, many of them 'certified'
and are causing death blue screens etc, so, the issues are theirs, not ours.