Windows 8.1 and Windows Server 2012 R2 RTM released on TechNet and MSDN

Following criticism from TechNet and MSDN subscribers, Microsoft has announced plans to release the Core and Pro RTM builds for Windows 8.1 and Windows Server 2012 R2 to users of those services. Additionally, the release candidate build for Visual Studio 2013 will be provided to TechNet and MSDN subscribers.

In late August, Microsoft announced that development of the RTM builds of Windows 8.1 and Windows Server 2012 R2 had been completed. However, the company also announced it would not offer those builds to its TechNet and MSDN subscribers ahead of the Oct. 18 launch date for both operating systems. It was a decision that upset many software developers, who complained on Microsoft's Windows blog that keeping the RTM files would be a hindrance in creating apps for both operating systems.

In today's announcement, Microsoft said they are still making some final changes to Windows 8.1 before the OS reaches its general availability stage. That was part of the reason why the company did not at first wish to release the RTM versions publicly. However, a representative of Microsoft told Neowin that, in taking feedback from software developers, the company decided that it was in fact a good idea to release the RTM build to TechNet and MSDN users.

Microsoft does say that since the Windows team will be making some final adjustments to Windows 8.1 before Oct. 18. The RTM builds are for testing purposes only, the company says, and developers will still have to do some final app tweaking of their own when the GA build is released.

Source: Microsoft | Image via Microsoft

Report a problem with article
Previous Story

Nokia: Microsoft wants a 'unified brand across Lumia and other Windows' devices

Next Story

Visual Studio 2013 RC gets a few new features

134 Comments

Commenting is disabled on this article.

Can anyone tell me why I get different has values every time I run a hash calc tool? I would assume that each time I fan it on the same file, I would get exactly the same values? Wonder if I have a failing hdd...

The mail app is nice. The 3rd party apps, mostly, are awful. Microsoft needs to go Apple style and enforce a design standard. I do not care if you have 100k + apps, most of them are "info" apps or just plain weird and buggy.

Soo... Will there be a "new" rtm build on the day of GA, or is this the latest build anyone's gonna get until the next .x build comes out (e.g. Win 8.2)?

I mean, i just wasted time backing up and wiping my system and am now on the "rtm" build of 8.1... If they're going to give us a new build on Technet then I totally just wasted my time. LOL

Now that 8.1 is on Technet and MSDN I hope MS will start releasing some Windows updates for them before GA. Many of the problems relate to the Store and apps.

Good to hear that they are still tweaking 8.1 before final release in Oct. I had already two crashes on my 8.1 RTM installation, once when upgrading my AMD drivers and another time it just stalled, no message or errors. Of course this could be drivers, but I never had any issues with that system under 8.0

Maybe I missed a comment above, but will my retail key work with this ISO? I have the upgrade key that they were charging $14.99 last year.

I don't really look at this as a change of heart. Im guessing this was the plan all along. There was little legitimate reason to release 8.1 to the developers unless the tools were ready to target it. Now that they are, it is available.

So what good is this really? If they are making more changes before October 18th then we are not really getting the final version of 8.1.

patseguin said,
So what good is this really? If they are making more changes before October 18th then we are not really getting the final version of 8.1.
You read my mind.

you're never getting the final version. Windows and OSX on ship day always come with several MB of updates

They probably had a slew of people telling Microsoft they are going to cancel their subscriptions to TechNet.

Money is always a factor to get people to change their minds.

texasghost said,
They probably had a slew of people telling Microsoft they are going to cancel their subscriptions to TechNet.

Money is always a factor to get people to change their minds.

Except that Microsoft already canceled TechNet subscriptions for everyone and gave them 90 days free

mmjm said,

Except that Microsoft already canceled TechNet subscriptions for everyone and gave them 90 days free


Technically they've stopped new subscriptions. Mine is valid for 14 months still.

As previously mentioned WZT iso is identical to the Technet iso for the X64 version:

==================================================
Filename : Windows_8.1_EN-US_x64.ISO
MD5 : f104b78019e86e74b149ae5e510f7be9
SHA1 : bc2f7ff5c91c9f0f8676e39e703085c65072139b
CRC32 : 2ed09cde
SHA-256 : 23dccb255fa73ce6e93b12fefeefb7204c1681b9a343b51126d3d79f3a34bcd3
SHA-512 : 25446f98ea6cf35e95ecb0cb3ff9584e67c252d78ca0ac98f08e97d9aa62ddf537ea9c55f6e730abfa09b5759c16d4d2a6ad64ff356a62db914495f203b92807
SHA-384 : d57ce2db1b461a3c19079397ba9272651436cd8685b7f0cb8969c867c7acabfce5f7a8783ea4c6b15684a715981a1211
Full Path : J:\Windows ISO Files\MICROSOFT.WINDOWS.8.1.RTM.X64.ENGLISH.DVD-WZT\Windows_8.1_EN-US_x64.ISO
Modified Time : 8/30/2013 6:57:41 PM
Created Time : 8/30/2013 8:45:14 PM
File Size : 3,899,295,744
File Version :
Product Version :
Identical : 1
Extension : ISO
File Attributes : A
==================================================

==================================================
Filename : en_windows_8_1_x64_dvd_2707217.iso
MD5 : f104b78019e86e74b149ae5e510f7be9
SHA1 : bc2f7ff5c91c9f0f8676e39e703085c65072139b
CRC32 : 2ed09cde
SHA-256 : 23dccb255fa73ce6e93b12fefeefb7204c1681b9a343b51126d3d79f3a34bcd3
SHA-512 : 25446f98ea6cf35e95ecb0cb3ff9584e67c252d78ca0ac98f08e97d9aa62ddf537ea9c55f6e730abfa09b5759c16d4d2a6ad64ff356a62db914495f203b92807
SHA-384 : d57ce2db1b461a3c19079397ba9272651436cd8685b7f0cb8969c867c7acabfce5f7a8783ea4c6b15684a715981a1211
Full Path : D:\My Downloads\en_windows_8_1_x64_dvd_2707217.iso
Modified Time : 9/9/2013 2:22:35 PM
Created Time : 9/9/2013 2:18:06 PM
File Size : 3,899,295,744
File Version :
Product Version :
Identical : 1
Extension : iso
File Attributes : A
==================================================

the only reason why they released is, is because everyone is installing the leaked copies which could be compromised. they even stated that even though developers have the rtm, the final version is not finished,and code changes still need to be done.

Does this mean they have published the .net 3.5 updates as well for 8.1 rtm? i can't install a bunch of software built on older .net systems.

also, is the enterprise licensing being turned on so people can license enterprise versions?

Run this in cmd:

dism /online /enable-feature /featurename:netfx3 /all /source:X:\sources\sxs /limitaccess

Replace X with your dvd or mounted iso drive letter

scumdogmillionaire said,
Happy with the decision. Downloading from MSDN now. However they're really making themselves look foolish and weak with all of these cave ins lately.

how is it making them look foolish and weak? i think it shows they're finally growing up and accepting what customers really want - access to the latest and greatest.

Listening to customers is great. The problem is they're too stubborn about it. They take too drastic of a stance the first time around then they look weak when they change it.

hey guys, im downloading it off Technet now but question, how would I go about installing this exactly? Would I do it within Windows 8 or boot from usb? Also, if im using Windows 8 Pro with Media Center, does this key affect that?

Ronald Wang EIGHTS said,
Existing product key doesn't work and can't upgrade within Windows 8. So you must reinstall Windows 8.1.

No, people that get this off Technet or MSDN can request a new key and use it to upgrade or install new. Otherwise you can upgrade using a generic 8.1 key, and after the upgrade activate with original 8 key. Have done this on serveral machines already.

But do you know if I will be able to upgrade from Windows 8 Pro with Media Center to 8.1 Pro without having to do a clean install?

sjaak327 said,

No, people that get this off Technet or MSDN can request a new key and use it to upgrade or install new. Otherwise you can upgrade using a generic 8.1 key, and after the upgrade activate with original 8 key. Have done this on serveral machines already.

I see, thanks for information.
But after upgrade, do the existing programs still need to be reinstalled? Or just like windows patch?

Ronald Wang EIGHTS said,

I see, thanks for information.
But after upgrade, do the existing programs still need to be reinstalled? Or just like windows patch?

The upgrade retains applications, settings and data. I did the upgrade on several systems and all of the desktop applications continued to work, so did al, of the metro applications. Of course the upgrade can only be done from the same version and architecture, so you can upgrade Windows 8 pro x64 to Windows 8.1 pro x64.

