Technical Preview 10525

[Big Al[_5_]]

I've still got on my VM the Win 10 TP and it updated to 10525 build. Supposedly to get better control of colors in
taskbar and title bars?

Will or have these updates seen it to the release version. I have a release copy on another PC and don't see any
diff. So I'm guessing it's already in the release??

[Brian Gregory]

On 20/08/2015 23:27, Big Al wrote:
> I've still got on my VM the Win 10 TP and it updated to 10525 build.
> Supposedly to get better control of colors in taskbar and title bars?
>
> Will or have these updates seen it to the release version. I have a
> release copy on another PC and don't see any diff. So I'm guessing it's
> already in the release??
>

Not in release version AFAIK.

I found 10525 to be a disaster.

Loads of Google processes to do with Google Chrome (which I installed)
just crashed on start up.

--

Brian Gregory (in the UK).
To email me please remove all the letter vee from my email address.

[Big Al[_5_]]

Brian Gregory wrote on 8/20/2015 10:19 PM:
> On 20/08/2015 23:27, Big Al wrote:
>> I've still got on my VM the Win 10 TP and it updated to 10525 build.
>> Supposedly to get better control of colors in taskbar and title bars?
>>
>> Will or have these updates seen it to the release version. I have a
>> release copy on another PC and don't see any diff. So I'm guessing it's
>> already in the release??
>>
>
> Not in release version AFAIK.
>
> I found 10525 to be a disaster.
>
> Loads of Google processes to do with Google Chrome (which I installed) just crashed on start up.
>
Luckily I don't have issues. I got rid of Chrome so it's not an issue. I saw another post that 10525 was buggy. I
did a backup before doing it in case.. :-)

[. . .winston[_2_]]

Big Al wrote on 08/20/2015 6:27 PM:
> I've still got on my VM the Win 10 TP and it updated to 10525 build.
> Supposedly to get better control of colors in taskbar and title bars?
>
> Will or have these updates seen it to the release version. I have a
> release copy on another PC and don't see any diff. So I'm guessing it's
> already in the release??
>

No...10525 Insider Build hits the Fast Ring first, Slow Ring second. If
acceptable the release version receives it last. If not acceptable, the
process is repeated - Newer Insider Builds (Fast, Slow, etc.).

There is no guarantee, either, that builds pushed down to Insiders will
be bit-identical to updates to the release version.



--
...winston
msft mvp windows experience

[Big Al[_5_]]

.. . .winston wrote on 8/21/2015 12:38 AM:
> Big Al wrote on 08/20/2015 6:27 PM:
>> I've still got on my VM the Win 10 TP and it updated to 10525 build.
>> Supposedly to get better control of colors in taskbar and title bars?
>>
>> Will or have these updates seen it to the release version. I have a
>> release copy on another PC and don't see any diff. So I'm guessing it's
>> already in the release??
>>
>
> No...10525 Insider Build hits the Fast Ring first, Slow Ring second. If acceptable the release version receives it
> last. If not acceptable, the process is repeated - Newer Insider Builds (Fast, Slow, etc.).
>
> There is no guarantee, either, that builds pushed down to Insiders will be bit-identical to updates to the release version.
>
>
>
That kinda falls in line with my experience. I knew or at least thought that Insiders were beta testers (if you want
to use those terms).

[Paul]

Big Al wrote:
> . . .winston wrote on 8/21/2015 12:38 AM:
>> Big Al wrote on 08/20/2015 6:27 PM:
>>> I've still got on my VM the Win 10 TP and it updated to 10525 build.
>>> Supposedly to get better control of colors in taskbar and title bars?
>>>
>>> Will or have these updates seen it to the release version. I have a
>>> release copy on another PC and don't see any diff. So I'm guessing it's
>>> already in the release??
>>>
>>
>> No...10525 Insider Build hits the Fast Ring first, Slow Ring second.
>> If acceptable the release version receives it
>> last. If not acceptable, the process is repeated - Newer Insider
>> Builds (Fast, Slow, etc.).
>>
>> There is no guarantee, either, that builds pushed down to Insiders
>> will be bit-identical to updates to the release version.
>>
>>
>>
> That kinda falls in line with my experience. I knew or at least
> thought that Insiders were beta testers (if you want to use those terms).
>

I think the right term for Insider users, would be "Alpha testers".

Regular (home) users, when they get that release, will be "Beta testers".

"Release grade" users are Enterprise customers.

Paul

[Neil]

