Readying Windows 8.1 for release (UPDATED)

Readying Windows 8.1 for release (UPDATED)

Readying Windows 8.1 for release (UPDATED)

  • Comments 106
  • Likes

We’ve hit an important milestone for Windows and for Microsoft—just 10 months after delivering on a bold, generational change in computing with Windows 8, our team is proud to share that we have started releasing Windows 8.1 and Windows RT 8.1 to our hardware partners. In many ways, this marks a new day at Microsoft, reflecting a number of rapid release firsts. Thanks, in part, to customer feedback and an unparalleled level of collaboration across product teams, Windows 8.1 is a important update. We have delivered in a very short time an update to the OS that will bring an even greater unified experience for our customers. As we consider the code we just handed off, and the new intuitive and fluid computing experience it provides - anytime, anywhere, across all devices – we’re confident we made the right bet in continuing our vision and following through on our commitment to rapid innovation and responsive engineering.

In the past, the release to manufacturing (RTM) milestone traditionally meant that the software was ready for broader customer use. However, it’s clear that times have changed, with shifts to greater mobility and touch as well as the blurring of work and personal lives. As such, we’ve had to evolve the way we develop and the time in which we deliver to meet customers with the experience they need, want and expect. We’ve had to work closer to our hardware partners than ever before. Reaching this milestone is about optimizing the overall experience for our customers. Our hardware partners are in a position to prepare the wide array of innovative devices our customers can expect later this fall - just in time for the holidays. Over the next several months we’ll see beautiful, powerful devices, from the smallest tablets to the most lightweight notebooks to versatile 2-in-1s, as well as industry devices designed for business.

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.

On behalf of the Windows engineering team, we want to thank you for joining us on this journey. So many people rely on Windows in so many ways, and so we thank you for your participation in previewing the product, for your feedback, for your contributions and for your support. You have helped us make Windows 8.1 great for everyone!

We are super excited to see Windows 8.1 help deliver the next generation of devices and a one-of-a-kind experience that’s in sync with the way you live - at home, at work, and on the go.

UPDATE 9/9 10:00am PST:

Based on the feedback from you and our partners, we’re pleased to announce that we will be making available our current Windows 8.1 and Windows 8.1 Pro RTM builds (as well as Windows Server 2012 R2 RTM builds) to the developer and IT professional communities via MSDN and TechNet subscriptions. The current Windows 8.1 Enterprise RTM build will be available through MSDN and TechNet for businesses later this month. For developers, we are also making available the Visual Studio 2013 Release Candidate, which you can download here. For more on building and testing apps for Windows 8.1, head on over to today’s blog post from Steve Guggenheimer.

