Microsoft makes latest Surface price cuts permanent

Microsoft makes latest Surface price cuts permanent

Summary: Microsoft is cutting prices on Surface Pro, Surface RT and touch covers and making those cuts permanent, rather than promotional.


Microsoft has made previously temporary price-cut promotions for its Surface devices permanent.


Starting August 29, Surface Pro, Touch Cover and Surface RT bundle price adjustments will begin to roll out all markets where Surface and Surface accessories are currently sold.

What are these adjustments?

  • $100 (U.S.) off Surface Pro (including the 256 GB SKU). This means the entry-level Surface Pro will now start at $799 (U.S.)
  • $40 (U.S.) off Touch Covers. Touch Covers will now start at $79 (U.S.), and Limited Edition Touch Covers will now start at $89 (U.S.)
  • $50 (U.S.) off Surface RT bundles. Surface RT bundles will now start at $399 (U.S.)

Microsoft will be doing a "phased approach" to these pricing adjustments "in order to meet customer demand and retailer expectations," a spokesperson said. Users can find information on pricing changes in their specific locations via, a spokesperson said.

"The customer response to recent Surface pricing and keyboard-cover promotions has been exciting to see, and we are proud to begin rollout of Surface Pro, Touch Cover and Surface RT bundles at even more affordable prices starting August 29," said a spokesperson in an e-mailed statement.

Neowin first reported that the $100 Surface Pro price cut, which originally was supposed to end today, would become permanent. WPCentral reported last week about the coming Surface RT bundle and touch cover cuts.

Topics: Microsoft Surface, Microsoft, Mobility, Tablets, PCs, Windows 8


Mary Jo has covered the tech industry for 30 years for a variety of publications and Web sites, and is a frequent guest on radio, TV and podcasts, speaking about all things Microsoft-related. She is the author of Microsoft 2.0: How Microsoft plans to stay relevant in the post-Gates era (John Wiley & Sons, 2008).

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.


