Windows 8 RTM Build 8500

[FaiKee]

WZOR had just reported that Windows 8 had already RTM'ed, build 8500.0.120623-1707 .

Google translate of WZOR report:

And so, here's what we provide:

A. Microsoft has concluded in July 2012 the final work on the creation of its new software Microsoft Windows 8 RTM.

Two. Officially, the "birth" of the final Microsoft Windows 8 RTM (Release To Manufacturing) will be announced at the annual congress of Microsoft TechReady/MGXFY13 be held from 17-20 July 2012 in Atlanta, Georgia (Atlanta, GA).

Three. The final RTM (Release To Manufacturing) build Microsoft Windows 8 will be the assembly of 8500, and while we stayed with Bill, Microsoft has managed to collect the first assembly in the RTM branch of builds win8_RTM builds: 8500.0.120623-1707

Any of the assembly appearing in the thread assembly win8_RTM can obtain the status of the final RTM build and get to the desktop computer makers ie ultimately we the users and buyers, but that it must still pass a final sign (Sign-OFF).

4. Definitive signature (sign-OFF) gold RTM assembly code Microsoft Windows 8 Consists as we reported earlier to July 21, with 99% probability that event will be held July 12, 2012.

And this time at Microsoft did not violate the mystical magic of dates and numbers, all the major events happened in the days of the summer solstice with a 18 - June 23, 2012.

According to canouna, the build 8500 exists, and atm it is a RTM Escrow, whenever a new build 8500 was compiled, the previous build 8500 would become obsolete, so we are yet to see the Final RTM Build. Just a speculation, the final sign-off RTM would be Build 8500.16385, where the minor build number 16385 comes from 2^14+1.

[FaiKee]

This space is reserved for a report about OA2.2 and OA3.0

[Motoko.]

Exciting!

[+Zlip792 MVC]

Soon shared on winunleaked, will surely test on my main desktop.. Personally waiting for SP2 for Win7.

[abysal]

Soon shared on winunleaked, will surely test on my main desktop.. Personally waiting for SP2 for Win7.

Has there been word on Win 7 SP2?

[Luka Radunovic]

This is probably true, and it is very interesting. I supposed we might see RTM in August available for download via Technet and other subscriptions. I wonder will they announce Windows 7 SP2 which i am very interested in. I supposed IE10 should be avaible soon for Windows Vista/7 users. Looking forward to SP2, IE10 and DX11.1 release for Windows 7. This is great news.

[chriscustom]

cant wait running preview now I like it better than 7...

[rfirth]

I'm hoping for a very quick Windows 9. If they want to really do well with tablets, they should adopt the Windows Phone development cycle. The entire software industry seems to have sped up their development cycles.

I wouldn't be surprised if the development cycle did speed up, now that Windows development will probably proceed in lockstep with Windows Phone development (between OS code and third party apps, they share so much code!). A Windows Phone 8.5 would at the very least line up with a service pack for Windows 8.

[George P Global Moderator]

I'm hoping for a very quick Windows 9. If they want to really do well with tablets, they should adopt the Windows Phone development cycle. The entire software industry seems to have sped up their development cycles.

I wouldn't be surprised if the development cycle did speed up, now that Windows development will probably proceed in lockstep with Windows Phone development (between OS code and third party apps, they share so much code!). A Windows Phone 8.5 would at the very least line up with a service pack for Windows 8.

I dunno about a faster Windows 9 but rather the service packs for Windows 8 might bring more with them other than just a batch of bug fixes. We could see another XP SP2 coming for example, as far as scale goes.

[FaiKee]

