共用方式為


Internet Explorer 9 Release Candidate available via Automatic Update

Starting today, Monday, February 14, 2011, the Automatic Update (AU) feature of Windows Update (WU) will offer users of Internet Explorer 9 Beta an upgrade to the Internet Explorer 9 Release Candidate. This rollout will start with a narrow audience and expand over the next few days to cover all Internet Explorer 9 Beta users. This post provides information on how the Automatic Update delivery will work and announces the release of Internet Explorer 9 Automatic Update Blocker Toolkit.

How IE9 RC Automatic Update Delivery Works

Screen shot showing new updates available notificationAU will notify you when Internet Explorer 9 Release Candidate is ready to install. You can click on the bubble to launch Internet Explorer 9 Release Candidate installation. You can also install Internet Explorer 9 Release Candidate from Windows Update manually by launching Windows Update from the Start Menu and checking for updates.

Screen shot of Windows Update showing an update ready to install

When Windows Update starts installing Internet Explorer 9 Release Candidate, you will see the IE9 installation screen:

Screen shot of Internet Explorer 9 install dialog

To install Internet Explorer 9 Release Candidate, click Install. If you choose Ask me later, WU will re-offer Internet Explorer 9 Release Candidate to you during the next update scan. If you choose Don’t Install, WU will not offer Internet Explorer 9 Release Candidate via AU to you again, and Internet Explorer 9 Release Candidate will appear as an optional item on Windows Update. Users who decline the update can download Internet Explorer 9 Release Candidate from https://www.beautyoftheweb.com. We strongly encourage all IE9 Beta users to upgrade to the IE9 RC.

IE9 Automatic Update Blocker Toolkit

With IE9 RC released via Automatic Update, now is good time to prepare for the final IE9 release (the Release-to-Web, RTW, build). To help our users be more secure and up-to-date, we will eventually distribute the IE9 RTW build via AU and WU to all users. We know that in a corporate environment, the IT organization often wants to delay the introduction of a new browser until they have fully tested its compatibility with internal applications and sites. We’ve done a lot of work in IE9 to maintain compatibility with sites designed for Internet Explorer 8 and Internet Explorer 7 and intranet sites continue to run in Compatibility View (IE7 mode) by default. Regardless, we know many IT organizations will want to test IE9 before it is widely deployed.

To help prevent users from installing IE9 RTW through Automatic Update, we are providing the IE9 AU Blocker Toolkit which, when deployed, prevents IE9 RTW offered as an important update via AU. This Toolkit has no expiration date and can be configured either by running the registry file on the client machines or via Group Policy in domain joined environments. The Toolkit also provides an unblock procedure which can revert the block. We believe this approach strikes a good balance by helping customers become more secure and letting organizations control when they are ready to deploy IE9 to their users.

The Toolkit to Disable Automatic Delivery of Internet Explorer 9 is now available from the Microsoft Download Center.

The IE9 Blocker Toolkit has no impact on the IE9 RC AU deployment to IE9 Beta customers and, further, will not block the final version of IE9 offered to users who already have pre-released versions of IE9 installed on their machine. This is to ensure that we provide the latest security fixes to users running older pre-release versions of IE9. The toolkit, also, does not prevent users from manually installing IE9 from the Microsoft Download Center.

There are different registry keys used to block or unblock automatic delivery of IE9 and IE8. If you previously used the IE8 Blocker Toolkit to block IE8 from being offered as an important update, you will need to run the IE9 version of the Blocker Toolkit to block IE9 from being offered via AU.

Organizations that use an update management solution such as Windows Server Update Services (WSUS) or System Center Configuration Manager (SCCM) do not need to deploy the Blocker Toolkit. WSUS and SCCM allow organizations to fully manage deployment of updates released through WU, including IE9.

We encourage the timely deployment of IE9 while at the same time respecting your desire to deploy it on your schedule.

—Vishwac Sena Kannan and Jatinder Mann, IE Program Managers

