Recommended Posts

Microsoft bombshell: no EFI support for Vista

Friday 10, March 2006 | By Dan Warne

From: Epinions › Hardware

Microsoft revealed today that it will not support EFI booting for Windows Vista on its launch. The news will be a shock for owners of Intel Macs who had hoped they would be able to dual-boot between Windows Vista and OS X. Intel Macs only support booting via EFI.

Speaking at Intel Developer Forum San Francisco, Microsoft development manager, Andrew Ritz, also revealed that there will never be any support for booting Windows via EFI on systems with 32-bit processors.

Although Microsoft has previously said EFI booting would be supported by Vista, Ritz admitted that EFI support won't be seen in any version of Windows until the release of Longhorn Server.

It will not be available in the release version of Windows Vista later this year – Microsoft says people will have to wait for an unspecified 'subsequent release of Windows client'. Ritz could not say whether that would be a service pack update to Vista or the next-generation of Windows.

NO EFI FOR YOU! Microsoft Development Manager Andrew Ritz has bad news for PC users hoping for next-gen booting.

Extensible Firmware Interface (EFI) is the modern and flexible successor to the 20-year-old PC BIOS. It is responsible for initialising hardware in the PC, and importantly, device drivers are stored in the EFI flash memory rather than being loaded by the operating system. It is a major change for the PC industry and both PC makers and Microsoft have been slow to make the switch. Because the Apple Intel Mac platform is entirely new, it does not have any legacy support concerns. It was hoped that 2006 would be the year PC makers would make the switch. Microsoft's lack of Windows support is a huge blow to Intel's hopes, and removes most of the incentive for PC makers to implement it in the short term.

That's terrible news for Intel Mac users who have been hoping that they could dual-boot Windows and Mac OS X on their new Macs: not only are their processors not 64-bit (and thus will never be supported by Windows EFI booting) but Windows Vista won't boot on EFI anyway.

It said its decision to 'reprioritise' EFI development to the server version of Windows was based on a lack of available desktop PCs with EFI support on the market.

"A combination of factors changed our plans. The big one, in my opinion was platform availability. With this huge move to 64-bit based platforms and for us to support it, we needed to see a large heterogeneous sample of 64 bit implementations out there for us to feel comfortable in supporting it." said Ritz.

source: http://apcmag.com/apc/v3.nsf/0/E666E4A0A30...A25712C008166C4

Link to comment
https://www.neowin.net/forum/topic/441073-no-efi-for-vista/
Share on other sites

I think this is a big mistake on Microsoft's part. I cannot imagine that it would take that much to add support for EFI (albeit I'm not a developer, so I could be wrong). We need to get rid of the aging BIOS and move to EFI and Microsoft not adding support for it means that OEMs won't add it (obviously). Bad, very bad decision.

It said its decision to 'reprioritise' EFI development to the server version of Windows was based on a lack of available desktop PCs with EFI support on the market.

Well theres a lack of desktop PC's with EFI support on the market because there is a lack of operationg systems supporting EFI. This is friggin stupid. Vista support all kinds of silly features that arnt released yet, where are thoes super high reselution displays they were touting a while back which vista will support?

They have a point, do any of you have a PC with EFI? I doubt it. It's useless right now. BUT...

I think new motherboards should start having them though, but I haven't heard of any PC motherboard company making the switch at all. And if Windows Vista EFI Support was only for 64-bit then its useless to Mac users since they're on 32-bit processors. For the ones that want EFI support, lets hope for a SP that adds it ;)

I find the current BIOS not user friendly at all for newbs, I've helped people over the phone with BIOS issues and its not easy since all BIOS are different. Hopefully EFI makes one standard and sets it easy.

I think this is a big mistake on Microsoft's part. I cannot imagine that it would take that much to add support for EFI (albeit I'm not a developer, so I could be wrong). We need to get rid of the aging BIOS and move to EFI and Microsoft not adding support for it means that OEMs won't add it (obviously). Bad, very bad decision.

