Windows Live Messenger 8.5 Update Soon!


Recommended Posts

I think it's a really stupid move to drop XP x64 support. I actually thought the next step for them would be to provide a native 64-bits build (for both Vista x64 and XP x64)... :pinch:

Back in November we shipped the final version of Windows Live Messenger 8.5 along with several other Windows Live applications and services. A lot of you have already upgraded, and for that we thank you and hope you?re enjoying it as much as we enjoyed building it. Starting soon, we?re going to make it easier for those of you who haven?t upgraded yet to get onto our latest and greatest.

This will happen in two phases. First, everyone running Windows XP or Windows Vista will get a prompt encouraging you to upgrade. When you accept the upgrade, the new unified installer will launch and start upgrading Messenger. While it?s installing, you?ll have the option to download and install other Windows Live applications. You don?t have to take any of them, but we think you?ll like them and hope you?ll give them a try.

It will take a couple of weeks for us to get this upgrade out to all users, so if you don?t get it right away don?t worry, it?s coming. If you don?t want to wait, you can go to http://get.live.com/messenger/overview to download and install Messenger 8.5 right now.

After everyone?s gotten the optional upgrade, those of you still running a beta version of Messenger 8.5 will receive a required upgrade to the final version. When this phase kicks in you?ll be blocked from logging in until you complete the upgrade. The final version is even better and more stable than the beta versions, we want you to have the best experience possible! A special note for those of you running Messenger 8.5 Beta on Windows XP 64-bit or Windows 2003 Server: the final version of Messenger 8.5 will not install or run on your OS. We don?t want you to get stuck out in the cold so you will not receive the mandatory upgrade to the final version. However, these operating systems won?t be supported by future Messenger versions. You may stay on your current beta version, or to get to a more stable final version we recommend that you uninstall Messenger 8.5 and go back to Messenger 8.1Source:->.

Source: Windows Live Messenger Team Blog

what the.... "these operating systems won?t be supported by future Messenger versions".

I really fail to understand this move, it makes no sense at all. How is Microsoft planning to push third parties to develop for x64 if even themselves don't give a damn about it?

Apparently, according to this source, Windows Lve Messenger v8.5 DOES support those operating systems, its the Windows Live Installer Suite that doesn't. So if you can download the messenger set-up file then it should work.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I don't understand the vision. Do people really want to buy a new computer from Dell with 6 browsers installed? We all keep asking for Microsoft to stop having so much junk on their OS, and adding a bunch of browsers seems to go against that. Ideally, we would just be asked what browser we want during OOBE but Google is just going to pay Dell a bunch of money to include Chrome. Additionally, would you want your phones to start including all the browsers too when you get them? The only thing I ever wanted was to be able to uninstall IE or edge and I believe you are now able to. I do agree that microsoft needs to chill with their "are you sure you don't want to try edge before you install chrome" ads when going to download chrome.
    • The funny thing here is that like 70% or so of the web browser users use 'Google Chrome' as web browser. What I don't understand is that why on earth would ANYONE choose 'Google Chrome' on Windows when 'Microsoft Edge' is not just better in most things, but it's already there right out of the box for the Windows users. Microsoft Edge has less data collection (yes, that's a fact), less RAM usage and is more optimized for Windows (as it's a Microsoft product) right out of the box. I'm sure you will come with the argument of bloat in Microsoft Edge. Sure, but most of that can be fixed with a simple tool (there are many good ones out there for this). Yes, that require a couple of clicks in the same way as it requires several clicks to install 'Google Chrome'. And I'm sure you really love the 4 GB of AI-slop data 'Google Chrome' is downloading for Chrome without you agreeing to it. Fun right? Sure, the way Microsoft is pushing 'Microsoft Edge' on users might not be the best way of doing it and might need to change. But I would never choose 'Google Chrome' over 'Microsoft Edge' today anyways. I'm sure there was a period back in the days when 'Google Chrome' actually was better in most things, but that period is not today.
    • JetBrains rolls out IntelliJ IDEA update with Markdown preview fixes and more by David Uzondu Image via JetBrains IntelliJ 2026.1.3 from JetBrains has landed, bringing several highly requested bug fixes that target common UI glitches and terminal rendering issues. If you run tmux inside the integrated terminal, the IDE no longer renders the cursor above the active line. The Markdown preview bug, which was fixed in this release, had annoyed developers for quite some time, as the preview pane failed to render images saved outside the project directory. Instead of displaying the actual image, the IDE simply showed a broken image icon, a problem that stuck around for two years before this update. Over on Windows, developers running WSL can now use wsl.exe to spin up their environments without losing terminal functionality. In previous builds, launching a terminal shell with something like wsl.exe -d ubuntu inside a Windows-based project broke both shell integration and active process detection. Other bug fixes in this release include: An issue where Gradle sync incorrectly reported success as a failure on WSL when using Gradle 9.5.0. A syntax highlighting bug that flagged valid Java for-loop initialization blocks with multiple statements as incorrect. A warning bug that triggered a false non-null local variable alert when using JSpecify annotations. A database generation bug that hid the option to use a DELETE statement instead of a TRUNCATE checkbox. A Kotlin highlighting failure where an assertion error in the Gradle redundant library inspection broke error highlighting. A UI bug where the ComboBox popup lacked a maximum height restriction. A Snowflake syntax error where DataGrip failed to support the "create temp" command. A Svelte syntax parsing failure that incorrectly flagged quotes inside inline expressions. A VCS repository manager deadlock that triggered thread pool exhaustion. A memory leak where the LazyTree component kept all previous versions of a tree in memory. IntelliJ 2026.1.3 is the third bug fix release for the IntelliJ 2026.1 series. The first one landed back in April with a fix for the WSL Python interpreter freeze, another fix for guest participants using Emmet abbreviations, and corrected WildFly server deployment errors.
    • That stupid annoying Sign in with Google on all these sites now... get the fk outta here
  • Recent Achievements

    • Collaborator
      Asgardi earned a badge
      Collaborator
    • Conversation Starter
      mobandz earned a badge
      Conversation Starter
    • Apprentice
      fernan99 went up a rank
      Apprentice
    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      469
    2. 2
      PsYcHoKiLLa
      243
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      73
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!