Windows 10 Build 15002 from Desktop Converter Base Images

[MrUTB]

Inside Windows was able to install Windows 10 Build 15002 from Desktop App Converter base images founded by WalkingCat.

In fact, I dunno how mrpijey going to manage this "leak".

https://t.co/q0aaxCkTUK

[ReztaNZ]

I'll take a look at this image and see what can be done about it. Did some stuff a few months back with a similar situation and managed to make a functioning ISO from the image file. But yes, Mr. Pijey may or may not want this

[ShadixAced]

The MEGA link for it is circulating over the web, just see that status : https://twitter.com/h0x0d/status/817496790303809536

But the image seems corrupted, someone tried to install it and got stuck at Setup. (54 % he said)

EDIT: Actually, MS was releasing it but cancelled it just after his publication, due to "things".

[Madonna]

The image isn't corrupt. I installed it just fine in Hyper-V

[ShadixAced]

Well, thought of it, that's why i said "seems" but thanks for telling me that it works.

[Windows OS]

Offtopic Comment

Holy crap I missed a lot in my absence. Two Windows 10 Leaks

Anyway, I wonder how many of the changes seen on 14997 will appear over here (since it should be from rs_prerelease instead of anything internal)?

[ShadixAced]

Windows OS, BuildFeed says rs_prerelease, so it's "internal" : 10.0.15002.1001 (rs_prerelease.170102-1700)
Notice that this build is the Creators Update, supposed to be launched this year.

[Windows OS]

Windows OS, BuildFeed says rs_prerelease, so it's "internal" : 10.0.15002.1001 (rs_prerelease.170102-1700)
Notice that this build is the Creators Update, supposed to be launched this year.

Whoops. That IS the Insider buildbranch. Sorry, I'm a bit rusty with this stuff. Haven't been here in a while. Post edited.

[ShadixAced]

Don't worry Windows, before it was rs2_release, so it can be normal if you mistake them.

[Lukas Marsik]

Don't worry Windows, before it was rs2_release, so it can be normal if you mistake them.

No builds from that lab were ever released.

[viper]

I found a Hyper-V .vhdx file (frankenbuild) for this one & installed it on a W8.1 x64 host for Hyper-V & after some tweaking I got it working to my satisfaction.

Here is a screenshot of the 'About Windows' window I saved.

[Matriks404]

Aaand it is released for Insiders..

https://blogs.windows.com/windowsexperi ... -15002-pc/

[ShadixAced]

It was already released for Insiders.... but got deleted just after it had being released due to a last-minute bug found.

[Windows OS]

It was already released for Insiders.... but got deleted just after it had being released due to a last-minute bug found.

So, I'm guessing that this is just one of those builds in which the changes are insignificant enough to only change what I call the "minor" build number (e.g. 14393.3 to 14393.5) to patch that bug. So, it might not be the exact build, but close enough to keep the major build number. Could someone install the build and check?

[Goldfish64]

It was already released for Insiders.... but got deleted just after it had being released due to a last-minute bug found.

So, I'm guessing that this is just one of those builds in which the changes are insignificant enough to only change what I call the "minor" build number (e.g. 14393.3 to 14393.5) to patch that bug. So, it might not be the exact build, but close enough to keep the major build number. Could someone install the build and check?

I have the officially released build installed and it is 15002.1001.

[Windows OS]

I have the officially released build installed and it is 15002.1001.

Hmm. That appears to be the EXACT same build number. Well, so much for that "last-minute bug" that caused a build to be delayed. I'm guessing now that the fix will just be an update.

[XDude]

I have the officially released build installed and it is 15002.1001.

Hmm. That appears to be the EXACT same build number. Well, so much for that "last-minute bug" that caused a build to be delayed. I'm guessing now that the fix will just be an update.

It could been a server side bug. The problem was regarding future updates. They could possibly fix the problem without even touching the code.

[Windows OS]

It could been a server side bug. The problem was regarding future updates. They could possibly fix the problem without even touching the code.

:facepalm: Why didn't I think of that!?

[ShadixAced]

Don't worry Windows, before it was rs2_release, so it can be normal if you mistake them.

No builds from that lab were ever released.

It may not be released in that branch, but was named that branch.

10.0.14894.1000 (rs_prerelease.160727-2341) was named 10.0.14894.1000 rs2_release.160727-2341 at the start of the PC.