For almost every build there now exists an adk, so what exact ADK version are you using on 19035 that causes the upgrade to 19041 to fail.
i actually ran setupdiag from ms, it didnt find anything useful except restore points deletion, which i already excluded by disabling system restore before upgrade. so i am left with drivers, or a mysterious other reason.
why would it try to use the dism from the adk, that is unreasonable for a software bundle. the setup iso has it's own mounting tools. I strongly beleive that in the near future, once a patch or two is released, everything will be fine. Simply too many users for now are failing the upgrade.I would report in feedback hub if I hadn't have all telemetry disabled.
If i can find a system/laptop that doesn't already have a HWID for Home or Pro (most have them since 2015), i will test, but if it was the 19035 ADK dism, causing this, it should have happened in a vm too.
Maybe it was rushed to think about DISM, since if it happens in real machine, it could be the "IP over USB" component
I showed my ADK settings, didn't cause a revert. Most upgrade faillures are because of driver problems, AV's and chopped/modified installs.
The scenario was the same, if it's not happening with a clean installed 19035.1 and the official ADK for 19035, then that is most likely not causing it.
I insist that one of the laptops happened to me with the 19035 and ADK 19035 just installed when trying to update it to 19041. Only updated drivers from WU and without any other software. And uninstalling the ADK let me install. And the failure happened at the same point as discussed in this thread, and at the same point where I failed in two other laptops.
Well, I don't know ... three times (Toshiba Portege), and uninstalling it works, I can't find an explanation.
for people having issues if this build goes public u may have to bite the bullet and do a clean install....this is what happens when user start modified and chop up their OS they run into all this issues.