1. Joined : Aug 2015
    UK
    Posts : 26
    Windows 10
       03 Aug 2015 #1

    Warning: iMac BOOTCAMP - Clean Install - BSOD Inaccessible Boot device


    My Son has an iMac on which he was running Windows 7 Pro via bootcamp.

    He wanted a clean install of Windows 10 Pro ...

    Installed the upgrade all went well.
    Made sure Windows was activated.
    Grabbed keys using Magic Jelly (now know this was flawed ) just in case.
    Started the revert process saying no to retain settings and format partition.

    On Start up got BSOD with message Inaccessible Boot device ...
    Obviously the boot sector on the windows partition got screwed up ...

    Booted back to OSX, used bootcamp assistant to wipe the old partition, then create a new one and re-install from official iso (downloaded using my MSDN subscription).
    Installed fine but would not active, message said key ending "3V66T" had been blacklisted grrrr, so much for auto re-activation. Maybe the "new" bootcamp had a different signature???
    So had to use up one of my MSDN keys for him, no big deal for me, but a right pain in the ... for anyone without an MSDN subscription.

    I have done a search for the key and I can confirm that the key ending "3V66T" seems to a generic key baked into the iso.
      My System SpecsSystem Spec


  2. Joined : Oct 2013
    Standish, Lancashire
    Posts : 4,765
    Windows 10 Pro x64
       03 Aug 2015 #2

    I upgraded then clean installed on my macbook air with not problem, when doing the clean install you shouldn't enter any serials and just skip/do this later at the prompts, then when the install completes it just recognizes the hardware and auto-activates.
      My System SpecsSystem Spec


  3. Joined : Oct 2013
    Newport, South Wales, UK
    Posts : 1,207
    Windows 10 Pro x64 - XP/Vista/Win7/Win8.1 in VM for testing
       03 Aug 2015 #3

    Due to the huge amount of activity on the MS activation servers there have been quite a few reports of blacklisted keys on otherwise Ok installs, this has been blamed on issues at Microsoft's end due to the servers not being able to cope mayb give it a few days and try the old "blacklisted" key again
      My System SpecsSystem Spec


  4. Joined : Aug 2015
    UK
    Posts : 26
    Windows 10
       03 Aug 2015 #4

    z3r010 said: View Post
    I upgraded then clean installed on my macbook air with not problem, when doing the clean install you shouldn't enter any serials and just skip/do this later at the prompts, then when the install completes it just recognizes the hardware and auto-activates.
    Are you using bootcamp to dual boot?
    When we re-installed after BSOD, we changed to size of the partition, maybe this was enough to trip up the auto activation.
      My System SpecsSystem Spec


  5. Joined : Aug 2015
    UK
    Posts : 26
    Windows 10
       03 Aug 2015 #5

    Barman58 said: View Post
    Due to the huge amount of activity on the MS activation servers there have been quite a few reports of blacklisted keys on otherwise Ok installs, this has been blamed on issues at Microsoft's end due to the servers not being able to cope mayb give it a few days and try the old "blacklisted" key again
    To be expected ...
    Maybe better to wait till the dust settles to do clean installs.
      My System SpecsSystem Spec


  6. Joined : Oct 2013
    Standish, Lancashire
    Posts : 4,765
    Windows 10 Pro x64
       03 Aug 2015 #6

    MikeWilliams said: View Post
    Are you using bootcamp to dual boot?
    When we re-installed after BSOD, we changed to size of the partition, maybe this was enough to trip up the auto activation.


    Yep it was bootcamp on dual boot, after the upgrade I went into OSX and deleted the partition and then recreated (50/50 split) and reinstalled - everything went fine.
      My System SpecsSystem Spec


  7. Joined : Aug 2015
    UK
    Posts : 26
    Windows 10
       03 Aug 2015 #7

    z3r010 said: View Post
    Yep it was bootcamp on dual boot, after the upgrade I went into OSX and deleted the partition and then recreated (50/50 split) and reinstalled - everything went fine.
    Same as we did, must have been due to load on activation servers.
    Although we had 60/40 (OSX/Win) split before BSOD.
      My System SpecsSystem Spec


 


Similar Threads
Thread Forum
Clean install - random BSOD
Hey guys Did a clean install this morning. I am getting the error INTERNAL_POWER_ERROR and it BSODs/reboots. This happens every 30-40 mins. I have installed and updated all drivers and installed the latest BIOS revision (which I don't normally do...
BSOD Crashes and Debugging
Clean install BSOD during sleep?
Just did a clean install of Windows 10 pro x64 last night. Everything was going well it seemed. Installed all my essentials and drivers. I put my PC to sleep last night. Woke up this morning and my PC was turned on for some reason, checked event...
BSOD Crashes and Debugging
Solved Upgrade from build 10061 to 10074 fails (Inaccessible Boot Device)
Hi all, I keep getting the Inaccessible Boot Device error when trying to upgrade from 10061 to 10074. I *think* this may be due to my symlinking the \Windows\System32\DriverStore\FileRepository folder to another partition on the same hard disk....
Installation and Setup
Clean install on EFI computer causing boot problems
I had made a clean install of Windows 10 on an older computer without any issues. Then I tried to do a clean install on a newer EFI-based computer. I had trouble like many others once I tried to install to a GPT partition having booted from a USB...
Installation and Setup
Solved build 9879 clean install with duel boot.
HI all, I have a partitioned drive running win 7 and win 10tp. I am just downloading 9879 build iso to perform a clean install. i have read on the forums that this build is causing duel boot problems and trashing the win7 (which is my primary...
Installation and Setup
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 14:27.
Find Us
Twitter Facebook Google+



Windows 10 Forums