With KB4465477 (SSU) and KB4464455 v2 (17763.107) directly integrated and KB4466596 v2 (dynamic update 17763.107) extracted to the sources folder the upgrade process works without that error message.
It's very unlikely that there will be a new build. Cumulative updates seem to fix all the problems so far.
I just hope they get their act tougher and fix this, maybe they should outsource it to someone that know what they are doing.
I hope they (MS) not release new build. It's big mess. We get used to this build although the big bugs.