I am pretty sure that they will come around with a fix probably on the next update for this build. At least, I was trying to find out if this workaround works for now. It is a good thing to have reported it to the Feedback Hub for MS to know about it.
I couldn't control myself and did it anyway. Followed your directions precisely, but it unfortunately didn't work for me on my Fast machine. It still quit at 34%.
Thanks for your feedback!. That's exactly what I am trying to find out, to see if it works for everyone. Like I said before, the fact of reporting it to the Feedback Hub for insiders, is already in and of itself a good step forward with the understanding that the frequency of updates in the Insiders' builds is not at the same cadence as for stable ones. Meaning, hopefully we will get an update soon enough from MS capable of fixing this glitch.
I did a clean install of 18890, didn't touch anything when it finished the install, went to windows update and got an error that it couldn't connect to the server. Internet is fine and my other windows operating systems have no problem with connecting to the server. Tried rebooting but didn't work. Anyone else have this problem?
Odd. My audio only works in Windows, everything else refuses to put any audio out.
Only problem with this build thus far, but it is increasingly an annoying one.
Just tried sfc again and it went through this time. It found corrupt files and successfully repaired them. At the end of the log file it was interested in this C:\WINDOWS\System32\WindowsDevicePortal\Plugins\LocationPlugin\\WindowsDevicePortal.LocationPlugin.d ll from store
Don't ask me what else was done as I don't have enough life left to go through the log!
Didn't do anything (knowingly!) to try to fix the 34% stop, so have no idea why it now works.
Quote