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

    • Meta announces a major leadership change at WhatsApp by Pradeep Viswanathan Meta has announced a major leadership change at WhatsApp, with Will Cathcart stepping down after seven years of leading the world's largest messaging platform. CRED CEO and founder Kunal Shah will take over as the next global head of WhatsApp. CRED is an Indian fintech company focused on creditworthy consumers. As part of the transition, Meta is also making a minority investment in CRED through its Series H funding round. Meta CEO Mark Zuckerberg said Will Cathcart will remain at Meta and move into a new role focused on building new products from the ground up. Cathcart led WhatsApp during a major growth phase, helping the app reach more than 3 billion users worldwide. He also played a key role in expanding WhatsApp’s business offerings while keeping privacy and end-to-end encryption central to the product. Meta’s Chief Product Officer, Chris Cox, said Kunal Shah was selected after a search for a leader who understands WhatsApp’s global scale and future potential. In a leaked internal memo, Cox described Shah as a “serial founder” and one of India’s most respected entrepreneurs, adding that he brings “entrepreneurial energy” and a strong product mindset to the role. As part of the Series H funding round, CRED is raising ₹8,550 crore, or about $900 million, in a round led by Meta. The funding values CRED at ₹43,239 crore, or about $4.5 billion, on a post-money basis. It is important to note that this investment will not give Meta access to CRED customer information. Kunal posted the following on X regarding his new role at Meta: Although Kunal Shah will be stepping away from his operating role as CRED CEO, he will retain his personal shareholding in the company.
    • It wouldn't be hard for me to turn off my TV, if I had one. For one thing, I never scroll Instagram. The only reason I have an account is because Meta created one when it merged the account systems for its various services.
    • OpenAI's new GPT-5.5-Cyber tops Claude Mythos 5 in vulnerability benchmark by Pradeep Viswanathan OpenAI today announced a major expansion of Daybreak, a cybersecurity initiative designed to help defenders find, validate, and fix software vulnerabilities earlier in the development process. The availability of powerful AI models has definitely changed the cybersecurity landscape by making vulnerability discovery much faster. However, the bigger bottleneck for the industry is now patching those vulnerabilities. Impacted software teams need to validate the discovered issues, understand their impact, develop fixes, test them, and deploy patches. Back in March, OpenAI launched a preview of Codex Security, which uses agentic reasoning with automated validation to discover high-impact issues and actionable fixes specific to the codebase. Since then, it has scanned more than 30 million commits across over 30,000 codebases; more than 70,000 findings were marked as fixed by human reviewers, while over 500,000 findings were automatically determined to be fixed. Now, OpenAI is releasing an updated Codex Security plugin that can run deep scans, review recent code changes, generate security reports, trace attack paths, validate findings, and create codebase-specific patches for human review. It can also triage findings from existing scanners, advisories, bug bounty reports, and ticketing systems. OpenAI says the plugin can export results to vulnerability management systems and integrate with workflows using SARIF files, CodeQL queries, the Codex CLI, and the Codex app. Back in May, OpenAI announced the preview of GPT-5.5-Cyber, a new model built on top of the recently released GPT-5.5, designed for specialized cybersecurity work. Today, OpenAI launched the full version of GPT-5.5-Cyber through a limited release for verified defenders. On CyberGym, GPT-5.5-Cyber scored 85.6%, compared with 81.8% for GPT-5.5 and 83.8% for Claude Mythos 5. It also scored 39.5% on ExploitGym, compared with 25.95% for GPT-5.5, and 69.8% on SEC-bench Pro, compared with 63.1%. OpenAI also announced the new Daybreak Cyber Partner Program, which will allow security vendors and service providers to use GPT-5.5 with Trusted Access for Cyber in their products and services. Accenture, Akamai, Cisco, Cloudflare, CrowdStrike, IBM, Palo Alto Networks, Proofpoint, SentinelOne, Wiz, Zscaler, and others were listed as initial partners for this program. OpenAI is also launching Patch the Planet with Trail of Bits, HackerOne, Calif, researchers, and maintainers. More than 30 open-source projects have committed to participate, including cURL, Go, Python, Sigstore, and pyca/cryptography.
    • AMD confirms 26.6.2 FSR driver breaks on many Windows PCs by Sayan Sen Earlier today AMD released a major graphics driver update as it brings support for FSR 4.1 to Radeon RX 7000 series GPUs. The new update, version 26.6.2, also brings support for Assassin's Creed Black Flag Resynced and more. And while the driver technically supports Windows 10 version 21H2 and newer, the tech giant has confirmed that there is a major issue with the new driver on non-Windows 11 PCs as it fails to launch properly on such systems. The error message says, "The version of AMD Software that you have launched is not compatible with your currently installed AMD graphics driver." Therefore on the surface it looks like a compatibility problem. AMD has also confirmed that the device manager will display the yellow bang or yellow exclamation sign alongside your GPU under the Display adapters dropdown. Here is what the Radeon team's official advisory recommends to affected users: "Users Running Windows 10 and AMD Software: Adrenalin Edition 26.6.2 May Encounter Yellow Bang in Device Manager Affecting AMD Radeon RX Series Graphics ... Our Engineers are currently investigating this issue and will provide a fix once it is available. Affected users may revert to AMD Software: Adrenalin Edition 26.6.1 as a temporary workaround." As such you should revert back to the previous 26.6.1 driver which was released earlier this month. In case you were looking to play Assassin's Creed Black Flag Resynced and DOOM: The Dark Ages | Revelations you will probably have to wait a while if you want the driver to support those games officially. You can find the support article here on Microsoft's website.
  • Recent Achievements

    • One Month Later
      nates earned a badge
      One Month Later
    • Week One Done
      Almohandis earned a badge
      Week One Done
    • Rookie
      dorf went up a rank
      Rookie
    • First Post
      mike_rumble earned a badge
      First Post
    • Dedicated
      tuben earned a badge
      Dedicated
  • Popular Contributors

    1. 1
      +primortal
      508
    2. 2
      +Edouard
      208
    3. 3
      PsYcHoKiLLa
      100
    4. 4
      Michael Scrip
      89
    5. 5
      neufuse
      71
  • Tell a friend

    Love Neowin? Tell a friend!