Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
[GUIDE] Install Windows 7 in MacBook Pro Early 2015 with almost fully support(include track pad)!!
- Thread starter tl166115
- Start date
- Sort by reaction score
BTTF_DeLorean
macrumors newbie
I finally got the installation screen, and I did the command prompt, but when I tried to install, it says "Setup cannot continue due to a corrupted installation file. Contact the vendor of your windows installation disk or your system administrator for assistance."View attachment 701207
BTTF_DeLorean
macrumors newbie
I finally got it to work, except for when I try install the bootcamp drivers, it says it's not intended for this computer model, even though I used bootcamp in OS X to download the drivers.
Has anyone simply tried Installing Windows 7 through VMWare Fusion on a separate partition?
I can remember the easiest way to achieve this is to simply use VMWare's "Raw Disk Access" to prepare an installation for Windows 7 so you don't have the initial 'hassle' of black screens, no SSD support etc.
And once installed, just get all the proper hardware drivers installed, and then boot natively into the installed Win 7 partition? I used to do this on an older mac, but assuming most basic drivers work it could be done. Or am I missing a part?
I'm tempted to try this on my MBP 2016 Late as I might want to play some games natively, and I can really not stand Windows since version 8/10.
I can remember the easiest way to achieve this is to simply use VMWare's "Raw Disk Access" to prepare an installation for Windows 7 so you don't have the initial 'hassle' of black screens, no SSD support etc.
And once installed, just get all the proper hardware drivers installed, and then boot natively into the installed Win 7 partition? I used to do this on an older mac, but assuming most basic drivers work it could be done. Or am I missing a part?
I'm tempted to try this on my MBP 2016 Late as I might want to play some games natively, and I can really not stand Windows since version 8/10.
Celeri
macrumors newbie
Hi there !
I just created an account to participate to this thread that saved my day : at least I can have a fully functionnal Win7 Pro on my MBP 13" 2015 ! So a HUGE thanks to davidcie and tl166115 for their great work !! 🙂
In order to help people that could have some problems with this tutorial, here are a few remarks from me :
- I used the current version of BootCamp drivers from Apple (use the "Download software" menu in the BootCamp Assistant) and installation of "BootCamp.msi" failed, because of a missing DLL. I ended up understanding that it was because this installer is for Win8 & Win10 only. So remember that if you want to use the most recent version of BootCamp drivers, you should however use an old version of the "Apple" subfolder in the "Drivers" folder. I used the 5.1.5769 version and it worked perfectly.
- I had trouble with the trackpad : despite following the process of disabling the driver signature enforcement, the "Apple Multi-Touch" driver would fail to load after a normal reboot (without holding F8), making the trackpad completely disabled until installing the driver again (you really should have a USB mouse during the whole operation). I had to do the whole trackpad driver install process 3 times before it remained stable, I don't know why... So if you have the same problem, just try it again from the beggining of the "hardest part" of the tutorial, it should work eventually.
- You should be REALLY careful at the moment of creating/resizing of partitions at the beginning of the whole process, because there is NO WAY (as far as I know) to make the Windows partition bigger afterwards. Since a small master boot partition is created by the Windows Installer "between" the Mac partition and the Windows partition, Disk Utility refuses to allow more space to the latter, even if you reduce the size of the Mac partition. I strongly advise you to allow AT LEAST 40 GB to your Windows partition, preferably 50 GB to be comfortable, especially if you want to install Office 2016 and all the system updates.
- Talking about disk space, you can save precious GB by two ways. First, since the "hybrid sleep" functionnality does not work, you can prevent the system of creating the "C:\hiberfil.sys" file that is roughly equal to your Mac's RAM ; for that, use the "powercfg -h off" command in admin mode. Second, if you think that you won't use apps that are heavy RAM-eaters, you can reduce the size of the "C:\pagefile.sys" file to 1 or 2 GB, because by default it will be as big as your physical RAM ; to do that, you can use "System protection" in the System Properties. In my case (8 GB of physical RAM), I saved more than 12 GB by these 2 simple steps !
I hope this will help some of you...
I just created an account to participate to this thread that saved my day : at least I can have a fully functionnal Win7 Pro on my MBP 13" 2015 ! So a HUGE thanks to davidcie and tl166115 for their great work !! 🙂
In order to help people that could have some problems with this tutorial, here are a few remarks from me :
- I used the current version of BootCamp drivers from Apple (use the "Download software" menu in the BootCamp Assistant) and installation of "BootCamp.msi" failed, because of a missing DLL. I ended up understanding that it was because this installer is for Win8 & Win10 only. So remember that if you want to use the most recent version of BootCamp drivers, you should however use an old version of the "Apple" subfolder in the "Drivers" folder. I used the 5.1.5769 version and it worked perfectly.
- I had trouble with the trackpad : despite following the process of disabling the driver signature enforcement, the "Apple Multi-Touch" driver would fail to load after a normal reboot (without holding F8), making the trackpad completely disabled until installing the driver again (you really should have a USB mouse during the whole operation). I had to do the whole trackpad driver install process 3 times before it remained stable, I don't know why... So if you have the same problem, just try it again from the beggining of the "hardest part" of the tutorial, it should work eventually.
- You should be REALLY careful at the moment of creating/resizing of partitions at the beginning of the whole process, because there is NO WAY (as far as I know) to make the Windows partition bigger afterwards. Since a small master boot partition is created by the Windows Installer "between" the Mac partition and the Windows partition, Disk Utility refuses to allow more space to the latter, even if you reduce the size of the Mac partition. I strongly advise you to allow AT LEAST 40 GB to your Windows partition, preferably 50 GB to be comfortable, especially if you want to install Office 2016 and all the system updates.
- Talking about disk space, you can save precious GB by two ways. First, since the "hybrid sleep" functionnality does not work, you can prevent the system of creating the "C:\hiberfil.sys" file that is roughly equal to your Mac's RAM ; for that, use the "powercfg -h off" command in admin mode. Second, if you think that you won't use apps that are heavy RAM-eaters, you can reduce the size of the "C:\pagefile.sys" file to 1 or 2 GB, because by default it will be as big as your physical RAM ; to do that, you can use "System protection" in the System Properties. In my case (8 GB of physical RAM), I saved more than 12 GB by these 2 simple steps !
I hope this will help some of you...
Good evening my friend
I recently sent my MacBook for repair because the screen was malfunctioning. Afterwards my hard disk was obliterated so I had to follow all of the process again. When I proceed to the driver part I also faced the same trouble. None of my solution worked at all until I found this tool: Driver Signature Enforcement Overrider (DESO).
USing this tool, you can SIGN the driver to match the Microsoft standards. Here are the three files that you need to sign:
C:/Windows/system32/DRIVERS/KeyMagics.sys
C:/Windows/system32/DRIVERS/WdfCoInstaller01011.dll
C:/Windows/system32/DRIVERS/applemtp.sys
Then enable the test mode. This will work 100%, guranteed.
Sincerely
Tom
Sorry for taking forever to reply. I recently have to follow all of the procedures again because my hard disk was obliterated. When I am re-doing all of the procedures that I posted years ago, I found errors, over-complex procedures and things that can be improved. I am currently trying to make a ISO file that has all of the required files on it so that the only thing you would need to do is to burn that to a USB disk and install. I know, my original procedure spends like 50% on preparation. Also I am going to fix some errors. I tried to make an YouTube but my camera malfunctioned, so I'll have to postpone it. But hopefully I'll simplify the entire procedure to a extend that almost everyone can follow. And yes, I will try to take pictures as well.
Sincerely
Tom
[doublepost=1512637246][/doublepost]
One year ago you had problems with the drivers on WIndows 7, one year later I finally found the answer to that:
Even if you have test mode enabled you still need to sign the driver, test mode only allows improperly signed driver to load, not drivers that did not got signed at all. Using this tool we can sign the driver easily:
Driver Signature Enforcement Overrider (DESO). This tool is easy to use, just click "continue" twice and then choose "sign driver"
Here are the three files that you need to sign:
C:/Windows/system32/DRIVERS/KeyMagics.sys
C:/Windows/system32/DRIVERS/WdfCoInstaller01011.dll
C:/Windows/system32/DRIVERS/applemtp.sys
Then enable the test mode. I tried this recently because my hard disk was obliterated, my previous methods did not work at all but this one solve the problem.
I recently sent my MacBook for repair because the screen was malfunctioning. Afterwards my hard disk was obliterated so I had to follow all of the process again. When I proceed to the driver part I also faced the same trouble. None of my solution worked at all until I found this tool: Driver Signature Enforcement Overrider (DESO).
USing this tool, you can SIGN the driver to match the Microsoft standards. Here are the three files that you need to sign:
C:/Windows/system32/DRIVERS/KeyMagics.sys
C:/Windows/system32/DRIVERS/WdfCoInstaller01011.dll
C:/Windows/system32/DRIVERS/applemtp.sys
Then enable the test mode. This will work 100%, guranteed.
Sincerely
Tom
[doublepost=1512636772][/doublepost]
Good evening my friend
Sorry for taking forever to reply. I recently have to follow all of the procedures again because my hard disk was obliterated. When I am re-doing all of the procedures that I posted years ago, I found errors, over-complex procedures and things that can be improved. I am currently trying to make a ISO file that has all of the required files on it so that the only thing you would need to do is to burn that to a USB disk and install. I know, my original procedure spends like 50% on preparation. Also I am going to fix some errors. I tried to make an YouTube but my camera malfunctioned, so I'll have to postpone it. But hopefully I'll simplify the entire procedure to a extend that almost everyone can follow. And yes, I will try to take pictures as well.
Sincerely
Tom
[doublepost=1512637246][/doublepost]
One year ago you had problems with the drivers on WIndows 7, one year later I finally found the answer to that:
Even if you have test mode enabled you still need to sign the driver, test mode only allows improperly signed driver to load, not drivers that did not got signed at all. Using this tool we can sign the driver easily:
Driver Signature Enforcement Overrider (DESO). This tool is easy to use, just click "continue" twice and then choose "sign driver"
Here are the three files that you need to sign:
C:/Windows/system32/DRIVERS/KeyMagics.sys
C:/Windows/system32/DRIVERS/WdfCoInstaller01011.dll
C:/Windows/system32/DRIVERS/applemtp.sys
Then enable the test mode. I tried this recently because my hard disk was obliterated, my previous methods did not work at all but this one solve the problem.
Right click and choose “run as administrator”
Regards
Tom
[doublepost=1516789638][/doublepost]
Tom
Regards
Tom
[doublepost=1516789638][/doublepost]
[doublepost=1516789804][/doublepost]
Taking about disabling driver signature enforcement, check out my previous post in Dec 7, 2017 about using Driver Signature Enforcement Overrider (DSEO)
Tom
Do you have administrative privilege? Try install using the real Administrator account or SYSTEM account if that’s an issue. I strongly doubt if you can use setup.exe because it threw me an error.
Here how to enable the “real Administrator”:
Press Command + R to to open “run” window, type in “lusrmgr.msc” and then press enter
Navigate to “Users/Administrator”. Double click it and uncheck “account is disabled.”
Log out of your current account and log into Administrator
Do the same installation again
Do you have the driver pack that your got from your BootCamp App? There should be a Bluetooth driver there. Try that driver under the Administrator account. If that doesn’t work, use the way you installed track pad and keyboard to do it(no need to do the driver signature enforcement override though, I think)
Tom
tl166115, you're a man! I registered to this forum to thank you very much - Win7 Corporate now works fine on my MacBook Pro 15 2015.
The only thing is ... the camera does not work ... You did not have a similar problem?
I tried the drivers from BootCamp Pro 15 2011 (Apple FaceTime HD v5.0.22.0) - they are installed without errors, but applications such as Skype said "Your webcam is currently being used by another application" and the camera did not start. I also tried the new drivers from here https://support.apple.com/kb/DL1831, they are also in BootCamp Pro 15 2015 (Apple FaceTime HD 5.1.6100.0) - after installation it was possible to see in windows hardware manager an exclamation mark - " Windows can not load the device driver for this hardware. The driver may be corrupted or missing. (Code 39) ".
What kind of driver did you use? Can you please specify the exact version and the place where you got them?
Many thanks again for this guide!
The only thing is ... the camera does not work ... You did not have a similar problem?
I tried the drivers from BootCamp Pro 15 2011 (Apple FaceTime HD v5.0.22.0) - they are installed without errors, but applications such as Skype said "Your webcam is currently being used by another application" and the camera did not start. I also tried the new drivers from here https://support.apple.com/kb/DL1831, they are also in BootCamp Pro 15 2015 (Apple FaceTime HD 5.1.6100.0) - after installation it was possible to see in windows hardware manager an exclamation mark - " Windows can not load the device driver for this hardware. The driver may be corrupted or missing. (Code 39) ".
What kind of driver did you use? Can you please specify the exact version and the place where you got them?
Many thanks again for this guide!
Last edited:
Good morning!
That’s an interesting question! Unfortunately I have not met such error before. However, based on the error message, I think there might be some possible solutions.
Do not use the driver for 2011, they are designed for older builds which means that they are designed for different hardware
The newest driver may or may not function because of the updates that Apple releases. However, you can try to have them installed the way you did for the touchpad and keyboard using command prompts.
If that doesn’t work, you can try the 1st version of the driver. If you have trouble finding such, try the original driver that BootCamp Assistant gives you.
Good luck!
That’s an interesting question! Unfortunately I have not met such error before. However, based on the error message, I think there might be some possible solutions.
Do not use the driver for 2011, they are designed for older builds which means that they are designed for different hardware
The newest driver may or may not function because of the updates that Apple releases. However, you can try to have them installed the way you did for the touchpad and keyboard using command prompts.
If that doesn’t work, you can try the 1st version of the driver. If you have trouble finding such, try the original driver that BootCamp Assistant gives you.
Good luck!
Also, you can disable it in the device manager and re-enable it again. Not sure what it is going on since I almost never use FaceTime
Can you tell me the version of the camera driver on your MacBook? 5.1.6100.0 is the version that BootCamp assistant gives me, but it does not work ( It would be easier for me to get to make a specific version of the driver, if I knew it was possible, than blindly look for the right version.
Sorry, I don’t have the machine with me right now, I will get you later. I apologize for the inconvenience
I want to thank you very much for provided guide, worked great on my MBP12.1 but 2 issues stayed.
1 is just the same as described here:
I have absolutely the same problem and still can't resolve it. It's been pain in the ass since laptop is used for work and Skype is absolutely must-have.. So without proper fix for this i would still need to move to 8.1..
One more problem i cannot resolve is related to Intel IO (SPI) driver code 9ce6. Bootcamp 6 only contained Win8 driver with SPBCX (Win8 kernel mode component) dependency inside, and latest release of Bootcamp 5 (5769) didn't have separate IO driver at all. Has anybody experienced the same?
1 is just the same as described here:
I have absolutely the same problem and still can't resolve it. It's been pain in the ass since laptop is used for work and Skype is absolutely must-have.. So without proper fix for this i would still need to move to 8.1..
One more problem i cannot resolve is related to Intel IO (SPI) driver code 9ce6. Bootcamp 6 only contained Win8 driver with SPBCX (Win8 kernel mode component) dependency inside, and latest release of Bootcamp 5 (5769) didn't have separate IO driver at all. Has anybody experienced the same?
I’ve never experienced the inter IO issue.
I’m sorry to tell you that I have stopped using Macs after I burn two logic boards that cost me half the price of the computer to repair; the USB port burnt my hard disk under the macOS and my Death Adder Chroma was killed by the same garbage USB port. I have the computer fixed and gave it to my father.
The only thing that I can suggest would be completely uninstall the driver and install everything that looks related using the CMD way. Try http://support.apple.com/kb/DL1831?viewlocale=en_US with the CMD installation. Run though all of the drivers that’s under /BootCamp/Drivers/Apple, with the CMD command if possible.
I’m sorry to tell you that I have stopped using Macs after I burn two logic boards that cost me half the price of the computer to repair; the USB port burnt my hard disk under the macOS and my Death Adder Chroma was killed by the same garbage USB port. I have the computer fixed and gave it to my father.
The only thing that I can suggest would be completely uninstall the driver and install everything that looks related using the CMD way. Try http://support.apple.com/kb/DL1831?viewlocale=en_US with the CMD installation. Run though all of the drivers that’s under /BootCamp/Drivers/Apple, with the CMD command if possible.
I believe IO issue is the one that gave you unknown PCI device:
And with Camera update - i've just tried it and it installs driver 5.1.6100.0 for FaceTime Camera which is shown with exclamation mark and Code 39 error in Device Manager..
Pity you don't hav access to HW now..
In regards to IO driver there is funny thing even - Intel has released drivers for Win7, but exactly the SPI driver is broken:
https://downloadcenter.intel.com/download/26660/Intel-Processor-I-O-Controller-Driver-for-Windows-7-
Other drivers (UART, GPIO, I2C, etc) seems to install smoothly on MBP, so I tried to fix the driver but can't find people with skills to sign the driver and test it. I haven't succeeded signing it with DSEO, signtool, signcode, etc...
DSEO shouldn’t be that problematic. You can locate the driver file in the device manager, and then you enable the test mode then sign it, based on the assumption that the problem is caused by the driver signature.