No signed device drivers were found. Make sure the installation media contains the correct drivers.

Discussion in 'Windows Server Forums' started by Bryan Fuscarino, May 27, 2015.

  1. Bryan Fuscarino

    Joined:
    May 26, 2015
    Messages:
    1
    Likes Received:
    0
    I am trying to install Windows Server 2008 R2 onto a different hard drive that I'm going to put in the other computer and I keep getting that error. I would like to know the reason of this as soon as possible. Thanks.
     
  2. ussnorway

    ussnorway Windows Forum Team
    Staff Member Premium Supporter

    Joined:
    May 22, 2012
    Messages:
    2,535
    Likes Received:
    315
    Thats not allowed... the motherboard drivers are loaded at install time and this other computer has a different motherboard (therefore needs different drivers). You can sometimes get around it by using the exact same motherboard on both machines or a default vmware set of drivers. note that without that error your board would now be dead because you put the wrong power into it.
     
  3. Josephur

    Josephur Windows Forum Admin
    Staff Member Premium Supporter

    Joined:
    Aug 3, 2010
    Messages:
    1,019
    Likes Received:
    125
    Actually this is not entirely correct, you can make modifications to the registry to enable base IDE/AHCI drivers so that the install is more generic and will move to a different system successfully in most cases.
    Windows Setup disables these boot modes as setup runs to speed up boot times, as it only needs to load the drivers that correspond with the system you are currently on.

    Commonly the values can be find at
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Msahci
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Pciide
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\IastorV

    These services's Start value can be set to 0 to re-enable them. You can set both of the Start values to 0, power down the OS and insert the drive into the new machine and you might have success. The other hurdle you might run into is that you may need to install the correct driver for the target server (or computer)'s IDE/SATA/RAID interface before you power down so that it will be available to the new motherboard when it boots. Another option would be to use sysprep, but I wont go into that as its a topic of its own.
     

Share This Page

Loading...