(I am unable to edit post#2) Recently, a MDL post reported on the coming OEM pre-installed windows 8 activation mechanism, the OP is a MDL admin and has good creditabilities:

http://forums.mydigitallife.info/threads/34580-Windows-8-preinstalled-licenses-AKA-OA2-2-and-OA3-0

Windows 8 preinstalled licenses, AKA OA2.2 and OA3.0

Latest news and summary. (20/06/2012) ***Will be updated if there are more news / changes.***

Preinstalled licenses of Windows 8 Sever will not use OA3.0. They will get OA2.2.

This is just an updated SLIC, probably the marker only (just we had at windows 7).

The reason for it is that OA2.2 can be activated offline against the SLIC in the BIOS.

OA3.0 will be a online activation method ONLY.

This was done to support offline servers.

OA3.0 will be for pre-installed client SKU's only.

How OA3.0 works:

The OEMs have two platform servers.

One is a OA3.0 key server and one a OA3.0 reporting server.

The OEMs have a master image of windows 8 that has a master key installed.

The purpose of this key is only one thing: To make w8 to be a pre-licensed version. (SLP channel)

The key is more like the old XP pre-licensed key. This key is NOT OEM specific, however, it is edition specific.

Anyway this key does not activate. It is only installed to determine the kind of licensing (SLP).

Those keys are generic.

Manufacturing process:

-The system is built. Manufacturing of complete systems.

-The system is brought online (online doesn't mean internet, just local network) and the OA3Tool is run (Either in WinPE or Full OS) and it requests a key from the key server, this generates a FULL MSDM table as output it contains the unique key for the particular system.

- A firmware specific tool is then run (could be in WinPE or DOS or whatever they wrote the flash tools for) which takes the MSDM table file and injects its key into the firmware, to NVRAM, ROMHOLE, or to wherever it is specified by the UEFI or BIOS.

The flash tool also checks to make sure that if a MSDM table does already exist, it fails.

The OEM can invalidate and delete a MSDM table with the tool, however, they have to report then this invalidation to M$ via the reporting server and then they can delete the MSDM table and over-write.

- The OS will be installed.

- Once that is complete and all testing is complete (no more hardware changes) then the OEMs can run the OA3Tool again.

This run of the OA3Tool generates the 128 bit hardware hash and reports that ALONG with the product key to the reporting server as CBR, the computer Build Report.

The tool has the ability to generate the hardware hash when there is NO network connectivity. This has been updated and wasn't possible before.

The reporting server then reports it (CBR) to M$ which sends an acknowledgement that it has received the Key+Hash. Once it has been received, then the CBR is removed from the PC.

If any hardware is changed except for external USB devices, and internal expansion cards (PCIe, PCI, SATA) then the OEM has to re-report to M$ a new hardware hash with the key or activation will fail.

Finally the OAtool is ran the last time again to lock the MSDM table to prevent any changes ever.

Then the OEMs ship the hardware to the customer.

The customer turns on the machine and goes through OOBE using the Master OA3 key which is valid for the key check but will not activate by itself.

Within 4 hours of OOBE finishing the system will automatically attempt to activate by seeing the OA3 Master Key, then reads the MSDM table for the key AND generates a NEW hardware hash and sends both to MS, the M$ servers then check to match up the hardware hash and key and if it matches (does not have to be an exact match, there is slop in there, it isn?t known what can be different) then the system is activated.

The essential requirements for OA3.0 are:

- The smBIOS UUID MUST be non-zero

- There has to be at least ONE MAC address in the system

If the above aren't there OA3 won't work and will fail.

The OEMIDs in the RSDT/XSDT tables don't matter at all. They did matter at older revisions of OA3, though (had to match those of the MSDMTable).

They no longer check those as part of OA3 only the MSDM table matters. There are no certificates or anything like that either. If you change enough hardware to require reactivation it will fail and you'll have to use the key on the machine.

OEM's pay for OS licenses based on number reported - number invalidated

An update was added later:

.I have to be careful to differentiate 'facts' from speculations.

Speculation:

First we might elaborate why M$ has 2 keys, yes two licenses at OA systems? They have the COA_SLP and the OEM_SLP licenses.

It seems the OEMs are adamant that the consumer has an additional way to (re)activate.

So they updated OEM_SLP and kept COA_SLP.

OA2.1 is an offline activation that doesn't require a hardware hash. This means this license remains as long as the BIOS exists.

OA3.0 will be invalidated if enough hardware is changed, so the key is also invalidated.

The consumer then would have to consult the OEM for reactivation.

The COA key is an additional new key which can be used to reactivate through internet by the consumer at home.

But regarding this there is lack of info and there are still some questions open.

'Fact':

I don't have any infos about 'the key on the machine'. There is a key on the machine and the consumer needs it to REactivate if he has changed enough hardware (that requires reactivation)

One attribute of MDL is to post about facts.

So I honestly have to mention:

I have no confirmation if this key is similar to COA or even a different key.

But since the OA3tool requests one from the key server I strongly guess (it's plausible) the one on the machine is different and hence similar or equally to COA licenses. And made that consumers can reactivate online at home when changed too much hardware and the original has been invalidated.

If what the post reported is legit, then apart from the OA3.0 being a more strict mechanism, it also added 2 more obvious changes:

1. In win7 and before, the OEM pre-installed windows are pre-activated, now it seems for win8 the user has to go thru on-line activation.

2. Since XP, a retail windows(box or OEM) installed when boot up, it checks on 10 devices, if less than 7 items returned with "yes", the user has to re-activate; but for OEM pre-installed windows, as long as the OS has the correct OEM files check against BIOS SLIC, the user can change any devices in whatever way, and now it seems for win8 the OS will also go thru a device check on boot-up, and the user has to re-activate if conditions is not satisfied.

Please be reminded that discussions on cracks/warez are forbidden in Neowin. :/

[Subhadip]

I'm hoping for a very quick Windows 9. If they want to really do well with tablets, they should adopt the Windows Phone development cycle. The entire software industry seems to have sped up their development cycles.

I wouldn't be surprised if the development cycle did speed up, now that Windows development will probably proceed in lockstep with Windows Phone development (between OS code and third party apps, they share so much code!). A Windows Phone 8.5 would at the very least line up with a service pack for Windows 8.

Yes, OS X has doubled down to a yearly schedule, Linux distros are executing semi-yearly, Android / iOS are yearly too. Remember that Windows is now competing directly with all of these.

MS definitely have to speed up, the old three yearly schedule simply won't do. I would be expecting Windows 9 by mid-2014 latest, maybe a Windows 8.5 next year.

[TheLegendOfMart]

RTM so soon?

The OS feels unfinished :/

I wish I could afford a Mac, I hate the way Windows is going.

[.Neo]

Yes, OS X has doubled down to a yearly schedule, Linux distros are executing semi-yearly, Android / iOS are yearly too. Remember that Windows is now competing directly with all of these.

Personally I like the notion of having smaller yearly OS X releases. But then again Apple is only charging us ?16. For Microsoft it would mean seriously rethinking their business model.

[TheLegendOfMart]

Apple charges less because they make their margin on the hardware, Microsoft doesn't sell machines so makes their money on the software hence the pricing.

[.Neo]

Apple charges less because they make their margin on the hardware, Microsoft doesn't sell machines so makes their money on the software hence the pricing.

Hence the reason I said Microsoft would have to rethink their business model. They don't have to drop all the way down to ?16, but it's unlikely many are willing to pay ?150 a year for a new Windows release. Keep in mind I'm talking retail prices here.

[TheLegendOfMart]

Why would they knock out a new version of Windows every year, traditionally its been every 3 years, a little bit more in some cases.

They aren't under any pressure from Linux or OSX, they still have the largest market share.

[.Neo]

Why would they knock out a new version of Windows every year, traditionally its been every 3 years, a little bit more in some cases.

They aren't under any pressure from Linux or OSX, they still have the largest market share.

Except Windows isn't facing OS X alone. Within the tablet space it's also directly competing with iOS which does see annual free updates and is currently market leader. Holding on to a three-year cycle could mean Microsoft is unable to respond quickly enough to new developments. Something we've seen happening the last few years.

[rfirth]

Why would they knock out a new version of Windows every year, traditionally its been every 3 years, a little bit more in some cases.

They aren't under any pressure from Linux or OSX, they still have the largest market share.

First, Microsoft is hoping to be competitive with Windows 8 in the tablet space. The iPad gets yearly upgrades. Second, WP8 shares the same kernel and WinRT app model. Changes to Windows Phone would affect Windows 8, and Windows Phone will likely be receiving at least yearly updates.

I'm thinking Windows 8.5 (or Windows 8 SP1) in 2013 and Windows 9 in 2014, to match WP8.5 in 2013 and WP9 in 2014.

[+Zlip792 MVC]

Has there been word on Win 7 SP2?

From WZOR, it will be in March 2013.

[0nyX]

I agree with everyone saying that this is too fast and that the OS feels unfinished.I sure hope that on the builds that were not given to public there has been some major work going on coz as far as i am concerned the current state of RP needs a lot of work.

Also i hope that they already have some new and finalized versions of many metro apps waiting to be released with the RTM because many of the current metro apps in terms of features and stability are facing problems.

So time will tell

[.Neo]

The current state of the default Metro apps in Windows 8 is indeed saddening.

[dafin0]

The current state of the default Metro apps in Windows 8 is indeed saddening.

yeah the apps that have been shown so far are pretty lacking but as for almost everything else it seams ready (would like new desktop icons :/).

Anyways i tend not to use 'apps' in Windows 8 so not a big problem for me and im sure other people/companies will make some nice apps to replace the default ones

[.Neo]

If a mail client needs a splash screen because it takes for ever to load you know something's wrong. I'm really hoping they'll fix that.

[Guest]

I wonder if Microsoft feel safer in releasing everything a little less polished (thinking mainly stock Metro apps) because they know they have a really easy way to push out updates for them with the store app.

Or maybe they really did get a lot of work in, more than we expected between the CP and now.

[dafin0]

If a mail client needs a splash screen because it takes for ever to load you know something's wrong. I'm really hoping they'll fix that.

for me its not so much the speed because even on my 4 year old budget dell laptop they all start in less than a second, its more the little things i find missing like a delete all button for junk mail in the mail up... yeah not the best example i know but that was the most recent thing i noticed