Hello, i have this problem, how to fix this problem ? Im run on Windows 10 Build 10125 Fr_fr x64 Thanks.
My advice is to move to the most recent official Insider Preview build of 10130 instead of spending time and energy on attempting to solve a problem with an older leaked build. Granted that is just my opinion.
Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsSelfHost\Applicability] "Ring"="WIF" "ThresholdRiskLevel"="low" "BranchName"="fbl_impressive" "UserPreferredBranchName"="fbl_impressive" "ThresholdOptedin"=dword:00000001
The persons issue is that they can't move to 10130 because that error comes up on Windows Update. I got the same error on my desktop. Try to actually read the post before commenting because the person clearly says they were trying to go from 10125 to 10130.
Yep, same thing here. I managed to get the .esd this way a few builds ago, but not anymore... Must be something I changed in the setup (I use WinNTSetup for installs, which uses lots ot tweaks anyway). I can't seem to reproduce what exactly causes this error now, though... Any ideas would be welcome. But as michaelmyers said, please read the question first... Thanks for all the "offline" esd links, I'm on 10130 now, but still would like to solve the esd-update-download error for next builds...
Well, I did a completely clean install on a separate system, this time without any tweaks or unattended stuff. No more errors this time, the esd was downloaded fine, and I could capture the link as well: Code: Get-BitsTransfer -AllUsers | Select FileList | Format-List I turned off all tweaks at once (no UAC off, no autounattend, no auto-activation, etc.), so I still don't know which one did the trick, so I'm still interested in other people's tips.
I did look at their post and noticed they were having issues with installing the latest "public" build deployed via WU in a leaked build. Issues moving to the "public" builds via leaked builds has had issues throughout the Insider Preview program. So my advice is valid and points out the fact you should likely not use leaked builds.