Microsoft begins work on IE9 RTM-Escrow build

Microsoft is getting ever closer to releasing the final version of the much anticipated Internet Explorer 9. After its release candidate launch on Feb 10, the next traditional step for Microsoft will be to release an RTM-Escrow version of the software. RTM-Escrow means that development is no longer occurring and the project officially goes into testing mode, with external beta testers joining the fray to weed out any remaining bugs in the final product.

According to @hb860 in a Twitter post, the build number of the RTM-Escrow is 9.0.8110.16409. Microsoft typically releases the full RTM less than a month after the RTM-Escrow build, so it’s safe to assume that we’ll be seeing the next major update to the project in the near future.

The RC version of IE9 has its fans and detractors. While the RC has been downloaded 36 million times in less than a month, there are many who feel that the product is nowhere near the state it needs to be in to warrant a final release. The final stages of the project should fix a lot of the issues that the skeptics are worrying about. There won’t be any new features in subsequent builds, but there are still bugs to be found and squashed, and Microsoft will hopefully release a final version that will be able to stop browsers like Google Chrome and Firefox from taking more of browser market share from the once-dominant software.  

Report a problem with article
Previous Story

Opera becomes the first browser on Mac App Store

Next Story

BlackBerry Messenger coming to Android, iOS?

37 Comments

Commenting is disabled on this article.

Hopefully with the RTM version it will play nice with J River Jukebox. Right now, Jukebox crashes all the time because of the IE9 RC. And when I tried to uninstall it, it removed all traces of IE! I think it's because of the SP1.

"much anticipated"?

I guess that depends on the user, doesn't it. I'll stick with a browser that I can actually customize to fit my needs. Firefox.

Have fun with IE none the less.

COKid said,
"much anticipated"?

I guess that depends on the user, doesn't it. I'll stick with a browser that I can actually customize to fit my needs. Firefox.

Have fun with IE none the less.


A fat ass memory hog that fits your needs?

Have fun with Firefox I did when she was lean...

I agree, I thought "development is no longer occurring and the project officially goes into testing mode" always meant release candidate, and if needed, there is no problem doing RC2, that's why it's called a candidate.

Edit: This is in response to TCLN Ryster's post above, hit wrong button.

RTM-Escrow means that development is no longer occurring and the project officially goes into testing mode, with external beta testers joining the fray to weed out any remaining bugs in the final product.

Grrr. That's what RC is supposed to be for. RC is supposed to be at a stage for mass testing, ie. a version they think is suitable for release and just needs testing for any last minute bugs. Why invent another meaningless level called RTM-escrow. Sigh....

So no hope of a spellcheck. IE9RC broke ieSpell for me (on two computers, it jumbles words together). Hopefully, Spekie will fix its zoom bug. If you don't zoom, it seems usable now. BTW, most ads can be blocked using the PrivacyChoice2 PTL. Also, it would be nice if MS would allow IE64 to be the default browser since Speckie works with it.

refinement on the UI just look at the back button and you realize that...

performance wise i find it acceptable and its good but the UI mess that they have done its bad, and giving more option for customization would fix a lot

eilegz said,
refinement on the UI just look at the back button and you realize that...

performance wise i find it acceptable and its good but the UI mess that they have done its bad, and giving more option for customization would fix a lot

I have no problems or hatred of the back button and the UI works fine for me.

The biggest issue I see if that the title is no longer in the top portion of the app, which will drive macro writers at work nuts. First they have to complain, then revolt, and then dive in to find a new way to accomplish what they did in the past. Wish we could skip the first two steps.

JonathanMarston said,
I still run into performance issues on a few sites. This page, for instance, runs at about 2 fps on my computer in the RC: http://web.me.com/brandonfoy/B...Compositing_%26_Motion.html

I hope they fix these for the final...


I'm not sure they'll able to fix this issue. The reason this page is so slow is because of all the flash content. There are 2 possible solutions that come to mind: First, they would have to use HTML5 or Adobe Flash Player would have to be optimized.
In either case, not much MS can do about it

James_H said,

I'm not sure they'll able to fix this issue. The reason this page is so slow is because of all the flash content. There are 2 possible solutions that come to mind: First, they would have to use HTML5 or Adobe Flash Player would have to be optimized.
In either case, not much MS can do about it

It works fine in Chrome though...

MS needs to start dong minor upgrades to internet explorer... like 9.1, 9.2 etc as they complete standards and add more HTML / CSS specs into their rendering engine

neufuse said,
MS needs to start dong minor upgrades to internet explorer... like 9.1, 9.2 etc as they complete standards and add more HTML / CSS specs into their rendering engine

That would be nice but so far they're sticking to that new IE every year cycle so minor updates seem to be out of the question at this point. On the other hand, taking into account the jump from IE8 to IE9 standards wise it was a pretty big one, if that same thing happens with the next version I wouldn't complain.

neufuse said,
MS needs to start dong minor upgrades to internet explorer... like 9.1, 9.2 etc as they complete standards and add more HTML / CSS specs into their rendering engine

I think Microsoft is taking a sensible approach starting with IE9. They have stated that they will have frequent updates to the rendering engine... however those updates will continue to be released as "Platform Previews" for development testing. This will help prevent unexpected updates breaking things unexpectedly.

For example IE 9 RC breaks the netflix viewer in Windows 7 Media Center while IE 9 Beta had no problems. Microsoft has stated that this will be fixed at RTM.

neufuse said,
MS needs to start dong minor upgrades to internet explorer... like 9.1, 9.2 etc as they complete standards and add more HTML / CSS specs into their rendering engine

Completely agree + they should start autoupdating it like Chrome and FF do. Web development companies have additional costs because of broken IE browsers (yes, we do code standard code, but supporting IE7 and even IE6 is a pain, there are missing/broken CSS/JS features, even IE8 has few problems, but it's WAY better) and it's pretty impossible to explain to customers why something does not work on their IE6 (some government offices use IE6 still, nothing we can do about it)... not saying it's Mirosoft's fault (except for not forcing upgrade on IE7), it's lame admins that need to be kicked here.

Anyway, looking forward to IE9, too bad about not supporting some popular CSS3 features, but luckily there are pretty good workarounds (ie. css3pie) that don't require much work

neufuse said,
MS needs to start dong minor upgrades to internet explorer... like 9.1, 9.2 etc as they complete standards and add more HTML / CSS specs into their rendering engine

They won't do that because it would undermine the stability of IE that businesses rely upon.

GP007 said,

That would be nice but so far they're sticking to that new IE every year cycle

IE 4 in 1996
IE 5 in 1999
IE 6 in 2001
IE 7 in 2006
IE 8 in 2009
IE 9 in 2011

Since when is that a new IE every year?

jakem1 said,

They won't do that because it would undermine the stability of IE that businesses rely upon.

Then businesses can do what they always do. Wait to release updates until they are tested to make sure they work. Currently IE does get KB releases and Windows does get SP releases and I have already seen my work push both of those out. Most of our PCs have IE7 or IE8 and alot of those were pushed via the network. Also alot of them had SP3 pushed via the network.