You must be logged in to comment. Sign in or Join Now
  • With Nokia Purchase, windows will grow more in my point of view. All apps are now becoming available on Windows Devices as well and developers are now moving towards windows platform. Official Barclays League App is also out for Football lovers

  • Just downloaded and installed the Windows 8.1 RTM on a Lenovo U430 (new machine with a Haswell processor) and nothing seemed to work. The base OS seemed to work fine, but Visual Studio 2012 and many other applications no longer run. They all give the same error message, "{App Name} has stopped working" and closes. I tried reinstalling Windows 8.1 and the same problem. Even Intel driver software give this error. Windows 8 apps run fine, but who uses those? I have searched the internet and I am not the only one with this problem. It was a problem with the Preview as well. This issue makes Windows 8.1 unusable. Please fix this issue.

  • avel
    0 Posts

    IDK where I can ask it else:


    Really, the core of your currect style is Win logo in the center bottom  With this you submit to dumb public opinion and pinching it to the old corner... That completely fail your fresh but strict style! Please listen to me.

    Other icons on the bar can be arrange on both sides of the start button with center alignment. Thus I suggest to bring Left and Right groups of icons in user interface conception, differ in function.

  • Thank you for listening to all our rants and deciding to provide early access!

    One small annoyance: I already cancelled my subscription and bought individual licenses for the software I need. Without early access there was no reason for me to pay extra for a subscription. Now I have to see if I can return the software I bought and then re-buy my subscription. It will cost me a bit of money and time so in the future, I'd much prefer some early warning and then sticking to a plan rather than the current scheme of announce a new policy and then change it shortly afterward. Thanks again.

  • jeanga
    0 Posts

    THANK YOU! THANK YOU! THANK YOU! for listening to our feedback.

    Following my previous comment (on Xbox One launch idiocracies), it would be nice if you guys could avoid pissing  off your audience in the first place!:-) (even if recognising mistakes _and correcting them_ is a proof of being smarter than most)

  • After the original announcement I canceled my subscription and purchased the individual products I needed.

    The changing of the policy back and forth is not only frustrating, it cost me some money.

  • Edduee
    0 Posts

    THANK YOU! THANK YOU! THANK YOU! for listening to our feedback.

  • Hi everyone - thank you all for your feedback and comments on this post. We are addressing your feedback and announced today that we will be making available our current Windows 8.1 and Windows 8.1 Pro RTM builds to the developer and IT professional communities via MSDN and TechNet subscriptions.

  • freeed
    0 Posts

    hola que tal

    Tengo un error en la tienda de Windows 8 com una aplicación.     "no se pudo instalar" y lanza un erro 0x80080205 y 0x80080206"

    como solucionar esto


  • well I'm using the final and it is great

  • > @IzsakSVK

    > The API is bad, the documentation is bad.

    I don't think the API is that bad; however, I agree that the documentation is *terrible*.

    For example, the method documentation does not include any information on which exceptions they throw. Every time I use a new method, I have to take an hour to write test code to try all the ways I can think of that it could fail. If MS included a table of which exceptions happen under which conditions, that would save every developer this time.

    Would MS rather us spend our time writing our apps or trying to figure out the undocumented corner cases with their APIs? Do all devs actually spend this time or do they just ignore the issue and have apps that might crash with unhandled exceptions?

    It's been a year since release and two years since the first beta and the documentation is still a major impediment to getting apps done.

    I'm pretty surprised that there isn't more of an uproar in the developer community over how bad the documentation is. Many of us are used to how nice the .NET docs are by comparison so I expected a bit more vocal complaints on the WinRT docs.

  • I got lucky, I was able to cancel my subscription before they charged my credit card for this year's renewal. Without early access, there's no reason for me to pay extra for a software subscription from Microsoft.

  • The search tool only searches in C: It doesn't search in other directories :/

  • Neno
    0 Posts

    Your Windows 8 also have small bug,

    the mouse cursor 'waiting' animation sometimes stop playing after some time.

  • Cedric
    1 Posts

    - Disappointing to say the least. How are it pros and partners supposed to evaluate 8.1 now and perhaps change scripts/applications/whatever as needed now? Does this mean 8.1 hasn't been tested by partners and that rtm is in fact an untested beta?

    - While Windows 8 is in many ways an outstanding product too many compromises have been done in favor of touch  users where it should have been in addition to touch, keeping keyboard/mouse users in mind. There does not seem to be enough improvements in 8.1 regarding this.

    - Whoever redid the start menu in 8.1 should be fired on the spot. While I personally do not miss the Windows 7 start menu at all and like the Windows 8 way, most people don't and have been very vocal about this. Windows 8.1 is faking the start menu, nobody will be fooled and I see a huge backlash coming. Why was it so hard to give peope what they wanted, or 80% of it?

    - The Windows Store App infrastructure, or the Microsoft apps themselves, are extremely buggy. Why does the music app suddenly crash and disappear without a single message about why it crashed? Why do I have to regularly reinstall the mail app and why does it fail to reconfigure my Hotmail account, forcing me to do strange things to get it to work again? Do not expect any success with Windows Store Apps if the foundation has not been tremendously improved in 8.1.

    - I'm looking forward to 8.1 and dearly hope that most of 8 annoyances will have disappeared.

    - Congrats on the milestone.

  • Neno
    0 Posts

    Fix Your Bug Please!!!

    Bing "move/copy dialog box" problem on your now...

    Your Windows 8/8.1 "layers manager" have bug.

    Windows 8 Background Display Bug - Road to Windows 8.1 (ready?)

    Affects only Windows 8/8.1

    Windows Bug.1 ver.1 (Bug Start time from 3:20-3:34)

    Video Link:

    Windows Bug.1 ver.2 (Bug Start time from 0:37-0:43)

    Video Link:

    Windows Bug.1 ver.3

    come soon

    PS:All Microsoft Win8.1PR modules, third party Apps was uninstalled

    Microsoft don't listen to Customer Feedback, don't fix this bug.

    This product quality to RTM again!? Joke~

  • This question is for Brandon LeBlanc.  I purchased windows 8pro from Sams Club back in Oct 12.  I was thinking about updating my computer around Christmas.  When windows 8.1 comes available for free download next month.  Will you be able to get the 8.1 disk?  Thank-you mamabear

  • So...Microsoft hates us developers now?

  • Infozed
    0 Posts

    What will be difference in Current Windows and Latest Windows?

  • , : Superb! So they've denied us the ability to test on the RTM version AND they've effectively denied us the ability to stop (or warn) a user that tries to run our application on (untested) Windows 8.1.

    Genius move Microsoft. Thanks.

    [MS: If you can't reverse this decision, how about making your blog system support Sarcastic Fonts in the comments. ]

  • hi there

    does it possible to running and playing music app but in minimize state and when it is playing it isn't being in app switcher ?

    means its playing but not inwell a space in app switcher area so we have a more free space to run more app in switcher while the music app is playing

    help me if any body know how can I fix it ?

    thanks again

  • Congratz and i hate you guys. Why are you so late?

  • @koxo: what can I say? The API is bad, the documentation is bad. And still we are not allowed to test officially for RTM version. We just have to magically figure out how applications will behave based on beta release.

  • koxo
    0 Posts

    @IzsakSVK  : i have solve the problem, there is an error in the xml format of the given manifest

    "app" should be "application"

  • koxo
    0 Posts

    why make it simple when you can make it complicated ?

    @IzsakSVK  : Thank you for your link,

    I have try to add a manifest in my test, but it's the same, the version is still 6.2.9200 on Windows 8.1 RTM

  • @koxo - that is actually not a bug but feature - a bugged feature. Yes, the new API behavior sucks and should *NOT* behave like this. People do want to get the number "6.3" and not some "shimmed" value.

    "The internal version number for Windows 8.1 Preview and Windows Server 2012 R2 Preview is 6.3. Only apps that are targeting Windows 8.1 will receive a return value of 6.3. Those apps that are not targeted for Windows 8.1 will receive a return value of 6.2 unless previously shimmed as discussed below."

    I wonder if Antoine Leblond will provide any feedback, or the Windows Team just made a huge party celebrating what they accomplished: 80 negative responses to the Windows 8.1 RTM and not a single positive one - and they are happy with this situation.

  • koxo
    0 Posts

    I have see the same bug than Windows 8.1 on Windows 2012 r2  preview and RTM versions :

    The API function "GetVersionEx" from "Kernel32.dll" returns Version 6.2 Build 9200 instead of Version 6.3 Build 9600

    Can you correct this please

  • Phrost
    0 Posts

    Terrible news... maybe now people will start switching to open source OS alternatives?

  • koxo
    0 Posts

    I have see a bug on win 8.1 preview and RTM versions :

    The API function "GetVersionEx" from "Kernel32.dll" returns Version 6.2 Build 9200 instead of Version 6.3 Build 9600

    Can you correct this please.

  • Soukyuu
    0 Posts

    Sooo am I reading this right? Now in addition to the still hated modern UI of win8, we users will also have to live with lack of apps supporting win8.1, aka what was one of the reasons for he vista-disaster? Have you not learned anything at all Microsoft? That's not a step forward, but another step backwards from win7.

  • jeanga
    0 Posts

    My disappointment is beyond words or words I don't feel comfortable posting online...

    If at least there could be some rationale behind this unfortunate decision.

    Is it the same guy who decided of the limitations on XBox One used games (and the other great limitations that paved the way for Sony to make fun of you) who decided this?

    If so, you should know what you have to do...

  • downloaded 8.1 and it sucks worse than 8. save your time and headaches and stay or go back to 7. 8.1 is too hard to use. and the mouse goes where wants to not where you place it. but this only the beta version. I am Shure the next one will be even worse. and outlook acts like a dictator telling you where you have to go. whether you want to go there or not. why should I have to log into my mailbox just to use my computer off line? or go to my favorites?

  • I'm ready to get update into windows 8.1.

    18 October is the day.

    <a href="">windowstechnics</a>

  • Well, if this is "about optimizing the overall experience for our customers", then I would expect both hardware and software partners to be given the chance to prepare. But, it seems that MSDN subscribers have been placed into the "customer" category and are no longer considered partners; which is unfortunate to say the least...

  • I was wondering when the free download for 8.1 comes out in Oct.  will there be a windows disk that you can get also?  I have windows 8pro. and I would like to have windows 8.1 also.  thanks

  • rasol
    0 Posts

    سلام نسخه نهایی ویندوز 8.1

  • As others have mentioned, this does change the value proposition of the various subscriptions. I pay more for a subscription than I would buying the individual software I need. The *only* reason I do that is for the early access benefit. I just renewed my subscription last week in anticipation of an end-of-August RTM. Do you think Microsoft might be willing to let me cancel and get a refund for my subscription? I pay out of my own pocket so it would be nice to save whatever I can.

  • danielgr
    73 Posts

    Uhm... already 68 comments here, add the 26 on the "all you need to know crap post", nothing to write home about yet still substantial when compared with anything else on this blog.

    The funny thing? For as long as I've been reading here (several years) it's the first time I have yet to read a single positive comment.

    I mean, for as many haters as there will always be when you announced controversial news, there had always been others defending your choices (including me, so many times), except now. Same reality reflected on the ratings of both articles, which is the lowest possible (don't remember having seen that either).

    Would hope that gives you something to think when considering the "excitement" for the launch of your single most important product, home of the whole Microsoft ecosystem.

    We can only hope; you have 2 months to change your stubborn mind and reconsider.

  • What to say??

    Good luck, Microsoft... I think you'll need !

  • just simple answer when client ask me about windows 8.1 too buggy to install even MS said so :-)

  • It's cool- we didn't plan on writing much software for it anyway.

    (from my MacBook Air running the prerelease Xcode and ios7 in the background)

  • Edduee
    0 Posts

    "We are continuing to put the finishing touches on Windows 8.1 to ensure a quality experience at general availability for (all) customers."

    How much quality experience can Microsoft customers expect with lack of applications and tons of broken ones on Oct. 18? If it's good enough for RTM, it should be good enough for devs and IT pros. We are not expecting perfection - we just want to align our product with what's out there. It's a terrible situation to be in when you are late to the market - Microsoft, of all people, should know that.

  • JaviAl
    0 Posts

    I read in the MSDN subscriptions page ( "Access to the newest Microsoft products as they release." I read "as the release" not "as General Available GA".

    Since Microsoft is not fulfilling the agreement i want the refund of my money.

  • llth
    0 Posts

    In the last year Microsoft has thoroughly hosed over their OEMs, phone developers, and TechNet members. It makes perfect sense to completely screw everyone over and now they've gone after their own developers and have reduced core MSDN features.

    Step 1 - Kill all relationships with HW manufacturers to sell you product. Make them angry and integrate tools such as Pokki to bypass the Windows store (Lenovo).

    Step 2 - Piss off all your architects, trainers, engineers, administrators, and everyone else that deploys your products. Make it so they cannot get any software to test. Make it impossible to download older versions to even test migrate from. Give them lame limited online trials or force them to pay 20x more.

    Step 3 - Alienate your developers. Why not, sounds like a smashing idea. If Windows 8 isn't selling well, partners are replacing your windows store with BlueStacks, and RT is a complete flop - why not start smashing on your developers. Really make them stay away from writing Windows software.

    Here's the reality last time I checked:

    1. Android. Free to develop. Access to pre-release code. #1 in HW. #2 in SW.

    2. iOS. $99 to develop. Access to pre-release code. #2 in HW. #1 in SW.

    3. Windows. Thousands to develop. No access to pre-release code. #3 in HW. #3 in SW.

    Microsoft has simply gone bonkers.

  • I can't understand why Microsoft treats Developers, IT Professionals, Partners, Trainers et cetera as they're currently doing.

    We are the ones who develop software for your systems.

    We are the ones who defend your decision regarding Metr... pardon.... Modern UI.

    We are the ones who write books or produce Video trainings for your products.

    We are the ones who pay a lot of money für a Technet / MSDN / Action Pack (...) Subscription to you for being able to do so.

    And now you expect us to test our Software and Systems against a Preview which is already several months old? Sorry, but that is ridiculous!

    The Preview edition is not identical to the version our customers hold in hands on 18th of October. How on earth shall we be prepared when we can start testing the same day our customers can already use 8.1?

    Please see sense and publish the RTM of Windows 8.1, Server 2012 R2 (and other products in general) as soon as possible to MSDN / TechNet / Action Pack - as you did in the past!

  • If this is the future of release then I will just cancel my MSDN. There's no reason to have it if we cannot get the bits early for testing. This change is infuriating.

  • As a head of development at a gold certified ISV partner, I find the recent policy changes disturbing. We have been supporting every new version of windows from day one, including the much criticized windows 8.0 even as demand for the OS does not justify our costs. And even as we go out on a limb to support 8.1, install the preview, and make sure everything is good, Microsoft now turns around and deny us the RTM release. And all for what? to avoid bad publicity because of an unfinished release? Worse publicity will follow when 8.1 starts breaking apps on day one because devs couldn't push updates ahead of time, on top of the already bad publicity version 8 carries both pre and post update.

    As a business software developer, our customers are already asking if our application is certified to work with windows 8.1 and we cannot give them an answer today. This is in sharp contrast to every previous windows version which we certified sometimes months in advance as we had the RTM bits early. Given our rigorous testing standards, we'll have to delay an official support recommendation of windows 8.1 for at least 30 to 60 days. This hurts us, and hurts Microsoft since we will not recommend 8.1 to any of our customers until we know all our apps and systems work ok with it. Customer uncertainty over 8.1 will only hurt Microsoft and its customers.

    I understand Microsoft is trying to prevent what most of the tech-press already figured out: windows 8.1 wasn't finished on time and Microsoft is in a last ditch effort to patch it. But hurting developers in order to keep the press in the dark isn't the right approach as leaks of the RTM are already floating around and the press will find out the problems for themselves.

    I urge Microsoft to return to common sense. You're only hurting your biggest fans, your captive audience, your greatest strength: developers. If you're so concerned with the windows 8 perception, I would suggest you re-think your product. If you're not confident enough about it, and this unprecedented change of policy seems to indicate it, maybe you should put out a better product.


    Gold Certified ISV.

  • So we pay for an MSDN Subscription to give us early access to Windows updates so we can prepare our apps for its release, yet we don't get it?

    Kinda funny when you consider that Windows 8 is seriously lacking in quality apps.

  • ceetee
    0 Posts

    oh wait... what's this.. a leak from china with a mangled language pack... this is a much better way of handling it.. :/

    how many people working at MS spend most of the day banging their heads on a desk? i'm betting it's a lot. You have so many clever people there yet these decisions appear to come from the minds of lunatics. Yeah, hold back the MSDN version until release day? huh? u heard! huh? but it'll leak...

  • ceetee
    0 Posts

    this is exactly why we pay thousands for MSDN developer licences. So I can wait until the day Joe Public gets the release, with no time at all for testing of our in house applications, SOE rollout etc. thanks microsoft for the complete nosedive of your product base (everything turning into tablet interfaces) and now this garbage. The real reason behind this is probably to prevent bad press around the disappointment of your windows direction. How long do we have to wait until you realise that PC users do not have touchscreens? It's boring waiting for the inevitable U-turn when you put back the desktop interface and make your dumbed down tablet experience OPTIONAL!

    now that Ballmer idiot has gone, maybe it's time to put some sense back into your organisation? (yes, with an S)

  • Alessio
    0 Posts

    This is hilarious, how do you expect to get a decent number of application ready for the GA if developers must use a beta compiled... 6 month ago?

  • SanjitA
    0 Posts

    Any update regarding accomodating Silverlight in the new build? Being a developer, with the older version blocking sites on Silverlight, was a major bottle neck.

  • IMO a very bad decision to leave MSDN/Technet subscribers out in the cold. As others mentioned, it feels like your turning your back on the people that help promote/support Windows.

    I think MS should reconsider withholding 8.1 to subscribers and allow access to 8.1 RTM as is.

  • Squuiid
    0 Posts

    Great work Microsoft! This is now what is doing the rounds...

    Bravo! You really thought this through didn't you?

  • As someone mentioned earlier. This is NOT just about "Windows Store App" developers. Most developers that are affected by this (I expect) are still working on normal desktop applications.

    My company, for example, has a 3.2 MLOC .Net/WPF application. Support that on Win 8.1 with no testing? No chance.

  • Squuiid
    0 Posts

    "our reasons are explained in the above blog post. We are continuing to put the finishing touches on Windows 8.1 to ensure a quality experience at general availability for (all) customers."

    And how does that affect IT Pros? There is no reason why Technet/MSDN paying subscribers should not get the RTM now other than Microsoft's short sightedness. You're seriously damaging your relationship with your product evangelists, IT professionals. Stop shooting yourselves in the foot, it's not as if Windows 8 has a good reputation in Business as it is. I'm sure trying to curb piracy is a big part of the Technet subs withdrawal but it is completely and utterly short sighted.

  • It's a shame that MSDN, Technet and SA subscribers don't get access to the Win 8.1 RTM!

    And to not get Server 2012 R2 after RTM is even worse! I can't think of a single reason for this except either that it isn't finished or that you're gradually dismantling the support for IT-professionals on purpose to force companies on to Azure.

    Seems like Microsoft is on a winning streak for bad publicity!

  • Have you noticed any pattern to the comments yet?

    Not one person is happy about being made to wait until October to get the 8.1 bits on MSDN and TechNet.

    The delay is a bad decision. Your communication about the delay has been very poor. The reasons you have stated for it do not make sense. Your response that the Windows 8.1 Preview and Visual Studio 2013 Preview are good enough is inadequate. We know they are not. There are bugs and bits missing that make our job as developers harder or impossible.

    You need to make Windows 8.1 bits available on MSDN & TechNet as soon as possible or give very good, technical reasons, as to why you can't do that.

    Pointing to a four paragraph blog about "writing Windows Store Apps" and saying "that's all you need to know" is insulting.

  • Rajtyn
    0 Posts
  • SvenC
    1 Posts

    Really disappointing. Paying for an MSDN Ultimate and being treated like someone who bought a single Win8 license.

  • kiLLe
    0 Posts

    To be honest, this sucks. You are backstabbing those that you rely on to make your platform usable. Yes, BACKSTABBING.

    I might just go over to *shudder* Apple, or Google. They at least know how to treat their "developers, developers, developers! developers, developers, developers, developers, developers!"

  • I can't say withholding the final bits from developers is a wise decision, guys. You're shooting yourselves in the foot, and 8.1 isn't even out the door yet. You're going to have nothing to launch the OS with, which is exactly the thing that caused the major issues with Windows 8.0. Your users are also still waiting for promised apps (Facebook and Foursquare, for example) that still have yet to see the light of day.

  • Microsoft's decision to withold Windows 8.1 RTM to developers and volume licence customers is a significant mistake.   It further discourages developers and enterprises to adopt it's new operating system by introducing unnecessary delays and roadblocks to readiness activities.  

    The reality is that rather than encourage developers and volume licence customers to continue with their preparations to support the retail release of Windows 8.1 on October 18, the majority will now suspend their preparations and wait until they receive the RTM build before continuing.    

    Microsoft really needs to seriously reconsider the logic of their decision.

  • jbondc
    0 Posts

    Also find this surprising, why not just call it an RTM beta for developers?

  • dhjohns
    0 Posts

    I have the SAME problem as exoskeletor, and I have NEVER been given a straight answer.  Does 8.1 rtm has the same requirements like 8.1 preview? 8.1 preview for 64 bit requires cpu with support for CMPXCHG16b, PrefetchW and LAHF/SAHF.   I would think that if it does, there is a good chance most people do not have this support.

  • dlhak
    0 Posts

    I guess this is one step for Microsoft to give itself reasons why it is closing TechNet service ...

  • danielgr
    73 Posts

    @Brandon LeBlanc And you keep with the jokes. So just tell me, why people paying you considerably more than the price of the OS to get (among others) access to an early release should rely on a buggy beta for public free consumption when you've got an RTM version in the shelves?

    Then say "that's all you need to know"?

    Again, stop insulting us, go straight and tell the truth: "I know it's not ideal, but for reasons I can't disclose that's all we can give you now folks, sorry about that", and you may get slightly better reactions.

    Win8.1 better be damn good and represent a good market opportunity for developers / appealing solution for companies, because you are losing the sympathy of many that have grown up with your damn company and in which you rely for success. That may be great if you were leading a monopole, but sure is a tricky game when you are falling over a cliff.

  • Is windows RT getting the Cisco Anyconnect VPN app? I badly need it IPSEC von to work using a groupname and a shared secret. Comeon Microsoft even the cheapest android device has it!

  • bstraka
    0 Posts

    While I understand Microsoft's argument about not providing early access to developers, it will put my company in the position of advising our customer base to not install 8.1 or purchase devices with it pre-installed until we have had time to run our certification process (which typically takes around a month depending on workload in QA).  

    I can't imagine that we will be the only software company taking this position.

  • Gary
    12 Posts

    another disappointing decision. i can't understand why microsoft keeps shooting themselves in the foot. look, you know windows 8 hasn't been the success you wanted. i use it and it's fine, but you've taken a PR beating in the press for 10 months now.

    now, you decide to wait almot 2 more months to release 8.1t? more bad PR, like you can afford it. peolpe actually get paid to make these horrible descisions?

  • It seems Microsoft has totally turned their backs to developers. I'm very disappointed. I was unhappy already about all this InstallShield thing in Visual Studio (and how they can ignore the huge feedback of the community), and now this. Come on, MS! You should play with us, not against us!

  • If you are a developing making apps for the Windows Store and Windows 8.1 - this blog post explains everything you need to know:

  • It seems clear that Microsoft is no more interested in supporting ITPros... No more TechNet subscriptions, no more early release for ITPros (and devs BTW). How are we supposed to support our customers (ah, they are also YOUR customers) if we can't test your software before it's released?

  • Same date for MSDN and GA is very unfortunate to say the least.

    In fact it will only delay acceptance of the new OS. But you know what? It doesn’t really matter, since we wouldn’t profit anyway even if we make our Apps ready for GA so it’s OK. Only Microsoft is loosing.

  • Jesse M
    0 Posts

    "In the past, the release to manufacturing (RTM) milestone traditionally meant that the software was ready for broader customer use. However, it’s clear that times have changed."

    No, times haven't changed.  Microsoft has changed.  They're finished with the product, but it's not ready for broader customer use.  Now, you're placing your MSDN and Technet subscribers in the "broad customers" category? Thanks a million.  Why the heck are we paying for these services, exactly?  But this is still a milestone? You've done what exactly?  Announced that 8.1 is now RTM, but it's still not finished.  So, no one can have it for 2 more months.  What was the point of an announcement?  Why not just say that it will be finished on October 18?

  • Summary: Windows 8.1 is released to OEMs, that's why an RTM version needed to be signed-off, but development is not really finished yet. It may be complete feature-wise, but there are still bugs and apps that are not ready for prime time. Plus, development tools (VS2013) are not ready, too.

  • Jorgie
    2 Posts

    I guess I know a university full of developers that no longer need an MSDN subscription. Time to just license a minimal version of Visual Studio.


    10000 Signatures reached

  • Seriously.... has Microsoft fallen off its rocker?  Windows 8/8.1 is nothing without the support of developers.  Microsoft cannot responsibly consider its product as fully tested and ready for release to the general public until your third party developers have had at least a month in advance to test their applications against it.  This decision is yet another that leaves me questioning the judgement of Microsoft's current management.

  • excelsi
    0 Posts

    I also cannot understand why you don't publish the downloads to the RTMs for Technet and MSDN before the rest of the public. Why do I pay for the Technet Subscription if i dont have the main advantage of early access. As an MCT the evaluation is very important for my courses. So whats your answer on that statement? Thanks.

  • "We are continuing to put the finishing touches on Windows 8.1 to ensure a quality experience at general availability for (all) customers."

    Translation: While Windows 8.1 should run very nicely (at least after a quick Windows Update to install the patches we've done post-RTM), a bunch of the third-party apps in the Windows Store might not work optimally, if at all, and any Windows 8.1 apps that take advantage of the new APIs won't have been tested on the RTM build with or without the patches, so it's anybody's guess whether those will work or not. But hey, we made every single link on the MSDN homepage take you to a marketing pitch for building Windows 8 apps; that's bound to make up for the way we're alienating all our loyal developers with this craptastic move.

  • b4rtw
    0 Posts

    Congratulations on the RTM of Windows 8.1!

    That said;

    - Windows 8.1 is ready to be used / apps to be developed for

    - You shout developers, developers, developers! from the roof tops

    - Windows 8 desperately need good apps

    - You make people pay for MSDN / Technet,

    Yet no access to the RTM bits???? Ludacris! Unbelievable!!!

  • I will add my voice to those requesting early access for subscribers. I am the author of a training course on how to write WinStore apps. I'd much rather use the RTM bits to update my course for 8.1. It would be to everyone's advantage if I had the updated course ready to run on October 18th. Thanks.

  • Quppa
    12 Posts

    > In the past, the release to manufacturing (RTM) milestone traditionally meant that the software was ready for broader customer use.

    When was this ever reflected in Windows releases? Historically there has been a gap of about three months between RTM and GA ('broader customer use'):

    Windows 8 - RTM: 2012-08-01, MSDN/TechNet Availability: 2012-08-15, GA: 2012-10-26

    Windows 7 - RTM: 2009-07-22, MSDN/TechNet Availability: 2009-08-06, GA: 2009-10-22

    Windows Vista - RTM: 2006-11-08, MSDN/TechNet Availability: 2006-11-17, GA: 2007-01-30

    What's new is not allowing MSDN/TechNet subscribers to test the RTM bits ahead of GA. I can understand Microsoft and its partners wanting to work on the broader hardware and software ecosystems in the next two months, but not providing early access to developers and IT professionals is surely more trouble than it's worth. It will:

    - generate more bad publicity surrounding Windows 8/8.1

    - encourage developers wanting to test their programs with Windows 8.1 to download the leaked copies that will inevitably surface

    - ensure very few apps will support new Windows 8.1 features on release

    What's the great benefit of delaying developer access?

  • Disappointing, A devaluation of msdn subscriptions/technet.

    I am not very happy with this....

  • Jesse M
    0 Posts

    Way to go, Microsoft.  Not only do you retire Technet Subscriptions because of the people who use it illegally, now you won't even make your next OS which is complete (or is it?) to the folks who pay to get software early for testing on.  Now, we're all in the same bag along with every Tom, Dick, and Harrry who can grab it off the shelf, when? Not in a month, but nearly two months from now!!  My Technet subscription expires 9/22, and I was hoping I would get 8.1 bits before it expired.  But I guess that's not going to happen now.  Now, I'll probably have to renew it for another year to get one more month of software.  I frankly wouldn't be surprised if you folks make an announcement after September 30 saying that since the Technet subscription service is going away, Windows 8.1 will not be made available for Technet subscribers on October 18.

  • No availability for MSDN/Technet before release?  Are you serious?  I guess you guys really aren't giving a hoot about developers and IT Pros anymore, are you?  And don't give me the company line about ironing out bugs, we're devs and IT Pros, we don't need to be treated like average joe consumer who can't even find his power button let alone deal with a simple error.

    I would have thought you would at least put this on MSDN early so people could release optimized 8.1 metro apps, but I guess app support won't come until after GA, sort of like driver support for Vista.

  • I can only echo the comments from others. This is very disappointing.

    The combination of NOT allowing developers early access to the RTM build, alongside the release of the build to all existing users as a free upgrade on the same day is a testing nightmare. Not to mention that I imagine MS will be promoting the free upgrade pretty heavily.

    The only reasonable response from a developer would be to add a runtime check against the version of Windows and prevent installation or use of the application on Windows 8.1 until such time (post October) that it can be tested. That's going to be a pretty disappointing experience for users of the application, but without testing can we really just assume that it will work?

  • Nathan
    63 Posts

    To the "Developers! Developers! Developers!" of Microsoft community. Would you guys release native OCR library (as opposed to cloud driven) for Windows Store and Windows Phone? Or convert tesseract ocr OSS project to the said platforms.

  • Outstanding!!

    I'm sitting here with a preview version of Windows 8.1 which is significantly different to Windows 8 in terms of all things development, and yet the first time I'll truly be able to try and develop something meaningful on it the whole world will also have access to all the apps that myself and others have not been able to develop.  Great idea, release a major update to the public and then inform them that they'll have to wait for any apps that can make best use of it as the developers didn't have early access.  I'll have to skirt around this issue with my Directors that pay for the MSDN subscribtion and make my excuses on your behalf.  Do be sure to send the subscription renewal  without delay!  If the preview is good enough for developers you can bet that the RTM is too, this is a weird disjointed Microsoft, great things happen in the ASP.NET Scott Guthrie, release often/release early space all the time, but you Windows folk just don't get it. Maybe more people should take the lead from Sinofksy & Ballmer!

  • What about those of us trying to write a book, or test apps on Windows 8.1 before GA?

    Is there any way we can get our hands on a pre-release NDA build, so that there can actually be third-party Windows 8.1 books available at launch?

    I already sent you a tweet (from @howtogeek), but so far I'm getting the feeling that authors and programmers are completely out of luck. Which means that users are out of luck too.

  • danielgr
    73 Posts

    @Brandon LeBlanc I'm afraid that excuse won't cut it for TechNet / MSDN folks. For most of us the testing and familiarizing will be done on current hardware (sometimes very old), which is unlikely to need the optimizations mentioned in the post whatsoever.

    I mean, Microsoft (you) may have good reasons for it, and it's your software so you can do as you please. I suspect you are planning to make the most of the new wave of devices to boost the OEM moral, and I'm fine with it. Either way, just don't pretend that you are doing it "for us", because at that point it simply becomes insulting. Your positioning is clearly not on behalf of the interests of the MSDN/TechNet communities.

  • Flexman
    0 Posts

    Hang on, as a ISV\Partner that supports the Win8 platform and is actively developing against it how are WE meant to test our apps against 8.1?

    We have the preview however quite a few of the nice new features don't seem to be even wired up in the preview. Point of Service needs serious testing which we are unable to do with the preview.

    Should we continue to support this type of behaviour from MS? It used to be about developers but sadly that is no longer the case. Do we need to kick up a public stink a-la Xbox One to get MS to do another embarrassing u-turn.

    Make the sensible decision and allow us to develop against RTM now!

  • Hallo!

    ... 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 ...

    These is not a step to the future ... this are 4 steps to the past. I am very angry about this. I will say it with segobis words: You are losing Partners!

    Thank you and Good Night

  • Does 8.1 rtm has the same requirements like 8.1 preview?

    8.1 preview for 64 bit require cpu with support for CMPXCHG16b, PrefetchW and LAHF/SAHF. for example on a pc with Intel® Core™2 Quad Processor Q9000 i wasn't able to install it.

  • This is great news! Now we won't be able to work out all the compatibility issues with crypto providers, antiviruses and other software that requires deep OS integration! No more day-1 support for end user!

    I'm sure all your partners that rely on early access to future products through MSDN / Tech Net will gladfully embrace the official announcement.

  • BAV0
    0 Posts

    Brandon, I think I understand the reasoning behind the decision to hold back RTM bits until launch. Microsoft wants the launch of Windows 8.1 to be perfect. If you release 8.1 now, idiots will call it Vista 2, because of a couple bug that will be ironed out by General Availability, drivers are not completely bug free yet, OEMs haven't released firmware updates to improve compatibility with 8.1, and because features like miracast may not work reliably due to bugs with gpu drivers and receivers' firmware.

    This was the case with Windows 8 too, it 'failed' even before launch, due to journalists testing RTM as far back as August, and criticizing it.

    But that's no reason to hold it back for developers, we pay thousands for MSDN access so we can test our software/apps properly, early testing, before GA, is an important part of that process! We don't care about a couple of bugs in your OS, we about bug in our software. Most of us actually want to support Windows 8.1, a lot of us want to get apps ready for the awesome 8.1 features, but we can't properly do that unless we get the RTM bits before the public gets the Windows 8.1 update!

    Brandon, please don't forget about us, the "Developers! Developers! Developers!".

  • Releasing finished software to Technet and MSDN subscribers so late? This really adds value to the subscriptions we are paying for. How are we supposed to test our software for Windows 8.1? The day it will be automatically installed on users' machines? So we - software developers - can take blame that applications don't work on Windows 8.1?

    As segobi said - great way to lose your partners.

  •  - I saw your previous comment with the link to your issue on the Microsoft Community website. That is the best place to post those types of issues. Sorry no one has gotten back to you yet but I will pass the link along. You can also send feedback to the hardware manufacturer of your chipset as well.

  • softeac
    0 Posts

    Brandon , you can back up the information, I'm a "nervous" because nobody responds to me for a year to find a commercial solution to my problem in chipset P45 and ALC1200. The "N" version -in French- beings not available in ... Belgium.