egeek84 said,
But do you know if I will be able to upgrade from Windows 8 Pro with Media Center to 8.1 Pro without having to do a clean install?

I didn't try this myself (yet) but have heard that you upgrade using 8.1 generic key, activate with 8 retail key and then add wmc using add features with your 8 wmc key.

I haven't been able to do an upgrade on my machine with 8 Pro with WMC. The only options on there are Keep personal files or Keep nothing. I believe you can follow the steps to remove WMC which basically involves doing an "upgrade" to Windows 8 Pro again using your Windows 8 Pro key rather than your WMC key. I believe you'll be able to upgrade then, but I haven't tried myself.

Edited by Jeston, Sep 9 2013, 9:10pm :

jeston said,
I haven't been able to do an upgrade on my machine with 8.1 Pro with WMC. The only options on there are Keep personal files or Keep nothing. I believe you can follow the steps to remove WMC which basically involves doing an "upgrade" to Windows 8 Pro again using your Windows 8 Pro key rather than your WMC key. I believe you'll be able to upgrade then, but I haven't tried myself.

I did upgrade one 8 WMC machine to 8.1 using upgrade, (using the generic 8.1 key), after the upgrade (apps, settings and files, so full upgrade), I activated using the original 8 retail key. The next step would be to add wmc back using the wmc key, that step I haven't tried yet.

francescob said,

What about the proper upgrade package, the one that will be
also distributed through the Windows Store?


That, I imagine, is still due for release in October as previously scheduled in recent announcements.

Actually RTM doesn't mean much other than it's a line in the sand where it is now a supported product. Even Windows 7 has updates and changes to code, currently, years after "RTM". The only difference here is that RTM is a supported release starting point from where you can expect the patches to actually function.

Waiting for "spit'n'polish" for street date is meaningless and irresponsible for MSDN and Technet, as I've said all along, since RTM was provided to OEMs and certainly patchable. Now developers can actually test their products on supported, final code. Microsoft came to their senses. Great... finally a smart move.

File Name: en_windows_8_1_x64_dvd_2707217.iso
Languages: English (United States)
Version: x64
SHA1: BC2F7FF5C91C9F0F8676E39E703085C65072139B

File Name: en-gb_windows_8_1_x64_dvd_2707421.iso
Languages: English (United Kingdom)
Version: x64
SHA1: 42458E48CECEBAB8BF5D58220478FDA42B0D2990

32-bit:

File Name: en_windows_8_1_x86_dvd_2707392.iso
Languages: English
SHA1: 802CFCD3A411D99C097EA7E747F0B6697F9BDAC4

File Name: en-gb_windows_8_1_x86_dvd_2707543.iso
Languages: English
SHA1: 7CD38ECE3D86339BC0BFEF4D4FAC6C5975248383

OrsenPike said,
File Name: en_windows_8_1_x64_dvd_2707217.iso
Languages: English (United States)
Version: x64
SHA1: BC2F7FF5C91C9F0F8676E39E703085C65072139B

File Name: en-gb_windows_8_1_x64_dvd_2707421.iso
Languages: English (United Kingdom)
Version: x64
SHA1: 42458E48CECEBAB8BF5D58220478FDA42B0D2990

Where do you find the HASH codes on the file? I was always curious about that.

OrsenPike said,
File Name: en_windows_8_1_x64_dvd_2707217.iso
Languages: English (United States)
Version: x64
SHA1: BC2F7FF5C91C9F0F8676E39E703085C65072139B

File Name: en-gb_windows_8_1_x64_dvd_2707421.iso

snip.

checked SHA1 with WZT confirmed 100% matched with en_us x64

Dane said,

Where do you find the HASH codes on the file? I was always curious about that.


Click "Details" under the title (left of the product keys and download button).

fobban said,

Click "Details" under the title (left of the product keys and download button).

If I have the ISO, I right click then details?

Dane said,

If I have the ISO, I right click then details?


Ah, no. I thought you wondered where you could see the hash on msdn.

kiddingguy said,
Great. Downloading now... not at a great speed though...

Yeah same. Not looking forward to trying to download Hyper-V Server 2012 tomorrow during peak times either.

