A closer look at the Windows 8 post-RTM update process

So, last week, Steven Sinofsky announced the availability of a cumulative update for Windows 8. Bundled with that announcement was some insight into what happens with fixes made after the OS goes gold (or RTM). Specifically, Sinofsky explained that certain fixes get delivered to OEMs prior to the public:

We would often create dozens of changes for each OEM for these new PCs. Those changes would be deployed during manufacturing of those PCs and thus would be invisible to customers. While those changes could potentially apply to a broader range of PCs, we did not have in place the testing and certification to broadly distribute these updates. As a result, customers would have to wait until the first service pack to see these enhancements.

He continued, indicating that with Windows 8 some internal processes changed, allowing Microsoft to deliver these updates sooner than general availability (GA):

During the final months of Windows 8 we challenged ourselves to create the tools and processes to be able to deliver these “post-RTM” updates sooner than a service pack. By developing better test automation and test coverage tools we are happy to say that Windows 8 will be totally up to date for all customers starting at General Availability. If you are an MSDN or enterprise customer, these updates will be available for your Windows 8 PCs via Windows Update as of today (October 9), following our standard cadence for Windows Updates on the second Tuesday of each month at about 10:00am.

Sounds good to me.

But let’s not fool ourselves into thinking this process is new. Gregg Keizer (Computerworld) fell into that trap, writing:

In Microsoft's terminology, RTM designates the point at which it considers the code completed, and ready to ship to computer makers for installing on new PCs. Microsoft has never updated a version of Windows between RTM and when the OS hits retail and PCs powered by it reach stores.

Matthew Siegler did too, mumbling:

Probably not the best sign in the world that Microsoft has to release service packs [sic] to the RTM version of Windows 8 before it has even launched. I mean, why declare RTM then? Well one possibility is that you’re working to meet a deadline rather than releasing when a product is fully baked.

Look, guys. Microsoft has been updating Windows in this manner for ages – at least since Windows Vista. That was so 6 years ago. To be more specific, Windows Vista saw a heap of updates, including the infamous Ultimate Extras pack, January 29, 2007 (a day before GA). Windows 7 received similar reliability updates on October 12, 2009 (10 days before GA).

Here's what the timelines look like, with the pre-GA/post-RTM release cadences in red:

What’s really new here is the delivery of updates previously reserved for OEM first use. (Ever wondered why OEMs had those atrocious software download pages with a weird assortment of Windows hotfixes?) It is the inclusion of these specific updates as part of the old patch delivery cycle that likely required the tooling and engineering improvements Sinofsky mentioned -- something definitely worth lauding.

Okay, maybe it's about app restrictions on Windows 8? Not that either.

[This is part 3 of the Minecraft/Windows saga. Go back and read part 1. Or part 2.] So if all this Minecraft noise isn't about closed marketplaces, then maybe it's about changes to how desktop applications get installed/run on Windows 8. That must be it, right?


Windows 8 will run all your existing desktop applications from Windows 7. Windows 8 simply introduces new channels to advertise and obtain software for your PC. A common mistake is to confuse Windows 8 with Windows RT, a subset of Windows 8 tailored for devices (like how iOS is a subset of Mac OS).

Here's a chart showing app options available to users, starting with Windows 7. As you can see, Windows 8 didn't lose any features. To claim it's closed or more restrictive than Windows 7 is just completely bogus.

Rev 1: Changed marketplace accessibility row label, removing the 120 markets it's not clear if App Store reaches 120 markets. (Not likely.) Added the 120 number onto the value for Windows 8 in this row.

Maybe it's about closed marketplaces? Nope.

[This is part 2 of an on-going saga. Re-read part 1. Or move on to part 3.] Yesterday, I brain dumped in response to Notch's complaints on Twitter. My goal with that post was to point out that Microsoft reached out to Notch in a friendly attempt to get Minecraft listed in the Windows Store as a desktop app, not a "Metro" app. His reaction to the email appeared to be based on confusion surrounding how apps work on Windows 8 and the new Windows Store.