Log in or register to join the discussion
  • It contiues

    I hope they find a good price to where people will start buying them more.
    Michael Alan Goff
    • Hoping for a SP2.

      A Haswell processor and 8-9 hours of battery life sounds wonderful.
      • A Fire Sale before Surface is Cancelled

        It's inevitable that Surface will be cancelled.

        Surface sales have been abysmal. CEO Ballmer has fallen on his sword as a result. His replacement isn't going to want to keep subsidizing the thing.

        Yes, a Surface 2 would have been better to resolve the terrible battery life, heat and weight issues.

        Microsoft was stuck between the ARM processor and a version of Windows (RT) that had no software and never will, a bloated and unusable full version of Windows ("Pro') and its spaghetti code base sitting atop a heat-belching x86 processor that required a thick and heavy battery to keep it alive. Next year's processor is not going to save it, as the code itself is bloated and never designed for mobile.

        Neither version of Surface will sell any more than Zune or Kin did. Axing Surface, along with Ballmer, is inevitable.
        • Inevitable?

          Because something doesn't sell well in the first iteration it is inevitable to be cancelled? Good thing you didn't lead Apple when they first came out with the iPod.
          Michael Alan Goff
          • its not about sales numbers

            It about the 1 billion they lost on them. And you can't compare it to apple's ipod because when apple launched the ipod it was a new market. The market for tablet is already saturated by other products that are just as good ( with a better app selection)
          • New market?

            Please research a bit. The original ipod was hardly a new market. Creative and Sansa both had MP3 players before Apple decided to join the fray. It was the first to market it right.
          • It was the iTunes store than made the iPod so great. It still is!

            M Wagner
          • That was a loss ON PAPER ONLY.

            It is an estimate of profits Microsoft WILL NOT EARN by selling them at $349 instead of $499. Surface will survive of fail based upon a number of factors. Price-point is only one of them. The rate of growth of Metro apps (or lack thereof) is another, which will impact Microsoft's entire tablet strategy.

            Perception is the biggest problem though. Microsoft HAS TO be able to explain why Windows RT is a good choice at a fair price.
            M Wagner
          • "it was the first to market it right"

            Correct. Apple was the first to market the mp3 player right (1000 songs in your pocket). Which made it a recognizable (new) market to the gen consumers willing to buy. The mp3 player market took of from that point.

            The same thing happened with the modern tablet market. Apple made it a recognizable (new) market to the most important set of consumers that was willing to open their wallets. The gen consumers. Just like their were no mp3 player market before the iPods (in gen the consumers eyes), there were no tablet market either.

            The tablet market is now saturated with dirt cheap Amazon Kindles and Android's on one end and high quality iPads on the other. Where is there room for a MS SurfaceRT, with no apps and no established everycosystem? The Surface Pro with its full OS, high price and low battery performance is really more notebook than modern tablet "device" and should'nt be compared.
          • When Apple first came out with the iPod,

            it was a huge hit.
        • "Spaghetti Code"

          Really? Can you please refer me to the specific areas of the source code that you feel are "spaghetti-like" in nature?
          • Please

            Windows is a lot of things, many of them good, but let us not pretend, whether technical or not, that there isn't a good helping of pasta there (particularly since this was specifically noted about the Pro.)

            There's the 16 bit and 32 bit subsystems. There's the still present (not by default, but present) POSIX system. And then there's a totally gesturally and graphically incompatible GUI system (currently labeled Modern) bolted on, using COM with a window dressing called "language projections" for more modern programming paradigms (like JS and .NET.)

            It all works together as well as such a thing can, providing remarkably capable backwards compatibility - there's really nothing else like it, with old DOS programs from decades ago able to run in a binary compatible way.

            But let no one pretend that this hasn't come with a healthy dose of spaghettini.... particularly since it is well known that most of Windows is written in pure C (and not C++), which definitely limits the object-orientedness of Windows' deeper plumbing in a lot of ways (as any Windows developer knows from their painful experience of Handles, a primitive reffing technique.)
          • Don't you think it is true for every operating system tha provides

            backward compatibility? I can show "your type" of spaghetti code that you mentioned for Windows in Unix, Linux, BSD, OSX or whatever you call the *ix. FYI, I started my career with Unix Clone only. I learned programming and administration on a Unix clone system. This was 25 years back. Please. Every system is written by humans and will have human like behavior, and features including spaghetti-ness you just mentioned.
            Ram U
          • Spaghetti Code is the product of poor programing practices not ...

            ... poor product design.
            M Wagner
          • Have you looked at Windows source?

            The kernel is written in C (those kernel guys don't like the idea of v-tables - they want to always make a direct call to a page that they know about). Otherwise, there's lots of C++ in Windows, lots...

            There's no 16-bit anything left in 64-bit Windows. The really wasn't much 16-bit code left in Windows anyway (it isn't like Win9x where there was tons of residual 16-bit goop).

            The WinRT APIs are layered on top of Win32. You could describe that as "bolted on", but hardly as "spaghetti". I haven't looked at how it's integrated with "legacy" Windows, but my guess is that it's layering is probably as clean as that of the .NET Framework.

            The code base is decades old now, and any decades old code is going to be a little messy (entropy in a code base is a real phenomenon), but with each release, Microsoft has been working to detangle things - remember your Thermodynamics, entropy can be overcome with work.
          • windows source

            The spaghetti thing is not about source.
            You can have very pretty code, with lots of "helpful" comments etc, yet... The thing may be spaghetti. It is all about the API layering.

            Windows's greatest features, the backwards compatibility and "ease to code" (as in, no discipline whatsoever, anything goes) is its damnation. Because there is no way to clean that up, except start from scratch.

            This is why Windows is "doomed", not any other fanboy reason. It is Microsoft who will kill Windows, as the only way to go forward. Or, Windows will kill Microsoft.
          • But will it run Linux?

            If I can pick up a pallet full for $25 from the scrap yard, I'd buy them.

            But only if I can install Linux on them.

            So will they run it?
            Wroger Wroger
          • This is why Windows is DOOMED!? Oh my! Ha!

            Boy oh boy Dr. Evil! I bet the whole MS gang is terrified about that bit of fortune telling!

            Ya, we will see how "doomed" Windows is.

            What century you figure this is all going to come down?
          • Incorrect

            There is no 16-bit subsystem in Windows 8 and the POSIX subsystem was removed in Windows 2000.

            Sure, Windows has a new app infrastructure and runtime environment. But that's a good thing because Win32 based UI infrastructure is now over 20 years old and is I'll suited to modern touch oriented apps. Not only that, but the Win32 infrastructure doesn't provide sufficient protection and isolation between apps.

            Oh, and the fact that some VERY old DOS & Windows apps continue to run today is a feature that was specifically and VERY carefully designed because customers NEEDED this feature. Such a capability doesn't happen by leaving old code alone and hoping for the best.

            The spaghetti you refer to was certainly present in (and to some degree because of) XP but was partly unraveled in Vista, massively unraveled in Win7. Windows' source was unraveled further still in Win8, whereupon Windows could be ported to ARM platforms and perform well from both a performance as well as power consumption perspective. The effort to clean up and better modularize Windows was called MinWin. You should read up on it.

            Much of Windows was built in C because, at the time (circa '89-95), C++ compilers generated code that was nowhere near as efficient as pure C compilers. Back then, the cost of a virtual method call was a measurable impact on the perf of an app. This, by the way, is why much of Linux is STILL written in pure C.

            Full disclosure: I used to work on the source of Windows, CLR, .NET and Visual Studio.
          • Um, you may want to check your Windows component options

            They're not calling it "POSIX", but yes, it very much still is there.

            Don't get me wrong, I'm not suggesting it has been wrong for Microsoft to put together this spaghetti-fest. I personally would be hosed without the ability to run a lot of things that should have been dropped long ago.

            But let's not go mistaking Windows for QNX. Like I said, there's a hearty helping of pasta there.