Announcing Windows 10 Insider Fast Build 16257 PC + 15237 Mobile Insider

cereberus · 22 Aug 2017

DavidY said:

It will be a shame when a new build comes out and this thread dies away.
Although the thread is probably 90% off-topic diversions, some of them have been very interesting. :)

Since little new stuff will come out on the Autumn Creators Update now, threads will go more like this as build get more robust.

(tongue in cheek)

Day 1 : installing now, nearly there x% way through

Day 2-4 : they have not fixed my really obscure bug that only I know about.

Day 5 : I am bored with this build. Did you see the blah blah blah

However, for those of us opting for the kangaroo builds (ask our Antipodean friends about Skippy).

Day : installing now, nearly there x% way through

Day 2-4 : wow, I like this new feature, don't like that one etc, I could not get that feature to work - why not etc.

Day 5 : I am bored with this build. Did you see the blah blah blah

Joking aside, we expect to see a build every week, and after a few days, we will probably go off topic all the time. Blame MS for using us nerds whom everybody in the real world knows that we have the attention span of a flea - LOL.

Kari · 22 Aug 2017

HippsieGypsie said:

Thanks again, Kari. Getting to it now.

Good! I would really appreciate the feedback.

DavidY · 22 Aug 2017

OilerNut said:

New ADK and SDK too!

Windows 10 SDK Preview Build 16267 and Mobile Emulator Build 15240 - Windows 10 Forums

Thanks for that - I may go and look for the new ADK.

Tony K · 22 Aug 2017

Kari said:

Good! I would really appreciate the feedback.

Sorry but you had an error I figured out. No space between DestinationImageFile:No spaceC:

The operation completed successfully. :)

Got your script loaded loading for updating and will run.

M4v3r1ck · 22 Aug 2017

No new build for PC? I blame the total eclipse! [emoji41]

swarfega · 22 Aug 2017

I've been bored for about 3 weeks now.

Tony K · 22 Aug 2017

@Kari

Ok, now what am I doing wrong? The esd to wim conversion went ok. I replaced (deleted) the install.esd file in Sources folder with my newly converted install.wim file (which was found in my ISO_Files folder). Here's a shot of both my monitors. Please notice the path I enter in your running script in PS.

Attachment 149996

But this is my results with that path.

Attachment 149997

Tony K · 22 Aug 2017

@Kari. Never mind I found my error. Sources folder, not Source.

tinmar49 · 22 Aug 2017

I'll be glad to get a new build, I am one of the unlucky ones with instability. Never mind, it's a record number of posts, probably.

Kari · 22 Aug 2017

HippsieGypsie said:

@Kari. Never mind I found my error. Sources folder, not Source.

No, not the Sources folder. The location of the Sources folder! For instance C:\ISO_Files, not C:\ISO_Files\Sources, as told in on-screen instructions.

Seems to be challenging to get instructions in a way that would be understood. I am totally unable to explain it any better, my English is not enough for that.

I thought that instructions were clear, would appreciate if some native English speaker would tell me how on earth I should explain what you can see in this screenshot in a more understandable way:

Announcing Windows 10 Insider Fast Build 16257 PC + 15237 Mobile-image.png

If you are updating a USB drive, just enter the drive ID (F: or Z:), or in case of dual architecture the drive letter and correct bit version folder (F:\x86 or W:\x64)
If you are updating a single bit architecture (default) ISO (#1 in screenshot, yellow highlight), enter the folder where you copied the ISO files, for instance W:\ISO or Z:\ISO_Files. Do not enter W:\ISO\Sources or Z:\ISO_Files\Sources. Just the folder where ISO content was copied to
If you are updating a dual architecture ISO, enter the folder where you copied ISO files plus the folder for correct bit architecture you are updating (#2, green highlight). For instance W:\ISO\x64 or Z:\ISO_Files\x86.