Call me crazy, but I think this is all politics.

I think this has something to do with the Intel Macs and the fact that many people were going to purchase them only because they could run both OS X and Windows.

Does anybody else feel like this is just a stab at Apple from MS? It seems so... Before, MS had every intention to do it, then the craze set in that people would be able to run Vista on their shiny new Intel Macs, and now MS isn't going to support it...

Strange, very strange.

Ahh yes, Micro$haft's brilliant R & D always leading the industry with innovation................NOT!!!

One would think that a company that has 80% of the World using it's product would prefer to be in the driver seat in the industry.....but not so it's seems...instead a small company with an Apple as it's logo still leads in design with 8% of the Market share making windows users dream of the next best thing. lol They are certainly not afraid to take the bull by the horns.

Call me crazy, but I think this is all politics.

I think this has something to do with the Intel Macs and the fact that many people were going to purchase them only because they could run both OS X and Windows.

Does anybody else feel like this is just a stab at Apple from MS? It seems so... Before, MS had every intention to do it, then the craze set in that people would be able to run Vista on their shiny new Intel Macs, and now MS isn't going to support it...

Strange, very strange.

I completely agree with you. I think this is a stab right at Apple since Apple said that they don't have a problem with users installing Vista on the new Intel-based Macs. Very poor decision on Microsoft's part.

EFI can load any program, including a traditional BIOS.

If Apple junkies want to run XP on their new Macs, they can write a no-frills BIOS. XP only needs a few Interrupts to set up and boot.

Well it can't be that easy. If it was, then wouldn't someone already have figured out how to do it. Especially with $12,000+ on the line :p

They have a point, do any of you have a PC with EFI? I doubt it. It's useless right now. BUT...

I think new motherboards should start having them though...

Certain Intel mobo's have EFI, and a few Media Center PC's use EFI, but they include a CSM so Windows behaves as normal.

I completely agree with you. I think this is a stab right at Apple since Apple said that they don't have a problem with users installing Vista on the new Intel-based Macs. Very poor decision on Microsoft's part.

If anything, MS wants Windows on Mac's, that then increases their market share to PC and Mac users, making them more money.