But a buddy of mine -- Leo Davidson -- suggested that I may have missed Notch's point, writing:

[...] he disagrees with the move to a model where Microsoft control[s] which [what] software people find [...] Rather than support that model, as easy as it might be for him, he would rather have nothing to do with it, even if it means his games reach a smaller audience as a result.

That would be a fair point, ... if Mojang AB wasn't already participating in identical models:

Rev 1: Added Amazon's App Store, thanks to reader Ian A.

Notch doesn't hate Windows 8, he's just confused

[This is part 1 of an on-going saga. Check out part 2. Or part 3.] http://twitter.com/notch/status/251239807257296897


So last night, Markus "Notch" Persson -- the Minecraft guy -- mentioned that Microsoft reached out to the company (Mojang AB) in an attempt to get the wildly popular Minecraft video game into the Windows Store. Shortly after, though, he denounced Microsoft for "ruining the PC" with Windows 8 and its "closed" nature. What's really going on here: Notch is just confused about Windows 8.

Allow me to help.

After Windows 8 hits the shelves, there will be two classes of applications that run on the PC:

  • Desktop Apps
  • Windows Store Apps (previously Metro Apps)

(There are also Desktop Device Apps but lets ignore those.) Desktop apps are the applications we use today. Photoshop. Visual Studio. Office. Each application has its own experience which, at times, can be difficult to use or even master. Take Minecraft for example -- it had a "textbox" for specifying the hostname or IP address of a server to connect to. But it wasn't until recently that users could paste text into this textbox from the clipboard. Users expected it to work, but it didn't.

