Thanks everyone for including your information on this issue. I think it's affecting quite a few folks based on what I've seen.
To Microsoft - is there a way to identify what specific driver caused the failure? Otherwise it's really a needle-in-a-haystack situation to try to identify the cause. If we could identify that, we could simply fully uninstall the device, perform the upgrade, and then go from there.