On 8/21/2015 12:01 PM, Paul wrote:
> Big Al wrote:
>> . . .winston wrote on 8/21/2015 12:38 AM:
>>> Big Al wrote on 08/20/2015 6:27 PM:
>>>> I've still got on my VM the Win 10 TP and it updated to 10525 build.
>>>> Supposedly to get better control of colors in taskbar and title bars?
>>>>
>>>> Will or have these updates seen it to the release version. I have a
>>>> release copy on another PC and don't see any diff. So I'm guessing
>>>> it's
>>>> already in the release??
>>>>
>>>
>>> No...10525 Insider Build hits the Fast Ring first, Slow Ring second.
>>> If acceptable the release version receives it
>>> last. If not acceptable, the process is repeated - Newer Insider
>>> Builds (Fast, Slow, etc.).
>>>
>>> There is no guarantee, either, that builds pushed down to Insiders
>>> will be bit-identical to updates to the release version.
>>>
>>>
>>>
>> That kinda falls in line with my experience. I knew or at least
>> thought that Insiders were beta testers (if you want to use those terms).
>>
>
> I think the right term for Insider users, would be "Alpha testers".
>
> Regular (home) users, when they get that release, will be "Beta testers".
>
> "Release grade" users are Enterprise customers.
>
"Alpha testers" are typically in-house developers that test the code
prior to presenting it to "beta testers", typically a closed-group of
volunteers. By the time software is presented for non-programmers to
test (i.e. "Insiders"), it's been through quite a bit.

Perhaps the home users that have already loaded W10 are "early
adopters", or "bleeding edgers", and those that will cling to W7 are
just ex-XP skeptics. ;-)

--
Best regards,

Neil

[. . .winston[_2_]]

Paul wrote on 08/21/2015 12:01 PM:
> Big Al wrote:
>> . . .winston wrote on 8/21/2015 12:38 AM:
>>> Big Al wrote on 08/20/2015 6:27 PM:
>>>> I've still got on my VM the Win 10 TP and it updated to 10525 build.
>>>> Supposedly to get better control of colors in taskbar and title bars?
>>>>
>>>> Will or have these updates seen it to the release version. I have a
>>>> release copy on another PC and don't see any diff. So I'm guessing
>>>> it's
>>>> already in the release??
>>>>
>>>
>>> No...10525 Insider Build hits the Fast Ring first, Slow Ring second.
>>> If acceptable the release version receives it
>>> last. If not acceptable, the process is repeated - Newer Insider
>>> Builds (Fast, Slow, etc.).
>>>
>>> There is no guarantee, either, that builds pushed down to Insiders
>>> will be bit-identical to updates to the release version.
>>>
>>>
>>>
>> That kinda falls in line with my experience. I knew or at least
>> thought that Insiders were beta testers (if you want to use those terms).
>>
>
> I think the right term for Insider users, would be "Alpha testers".
>
> Regular (home) users, when they get that release, will be "Beta testers".
>
> "Release grade" users are Enterprise customers.
>
> Paul

It's more like this

Pre-Alpha - Internal (Development, select employees)
Alpha - Same as above, larger employee sample
Beta - Same as Alpha plus Insiders (Fast Ring)
Release Candidate - Same as Beta, Insiders (Fast and Slow Ring)
RTM version - Internal, Insider Fast and Slow Ring, and
Consumers/SMB/Enterprise



--
...winston
msft mvp windows experience

[Steve Silverwood [KB6OJS]]

On Fri, 21 Aug 2015 03:19:28 +0100, Brian Gregory
> wrote:

>I found 10525 to be a disaster.

Worked okay for me.

>Loads of Google processes to do with Google Chrome (which I installed)
>just crashed on start up.

Were you using the 64-bit version of Chrome? That has known problems
in 10525 and the newer 10532. The 32-bit version works fine.

[Steve Silverwood [KB6OJS]]

On Thu, 20 Aug 2015 23:06:40 -0400, Big Al > wrote:

>Luckily I don't have issues. I got rid of Chrome so it's not
>an issue. I saw another post that 10525 was buggy. I
>did a backup before doing it in case.. :-)

Wise move, one I highly recommend to everyone. Macrium Reflect saved
my bacon on one occasion, fortunately the problem happened right after
I made the backup so I didn't lose anything.

Why did you get rid of Chrome? It's my go-to browser of choice, has
been for long enough that I don't remember how long ago it was I
switched and stayed. :)

For the record, 10525 worked fine for me. Some cosmetics with 10532
and some settling-in issues. '32 has some problems with coming back
when the screen is turned off by the power saver in Win10, and I'm
working around that for the time being by keeping the display on all
the time on my laptop. Have to write up a complete and detailed
report of the problem for MS to digest, but other than that one
significant issue I'm happy with '32.