Things are very, very slow for me as usual. Now downloading at 2 %. I am really hoping that this build will fix my File Explorer's search bar. In my case, it has never been fixed despite the fact that there was a fix for it in the previous build.
What's the viability of just doing a patch instead a doing a full download/getting things ready/install etc. ?
I am "looping" at the present.
That's what they're doing for 1903->1909, but one problem with CUs forever would be that we'd be locked into the same primary build number forever. And the CUs would get HUGE eventually.
If you were responding to my post ?I just had my Windows Phone updated and in the info notes they said "If you installed earlier updates, only the new fixes contained in this package will be downloaded and installed on your device." After "X" amount of patches, issue a build to start fresh. ??
Only 44 minutes from start to finish on my Fast machine. Now on to Skippy. If that holds true to form, it will take at least 2 times as long... that is if it updates at all.
Still getting this on physical machines. VMs update ok.
If you have attempted to install Build 18936 or Build 18941 and experienced install failures with error code c1900101 – see below section regarding this issue.
My first attempt on my desktop was with a ISO made with UUPDump. The results was a black screen and no activity shown with the HDD light. I had to hold the power button to restart my computer. I'm now trying with Windows Update It's at 63% installing. I can't believe this install problem wasn't fixed before MS decided to release another build. I hate to say it but IMHO MS has a bunch of over educated nitwits working on the Insider Builds.
Updated 18936 to 18941 from ISO, no issues other than update itself was a little slow.
I am at 64% installing, in the middle of a major lightning and thunder storm, outlook not promising.
Update: After 1st restart it reverted back to previous build. 2.5 hrs wasted!!
Last edited by meebers; 18 Jul 2019 at 16:05.
Quote