Comments

  • Anonymous
    February 14, 2011
    in b4 arguments for IE switching to another engine

  • Anonymous
    February 14, 2011
    Great news! :D keep up the good work MS :D Best regards from Peru!

  • Anonymous
    February 14, 2011
    What OS(s) will this AU include? Also, is this for IE7-8 only?

  • Anonymous
    February 14, 2011
    Please do something about Gmail in IE9 RC. IE9 RC + Gmail + DISQUS social.answers.microsoft.com/.../9614b3b3-9ff7-4b42-ad3b-604f4793645b

  • Anonymous
    February 14, 2011
    Does this mean we aren't too far from the final IE9? I'd love to see IE9 released in the next few months so I can start getting the IE8 users I know to update =p

  • Anonymous
    February 14, 2011
    @kevindees: As called out in the blog, this Automatic update made available today only targets existing IE9 Beta users (on all IE9 Beta supported platforms).

  • Anonymous
    February 14, 2011
    All my Windows applications hosting IE as an editor ("designMode"="On") don't switch to design mode anymore :-( Any hints on this?

  • Anonymous
    February 14, 2011
    And IE9 will be offered through MU/WU ~3 months after release?

  • Anonymous
    February 14, 2011
    I am wondering when the IE 9 RTM is intended to be shipped (in about one/two months or more)? I am eager to propose my clients to use the new IE official version for the future web projects I will develop for them..

  • Anonymous
    February 14, 2011
    I look forward to the next version of Internet Explorer to restore all of the customization that was removed from this release. I'm sorry to see that requests of power users are getting ignored over and over. Doesn't it occur to the IE team that the great success of Firefox in the non-geek community is driven by requests from power users and subsequent implementation by FF developers?

  • Anonymous
    February 14, 2011
    The comment has been removed

  • Anonymous
    February 14, 2011
    @Máté Benyovszky: By changing the global setting.

  • Anonymous
    February 14, 2011
    That's what I'm talking about!!! I wish all pre-releases could be handled this way. Give me an option to see pre-release Microsoft products as optional updates. That would greatly simplify the beta process for us faithful beta users.

  • Anonymous
    February 14, 2011
    Its a fair bet that IE9 will be released (RTM at least) at MIX this year, Apr 12- 14.  Worst case, we can expect the RTM date to be announced then.

  • Anonymous
    February 14, 2011
    @Björn: thanks. Globally (Win7) font smoothing was switched off, but ie9 forced the use of it. Using Microsoft Cleartype tuner I switched on ClearType at a low level, which helped me te get readable fonts

  • Anonymous
    February 14, 2011
    Are their any statistics on if the percentage of users who turn off automatic updates is better in Win7 & Vista is any better than previous versions?

  • Anonymous
    February 14, 2011
    Stop trying to change the world's terminology.  Its RTM! always was, always will be. Just print:  IE9 RTM will be officially launched on April 12, 2011.

  • Anonymous
    February 14, 2011
    I am using IE9 Beta and i didnt get the update through my update and i have my WU set  to automatic so what does that mean

  • Anonymous
    February 14, 2011
    Very nice news !! I love IE.

  • Anonymous
    February 15, 2011
    We are thinking of doing some internet marketing ourselves, what do u think of using a website and newsletter like this marketing-mistress.com/JoinMyNewsletter.html

  • Anonymous
    February 15, 2011
    I just ran SunSpider with IE9 RC and Chrome 9, and my results: IE9 RC: 380.2ms Chrome 9: 597.2ms Nice work IE team!

  • Anonymous
    February 15, 2011
    The comment has been removed

  • Anonymous
    February 15, 2011
    @Máté Benyovszky: I believe that unlike XP there is no way to turn off font anti-aliasing and there is only the option of switching to greyscale anti-aliasing.

  • Anonymous
    February 15, 2011
    IE9 RC fails to install via Automatic Update, exactly the same way the downloaded version failed on my machine (see my post in Acting on Feedback: IE9 Release Candidate Available for Download). Essentially, I have all updates installed, Windows Updates sees nothing out of date, IE9 fails to install citing missing updates, and it fails further when clicking the [Get Updates] button. This is really annoying.

  • Anonymous
    February 16, 2011
    The comment has been removed

  • Anonymous
    February 16, 2011
    @geniuseire: There's a known issue on first startup on certain hardware with a certain number of fonts installed. We have a plan to address this, thanks.

  • Anonymous
    February 16, 2011
    @Vishwac Sena Kannan, Thanks.

  • Anonymous
    February 16, 2011
    Please make a Virtual PC image for IE9 RC available. I downloaded the Vista+IE8 VPC image last night. It's almost two years old, so there were ~80 updates, which bloated the main VHD to 10GB. Then I had to install Vista SP2 on a differencing disk, 6GB. Only now have I finished installing IE9. thanks

  • Anonymous
    February 17, 2011
    ERIC , Thank you for your response the accelerated graphics is unchecked (rendering)  Graphics card Ati Radeon 5770 1 gb gddr5

  • Anonymous
    February 18, 2011
    The comment has been removed

  • Anonymous
    February 20, 2011
    At Win7 64bit, two "iexplore.exe*32" keep running at background.

  • Anonymous
    February 22, 2011
    This is really good and it help me a lot.read more:www.inetmystreet.com

  • Anonymous
    February 25, 2011
    Ditto on the designmode issue mentioned here.  This is a pretty serious issue that was not present in the beta.