and bob, elilo

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

    • No registered users viewing this page.
  • Posts

    • And thereby lies the rub. AV1 support is not as wide as paid analysts would have the industry believe. With AV2 around the corner, it's going cause more time backlog in adoption (how many recent purchasers will upgrade yet-again within the next 6-12 months? most would rather stay pat for another 1+ years before even thinking about upgrading their setups).
    • Microsoft OneDrive is getting a simple yet much needed feature by Sayan Sen Microsoft has been steadily expanding OneDrive’s file management capabilities over the years, including for shared content and shortcuts, although it has had its flaws, too. The cloud storage platform introduced support for folder shortcuts several years ago, allowing users to pin frequently accessed shared folders from OneDrive, SharePoint, and Teams. Now, Microsoft is refining that experience further with a new way to organize those shortcuts as revealed in a recent Microsoft 365 roadmap addition. Previously, shortcuts added through the “Add shortcut to My files” option would appear alongside all other files and folders in the root of a user's OneDrive. And although it's meant to be useful, this approach could also create clutter along the way, especially for heavy users who may have to work with large numbers of shared folders across multiple projects and teams on their systems. This is where Microsoft’s latest feature comes in, as it is looking to address this inconvenience by giving users the option to place new shortcuts inside a dedicated “Shortcuts” folder instead. The feature is designed to keep shortcut links organized into a single location instead of scattering throughout the main OneDrive directory. Hence, the idea is to make navigation and usability easier and simpler. The first time a user chooses this option, OneDrive will automatically create the folder, and to help make it stand out from the other folders, the Shortcuts folder will have a distinct visual identity featuring a unique color and a building-style icon. That being said, the new Shortcuts will behave just like any other folder in OneDrive, and as such, users will be able to move it to a different location, rename it, share it with others, or remove it entirely if they prefer a different structure. You can view the entry on the Microsoft 365 roadmap website here. Currently, the feature is in the "in development" phase, but the tech giant expects the rollout to start next month (July 2026). Do keep in mind, though, that new feature rollouts often get delayed.
    • VS Code 1.123 introduces massive upgrades for persistent AI developer workflows by Paul Hill Microsoft has just released Visual Studio Code 1.123 alongside its annual developer conference, Build 2026. This release, as always, has a heavy focus on advanced AI agent integration and making the built-in browser more robust. Notably, this update brings big sync changes that keep your AI agents persistent across sessions. With this update, VS Code now supports cross-machine syncing for chat histories, touched files, repository contexts, and related PRs via GitHub accounts, tying users even more into Microsoft’s developer ecosystem. This update also introduces the new /chronicle command that allows you to query past sessions using natural language, generate instant standup reports, and get personal productivity insights. Microsoft has also made some improvements to network-dependent operations, it explains: “When a terminal command that is run by a local agent requires access to domains that are not configured as allowed domains, the command is automatically retried inside the sandbox with unrestricted network access. After that, if it still fails, it falls back to unsandboxed execution. This allows network-dependent operations such as git fetch to finish, while keeping filesystem protections in place.” Microsoft has not stopped there; in this update, it also allows developers to drag, drop, and pin multiple agent sessions side-by-side for easy code comparisons in real-time. It also introduces the Research Agent, accessible via /research. This is a read-only, depth-optimized tool that gets data from the web, local codebase, and GitHub to give you a Markdown report on complex APIs or unfamiliar code. Now, let’s talk about the integrated browser and some security enhancements. VS Code 1.123 features enhanced screenshot capture tools that allow for targeted Area Screenshots and Full Page Screenshots to send layout context instantly to AI chat. The address bar has also been revamped, supporting favorite pages and tab management. Finally, on the security front, this update introduces a safety-first two-hour delay on third-party extension auto-updates to safeguard against compromised or buggy releases. This release is now available for Windows, Mac, and Linux. If you have VS Code, keep an eye out for the update availability notification. If you still don’t have VS Code, you can get it here.
    • I'm hoping with the Surface Pro 12, I can use either USB-C for my Xreal One Pro glasses. With my Surface Pro 11 OLED X Elite, I have to plug them into the top port. The bottom port will power it, but nothing shows on the screen. Maybe it's my setting. When I plug in the glasses, I have it output only to the glasses. So maybe I need to turn on both displays with it in the top port, then switch the glasses to the bottom port and set it to output only to the glasses. And then hopefully Windows remembers the settings for either the top port and bottom port (one of the awesome features of Windows where it remembers the exact configuration when plugging in external monitors.
    • Forgive my ignorance, but the only difference I see here is that a USB-A is now a USB-C, so there are two of them. For the modern age (and I'd argue since 2020), most products would now come with USB-C as an option, if not the default. Display, charging, devices, etc on TWO connectors, sometimes all combined! So having 2 of those powerful ports is great for something this size! Meanwhile my Surface Pro (5) has a single USB-A port which I cannot even get display out to, instead relying on some Surface Connect dock which I don't have. That is a poor experience, not to mention expensive and not compatible with other devices. Thank God USB-C is mainstream!
  • Recent Achievements

    • One Month Later
      B2Proxy earned a badge
      One Month Later
    • One Year In
      MadMung0 earned a badge
      One Year In
    • Week One Done
      jefred earned a badge
      Week One Done
    • Apprentice
      JoeyNeo went up a rank
      Apprentice
    • Week One Done
      oliviaexpo earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      482
    2. 2
      PsYcHoKiLLa
      227
    3. 3
      Skyfrog
      71
    4. 4
      FloatingFatMan
      60
    5. 5
      Nick H.
      54
  • Tell a friend

    Love Neowin? Tell a friend!