Announcing Windows 10 Insider Preview Build 14986 for PC Insider

Wynona said:

I did the search yesterday, but only in the $BT folder. Guess I didn't go far enough.

I searched all of C:\ just now and find that*only the first one*"Microsoft-Windows-Client-Features-Package.ESD" is even possibly large enough (1.5GB) to create an ISO. The rest are only MBs in size.


I'm afraid to click on it, though. If it messed me up, I'd have to start all over with Build 14971!

THE en gb esd*expanded*with 7-zip to give directories 1, 2, 3. Don't know how to use them.

Wynona said:

I think that's for Build 14971.

Could be although the setup.exe is for 14986

fjk61011 said:

Could be although the setup.exe is for 14986

So, if I understand correctly, you're saying that the install.esd in windows.old is for Build 14986?

Hmmmm, I guess I could sacrifice my lappy. She mostly only gets used when I travel and that'll be less and less until the temperatures start to rise instead of fall. I have my self-made ISO of Build 14971.

I still have $windows.~bt copied to another drive, no such .wim in it. Only winre.wim.

Wynona said:

So, if I understand correctly, you're saying that the install.esd in windows.old is for Build 14986?

Hmmmm, I guess I could sacrifice my lappy. She mostly only gets used when I travel and that'll be less and less until the temperatures start to rise instead of fall. I have my self-made ISO of Build 14971.

For me it's Professional_en-gb.esd.*Expanding that gives three directories 1, 2 and 3. Directory 1 has a layout like an iso image

fdegrove said:

Hi,



Probably because it was copied prior to the first restart. Maybe it's on your C:\ drive ?

Either way, I don't see much use for this if you have an image of the previous install.
The latest installation procedure is totally different now. No idea how one would create an ISO from it since setup files are written to various places and no .esd file that appears to be usable for ISO creation.

Cheers,

I just kept it in case somebody finds a way to make ISO or bootable drive from it, It will be deleted soon.

Wynona said:

Very strange, to say the least. I did a clean install of 14971 a week or so ago, and reset my computer to the fast ring. Today, when 14986 dropped, I checked and I was back on the slow ring.

Something is definitely wrong with that!

I had the same issue when I clean installed 14971, but I noticed it only a couple of days after installing, so I was already back on Fast ring yesterday.

lmod said:

My "Insider" system has a 2GB recovery partition since updating to Build 14986. Windows Disk Management reports that the "Recovery Partition" (which has not had a drive letter allocated to it) has 100% free space. Mini-Tool Partition Wizard Free (9.1) reports it is 48% used.
Is this something that has been added to facilitate the 'incremental' updating process?
Anyone else seeing this?
Feedback submitted.

New one here as well, 1.98 GB

lmod said:

No, this is new, A 450MB "System Reserved" partition has always been present. This drive (SSD) has only ever had Insider builds installed on it. OS that is, I use the Insider system almost all the time, so I have dozens of programs/apps installed on the drive.

Yup - same here

CountMike said:

Same happened here, I got rid of old recovery partitions but new one, 1.97GB was made. It's much smaller than before (25+GB).

f14tomcat said:

@IMod

Disk Management will always show 100% free for a non-lettered partition or a partition that is off-line. That's normal. MiniTool goes in thru the backdoor and reports proper usage. All normal. The 1.97GB recovery is a bit of a mystery.

Using MiniTool, here is the content of that 1.97 (2.0) Recovery Partition. Maybe someone familiar with Winre.wim could explain it.

Attachment 112804

To me that looks like the future of how they are going to install builds. The recovery partition is going to be used to boot up the machine, just as if you had plugged in a DVD / UFD to start an upgrade / new install.

This allows them to deliver the files that will be replacing your current files only, with the actual setup.exe and other stuff always residing (out of the way) on the hidden partition.

Mind you, this is my supposition, only....

Winuser said:

I just tried the time sync. I do get the error but the time and date does*reset to the correct time and date.

f14tomcat said:

Maybe some of this issue is a confusing error message. It does not say it could not sync, it says it could not get the last status of the sync. I, too, clicked update and it updated the time correctly. I had purposely set it wrong before trying.

Attachment 112805

Cool, I'll see if it works like that on my end as well.

Winuser said:

MBAE beta seems to be working. The only thing is that Edge is slow to start*and slow to open new tabs.

fjk61011 said:

I found it in the windows.old directory after restart

CountMike said:

I just kept it in case somebody finds a way to make ISO or bootable drive from it, It will be deleted soon.

I did as well, CM. In fact, I made copies of both .~BT folder and SoftwareDistribution/Download.

If my supposition above is correct, though, we're going to have to get really creative in order to make .ISOs from here on out....


For all folks having issues with MBAE / MBAM, let me report that MB 3.0 Beta had no glitches at all after upgrade. For those that haven't looked into it yet, MB 3.0 combines MBAM, MBAE, MBARW, (and technically MBAR since it continues to include the rootkit scanning that MBAM had it in) all into one product.

And if you have a valid license for MBAE, MBAM (and I think MBARW as well, but not 100% sure, as I never actually got that one) you can plug it into MB 3.0 and it will register. That means all you folks with the single-PC lifetime licenses won't have to worry - mine works just fine in MB 3.0.

HTH