What is the latest build of Windows Vista?

Hi. Is the build 6000 latest?

Yes, that's the RTM (Release To Manufacturer) version


--
John Barnett MVP
Associate Expert
Windows Shell/User

Web: http://xphelpandsupport.mvps.org
Web: http://vistasupport.mvps.org

The information in this mail/post is supplied "as is". No warranty of any
kind, either expressed or implied, is made in relation to the accuracy,
reliability or content of this mail/post. The Author shall not be liable for
any direct, indirect, incidental or consequential damages arising out of the
use of, or inability to use, information or opinions expressed in this
mail/post..

"ViPeRaY" <erayyilmaz@msn.com> wrote in message
news:BF905C45-BD2E-4EF3-AF11-5AFD3EF10E8A@microsoft.com...
> Hi. Is the build 6000 latest?

Yes, Build 6000 is the latest.

Technically, it is 6.0.6000.16386. Winver simply reports 6000 -- there are
loads of other ways to explore versions of various files and modules.

The build was -- allegedly --- frozen in November, the files are dated
November 2 (my birthday -- smile) and released to certain subscribers,
volume customers, valued beta testers, etc. in the last 2 weeks of November,
with the official first "event" on November 30.


The screen clip I've attached will show you a bit more detail. It's the
Properties/Details screen for Windows Mail.

Whether MS can resist fixing a few critters by updating just a few files
before sending the DVDs to their duplication contractors is a question only
Bill Gates can answer. With a January 30th "public" release date, I think
they are VERY close to their "now it REALLY is final" deadline.

None of this matters. If they do some silent or even public fixes to the
so-called RTM code, you'd get the fixes via Windows Update anyway, assuming
your copy isn't a "Frankenbuild." :-}

what's ""Frankenbuild"

"Robert Blacher" <rblacher@community.nospam> wrote in message
news:B6CC8F7A-87F8-43D0-8684-2B9FB9318A89@microsoft.com...
> Yes, Build 6000 is the latest.
>
> Technically, it is 6.0.6000.16386. Winver simply reports 6000 -- there
> are
> loads of other ways to explore versions of various files and modules.
>
> The build was -- allegedly --- frozen in November, the files are dated
> November 2 (my birthday -- smile) and released to certain subscribers,
> volume customers, valued beta testers, etc. in the last 2 weeks of
> November,
> with the official first "event" on November 30.
>
>
> The screen clip I've attached will show you a bit more detail. It's the
> Properties/Details screen for Windows Mail.
>
> Whether MS can resist fixing a few critters by updating just a few files
> before sending the DVDs to their duplication contractors is a question
> only
> Bill Gates can answer. With a January 30th "public" release date, I think
> they are VERY close to their "now it REALLY is final" deadline.
>
> None of this matters. If they do some silent or even public fixes to the
> so-called RTM code, you'd get the fixes via Windows Update anyway,
> assuming
> your copy isn't a "Frankenbuild." :-}
>
>
>
>
>
>

Well, I'm gonna pretty much punt on that one. The Frankenbuild is software
piracy (albeit not very clever piracy).

It's a partial crack of the RTM using a few files from the beta. You must
have a valid beta key to get it it work. So, it allows CPP folks to
"upgrade" to the RTM if they can get hold of an RTM copy and follow the
instructions in the "crack." My wife, a pretty experienced "user" but not a
techie, read the crack instructions and said: "What?" But, she is still
running Win XP anyway.

Two catches:

(1) It will still "drop dead" the evening of May 31, 2007, just like all the
beta builds;

(2) MS has declared nuclear war on this one, for reasons that are unclear to
me -- I've posted some messages on the Vista Team Blog explaining my
confusion. To see the declaration of war, go to:


http://blogs.msdn.com/wga/archive/20...d-monster.aspx

Those running the Frankenbuild must turn off Windows Update now to keep
their copies from being deactivated. That means they have the RTM (until
May 31) but will get no fixes, updates, etc. If *that* were my only choice,
I'd stay with the last beta I had (5744) and hope it is supported by Windows
Update when the first round of patches, driver updates, etc. start to flow.



"abcdefghijklmnopqrstuvwxyz" <cliz_yan@126.com> wrote in message
news:Ohf7FNRIHHA.1276@TK2MSFTNGP04.phx.gbl...
> what's ""Frankenbuild"
>
> "Robert Blacher" <rblacher@community.nospam> wrote in message
> news:B6CC8F7A-87F8-43D0-8684-2B9FB9318A89@microsoft.com...
>> Yes, Build 6000 is the latest.
>>
>> Technically, it is 6.0.6000.16386. Winver simply reports 6000 -- there
>> are
>> loads of other ways to explore versions of various files and modules.
>>
>> *BIG SNIP*

>> None of this matters. If they do some silent or even public fixes to the
>> so-called RTM code, you'd get the fixes via Windows Update anyway,
>> assuming
>> your copy isn't a "Frankenbuild." :-}
>>
>>
>>
>>
>>
>>
>
>