Forum Discussion
Announcing Windows 10 Insider Preview Build 19587
You can try the following:
Command Prompt with Administrator privileges...
type reagentc /info
In my case Windows RE status: was disabled / missing.
I had to find a copy (on the local hard disk) and then enable it....after that I was able to install new builds.
yep tried that already. It was enabled
issue still persist.
I even tried resetting the SoftwareDistribution folder (a couple of times) but no luck with that either
This is what I did to get past the 62% after months of broken updates...
In order to locate the Winre.wim file, you can search the file on your computer. From an elevated Command Prompt, type the following command to search for the Winre.wim file on C: drive:
dir /a /s c:\winre.wim
When you find the Winre.wim file and it is vaild, you can type command “reagentc /setreimage /path [path of Winre.wim]”. For example, “Reagentc /setreimage /path C:\Recovery\WindowsRE”
Then reboot enough to get WU to restart the download / install of the new build.
I have no proof...but I believe that the winre.wim on the recovery partition was corrupted by a past build. I tried many things during Jan and Feb to get the builds to install....and this is the only thing that worked.
Hi,
ok got it.
However, my winre.wim file is ENABLED
So i don't think there is a need to do something to it to make this work
Having said all that, i did fine i had a big $windows.~BT file. Apparently, this is a folder to hold a lot of older windows updates. It can be deleted but you have to go through a process to do so.
I have gone through the process & it is deleted now so i will try the windoes updates again shortly.
cheers ian
I just went through this problem again with 19603......you don't have Conexant HD Audio by chance?
Both of my machines that have issues do....I deleted the item (device manager) with driver. On reboot It assigned the Microsoft HD Audio driver, and the update went through.
With the install stuck at 62% I looked at C:\$WINDOWS.~BT\Sources\Panther\setupact.log and the last line (where it was stuck) was the Conexant HD audio line (looking for an oem cab)....maybe that will point you at what is getting stuck.