I have a tablet where when attempting to install 1709 (ISO) from 1703, the message in the subject line is the end result, preventing the upgrade from getting past the preliminary stages. Is there a way past it? I did see the "AllowOSUpgrade" Registry change, but it had no effect (I think it only pertains to getting new builds to show up in WU). The tablet is Clover Trail-based, which in my case does work properly with 1703, and is also a build that supposedly didn't have support but was in fact the first build since early W10 builds to work properly. (1703 later was also blocked from installation on Clover Trail, but I installed it very early on, apparently before the block was put in place.) I strongly suspect that if I were able to actually install 1709, it would also work.
what about cloning the hard drive to a portable drive so you can recover to what you've got now then wipe the hard drive and attempt a clean install of 1709 ...T
I could test that, but is there precedent for the installer used during a boot from USB being any more forgiving than the installer run from Windows? I would think that they should have the identical checks built in to them.
I got 1709 (November Update) and ran it with these switches on 1703: Setup /compat /IgnoreWarning Surprise! No blocking message, and the upgrade worked. Not sure if it was something about the new 1709, but probably not. Most likely it was just the switches that allowed it to proceed.