Good news (for those interested)! They also release Windows Embedded 8.1 Industry Enterprise and Windows Embedded 8.1 Industry Pro on MSDN.

Bamsebjørn said,
Good news (for those interested)! They also release Windows Embedded 8.1 Industry Enterprise and Windows Embedded 8.1 Industry Pro on MSDN.

They almost have more product renames for that than Citrix do for their products!

Nelson: haaa-haaa
Same hashes as WZOR iso-s
This is so funny it's killing me!!!
Meaning that Sicromoft guys were just thinking that aaah f**k it, they have it anyway...

Made my day

An issue reported with the ISOs leaked was that they required a specific key be used during installation as it did not accept valid Windows 8 keys. If they are the same ISOs (which they are as the hashes match) then what is the word from Microsoft on the key to be used?

OrsenPike said,
An issue reported with the ISOs leaked was that they required a specific key be used during installation as it did not accept valid Windows 8 keys. If they are the same ISOs (which they are as the hashes match) then what is the word from Microsoft on the key to be used?

Surely that's to do with Microsoft's activation servers and not the OS itself?

It's because you need a valid Windows 8.1 key for the clean install, 8.0 key works only on upgrade/update, at least it's how it's probably meant for regular users. Of course afterwards inserting 8.0 key and activating with it works as well, since at this point you can't really identify if the OS was upgraded or a clean install was made.

At least that's what my logic says

Interesting, people at MDL seem to suggest that the activation bits are half finished.. but I guess it was intended to be that way by Microsoft.

That doesn't make much sense. Why accept a key post install but not during install? 8.1 is a free upgrade to Windows 8 users so a valid 8 key should be fine. It is a little confusing and I can't seem to find any details for Microsoft on the matter however the links to the release note on MSDN point to a page that is not available so it looks like the MSDN guys are working a little quicker than the knowledge base gusy

OrsenPike said,
That doesn't make much sense. Why accept a key post install but not during install? 8.1 is a free upgrade to Windows 8 users so a valid 8 key should be fine. It is a little confusing and I can't seem to find any details for Microsoft on the matter however the links to the release note on MSDN point to a page that is not available so it looks like the MSDN guys are working a little quicker than the knowledge base gusy

Actually the way (most users) are supposed to upgrade is by using the App store, not the iso. The ISO indeed does not accept Windows 8 Retail keys at installation or even when using the upgrade function (which is merely running setup from within Windows) but after the upgrade it does accept the original Windows 8 retail key for activation.

Of course now it dropped on MSDN, valid 8.1 retail keys are obtainable and these are accepted during installation and activation.

I think the way this should normally work is:

Upgrade 8 to 8.1 via store, no need for any keys
Install 8.1 clean, use 8.1 retail key.
Upgrade 8 to 8.1 via iso, use 8.1 generic key to install, original 8 retail key to activate.

Most users will probably use the in store upgrade and be done with it.

i_was_here said,
So theres no way to directly have a clean Windows 8.1 install with a 8.0 key?

No, you need a 8.1 key to install (use the generic, published key, which allows you to install but not activate) than after the install use a genuine 8 key to activate.

Hmm about time. It's odd having all my friends with MSDN / TechNet access using a leaked build for some testing and stuff.

techbeck said,
Should of been released already and shouldn't of even been delayed.

If I remember correctly MSDN and TechNet never got RTM builds of older Windows releases right away either, there's always been a gap/delay between when OEMs got it and when developers did.

GP007 said,

If I remember correctly MSDN and TechNet never got RTM builds of older Windows releases right away either, there's always been a gap/delay between when OEMs got it and when developers did.

Yea, but then again you never had apps like Win8 that needed to be tested. Its those people that were complaining and with MS making a statement...developers developers developers...you would think giving RTM to devs would be a no brainer.

techbeck said,
Should of been released already and shouldn't of even been delayed.

If it didn't depend on the a large number of server side integration, from outlook.com and profiles for MS Account features to even the server changes for Xbox Music/Video that coordinate with Xbox One as well.

Ideally the server side changes should have been in place sooner. However the designed timeframe was October to give the team times to coordinate, no matter how early the 8.1 bits were ready.

It has already created confusion and problems with leaked copy users having App issues and errors building up in the event viewer that are the result of the backend server service not being enabled, migrated, integrated, updated.