Cue Windows Store Apps. These are newer PC apps that are held to a strict code to ensure users are provided a consistent, elegant, and easy-to-use experience. These apps come from one place -- the Windows Store -- with dependencies quietly in tow and out of sight. You can say, in most cases, they Just Work. (For more insight on this vision, be sure to check out Steven Sinofsky's write up on the Building 8 blog.)

Both app types are supported in the Windows Store. Windows Store Apps obviously get preferential treatment -- that is, they are submitted to and hosted by Microsoft, tie into bug reporting and analysis tools, support in-app purchase, etc. Desktop apps are left to continue doing what they do today but can benefit from a listing in the Windows Store. (More details on how desktop apps look and behave in the store can be found on the Windows Store blog.) [Added 9/28/2012 @ 8:55PM PST]

Like the classified ads in your local newspaper, listing your app in the Windows Store isn't free. Justifying those fees, however, is access to Windows users across 120 markets -- that is, nearly anyone on this planet using Windows. Crazy, right?

And one other thing: Your application must follow some rules to ensure nothing goes awry on the user's machine. These rules differ based on what kind of app you're submitting and unsurprisingly require one of two certifications: Windows Store App Certification or Desktop App Certification.

Let's return to the tweet situation for a moment.

I contacted Microsoft about the ordeal and they confirmed reaching out to Notch. But Microsoft did not ask for the guys to rework Minecraft into a Windows Store App or participate in any walled app gardens. (Though it's noteworthy that Mojang AB is not unfamiliar with playing in these spaces. After all, they have Xbox 360, iOS, and Android versions of Minecraft in some form on the market today.) Microsoft was simply offering assistance in pushing Minecraft through the Desktop App Certification process.

Let's dissect that process now.

The Desktop App Certification process isn't new. Back in the days, it was called the Windows Software Logo Program -- you know, that program that Microsoft tried to nudge developers to participate in to no avail. Generally speaking, it's a document filled with best practices-turned-requirements that if implemented net you a spot in the Windows Store. A fair deal, I think.

But you can't implement and submit your app to the Windows Store blind. Microsoft conveniently provides a set of tools to mock certify your application, eliminating most of the guess work associated with submitting your application to the Windows Store. They run the same tests over there.

I took Minecraft and ran it through these tests myself, to see what passed and what failed. While I passed my mock certification, I did so with some warnings that would very likely result in rejection or at the very least raise some eyebrows. (I suspect they are labeled as warnings because waivers could work around them if needed.)

Here's what I got dinged on:

Windows Security Features Test

Microsoft is constantly evolving the security landscape of Windows operating system, developing and improving protection against coding mistakes that lead to scary-sounding issues, like buffer overflows. Enabling these features once required app developers to opt-in to the protection. Not anymore. To play ball, you need to get with the program and ensure you compile your app with the following security features enabled:

Details: Minecraft.exe currently fails this test (with a warning). While I can't be certain, it appears Mojang AB cross-compiles Minecraft.exe for Windows via gcc. Or perhaps they use a mingw/cygwin/vc++ compiler environment. Let's hope for the latter because gcc doesn't support some of these features. A switch to the Windows SDK or Visual Studio 2012 Express for Windows Desktop software is likely in order.

User Account Control (UAC) Test

UAC is a set of complicated security technologies that debuted in Windows Vista. Short version: Your application is reduced to having little to no privileges by default, requiring "elevation" or hoop jumping by authorized users to gain access to sensitive bits of Windows. They relaxed it a bit in Windows 7, to the point where it's now a Good Thing. (You can read all about it on MSDN.) This particular test just inspects the app for a little XML file called the Application Manifest. It describes to the OS what the app needs in terms of permissions, dependencies, etc.

Details: Minecraft.exe fails this test (with a warning). This is trivial to fix -- embed a tiny Application Manifest that simply indicates that it needs no special access and can run safely in the user's sandbox. (i.e. add requestedExecutionLevel level=asInvoker)

Digitally Signed File Test

This one is simple. Code should be digitally signed to confirm where it came from and to ensure its intact when the user receives it.

Details: Minecraft.exe fails this test (with a warning). It isn't digitally code signed. (Now, there's no requirement that Mojang AB actually "check" this signature, so modders fear not.)

Install To Program Files Test

For application storage consistency and security, Microsoft requires apps be installed to the trusty ol' Program Files folder.

Details: I put together a quick, NSIS-based per-user installer for Minecraft.exe. Per-user installers typically install apps for use by a single user so naturally they cannot be installed to Program Files. I chose per-user in the certification tool but Minecraft still failed this test (with a warning). It appears I hit a certification bug but I'm waiting for Microsoft to get back to me on this one.

... and, that's it. Minecraft passed every other test.

If Mojang AB needs a hand, feel free to email me. I'd be delighted to help.

Rev 1: Added a clarifying paragraph on how Windows Store/Desktop apps get hosted in the Windows Store. It has been time-stamped with gray text accordingly.

Windows 8 Secrets: RTM Graphical Assets

With tech enthusiast web sites from around the world now leaking the RTM version of Windows 8, your intrepid “Windows 8 Secrets” co-authors offer a better look at the graphical assets that other sites only hint at. In this new co-post, we look briefly at leaked images of the Windows 8 RTM Start screen patterns, and lock screen and desktop wallpapers. Pre-order Windows 8 Secrets today on Amazon.com and save!

This week, Win8China leaked some of the new default lock screen images in the RTM version of Windows 8. But what they don’t show you is what this actually looks like on the lock screen. Here it is:

Here’s what the full set of default lock screen images looks like:

Win8China.com also leaked the final set of Windows 8 Start screen patterns. You may recall that Microsoft had previously provided a small number of these patterns in previous Windows 8 milestone releases. But in the final, RTM version of Windows 8, we can see that not only are there 20 patterns—up from 10 in the Release Preview—but that many of these patterns are quite colorful.

Here’s the PC Settings interface for personalizing the Start screen in the RTM version of Windows 8:

Earlier this week, TECHIT leaked the default Windows 8 wallpaper, which is a beautiful flower photograph:

Windows 8 also ships with a set of default themes, Earth and Flowers. Here are thumbnails of the wallpaper sets that come with these themes:

Have you seen any other Windows 8 leaks you’d like to know more about? Drop us a line and let us know!

–Rafael Rivera and Paul Thurrott