My other home Computer had the same. The dead end in 14295 (updates were from Windows 7 until 14295) - I tried all what I knew, but I did not find a solution. Windows update always failed with a new build, but worked for all other updates. Updating a new build by ISO failed too. I think that it was a registry problem (access denied, not fixable), so a solution was a clean install of new build (14328 / 14332) ...
If you remove the duplicate -All-Users from the second command it should work perfectly. You have to be actively downloading the update through WU at the time as well
Cristianlp All Esd Spanish enjoy Thanks for the links, but do you know which of the esd is windows 10 home x64 also windows 10 pro x64?. Kind regards.
Same way you get anything on the taskbar. Open it, right click the icon which is now on the taskbar, select pin to taskbar.
Both 14328 and 14332 were extremely buggy for me--while 14316 is the best build yet for my hardware. I've reverted to 14316 after the last two builds. It's not a question of Microsoft addressing newer hardware--you are having trouble for the same reason that I and many other people are--these builds are "works in progress"--very, very buggy... If anything is to "blame" it's their attempt to support very old/weak hardware (like you find in current cell phones) alongside powerful x86-64 desktop hardware, circa the last couple of years. I think that currently the UI is a buggy mess...! Microsoft calls this "UWP"...so far, UWP fails to impress...
Well tried a NEW install with 14328 DVD on another hard drive (on the same computer) with official win 10 and it mucked it all up and went into a loop trying to solve the install problem...anyway went back to the oficial win 10 dvd (for a new install) and it installed with no problem.
For anyone experiencing the narrow font problem with some alternative Chromium-based browsers (among other programs, like Steam) over the last three builds, the answer is to disable DirectWrite: chrome://flags/#disable-direct-write This should not have been removed from Known Issues. It was in 14328, the build before that, and the current build: "If you are in an app and click on a link with a URL longer than 260 characters, it will bring up the “Open with…” dialog instead of opening with your default browser."
You have a point...wouldn't it be great if a build was clever enough to tell you exactly why it wont install as I didn't get any error codes (even some of those are vague when you get them).