For my windows laptop I actually purchased the full version of 8.1 so it's not the OEM copy that came on the laptop. I actually don't even use the windows laptop much anymore and if I can get windows 10 loaded onto my MacBook, I'll never use it.
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.
Windows 10 Upgrade Thread
- Thread starter giodelgado
- Start date
- Sort by reaction score
For my windows laptop I actually purchased the full version of 8.1 so it's not the OEM copy that came on the laptop. I actually don't even use the windows laptop much anymore and if I can get windows 10 loaded onto my MacBook, I'll never use it.
So then use that retail key to do a Bootcamp installation of Windows 8.1 and then do an in-place upgrade to Windows 10.
How many installs (machines) should the key be good for? The 8.1 bootcamp install said "please enter a valid key" or something along those lines.
Each key is good for one machine only but if you're going to discontinue using your Windows laptop and only use your MacBook then you can rightfully claim to Microsoft that you're installing it on one machine only.
Search for generic Windows 8.1 installation keys and use one of those generic keys to do the Bootcamp installation.
Then after it's installed use your purchased key to activate.
When you get the error use their telephone support option to complete the activation.
Search for generic Windows 8.1 installation keys and use one of those generic keys to do the Bootcamp installation.
Then after it's installed use your purchased key to activate.
When you get the error use their telephone support option to complete the activation.
I had no trouble upgrading from Windows 8.1 to Windows 10 Preview and then to Windows 10 on my Boot Camp Partition.
The only way I could update the Boot Camp 6 drivers was through Apple Update, and it kept getting stuck late in the install process after the DL, asking for the BC 5 Boot Camp.MSI file, which was right where it should have been on my BC HD.
So, I looked at the Properties of the various folders all the way down to the MSI file, and they were all "read only". I could uncheck the read only box and hit "apply", but it wouldn't hold, telling me I didn't have administrative privileges, even though I am the only user and am an administrator.
I found this site and enabled the hidden Administrator user in Win 10.http://www.ghacks.net/2014/11/12/how-to-enable-the-hidden-windows-10-administrator-account/ The process is a little confusing, but very doable. it also permits you to make your personal user a real administrator, or so it says, although I haven't tried it out.
I booted into that Administrator user, unchecked the read only boxes all the way down to the Apple install cache directory or whatever, and it all held. I then ran Apple Update, chose the Boot Camp 6 file, ran it, and it worked. Actually, i had to run it twice for some reason--the first time it said it worked, but it hadn't.
I have no idea why my original user account wasn't seen as an administrator, and why other people don't have this problem with the BC update.
The only way I could update the Boot Camp 6 drivers was through Apple Update, and it kept getting stuck late in the install process after the DL, asking for the BC 5 Boot Camp.MSI file, which was right where it should have been on my BC HD.
So, I looked at the Properties of the various folders all the way down to the MSI file, and they were all "read only". I could uncheck the read only box and hit "apply", but it wouldn't hold, telling me I didn't have administrative privileges, even though I am the only user and am an administrator.
I found this site and enabled the hidden Administrator user in Win 10.http://www.ghacks.net/2014/11/12/how-to-enable-the-hidden-windows-10-administrator-account/ The process is a little confusing, but very doable. it also permits you to make your personal user a real administrator, or so it says, although I haven't tried it out.
I booted into that Administrator user, unchecked the read only boxes all the way down to the Apple install cache directory or whatever, and it all held. I then ran Apple Update, chose the Boot Camp 6 file, ran it, and it worked. Actually, i had to run it twice for some reason--the first time it said it worked, but it hadn't.
I have no idea why my original user account wasn't seen as an administrator, and why other people don't have this problem with the BC update.
Hi Guys, I've a MacPro 4,1 and I test Windows 10, fine but I've not Boot Camp 6, is it possible to someone to add the content of "Boot Camp 6" USB key ? generate by El Capitan or something like that ?
I would like to test some drivers manualy,
Because, I've lost my apple keyboard, the light of the apple screen can't be modified .... my headphone doesn't work ... heeeelp.
I would like to test some drivers manualy,
Because, I've lost my apple keyboard, the light of the apple screen can't be modified .... my headphone doesn't work ... heeeelp.
You can find BootCamp 6 here:
https://forums.macrumors.com/thread...6-no-support-for-systems-before-2012.1907386/
FYI UPDATE:
I recently encountered the same error message installing Windows 10 on a 2012 Mac Mini Server:
0x80073892-0x20009
The installation failed in the SAFE_OS phase
with an error during PREPARE_ROLLBACK operation.
I did some new research and discovered many users were having this problem, usually on PC desktop machines. There were many convoluted suggestions, even from Microsoft Tech Support, but seldom did they seem to fix the problem. Then I ran across one post that fixed it. For users with 2 drives (SATA) in their system, disconnected the one not being installed to. I did this, and the Windows 10 upgrade completed flawlessly.
On this system I had replaced one of the hard disks with a 512GB SSD partitioned in half for Windows, and the other half as part of a DIY Fusion OS X drive with the remaining hard disk (the one I had to disconnect temporarily). On another similarly configured but NON-Fusion Mac Mini, I initially encountered the same error message, but I decided to "clean install" the upgrade without saving any data or programs and that seemed to work. Apparently the "PREPARE_ROLLBACK" wasn't an issue on a clean install.
Not a very robust installer program released with this update by Microsoft!
If you get the Black Screen of Death (yes black) this is a bug that has been around since Windows 7. A black screen will appear instead of a log in screen but you will notice it isn't a crash because the cursor is visible and you can still hear disk activity (if you use a HDD). The reason for this bug is usually the graphics card utility that you have installed has caused the GUI not to fully load, or it thinks you have two cards installed and doesn't output correctly on the main monitor, or it has sensed there is a graphics driver update and failed to initialise the current driver properly. This happens for AMD and Nvidia users. The only solution is to either turn off all automatic updates and notifications inside Catalyst Control Center/GeForce Experience or remove those apps entirely and allow Windows update to manage drivers.
Yes.
Check out Microsoft's Technet blog.
http://blogs.technet.com/b/msrc/
In each blog posting, there is a link to the specifics of the updates they roll out.
Or
https://technet.microsoft.com/security/bulletin
There is also the Security for IT Pros page with lots of information as well.
https://technet.microsoft.com/en-us/security/bb291012
He means within the OS without looking online. Enterprise Edition is reintroducing it in an update but other editions aren't.
Why you want to do that ? You may miss half of the updates, which are bug fixes and functional enhancements as well. If you have a specific device you can´t update ( like I have with the integrated Geforce 320M GPU ) , exclude the specific device from being updated by defining it´s device IDs in the group policy editor. Works perfect.
Just thought I would add my 2 cents for other people searching for solutions:
I have a MacPro (new, cylinder) with an external thunderbolt enclosure with 4 drives inside (an NTFS-formatted SSD with Windows, an NTFS hard drive for Windows files, and 2 hard drives formatted for OS-X). The internal MacPro drive SSD contained OS-X.
In the end, I finally got things installed after getting the same error message by:
1. Disabling BitLocker on the Windows boot-drive SSD (not sure if this was necessary). I left it enabled on my other non-boot windows drive.
2. Changing the boot priority to start with the Windows boot-drive (I couldn't get the drive to show up in "Startup Disk" until I disabled BitLocker, but this may have been unnecessary)
I did the above first, hoping that assigning the Windows boot drive as first priority would fix things - it didn't. So I then removed all drives with EFI-partitions other than my Windows boot drive. This meant.
3. Open the enclosure and removed the 2 OS-X formatted drives (they all get EFI partitions, apparently). I kept the 2 windows drives installed.
4. Open up the MacPro and removed the internal SSD.
After this... Finally everything worked, like magic - except that my keyboard wasn't working properly (function keys like volume control weren't working). So I...
5. Re-installed bootcamp 6 drivers (a repair install option will be available).
Finally, to get everything back the way it was:
6. Reinstalled all drives and re-actived BitLocker on the windows SSD.
Windows 10 is nice, I think a worthwhile upgrade, but there has to be a way to make installation smoother...
Cheers!
I have a MacPro (new, cylinder) with an external thunderbolt enclosure with 4 drives inside (an NTFS-formatted SSD with Windows, an NTFS hard drive for Windows files, and 2 hard drives formatted for OS-X). The internal MacPro drive SSD contained OS-X.
In the end, I finally got things installed after getting the same error message by:
1. Disabling BitLocker on the Windows boot-drive SSD (not sure if this was necessary). I left it enabled on my other non-boot windows drive.
2. Changing the boot priority to start with the Windows boot-drive (I couldn't get the drive to show up in "Startup Disk" until I disabled BitLocker, but this may have been unnecessary)
I did the above first, hoping that assigning the Windows boot drive as first priority would fix things - it didn't. So I then removed all drives with EFI-partitions other than my Windows boot drive. This meant.
3. Open the enclosure and removed the 2 OS-X formatted drives (they all get EFI partitions, apparently). I kept the 2 windows drives installed.
4. Open up the MacPro and removed the internal SSD.
After this... Finally everything worked, like magic - except that my keyboard wasn't working properly (function keys like volume control weren't working). So I...
5. Re-installed bootcamp 6 drivers (a repair install option will be available).
Finally, to get everything back the way it was:
6. Reinstalled all drives and re-actived BitLocker on the windows SSD.
Windows 10 is nice, I think a worthwhile upgrade, but there has to be a way to make installation smoother...
Cheers!
FYI UPDATE:
I recently encountered the same error message installing Windows 10 on a 2012 Mac Mini Server:
0x80073892-0x20009
The installation failed in the SAFE_OS phase
with an error during PREPARE_ROLLBACK operation.
I did some new research and discovered many users were having this problem, usually on PC desktop machines. There were many convoluted suggestions, even from Microsoft Tech Support, but seldom did they seem to fix the problem. Then I ran across one post that fixed it. For users with 2 drives (SATA) in their system, disconnected the one not being installed to. I did this, and the Windows 10 upgrade completed flawlessly.
On this system I had replaced one of the hard disks with a 512GB SSD partitioned in half for Windows, and the other half as part of a DIY Fusion OS X drive with the remaining hard disk (the one I had to disconnect temporarily). On another similarly configured but NON-Fusion Mac Mini, I initially encountered the same error message, but I decided to "clean install" the upgrade without saving any data or programs and that seemed to work. Apparently the "PREPARE_ROLLBACK" wasn't an issue on a clean install.
Not a very robust installer program released with this update by Microsoft!
Do we have a way to install the bootcamp drivers on MBP 2011 models? Everyone works aside from the volume and brightness keys, and it would be nice to have those working again.
I had to temporarily move my external Thunderbolt SSD Windows installation to a partition on the internal drive using WinClone. I then performed the Windows 10 update there (it looks like a normal BootCamp installation). It is working fine, so my next step will be to again use WinClone to move the working Windows 10 back to the external drive, and then use the normal BootCamp Installer to remove the internal partition and restore the space back to OS X.
I finally got Win10 up and running... Having upgraded to El Capitan made the difference. The new BootCamp assistant is irritating, but it works. I had to disconnect all my Thunderbolt devices to make the formatting in the Windows installation process work, but eventually it did. Then I set up Win10, and all was fine, until I reconnected my external Thunderbolt PCIe box. As soon as I connect any Thunderbolt devices to my Mac Pro, I get the BSOD Cache_Manager error. I disconnect the Thunderbolt devices, and all works fine???
Hi just wondering if anyone has any definitive solution for this error? I now spent each weekend trying to upgrade my windows 8.1 Bootcamp to 10 but always failed at the same stage: SAFE_OS rollback error. Have tried all the methods mentioned: move Bootcamp from external SSD to internal (fusion drive), clean boot, uninstall Bluetooth drives and anti virus, delete files under xxx folder, system file cleanup, media creation tool, Windows update, create USB (always fail don't know why), create bootable DVD (still fail at same error), choose to keep nothing, ... it's driving me crazy... HELP!
I was originally running 10 on an 850 Evo in my Mac Pro but some defect or error in th drive was causing random crashes. On a big spinning hard drive there was no problem. So yesterday I moved the OS to an OCZ SSD and it's all good.
Microsoft pulled the Windows 10 1151 10586.0 from their download servers and reverted to the 10240 release. Let's wait for an explanation from Microsoft about the issues with this build.
Cheers
Cheers
They explained they want people to go through Windows Update. It's most likely because they get more useful data and statistics from updaters instead of full installers.Microsoft pulled the Windows 10 1151 10586.0 from their download servers and reverted to the 10240 release. Let's wait for an explanation from Microsoft about the issues with this build.
Cheers
Official response on many sites:
'The November update was originally available via the MCT tool, but we've decided that future installs should be through Windows Update. People can still download Windows 10 using the MCT tool if they wish. The November update will be delivered via Windows Update.'