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

    • Microsoft releases PowerToys v0.100.1, fixes a bug that made remapped keys misbehave by Ivan Jenic Microsoft just released PowerToys v0.100.1, a patch update that addresses several stability and behavior issues found in v0.100.0. The v0.100.0 patch was a significant update for PowerToys, as it introduced all sorts of new features and additions, such as a rebuilt Shortcut Guide, a Command Palette Extension Gallery, webcam overlay support in ZoomIt, and more. However, the v0.100.0 version also introduced some bugs and stability issues. And now, Microsoft is addressing these issues in the new patch. The most impactful fix in this release perhaps is in Keyboard Manager, where remapped modifier keys were being delivered as system-key events, causing unexpected behavior in apps. The clearest example of this was Alt-to-Backspace remaps, deleting whole words instead of a single character. So, if you thought there was an issue with your keyboard, Microsoft just confirmed that it was PowerToys. Beyond the Keyboard Manager fix, v0.100.1 also addresses several other issues. It fixes a bug with Power Display that was preventing monitors from waking from standby correctly. Additionally, the new update patches Quick Access crashes on launch, and resolves a Shortcut Guide crash that occurred when switching between sidebar sections. Here’s the full changelog: Color Picker Fixed a bug where the main Color Picker window could appear inside the zoomed-in picker view Command Palette Fixed Run history initialization in AOT builds Fixed a bug where the Performance Monitor dock item could show ??? after restart Fixed the Hibernate command using the Sleep icon Limited the "pin to dock" dialog to displays where the dock is enabled Keyboard Manager Fixed modifier keys remapped to non-modifier keys being delivered as system-key events, which caused unexpected behavior in apps such as Alt-to-Backspace deleting whole words Power Display Fixed a bug where selecting On in the monitor power-state control did not wake a monitor from standby Fixed built-in display detection and brightness control on dual-GPU laptops where the internal panel is driven by the discrete GPU PowerToys Run Fixed VS Code Workspaces discovery after VS Code moved recently opened workspace data to shared storage Quick Access Fixed Quick Access flyout crashes caused by unhandled XAML exceptions during launch or page navigation Shortcut Guide Fixed a crash when navigating between Shortcut Guide sidebar sections Fixed number-key rendering in shortcut manifests and added a Postman shortcut manifest Updated bundled shortcut manifests to use the literal number-key token so number keys render correctly across apps ZoomIt Fixed a race condition in audio initialization for ZoomIt video recording You can download PowerToys v0.100.1 from the official GitHub releases page.
    • OBS Studio 32.2.0 Beta 2 by Razvan Serea OBS Studio is software designed for capturing, compositing, encoding, recording, and streaming video content, efficiently. It is the re-write of the widely used Open Broadcaster Software, to allow even more features and multi-platform support. OBS Studio supports multiple sources, including media files, games, web pages, application windows, webcams, your desktop, microphone and more. OBS Studio Features: High performance real time video/audio capturing and mixing, with unlimited scenes you can switch between seamlessly via custom transitions. Live streaming to Twitch, YouTube, Periscope, Mixer, GoodGame, DailyMotion, Hitbox, VK and any other RTMP server Filters for video sources such as image masking, color correction, chroma/color keying, and more. x264, H.264 and AAC for your live streams and video recordings Intel Quick Sync Video (QSV) and NVIDIA NVENC support Intuitive audio mixer with per-source filters such as noise gate, noise suppression, and gain. Take full control with VST plugin support. GPU-based game capture for high performance game streaming Unlimited number of scenes and sources Number of different and customizable transitions for when you switch between scenes Hotkeys for almost any action such as start or stop your stream or recording, push-to-talk, fast mute of any audio source, show or hide any video source, switch between scenes,and much more Live preview of any changes on your scenes and sources using Studio Mode before pushing them to your stream where your viewers will see those changes DirectShow capture device support (webcams, capture cards, etc) Powerful and easy to use configuration options. Add new Sources, duplicate existing ones, and adjust their properties effortlessly. Streamlined Settings panel for quickly configuring your broadcasts and recordings. Switch between different profiles with ease. Light and dark themes available to fit your environment. …and many other features. For free. At all. OBS Studio 32.2.0 Beta 2 changelog: Beta 2 Changes Fixed a CI deployment issue. There are no application changes since Beta 1. 32.2 New Features Replaced add source dropdown with new dialog [Warchamp7] Improved FPS selector UX [jcm93] Added missing file support for filters [exeldro] Added ability for plugins to set custom icons for new source types [cg2121] Included .webp files when adding a directory to Image Slide Show source [TarunCore] Added copy paste functions to frontend API [exeldro] Added filter to compose SDR into HDR [jpark37] Added delete as a hotkey to delete sources on macOS [PatTheMav] Added dynamic bitrate support to multitrack video [lexano-ivs] 32.2 Changes Forced Intel-based installations to update to Apple Silicon version on macOS [PatTheMav] This change means that OBS Studio versions built for Intel-based Macs but running on Apple Silicon Macs will automatically update to OBS Studio built for Apple Silicon Macs. If an installation was using third-party plugins, those plugins will no longer load until replaced with Apple Silicon versions. Fixed audio mixer state getting out of sync when changing settings via websockets or plugins [Warchamp7] Added theming for checked QToolButtons [glikely] Improved OpenGL performance slightly on low-end machines [kkartaltepe] Set minimum size for color source to 1 pixel [exeldro] Added minimum width to spinboxes [Warchamp7] Disallowed overwriting the crash handler [sebastian-s-beckmann] Applied process mitigation policies for Windows [notr1ch] Adjusted description of multitrack video [jhnbwrs] Changed new capture devices to use fallback frame rate by default [PatTheMav] Improved DLL loading behavior on Windows [notr1ch] Limited multitrack video config to Custom service [PatTheMav] 32.2 Bug Fixes Fixed OAuth and dock state save corruption [PatTheMav] Fixed group bounds not resizing when removing items [howellrl] Fixed canvas mixes not being restored after video reset [dsaedtler] Fixed some erroneous crashes during shutdown [Warchamp7] Fixed display capture sometimes capturing black after a duplicator failure [ThrowTop] Fixed color of controls dock output buttons in System theme [shiina424] Fixed virtual camera reset failures [stephematician] Fixed potential crash when user discards changes in the settings window [suogesi] Fixed incorrect return value in virtualcam filter [xtfo] Fixed source toolbar buttons not working after dragging a source into a group [Warchamp7] Fixed properties hint icon spacing [Warchamp7] Fixed potential crash when a video device reconnects on macOS [jcm93] Fixed an issue where PipeWire could fail on NVIDIA GPUs [hoshinolina] Fixed obs_canvas_get_video_info returning incorrect framerate [dsaedtler] 32.2 Deprecations Deprecated obs_properties_add_button [sebastian-s-beckmann] Download: OBS Studio 32.2.0 Beta 2 | Portable | ARM64 | ~200.0 MB (Open Source) View: OBS Studio Homepage | Other Operating Systems | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Is a fast food restaurant a good metric to compare against?
    • Grand Theft Auto VI pricing revealed alongside Ultimate Edition and pre-loading details by Pulasthi Ariyasinghe Last week, Rockstar revealed Grand Theft Auto VI pre-orders will be starting soon, and just a day ahead of that, now the studio has announced the official pricing for the highly anticipated game. This has been a hotly debated topic among fans and industry veterans for a long time, considering the game is expected to be the biggest entertainment product launch ever. The confirmed pricing for the Grand Theft Auto VI standard edition is $79.99, which Rockstar says gives access to the "single-player experience set in the biggest, most immersive evolution of the series yet." This follows what most of our readers thought would happen with the pricing too. At the same time, a $99.99 Grand Theft Auto VI: Ultimate Edition has been confirmed as well, which lands with "an exclusive collection of premium vehicles, weapons, apparel, and action threaded across all aspects of Jason and Lucia’s story." Pre-ordering will also give fans extra bonuses, including a Vintage Vice City Pack of cosmetic items as well as a free month of GTA+. Head to the official website of the game here to check out all the cosmetic rewards the Ultimate Edition and pre-orders bring. Interestingly, the studio does not mention Grand Theft Auto VI multiplayer at all in today's announcement. Perhaps this will arrive later, following the campaign launch, or the studio is keeping that reveal for a later date. Digital pre-orders for Grand Theft Auto VI will begin on June 25, 2026, at midnight local time across regions for Xbox Series X|S and PlayStation 5. The title is slated to launch on November 19 on those same platforms. Pre-loading for Grand Theft Auto VI will kick off on November 12, giving players a week to get the game ready on their consoles. As for the physical edition, Take-Two has confirmed that this will be available without a disc, with the box only containing a download code inside. This will be purchasable starting November 12, giving players who take this route time to pre-load the title as well.
  • Recent Achievements

    • One Year In
      OHI Accounting earned a badge
      One Year In
    • First Post
      Almohandis earned a badge
      First Post
    • Rookie
      DaviKar went up a rank
      Rookie
    • Dedicated
      HidekoYamamoto94 earned a badge
      Dedicated
    • One Month Later
      timbobit earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      474
    2. 2
      +Edouard
      172
    3. 3
      PsYcHoKiLLa
      122
    4. 4
      Michael Scrip
      83
    5. 5
      Xenon
      72
  • Tell a friend

    Love Neowin? Tell a friend!