Windows 7 support by the end of the year?


Recommended Posts

I have been waiting for this before i wanted to setup mine to work on it. I have a Early 2009 MacBook (Aluminum Unibody) however I was waiting for the bootcamp support before i Attempted it.

Everything works fine in Bootcamp for me under Windows 7.

******! You're using old outdate Windows Vista drivers. There are no officially supported Windows 7 bootcamp drivers yet.

On new 13 inch Macbook pro, sleep is sometimes messed up when the lid is closed, the audio drivers don't function correctly (there's more sound output from the left audio channel than the right, no stereo and the sound is very poor quality), the SPDIF output light is also also always on, and additionally the trackpad is also often horribly over sensitive.

All is not quite as sweet as you assume it to be. These are among a few of a great many very well documented faults.

Edited by bmaher
Swear filter evasion
******! You're using old outdate Windows Vista drivers. There are no officially supported Windows 7 bootcamp drivers yet.

On new 13 inch Macbook pro, sleep is sometimes messed up when the lid is closed, the audio drivers don't function correctly (there's more sound output from the left audio channel than the right, no stereo and the sound is very poor quality), the SPDIF output light is also also always on, and additionally the trackpad is also often horribly over sensitive.

All is not quite as sweet as you assume it to be. These are among a few of a great many very well documented faults.

10.6 has Windows 7 drivers. P.S you can use Vista drivers for 7. Quit spreading the FUD.

Edited by bmaher
fixed quote
Apple engineers are on holiday at the moment (probably) so it'll have to wait til the new year.

Seriously, can they say that? I mean can they say something as definite as that and then just not bother? Is that how Apple works?

Anyway I am using 10.6x. My MBP came with it installed - and the lasted boot camp drivers. No official Windows 7 drivers there. I have no clue why you're talking about 'fud'. These are real faults, why would anyone even go to the trouble of making them up?

Edited by jebus197
******! You're using old outdate Windows Vista drivers. There are no officially supported Windows 7 bootcamp drivers yet.

On new 13 inch Macbook pro, sleep is sometimes messed up when the lid is closed, the audio drivers don't function correctly (there's more sound output from the left audio channel than the right, no stereo and the sound is very poor quality), the SPDIF output light is also also always on, and additionally the trackpad is also often horribly over sensitive.

All is not quite as sweet as you assume it to be. These are among a few of a great many very well documented faults.

Whether they be Windows 7 drivers or Windows Vista drivers - it works - flawlessly. 99% of Vista drivers work fine with Windows 7 anyway.

Everything works, I have no errors, and the only really important driver (performance wise), the graphics driver, is automatically updated via Windows Update anyway.

Also...

Thread Cleaned.

Please keep it civilised and please don't evade the swear filter.

Whether they be Windows 7 drivers or Windows Vista drivers - it works - flawlessly. 99% of Vista drivers work fine with Windows 7 anyway.

Everything works, I have no errors, and the only really important driver (performance wise), the graphics driver, is automatically updated via Windows Update anyway.

I am very glad everything works for you. But the point I was trying to make is that this isn't the case for everyone - and in this case they clearly don't work completely effectively for me.

