Announcing Windows 10 Insider Preview Build 15025 for PC Insider

f14tomcat · 03 Feb 2017

fjk61011 said:

That was sent from my phone.

On PC now. Kari's post about UUP and ISO,*or new policy.

Thanks. Somebody will read about the ISO being available and ask if that means the build is going to be released to the Slow Ring. Happens every time.......

Fabler2 · 03 Feb 2017

32-bit iso downloaded. Will mount and install. See if UI text is still in multicoloured rectangles,

rmonroe36 · 03 Feb 2017

kado897 said:

Finally 15025 up and running.

Me too. It took a clean boot after trying various other "fixes".

Rich

Fafhrd · 03 Feb 2017

Despite being an Insider Preview, the EULA is the full December 2016 version, with the regular licence terms:

Announcing Windows 10 Insider Preview Build 15025 for PC-2017_02_03_20_29_351.png

and not the usual March 2016 Insider Preview version:

Announcing Windows 10 Insider Preview Build 15025 for PC-2017_02_03_20_32_392.png

So I guess they are preparing the first 2017 Feature edition in earnest now

CountMike · 03 Feb 2017

I'm getting slightly different wording but date is same.

AndreTen · 03 Feb 2017

Restrictions are interesting! No workarounds!

Technically we are not allowed to work around limitation of UUP..

Announcing Windows 10 Insider Preview Build 15025 for PC-image.png

CountMike · 03 Feb 2017

AndreTen said:

Restrictions are interesting! No workarounds!

Technically we are not allowed to work around limitation of UUP..

A built in loophole ?

f14tomcat · 03 Feb 2017

AndreTen said:

Restrictions are interesting! No workarounds!

Technically we are not allowed to work around limitation of UUP..

From 15019 release notes. Not pertaining to UUP per se, but.... Depends, I guess.

Quicken 2016 will fail to run with an error stating .NET 4.6.1 is not installed. For Insiders familiar with Registry Editor, there is an optional workaround. Take ownership of the following registry keys and edit the “version” value to be 4.6.XXXXX instead of 4.7.XXXXX:

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\NET Framework Setup\NDP\v4\Client
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\NET Framework Setup\NDP\v4\Full
Note: Please take caution when editing the registry. Changing the wrong value can have unexpected and undesirable results.

DavidY · 03 Feb 2017

Fafhrd said:

So I guess they are preparing the first 2017 Feature edition in earnest now

Perhaps the plan is this?:

Get as many Creators Update features as possible in this build and the last few - a lot of things have been added since the start of Jan.
Use the Bug Bash thing to try and find bugs in those new features
Only introduce new features from now on if they are 100% they can be made to work with no problems.
Keep ironing out bugs until the final version

Mind you I imagine it will still take a few iterations to get UUP working.

CountMike · 03 Feb 2017

At this rate it will take years to get UUP working.