Same problem here - but solved it by going to the "normal" windows update where the windows10 update now was available.