New
#21
I think he went like this:
W8.1Pro > Insider TP10162 > RTM10240
and now he is waiting for 10525.
He has the $Windows.~BT folder with install.esd, but the ESD is corrupt and he can not make the ISO from it.
He has toggled from Fast to Slow, rebooted and back to Fast. He will wait now 24-48 hours to see if it tries to install again.
If nothing happens, maybe next step is to turn WU off, delete the software distribution folder, and restart WU.
The distinction is that after 29 July there are two Windows 10
1) Retail
This is what most people want and is what a system has after upgrading a qualifying OS.
2) Technical Preview (aka evaluation)
This is what people use to test development code as it is released to Insiders.
I dual boot Retail (upgraded from 8.1) and Insider (currently 10.0.525)
The real difference is
Windows Updates to a Retail install have gone through more rigorous testing, the same as previous versions of Windows / Windows updates.
Windows Updates to an Insider install are hot-off-the presses and have not been tested as thoroughly. Insiders are a big part of testing updates that eventually get delivered to Retail installs. These releases and updates can be very buggy. It is pre-release software.
I recommend keeping the two separate.
Launch a Command Prompt (Admin) and enter the following command.
reg query HKCU\SOFTWARE\Microsoft\WindowsSelfhost /sexit
This is the result from my Preview build machine, I'm not sure what the key=values really mean, but it would be interesting to see what the key=values are on your Retail install.
HKEY_CURRENT_USER\SOFTWARE\Microsoft\WindowsSelfhost\Applicability
UXOptions REG_DWORD 0x1
ErrorState REG_DWORD 0x0
LastHR REG_DWORD 0x0
PilotInfoRing REG_DWORD 0x3
FlightingOwnerGUID REG_SZ 6dc60aab-52b3-4001-a1aa-f48298e97033
BranchList REG_SZ {
"Branches":[{
"BranchRings":["WIS","WIF"],"FlightingDisabled":false,"Migrate":"","Name":"th2_release","Platform":"Windows.Desktop"}]
}
RingsList REG_SZ {
"Rings":[{
"Alias":"Fast","Name":"WIF","Order":"1"},{
"Alias":"Slow","Name":"WIS","Order":"2"}]
}
I did a little formatting (new lines) to make it easier to read.
Yes, I was thinking that too at first, because it has happened to some people. But he mentioned he had the $Windows.~BT folder with the ESD file in it, so the computer was indeed trying to update to 10525, but was failing. I read somewhere that 0x80240031 error indicates a damaged file.
Although Slartybart may be on to something here...