i'm not sure but it seems to me that they actually fixed the problem already, since there is a driver that we can install and fix this issue. but the new machines was still shipped with the old problematic drivers, maybe they are already in the pipeline or already in the warehouse.
maybe you can try to connect the device to network through cable first, and do all the updates of all the drivers and force check updates for again a couple of time until there are no more updates to be installed before installing anything else.
in retrospect i think i should have done that, but i just got so used to just get the wifi connected and then do the updates through the wifi, i didn't think the problem actually hit that Achilles' heel.