Windows 8 is unlike even Windows 7 that is a localized set of bits that have little server side dependence.

GP007 said,

If I remember correctly MSDN and TechNet never got RTM builds of older Windows releases right away either, there's always been a gap/delay between when OEMs got it and when developers did.


True but, in the past, MS also stated right away that the builds were coming soon; this time the original statement said that MSDN and TechNet users were going to receive them at the same time of GA.

smooth_criminal1990 said,
Right after I lose access to my university MSDNAA *rages*

Give it an hour and they will be leaked. If they have not been already.

techbeck said,

Give it an hour and they will be leaked. If they have not been already.

They were leaked by WZOR what 2 weeks ago?. Same hashes..

smooth_criminal1990 said,
Right after I lose access to my university MSDNAA *rages*
You do realise that if you have Win8 already you will get 8.1 through windows update for free??

Why not?
We got Windows 8. I don't see a reason we won't get something that will be released as a free update since we got Win8 in the first place.

MSDNAA doesn't get RTM builds ahead of time, only Previews/RC and the final version - well after it hits retail at that.

This is a good move on Microsoft's part. I wish I had been a little patient and waited a week or so. But at least I can get the RTM directly from MS and with a new product key.

Can someone remind me what the N versions are? Are they the ones without the Media Player and related codecs, or the one without IE?

devHead said,
This is a good move on Microsoft's part. I wish I had been a little patient and waited a week or so. But at least I can get the RTM directly from MS and with a new product key.

Can someone remind me what the N versions are? Are they the ones without the Media Player and related codecs, or the one without IE?

It was that way with Windows 7, and I think it's only for some international versions (probably due to certain laws). The N would be the one that would allow for other media codecs to be used, not sure if it includes excluding IE, but I know it excludes Windows Media Player.

Tarrant64 said,

It was that way with Windows 7, and I think it's only for some international versions (probably due to certain laws). The N would be the one that would allow for other media codecs to be used, not sure if it includes excluding IE, but I know it excludes Windows Media Player.


Correct, it is for EU and it includes IE but comes with an automatic browser ballot update download.

Shadowzz said,

Correct, it is for EU and it includes IE but comes with an automatic browser ballot update download.

Actually the browser ballot screen is applicable to all editions of Windows 8.1 and is delivered using Windows update. the N versions are severly crippled and exlude Windows media player and most of it's codec support. However, one can download it from Microsoft, effectively turning it into a normal Windows version. i suppose the N versions are the ones that no OEM preloads on their machines, and nobody buys them at retail.

Shadowzz said,
I never encountered N version in the wild afaik. With other Windows editions I thought it was an optional download in EU region.


