If you can manually download you are missing multiple updates.
As of today 6/18/2017 the most up to date build is 15063.413.
Before the in place upgrade repair your build was 15063.296
After the in place upgrade repair your build was 15063.0
Before the in place upgrade you had attempted a manual install of KB4022405 and indicated that it failed.
There are multiple KB# that you don't currently have that are listed in the logs.
Do you want to manually update these?
Before the in place upgrade didn't the manual update fail? Isn't that the reason that you proceeded to the in place upgrade?
If you can perform manual updates these would bring you up to date:
KB4022405
KB4022725
KB4022730
Well the windows update works, thanks to unchecking the checkbox of my ethernet metered connection, I can use windows update just fine now. Winver says I have 15063.413 now, but thank you!
yes it did fail, because it said I already had it installed but I hadn't installed it. The in-place fixed that bug and the uncheck of metered connection let me actually use windows update
This information I found on metering: Block forced Windows 10 updates using a metered connection | InfoWorld
I spent hours working on these logs. It was painful as I looked at so many HResults and did not find info about metering. What I was guessing was a hidden blocker but could not figure it out.
Glad you got it working.
Bree must have had experience with this problem.
Thanks for posting back @AliveButAFK. Nothing embarrassing here :) There are so many possibilities for something to go wrong (and so few relevant indications), that some luck is needed sometimes.
Yes. Prior to 1703 a metered connection blocked all updates. A manual check would find updates were available and bring up a 'download now' button. 1703 modified this behaviour...
...but it doesn't seem to be working quite as intended yet. For Defender updates you still get the 'download' button as before, but for 'updates required to keep windows running smoothly' it seems to download a few percent then stall. Turning off metering allows it to continue.
Microsoft don't seem to see metered connections as important. There was a similar problem when the Anniversary Update was released, in fact it was researching that problem that led me to TenForums and this post in particular...
Set Wireless Network as Metered or Non-Metered in Windows 10
That got fixed a few builds later on, I expect this one will too.
Quote
