Announcing Windows 10 Insider Preview Build 14971 for PC Insider

I thought people were talking about the install.esd that used to be the Sources sub0dir of ~BT?

martyfelker said:

I thought people were talking about the install.esd that used to be the Sources sub0dir of ~BT?

It's still there, has been in every build since October 1^st 2014 and first Technical preview build.

Update:

Hey #WindowsInsiders : we are parsing data from yesterday's flight, so no new builds today

Tweet

— Twitter API (@user) View on Twitter

fireberd said:

I'm still on 14959 and have always been set for "fast" updates. When I check for updates, none are found.

@fireberd, you can easily create an ISO from the install.esd and do an in-place upgrade. If you have the install.esd, which you obviously don't!

I have the 14971 install.esd on One Drive. If you would like a link to DL, PM me. TC

It's not on any of the 4 copies of 14971 I have installed. Other peopole have said the same Karl

martyfelker said:

It's not on any of the 4 copies of 14971 I have installed. Other peopole have said the same Karl

Marty, are you referring to the install.esd?

I'mgoing to dual boot now with Winodows Server 2016.

I have no idea what Dora's tweet means. What does parsing a flight mean. Buildfeed is 14984l compiled last Weds.

martyfelker said:

It's not on any of the 4 copies of 14971 I have installed. Other peopole have said the same Karl

No Marty (look, I can spell your name even it has more letters than mine), some have said that but they have been as wrong as you are now. Get your facts straight.

As has been repeatedly told, in these announcement threads and for instance in ESD to ISO tutorial thread (here for instance complete instructions), the ESD file has always been in every build in the C:\$Windows.~BT\Sources folder and users wanting to make an ISO should copy it to a safe location before restarting the computer to upgrade. The same with 14971: it's there.

It's users like you who due their own actions and wrong procedure will not find it: As was in earlier builds until build 11082, and now with builds 14965 and 14971, the ESD file will be removed when upgrade is done. If it was not copied to a safe location before you click Restart to perform the upgrade, it will be gone. Your own fault.

In builds since 11082 ESD file was not removed when upgrade was done, build 14965 brought this feature back and in two last builds the ESD file have been removed after the upgrade. As this behaviour should already be known to all Insiders because in early builds it really was always removed (a feature which now made a come back), in addition to numeral warnings on this and other sites, it's your fault if you just click Restart to start upgrade without backing up the ESD file.

I repeat: ESD file has been since first build we received in C:\$Windows.~BT\Sources folder. It is there also when you download and prepare upgrade to build 14971.

Really, check your facts.

Kari

martyfelker said:

I'mgoing to dual boot now with Winodows Server 2016.

I have no idea what Dora's tweet means. What does parsing a flight mean. Buildfeed is 14984l compiled last Weds.

Dona's tweet means they are analyzing the code, in chunks. From Wikipedia:

Parsing or syntactic analysis is the process of analysing a string of symbols, either in natural language or in computer languages, conforming to the rules of a formal grammar.


Buildfeed is reporting what they heard from a leaked private source ( which they do not divulge). It's what they believe will be the next build. It is not anywhere near an official source for anything. To imply a lab build from 48 hours ago should be on the street is, well......