I did install Windows 8 pro N last year (it was the first rtm version that leaked . As far as I know the browser ballot screen is optional on all versions of Windows in Europe, it is trivial to not install it and hide it.

Curious, I'm assuming since this is officially RTM that, while there will be last minute changes before it goes public, any install of the RTM available now won't require you to re-install all of the applications later (as was the case with Beta). If that's the case, I'm happy to utilize my MSDN/TechNet now.

Tarrant64 said,
Curious, I'm assuming since this is officially RTM that, while there will be last minute changes before it goes public, any install of the RTM available now won't require you to re-install all of the applications later (as was the case with Beta). If that's the case, I'm happy to utilize my MSDN/TechNet now.

I don't think that's the case at all, it probably just means some patches get pushed out via WU and nothing more. People seem to think they're going to have some all new build coming out for GA, I doubt it. Heck I bet most of the work they're talking about doing is to the apps that will come with it and not so much the OS itself.

GP007 said,

I don't think that's the case at all, it probably just means some patches get pushed out via WU and nothing more. People seem to think they're going to have some all new build coming out for GA, I doubt it. Heck I bet most of the work they're talking about doing is to the apps that will come with it and not so much the OS itself.

You got it right, RTM build that is available on MSDN now, is the same one that leaked and that went to OEM's and it will be the same one that goes out at GA.

There is no reason to compile a new build, all the updates that are being made will be delivered through Windows Update. I believe the RTM build will simply remain at 9600.16384 and will not even see the minor build number being increased.

What a dick move to recant so late. Two clients went ahead with 2012 installs cause they thought they were over a month away from the new bits.

They still are.
MSDN licenses are not meant to be used on production systems, only systems from testing so regardless if they had access to 8.1 now or in a month, they still could only use it for testing.

I'm not talking about the license, I'm talking about the installation bits. Licensing is with their SA keys...

Worst case they can 'test' for a month, then use a production key.

yet another fine reason that you should wait until the final release prior to updating. strange that they would release it to manufacturers if they still expected so many changes to be made to the release.

This is the biggest issue with this whole debacle. They called it an RTM when it isn't really an RTM in the true (historic) meaning of the world. If they are not using it as a baseline build then it isn't an RTM it is still a test release. RTM is a label for a finished product. What they are saying is they are having an RTM for OEMs and an RTMv2 for IT professionals and end users. It was a stupid mistake on Microsoft's part calling it an RTM if they were not actually finished with the product.

OrsenPike said,
This is the biggest issue with this whole debacle. They called it an RTM when it isn't really an RTM in the true (historic) meaning of the world. If they are not using it as a baseline build then it isn't an RTM it is still a test release. RTM is a label for a finished product. What they are saying is they are having an RTM for OEMs and an RTMv2 for IT professionals and end users. It was a stupid mistake on Microsoft's part calling it an RTM if they were not actually finished with the product.
Ermm..the RTM build is the build they released to manufacturers. How is that wrong?
They've always had patches ready before consumers get their hands on the build. If fact when is Windows ever finished? As XP is still being patched every month I would argue, that by your definition, they haven't reached RTM yet as they're still fixing it.

@mog0, RTM has always meant the "gold master" release that is used as a baseline for manufactuers, developers, it professionals and similar to work from. Never in the history of Windows has the OEM and gold master release been different until now. Of course there are post RTM patches. Nobody is saying that Windows is perfect however there needs to be a line drawn in the sand when a product is feature complete and stable enough to be deemed as "production ready". Once that line is drawn we have a stable base from which we can develop and test against that we know is the same as everybody else.

The issue here is that Microsoft have been hugely inconsistent with how things have always worked in the Windows release cycle and it came as quite a shock to pretty much everyone. Also a lot of people and companies pay a lot of money in order to get "before pulic release" access to Windows via their MSDN and Technet subscriptions and Microsoft's attitude was that people paying for this service no longer had that benefit. While you might not see it as an issue a hell of a lot of people did. So many that Microsoft have done a 180 on the matter and buckled to their demands.

Just to be totally clear nobody was expecting access the same day that Windows went RTM. There has always been a delay of a couple of weeks before it hits MSDN/Technet however until yesterday Microsoft said that it would not be available to MSDN/Technet subscribers before the puclic release on October 17/18.

ChuckFinley said,
So why bother even say its RTM. RTM has ALWAYS been the defacto. *******! lol. ElementryOS for the win!

We never got RTM right away, even in the past, maybe MSDN and TechNet did though but that's a minority in the overall Windows world. People who have run the leaked RTM build have said that apps don't work from time to time or not at all so I think there's still a bit more work to do on the server side because many of those apps connect to some service, like Xbox Music, or they're still updating the apps as well right up till GA and wanted to hold off till those were ready as well?

What ChuckFinley is saying is that in the past RTM has always meant a solid, final base on which to test/deploy. Yes there are updates, often on public release day, however developers and IT professionals have always had slightly earlier access to the RTM build. This changed with 8.1 and there was a lot of negative feedback which is why Microsoft have done a 180 on the matter. The frustrating thing is that they have called a build the RTM and released it to OEMs for deployment ready for the general release however they are saying that the RTM isn't really an RTM in the true sense of the word. They could have avoided a lot of negative press in the tech world by not calling it RTM but an "OEM Base Build" or similar and then releasing an RTM when they really have an RTM. While the M does mean manufacturing it has historically been known as a release to technical professionals as well which is where all of the angst has been coming from.

@GP007 this isn't so much about availability of the build but that fact that the RTM is not the final build. MSDN/Technet have always got the RTM a few weeks after it actually hit RTM but the build we got was always the same build OEMs got. This is not the case with 8.1 which is frustrating as it means the RTM is not really the RTM. What will happen when the *real* RTM comes out? Will OEMs stick to the first RTM they got or will they use the newer RTM? It is annoying and inconsistent. If they wanted to change what they call the builds they should have just done that rather than being inconsistent with their terminology.

OrsenPike said,
@GP007 this isn't so much about availability of the build but that fact that the RTM is not the final build. MSDN/Technet have always got the RTM a few weeks after it actually hit RTM but the build we got was always the same build OEMs got. This is not the case with 8.1 which is frustrating as it means the RTM is not really the RTM. What will happen when the *real* RTM comes out? Will OEMs stick to the first RTM they got or will they use the newer RTM? It is annoying and inconsistent. If they wanted to change what they call the builds they should have just done that rather than being inconsistent with their terminology.

Hold on, I'm pretty sure the build you're going to get is the same build OEMs got already. I was just commenting on why they might have delayed giving it out to developers a bit more because they wanted to keep working on the core apps/services side of things, not so much the OS itself.

We already know that day 1 patches are going to be coming, they've said as much, but that's not a surprise is it? OEMs will find problems I'm sure and developers will probably as well, I wouldn't be surprised if developers already get the updates pushed out to them specifically and not have to wait till GA comes to get them.

ChuckFinley said,
So why bother even say its RTM. RTM has ALWAYS been the defacto. *******! lol. ElementryOS for the win!

This was 'true' when the OS didn't depend on, use, integrate with server side services.

Even non-Modern UI users that use a MS Account DEPEND on the server side features to be enabled and updated. So the base OS can be 'RTM' and if the server services have not been updated, migrated, or enabled it creates problems/confusion.

(Go look at the Neowin forums of 8.1 leaked users complaining about errors and App problems that are failing due to the server side functionality not being implemented.)

There are going to be day 1 patches for Windows 8.1, but more importantly, they are based on and waiting to coordinate with the server side features.

(Even just one App was affected by Xbox Music server features that were turned on yesterday to support the changes in 8.1.)

@Mobius Enigma, I noticed some issues with the add/remove Windows features in 8.1 which I assume is down to the servers not being fully 8.1 compatible yet.

Lol these two people claim such strong positions about elementary OS, but they don't even know how to spell its name.

You can minimize an application in elementary OS. They just don't allow you to do it from the title bar. Click the app icon in the dock to do that.

So they finally caved in.... It was pretty stupid not to release it to these people who pay quite a bit of money for it (maybe not technet...)

I don't remember ever seeing anything official saying that it wouldn't hit MSDN early so I don't see why you would say that they caved in.

I don't remember ever seeing anything official saying that it wouldn't hit MSDN early so I don't see why you would say that they caved in.

You're joking, right? Their blog post said that MSDN and Technet subscribers would be receiving the bits when it became available to the General Public on October 18, rather than earlier which has historically what they've done for paying subscribers. Where have you been the past 2 weeks, bro?

jakem1 said,
I don't remember ever seeing anything official saying that it wouldn't hit MSDN early so I don't see why you would say that they caved in.

http://blogs.windows.com/windo...indows-8-1-for-release.aspx

While our partners are preparing these exciting new devices we will continue to work closely with them as we put the finishing touches on Windows 8.1 to ensure a quality experience at general availability on October 18th. This is the date when Windows 8.1 will be broadly available for commercial customers with or without volume licensing agreements, our broad partner ecosystem, subscribers to MSDN and TechNet, as well as consumers.

Rudy said,
So they finally caved in.... It was pretty stupid not to release it to these people who pay quite a bit of money for it (maybe not technet...)

As mentioned before, there are server side features that are still being migrated and App changes that currently affects the functionality of 8.1.

People with leaked 8.1 builds are complaining that they are getting App errors and event errors as the server side features are not fully available.

The decision to release a 'free' update to users in October was not to 'punish' anyone, it was a designed timeframe to coordinate with the ancillary back end features that Windows 8.1 depends on.

Just yesterday Microsoft was able to release the new Xbox Music server services features that the 8.1 App depends on.


Microsoft could have dumped 8.1 at the end of August, but the user complaints of things not working because the backend server features were not in place would have created a HUGE mess.

Even with the TechNet release, Microsoft is 'risking' a backlash from less informed users that will complain of the same event errors and App problems waiting for the backend to be in place.

Windows 8 is not like previous generations of Windows in that it directly uses online server services for 'profiles' and other optional functionality through the MS Account integration. If they are not fully enabled or completed, even the non-Metro/Modern users will be affected.