Also Windows Vista drivers are still Windows Vista drivers. Just because they work (although again, they don't work all that well for me) doesn't mean by any measure that they have been optimised for Windows 7. There are still likely to be several improvements to be gained from using fully dedicated drivers.

Whether they be Windows 7 drivers or Windows Vista drivers - it works - flawlessly. 99% of Vista drivers work fine with Windows 7 anyway.

Everything works, I have no errors, and the only really important driver (performance wise), the graphics driver, is automatically updated via Windows Update anyway.

Also...

Thread Cleaned.

Please keep it civilised and please don't evade the swear filter.

I didn't evade it. I edited it myself. Lol. Since when is **** swearing anyway?

Anyway sorry for being frustrated, I just don't get it when people idiotically deny any possibility of a fault with a sytem purely on the basis of what seems like some kind of obsessive brand loyalty. What makes it especially dumb and frustrating is that these faults are real and are not made up, or 'fud' at all.

Edited by jebus197

The Vista boot camp drivers may "work" with Windows 7, but there's obviously room for improvement, as my 2 year old lower-spec'd HP boots and runs 7 faster than my brand new MBP. There's also the hyper-sensitive touchpad driver. Many times I'll accidently click something when I'm meaning to scroll. And they need to update the drivers to allow Windows 7's power management to do its job better - as it is it can't even control screen brightness...

Everything seems to work fine here. Windows 7 Ultimate 32Bit. I got the latest drivers from the NVIDIA site. However I had a nightmare installing it because when it rebooted it didnt turn the screen back on. It just sat there black screen. I eventually got it sorted just guessed when to press next on the windows install lol. It rebooted fine though.

As I said, I think you guys are possibly missing the point slighly. The point of the thread, and my question isn't that 'it works for you', it's that there are plenty of cases, especially with some of the newer MBP's where the old Windows Vista drivers don't work all that well at all.

Also the point is that they are mostly all still Windows Vista drivers, hence not optimised for the new Windows 7 kernel etc. Thus at some point or other, you will still be missing out on performance.

Moreover the starting premise of the thread was simply that Apple seemed to be taking their own dear sweet time in holding themselves to a promise they made shortly after Windows 7 was officially released.

There's still clearly some time for them to do this, but it does seem odd that they are cutting it so fine.

Edited by jebus197
Seriously, can they say that? I mean can they say something as definite as that and then just not bother? Is that how Apple works?

Anyway I am using 10.6x. My MBP came with it installed - and the lasted boot camp drivers. No official Windows 7 drivers there. I have no clue why you're talking about 'fud'. These are real faults, why would anyone even go to the trouble of making them up?

Well maybe they planed to release before Christmas but some major bug appeared they ran out of time and rather than release a pile of crap come back in the new year.

The Boot Camp drivers work in Windows 7. They work just fine, in fact, considering that it's not the OS the hardware was designed for. However, the drivers are designed for Vista, and my understanding is that 7 offers some new things, like better power management, multi touch support (via the trackpad), etc.

I'm hoping that the reason Apple is taking their time is because they're taking advantage of all Windows 7 has to offer. They showed some promise with the improved drivers included with Snow Leopard.

The Boot Camp drivers work in Windows 7. They work just fine...

But the point is they don't work well in all cases! Look up the issues I have described on any notable Apple forum and you will find more than plenty examples of these.

However you are correct that Windows Vista drivers have also not been optimised for Windows 7, so overall performance is unlikely to be on the same level as a sytem running fully dedicated drivers.

Vista drivers works fine on my MacBook Pro 13"... but the tap click is too sensitve, the optical light is always on and Im using a modified sound driver to get max. volume. Then the line-in doesn't work... I would be glad if they improved the trackpad driver alot, and released it soon...

I installed Windows 7 x64 without Bootcamp, erasing everything the disk had, natively alone, at an Aluminium iMac.

I also installed drivers natively from each hardware manufacturer missing ( one :p )

All that was missing, a stupid Bluetooh stack Apple uses and a Special Key, in iMac keyboard for eject.

Everything, even iSight Camera was instantly recognised by Windows 7 + Windows Update.

I just installed Bluetooth Stack from Vista, and the stupid button.

I updated even Drivers that Windows 7 recognised such as Realtek Audio, Marvel Yukon Gigabit and Broadcom Wireless.

PC..errrrm the Mac now runs superb/splendid Windows 7 x64 native, alone.

No need to wait for Apple SuperDuper Engineers...

P.S. to install I had to alter the original win7 iso, so Apple's stupid EFI co-operates with UEFI 2.x that Windows 7 x64 support, or else both Windows/EFI boot were halted.

Lol, I give up! It's completely irrelevant that "it works for you." Clearly if you read the links I supplied above you will find that this is not the case for everyone.

Many of the drivers for the newer Macbook Pros cannot be downloaded directly from the manufacturers site. This includes trackpad and audio drivers (and chipset drivers too - which will almost certainly have a direct impact on performance).

I also have to run hacked audio drivers to get 'full' volume, although the sound quality is still nothing short of terrible and there is higher volume coming from the left speaker than the right speaker.

Again I genuinely can't see the point of posting comments saying 'it works for me.' If it does, then great, what this means is that you're not affected. It probably also means you're running a slightly older version of a Macbook.

Moreover working drivers and 'optimised' drivers are not the same thing. Working Vista drivers may appear to work, but they are not optimised for Windows 7, hence performance overall is likely to suffer.

http://support.apple.com/kb/HT3920

Note: The following models will not be supported for use with Windows 7 using Boot Camp.

iMac (17-inch, Early 2006)

iMac (17-inch, Late 2006)

iMac (20-inch, Early 2006)

iMac (20-inch, Late 2006)

MacBook Pro (15-inch, Early 2006)

MacBook Pro (17-inch, Late 2006)

MacBook Pro (15-inch, Late 2006)

MacBook Pro (17-inch, Early 2006)

Mac Pro (Mid 2006, Intel Xeon Dual-core 2.66GHz or 3GHz)

Does anyone know why this is the case that they are not supported? is it a technical reason or a matter of policy because these products are End of Life? And does anyone know if any technical restriction will be put in place to prevent attempted installation on this hardware in an unsupported manner?

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

    • No registered users viewing this page.
  • Posts

    • NASA: This asteroid may not kill us but it probably won't be far off either by Sayan Sen Image by Zelch Csaba via Pexels New observations by NASA's James Webb Space Telescope have eliminated the last remaining impact threat posed by asteroid 2024 YR4, ruling out the possibility that the near-Earth object could strike the Moon in December 2032. NASA said observations collected by Webb on February 18 and 26, 2026, enabled scientists to refine the asteroid's orbit enough to "rule out a chance of lunar impact on Dec. 22, 2032." Instead, asteroid 2024 YR4 is now expected to pass the Moon at a distance of about 13,200 miles (21,200 km). The agency stressed that the update "reflects improved precision in our understanding of where the asteroid is expected to be in 2032 rather than a shift in its orbital path." The announcement closes a remarkable chapter in planetary defence that began in late 2024, when the approximately 60-metre-wide asteroid briefly became the most closely watched near-Earth object in the world. Discovered on December 27, 2024, by the ATLAS telescope in Chile, 2024 YR4 initially appeared to have a small chance of colliding with Earth on December 22, 2032. As astronomers gathered more observations, the impact probability briefly climbed to around 3%—the highest ever recorded for an asteroid of its size—before steadily falling as its orbit became better understood. By early 2025, international observations had ruled out any significant risk to Earth. However, astronomers were left with another possibility: a roughly 4% chance that the asteroid could instead strike the Moon. "The probability that asteroid 2024 YR4 will strike the Moon on 22 December 2032 is now approximately 4%," the European Space Agency (ESA) had said last year, noting that "there is a 96% chance that the asteroid will not impact the Moon." ESA said such an impact, while unlikely, would have presented an extraordinary scientific opportunity. "It is a very rare event for an asteroid this large to impact the Moon – and it is rarer still that we know about it in advance. The impact would likely be visible from Earth, and so scientists will be very excited by the prospect of observing and analysing it," said Richard Moissl, Head of ESA's Planetary Defence Office. "It would certainly leave a new crater on the surface. However, we wouldn't be able to accurately predict in advance how much material would be thrown into space, or whether any would reach Earth," he added. The asteroid also exposed an important blind spot in planetary defence. Because 2024 YR4 approached Earth from the direction of the Sun, it remained hidden from ground-based telescopes until after its closest approach. "We looked into how Neomir would have performed in this situation, and the simulations surprised even us," Moissl said. "Neomir would have detected asteroid 2024 YR4 about a month earlier than ground-based telescopes did. This would have given astronomers more time to study the asteroid's trajectory and allowed them to much sooner rule out any chance of Earth impact in 2032." He added, "As an infrared telescope, like Webb, Neomir would have also immediately given us a much better estimate for the asteroid's size, which is very important for assessing the significance of the hazard." The latest NASA observations underscore the value of space-based infrared telescopes in tracking faint asteroids. According to NASA, Webb made "among the faintest ever observations of an asteroid," extending the object's observational record by nearly eight months at a time when it had become too faint for other telescopes. That additional data allowed scientists to eliminate the remaining uncertainty surrounding its 2032 flyby. Although asteroid 2024 YR4 is now confirmed to pose no threat to either Earth or the Moon, scientists say its discovery remains one of the most significant real-world tests of the international planetary defence system, demonstrating how continued observations can rapidly transform an object once considered hazardous into one whose future path is known with high confidence. Source: NASA, ESA This article was generated with some help from AI and reviewed by an editor. Under Section 107 of the Copyright Act 1976, this material is used for the purpose of news reporting. Fair use is a use permitted by copyright statute that might otherwise be infringing.
    • Yup. Google is just scraping the entire internet for their own ad profits without sharing revenue with the sources. It's obviously stealing, but since these sites depend upon Google's search scraps to survive... As for me, I just stopped using Google for anything except Reddit searches. If Reddit's own search wasn't complete crapola, I'd never use Google search again.
    • I had a feeling this was coming. Picked up my first Mac ever last Saturday. Glad I did.
    • In a major surprise there is actually some good deals for the first time in years. At least for me.
  • Recent Achievements

    • Conversation Starter
      Admir earned a badge
      Conversation Starter
    • First Post
      The_Focal_Point earned a badge
      First Post
    • Apprentice
      daryld went up a rank
      Apprentice
    • Contributor
      Carltonbar went up a rank
      Contributor
    • One Month Later
      The_Focal_Point earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      419
    2. 2
      +Edouard
      169
    3. 3
      PsYcHoKiLLa
      130
    4. 4
      Xenon
      70
    5. 5
      neufuse
      69
  • Tell a friend

    Love Neowin? Tell a friend!