B75A-G43 UEFI booting

i'm new to UEFI booting. i have a B75A-G43 mobo. where in BIOS setup do i specify UEFI boot rather than BIOS boot?
i am using Clover bootloader to boot UEFI and want to boot from a USB stick, before writing the bootloader to my HD.
thanks
ken

thanks. i have been able to boot using UEFI with a USB stick. i then did an OS install to a HDD, and installed the UEFI bootloader.
the HDD will only UEFI boot if it is in an external USB enclosure, but when i connect the HDD via the normal internal sata, UEFI doesn't work.
i have UEFI as first in the boot order, and i made NO CHANGES in setup between the successful USB HDD boot and the unsuccessful SATA HDD boot, again, using the same HDD.
thanks

Similar Messages

B75A-G43 low memory frequency

I have bough MSI B75A-G43 motherboard and four AMD AE34G1609U2-U memory modules (built by Patriot). In BIOS each of modules frequency shown as 1600, but memory frequency set to 1333, and no option 1600 provided in menu.
I have updated BIOS to latest version, but no success.
Is there some way to set memory frequency to 1600?

I see that, that is because it is AMD memory designed for AMD systems.
You will need to manually set the speed and timings although it SHOULD work even though it is not ment for intel.
Do you need help with this?
How to manually set the memory to it's spec (as stated on thier website)
Enter UEFI/Bios
Click OC
Goto DRAM FREQUENCY: AUTO and change this to 1600
(At this point you can try to save and exit, but i prefer to set the timings manually.)
Next:
Change the Dram Timing Mode to either Link or Unlink either one will work.
Click on advanced dram configuration
Set the timings as follows:
tCL: 9
tRCD:9
tRP:9
tRAS:24
save and exit
It is possible that these settings will not work, if your system won't boot after doing this, you will need to clear the cmos and start over.
>>Clear CMOS Guide<<

IS GTX 970 GAMING 4G compatible with MSI B75A-G43 ?

So i bought myself today this card GTX 970 GAMING 4G
When i went home to install it i found out that it does not work. the fans spool up, the msi logo lights up, but no picture on monitors, not even the bios screen. i managed to boot up with the ntegrated graphics, GTX does not show up in device manager. Motherboard bios is up to date with the last bios version from the boards support/dovnload page version 10.10
Motherboard: B75A-G43
PSU: Corsair CX750T
My question, are the graphics card and motherboard compatible, did i get a bad card or do i need a new motherboard.

The warranty guys did check the card out and confirmed that it was dead on arrival. So they replaced the card and i had them check first if the new one works. It did so now it's waiting until evening for some gaming action

B75A-G43 board with OCZ Agility SSD

Thought I would challenge my self to building a new PC!
All has been going very well and all seems to be working well EXCEPT when I try and add anything else to the board like a CD drive or another HDD. Then troubles begin. Basically everything freezes up, CD's won't load and the SSD light stays on continuously. I have no idea if this is a SSD issue or a motherboard issue, but it is rather frustrating.
If it is of any help, I have done a clean install of Windows 7. For this the CD drive worked fine with the board and loaded Windows onto the SSD no problem. It seems once all is done, adding any other drive causes issues.
SATA settings are on AHCI and I have tried other drives, cables and PSU's
I have also updated the board to latest BIOS and everything else via Live Update.
Thanks for your help.
PC details:
Board: B75A-G43
Intel i3 chip
8GB RAM
Windows 7 32 bit
OCZ Agility 3 SSD
Sony CD/DVD drive

Many thanks for those tips which I carried out.
I thought I'd load windows onto a normal HDD I had from an old setup to see if the same thing happened as this would then take the SSD out of the equation potentially as being the problem. Sure enough, the same thing happens so not sure the SSD is the issue.
Also, I can't help feeling that this is significant: when booting with the bits I ideally want attached to the motherboard, 'A2' comes up bottom right corner of the screen and stays there for quite a while before I see the motherboard flash screen and then eventually boots to windows. If however I just have the drive with windows attached on its own, you don't get this 'A2' delay and the boot is very fast. Surely this must mean something to someone?

Satellite C50-B with Win 8.1 - PXE error appeares using UEFI boot mode

I have a C50-b laptop running Win 8.1 and recently needed to boot it from a usb key so eventually found the way to do that (miss the bios first boot menu) and managed to do that.
My problem is even when I have returned to uefi and set the boot order to be local disk, cd, network it asks everytime do I want to boot for PXE IP4,IP6 then IP4 and IP6 again. I have also disabled secure boot
I think some value is missing when I switched to BIOS and back to UETI boot option but where is the laptop getting the setting to tell it to PXE/Network boot when its down the list and wake on LAN is disabled.

According to the automated support on the site I should do the following for Win 8
Switch on the notebook and immediately begin tapping the F2 key continuously.
When the system setup (BIOS) appears, stop tapping F2. Tap F9 once, select 'Yes', and press Enter.
Use the cursor keys to move to the Advanced menu.
Choose System Configuration and press Enter.
Ensure that Boot Mode is set to UEFI Boot.
Press Escape to return to the Advanced menu and choose the Security menu.
Set Secure Boot to Enabled.
Press F10 once, select 'Yes', and press Enter.

V2P Virtual Machine to physical Server migration on IBM x3650 M4 and switch from BIOS to UEFI Boot environment

Hi there,
just wanted to share my experience with a manual P2V Migration. The VM became to ressource hungry and it was decided to move it off an ESX 5 Cluster to a dedicated physical Machine.
V2P Virtual Machine to physical Server IBM x3650 M4 and switch from BIOS to UEFI Boot environment
Task:
V2P Migrate a VMware virtual machine to a IBM x3650 M4 with a ServeRAID 5110e RAID Controller or any other LSI RAID Controller without 3rd Party tools.
This should also work with other RAID Controllers or Servers but be sure to pick the right drivers then.
Extra Task:
The VM's boot environment/virtual BIOS is BIOS, not UEFI (as per default VMware Setting). The physical Server is running in UEFI mode.
The Challenge:
After restore the Server won't boot or get into a BSOD (7B), because the RAID drivers are missing.
After restore the VM won't boot because the boot environment has changed from BIOS to UEFI
Preparations:
An existing physical Server of the same type and with the same RAID controller and same OS would be nice for troubleshooting and checking the registry.
An existing DHCP server will make networking things easier.
Connect the new physical server x3650 M4 to power and network
   create a virtual drive that has at least the size of the existing VM plus the size of the full backup (.vhd). Should be about twice the size of the original vmdk.
Get a USB Flash stick (I used a 8GB modell so no problem with larger sticks)
Download and extract LSI MegaRAID Driver on that USB media (I used 6.705.05.00-MR_Windows_Driver directly from LSI website)
Download and extract INTEL Network Adapter Driver on that USB media (I used 12.11.97.0 of e1r62x64.inf from 19.5 driver release from 2014.09.26 directly from LSI website)
Step by Step:
if you have an other physical Server of the same type and same Controller and same OS:
1.   open regedit and export everything related to SCSIAdapter and megasas2 to .reg files or skip this step and use my files below
   some of this (sub)keys may not be accesible - you will then first take ownership and/or modify permissions to read them
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E97B-E325-11CE-BFC1-08002BE10318}
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI\VEN_1000&DEV_005B&SUBSYS_04121014&REV_05
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\megasas2
   this one is more complicated:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase (only relevant are those devices where the service name is megasas2 - export the whole subkey and get the filtering done with tools like notepad++)
   Make a copy of the following files/folders:
   c:\programdata\LSI\
   c:\windows\inf\megasas2.INF
   c:\windows\inf\megasas2.PNF
   c:\windows\system32\drivers\megasas2.SYS
on the existing VM:
1.   create a full backup (image) with the built-in Windows Backup Utility and save it in an accessible network location (you will need this one, if anything goes wrong or you want to come back to this point.
   Alternatively you could create a VMware snapshot.
2.   import the .reg files you created earlier or import my files below.
   Attention: This will make the VM unbootable!
   But it is required to prepare the VM for the new RAID controller when it will be restored on the physical server.
   Do NOT reboot now as this will make the VM unbootable!
4.   Copy the LSI folder and the megasas2.INF/PNF/SYS files to the appropriate destination folders on the VM.
3.   again create a full backup (image) with the built-in Windows Backup Utility and save it in an other accessible network location but not where you safed the first backup.
   This will be the "golden" backup if you want, where the RAID controller is prepares. We will rebuild the new machine with this second backup.
4.   Optional: you could use the Backuputility now to restore the Systemstate of the first backup and reboot or restore the VMware snapshot.
   This will undo the changes we made to the VM.
on the new physical server:
1.   boot the physical server from Windows Server 2008 R2 SP1 DVD
2.   when it is ready to install, press shift+F10 to get command prompt and do not click to install Server 2008
3.   check driveletter of the USB stick with diskpart list vol (was C: at my Server, so don't wonder about that letter)
3.   load drivers for ServeRAID SAS controller (this is mandatory to see the volume in diskpart)
   drvload c:\srv_2008_x64\megasas2.inf
4.   load drivers for INTEL I350 Gigabit NIC's (you will need this to access the backup that is on the network)
   drvload c:\PRO1000\NDIS62\e1r62x64.inf
5.   wpeinit (will start network. wait ~15 sec to let it start and get IP address)
   check if you have IP connectivity an address with ipconfig, if not, use an other NIC driver and repeat steps 4+5
6.   create the EFI and BCD
   diskpart
   list disk
   select disk x (where x is the number of the disk to convert)
   clean
   convert gpt
   create partition EFI size=128
   format fs=fat32 quick label=EFI
   assign letter=i or any other free drive letter
   create partition MSR size=128
6.1   Copy EFI bootloader to EFI partition
    i: (where i is the letter of your EFI partition)
    mkdir EFI\Boot
   mkdir EFI\Microsoft\Boot
    copy x:\Windows\Boot\EFI\bootmgfw.efi i:\EFI\Microsoft\Boot (where x ist the default letter of the current Windows PE environment)
    copy x:\Windows\Boot\EFI\bootmgfw.efi i:\EFI\Boot\bootx64.efi (note that the file will be renamed to bootx64.efi)
7.   create the new partitions
   diskpart
   create partition primary size=100000 (edit the size to your needs. this will later become the system drive of your server)
   format fs=ntfs quick label=Windows
   assign letter=Y or any other free drive letter
   create partition primary size=990000 (this will temporarily store your backup and we need it for the restore process)
   format fs=ntfs quick label=Backup
   assign letter=B or any other free drive letter
   exit
8.   map network drive and copy the backup .vhd to the local disk
   net use L: \\networklocation\where\you\saved\the\backup (enter the credentials when asked)
       copy the .vhd file that contains the OS of your VM to the local Backup Partition B. The relevant vhd file is usually the largest file in that fileset.
       Note that the names are very similarly - be sure to get the correct file!
   copy "L:\WindowsImageBackup\VMNAME\Backup 2015-02-03 123456\00e767c6-xxxx-xxxx-xxxxxxxxxxxx.vhd" B:\
       give it time, this is slow and will take some minutes/hours and you will not see any progress! Look at the disk-LED's to see if anything is still happening
9.   mount the .vhd and copy it's contents to the new system partition
       Note that you can only mount a locally stored .vhd. You cannot mount a .vhd in a network location.
   diskpart
   select vdisk file=B:\00e767c6-xxxx-xxxx-xxxxxxxxxxxx.vhd
   attach vdisk
   select vol 5 (where 5 is the number of the mounted vdisk)
   assign letter=Z or any other free drive letter
   exit
10. Restore the files from the image
   z: (where z is the letter of your mounted .vhd)
   xcopy * Y:\ /e /c /h /k /o /b /q /y (where Y: is the letter of your new partition with the label "Windows")
       several "Access denied" messages appear, ignore them. Those are SystemVolumeInformation folders.
11.   Create Boot Configuration Data (BCD)
    bootrec /RebuildBcd
       this will try to repair the missing BCD on the second of the two small partitions we created earlier in and should normally work, otherwise you'll have to create BCD manually (search google for that procedure)
       Note that it may find more than one Windows installation and ask which sould be added to the boot list. Be sure to select only the one that is in the correct Volume (Y:\)
   that's it - exit the DOS command box and close the "Install Windows" Window, after a prompt it will reboot.
   Select "Start Windows Normally", if Windows Error Recovery appears.
12. Preparing Windows
   When Windows boots for the first time, DO NOT reboot if you are asked, it won't come back at this stage!
   Install Intel chipset drivers for the Server (I used "intc_dd_inteldp_9.4.0.1026_windows_32-64.exe" from IBM website)
   Open Device Manager, uninstall the "RAID-Controller" with the exclamation mark. You cannot install the correct driver for this Device at this point, it will bring you the error: "Cannot create a stable subkey under a volatile
parent key"
   Once again, DO NOT reboot!
   In Device Manager select Action>Add Legacy Hardware
   click Next
   select Hardware manually
   select Storage Controller as Type
   LSI should be listed, select "LSI MegaRAID SAS 9281-8E"
   click Next, ignore the error "Code 10" Message.
   Click Done.
   Rightclick the LSI MegaRAID SAS 9281-8E device with the exclamation mark in Device Manager
   select Update driver
   select Browse my computer for driver software
   select let me pick from a list of device drivers on my computer
   select "Have Disk"
   browse to the folder where the extracted RAID driver 6.705.05.00-MR_Windows_Driver is located (e.g. USB Flash stick E:\6.705.05.00-MR_Windows_Driver\srv_2008_x64)
   then unselect "Show Compatible Hardware"
   on the right side, scroll up and select "IBM ServeRAID M5110e SAS/SSATA Controller"
   ignore the Update Driver Warning and click Yes
   click Next, ignore the error "Code 10" Message.
   ignore the exclamation mark on "IBM ServeRAID M5110e SAS/SSATA Controller" in Device Manager but be sure that there is only this controller and no other RAID-Controller or LSI SAS Controller listed under "Other Devices"
or "Storage Controllers"
   NOW you are safe to reboot
   After reboot you will find two "IBM ServeRAID M5110e SAS/SSATA Controller" in Device Manager
   Rightclick and uninstall the one with the exclamation mark. Do not tick the checkbox to remove the driver as well!
You're done!! (hopefully)

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C31115D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C38015D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C41115D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C48015D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C51115D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C58015D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C61115D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C68015D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C71115D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C78015D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C81115D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C88015D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C91115D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C98015D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_D20219E5]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_D20319E5]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0071&SUBSYS_00721137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00011BD4]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00721137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00731137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_008F1137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00B01137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00B11137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00B61137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00B71137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00C21137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00C31137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_03B11014]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_040015D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_040D1014]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_10541000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_11771734]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_14581002]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_1F201462]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_30351054]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_350C8086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_350D8086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_822910F1]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_843B1043]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_84711043]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92211000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92401000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92408086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92411000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92418086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92421000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92431000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92441000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92A01000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92A11000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0078&SUBSYS_92501000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0078&SUBSYS_92511000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0078&SUBSYS_92701000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_00011BAA]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_00021BD4]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_00791137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_02001AE3]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_03B21014]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_03B31014]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_03C71014]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_070015D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_11761734]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_11B31734]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_30361054]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_350B8086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_84731043]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_84801043]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_8985152D]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92551000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92561000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92568086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92601000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92608086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92611000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92618086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92621000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92631000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92641000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92648086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92671000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92678086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92681000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92688086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92751000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92758086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92761000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92768086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92771000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92801000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92808086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92811000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92821000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92828086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92841000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92881000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92891000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92901000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92908086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_D20819E5]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_D20919E5]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0409&SUBSYS_10091000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10011000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10018086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10021000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10031000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10038086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10041000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10081000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10088086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_100C1000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_100D1000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10811734]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10a31734]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_20041000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_20051000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_30161054]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_34908086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_35008086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_35018086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_35048086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_35078086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_82871033]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0413&SUBSYS_10051000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"

Disable UEFI boot in Lenovo B470

How can we disable UEFI boot for B470 laptop?
I have checked the BIOS settings but found no options to select legacy boot option. Please help.

Hi
Welcome To Lenovo Community
Enter BIOS Setup by
Select Boot. It will display you the Boot Priority Order
Please share the details listed there
Hope This Helps
Cheers!!!
Important Note: If you need help, post your question in the forum, and include your system type, model number and OS. Do not post your serial number.
Did someone help you today? Press the star on the left to thank them with Kudos!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
Follow @LenovoForums on Twitter!

Booting hangs at loading vmlinuz-arch.efi (UEFI boot)

Hello,
I have just installed Arch Linux on my desktop machine (UEFI motherboard) which contains drives & partitions as follows:
1. /dev/sda (~ 250 GB) with
1: Win 7 64 bit
2: ntfs partition for data
3: ntfs partition for programs
2. /dev/sdb (1 TB) with
1: ntfs
2: fat32 / vfat as the uefi partition thingy
3: linux fs with swap, root and home
I have followed the Beginners' Guide dow nto the letter.
So I used rEFInd to set up the UEFI boot manager. However, it hangs at using the vmlinuz-arch.efi file/partition (?) on boot.
I have tried booting with a new efibootmgr entry as well, but it still hangs.
At this point, I'd like to know:
How can I get rid of all the rEFInd boot manager entries?
What precisely do I have to do to get it working? I could, of course, read around on here all day, but I somehow won't really learn anything as I can't deduct the right path of action for myself. If the machine weren't my productive system I'd definitely "play" around a lot more, that's for sure.
Any advice is greatly appreciated.

henrik wrote:
Thanks for your reply.
s1ln7m4s7r wrote:
OK, i will post, maybe it can help you!
First you need to boot from the arch installation media in UEFI mode. Mount your system partitions and chroot into it.
If you only have refind and kernel files under /boot/efi/ you can delete all files (clearing the EFI partition).Then run
modprobe efivars
. If you want to remove any efi entry, you can do it with
efibootmgr -b <entry_number> -B
Ok I did that.
sed -i "s/root=PARTUUID=XXXXXXXX rootfstype=XXXX ro/root=UUID=$(blkid -s UUID -o value $(df -k /)) rootfstype=$(blkid -s TYPE -o value $(df -k /)) ro/" "/boot/refind_linux.conf"
You meant here for me as wlel to exchange the X's wit hthe corresponding keys, right? I mean I did it. Would not make sense to me to call the comman with lots of Xs.
The rest was quite easy, I paid a lot of attention and made sure I typed in everthing correctly.
I am now at a blank black screen and there is a white underscore flashing in the upper left corner.
edit Can't boot into Windows anymore. Can't repair the MBR / UEFI boot with the Windows 7 DVD either...
edit2 Did lots of googling and at least Win 7 works fine again.
No. All the code is for you to type exactly as it is. The only statements you need to replace are <drive_with_efi_partition> and <efi_partition_number> with your current setup. What the line you questioned does is to replace the lines with "root=PARTUUID=XXXXXXXX rootfstype=XXXX ro" using the linux "sed" command, in refind_linux.conf with "root=UUID=<autodetected_uuid_of_your_root_partiton> rootfstype=ext4 ro". That will only work with the original refind_linux.conf, so if you edited it, you need to rerun
cp -r /usr/lib/refind/config/refind_linux.conf /boot/
There are 3 main reasons that may caused you to boot into a black screen with nothing written on it.
1. By not writing the code as it is, and editing files by hand instead, you may have done something wrong;
2. Your computer is booting from the wrong uefi entry, intead of the one created earlier;
3. You need to have "nomodeset" in your kernel boot line.
When does the black screen apears? After selecting a refind entry from refind's menu? Right after the pc boots (refind menu does not appear)
Another thing. In order for you to have access to windows, you need to edit refind.conf windows corresponding entry and remove the disabled statement or it wont appear on refind menu
Last edited by s1ln7m4s7r (2013-04-05 17:02:18)

Disabling UEFI boot or prioritizing legacy boot in dv6tqe-7000 laptop

Hey guys, I currently have windows 7 on my pavilion laptop. I'm trying to install ubuntu 14.04.1 LTS on it from the cd-rom drive. Unfortunately, the ubuntu installer does not detect my hard drive's windows 7 partition while booting in UEFI mode as Windows 7 was installed in legacy/bios mode.
I want to either disable UEFI booting or to make the bios prioritize BIOS/legacy boot ahead of UEFI so I can correctly install a second OS. Unfortunately, the bios options I see do not seem to allow me to switch to a legacy boot, they only allow me to change the boot priority within each of those modes. Is there any way for me to boot with legacy?
A screenshot of what I see in the boot options menu in the bios is here: http://imgur.com/aBaZ0Xi
The blue items are the only things that are selectable; the gray/black items cannot be navigated to.

Anyone?

Sound Blaster Z UEFI Boot

Anyone heard of this...
Apparently there's a known issue with Sound Blaster Z not getting initialized or recognized when booting in UEFI mode. Apparently reloading your system in legacy mode (MBR) fixes this issue...
Any word on the status of this getting fixed?
AJ

System specs Please
I have a zxr and I'm running full uefi boot without issues
have tried reseating or changing slots?
have you checked for a more recent bios?

Extended partition on old MBR HDD makes Windows 7 UEFI boot fail

There seems to be a bug in Windows 7 Pro x64 that prevents it from booting on a GPT partitioned HDD when the same machine also has an MBR partitioned HDD with an extended partition.
I have a UEFI bootable PC with two HDDs:
Disk 0 is GPT partitioned and contains Windows 7 Pro x64 and openSUSE systems.
Disk 1 is MBR partitioned and contains Windows XP Pro x64 systems and bootable ISO images.
Both the disks also have separate partitions for data and for booting.
They are normally booted via rEFInd on disk 0 as follows:
UEFI => rEFInd => Windows 7 or GRUB2.
UEFI => rEFInd => disk 1 MBR => GRUB4DOS.
I had previously installed Windows 7 when it was first released, but abandoned it in favour of XP and openSUSE instead. With the end of support for XP I decided to re-install W7. Before doing so I unplugged disk 1 to ensure that W7 booted completely
independently of XP. After installing W7 I installed SP1 and all the Windows updates. The new W7 system could be booted without problem via rEFInd => \EFI\Microsoft\Boot\bootmgfw.efi
However when I plugged in disk 1 W7 would no longer boot. It displayed the message "Windows is Loading Files" as the bar progressed twice before returning to the rEFInd menu. On selecting W7 again it presented the option to "Launch
Startup Repair", but on doing so it too just displayed "loading files" and returned to the reEFInd menu.
I UEFI booted from the installation DVD and ran Repair. When re-booted W7 presented a menu with choice of new and recovered systems, but both failed as before. Neither could be booted in safe mode. Booting directly from the UEFI firmware menu
into W7, instead of via rEFInd, gave similar results.
Investigations showed that the problem is caused by the extended partition on disk 1. If it is deleted, or just hidden by changing the partition type from 0x0F to 0x00, then W7 boots OK. Plugging in an external USB HDD with logical partitions also
prevents W7 from booting.
This all seemed to be similar to the problem described in KB979374, so I downloaded the hotfix (404153_intl_x64_zip.exe), which is supposed to be applicable to Windows 7 as well as WindowsServer 2008 R2. However when the hotfix was run it displayed "The
update is not applicable to your computer" and logged the following error:
error 2149842967 "" (Command line: ""C:\Windows\system32\wusa.exe" "<pathname>\Windows6.1-KB979374-x64.msu" ")
Is this because the version of files mentioned in KB979374 is older (6.1.7600.20617) than the version of Winload.exe in my system (6.1.7601.17556)?
According to http://www.techienewsnetwork.com/247/22/ SP1 included hotfix 979374, but it doesn't appear in the list of Installed Updates given in my W7 control panel. Should it, are hotfixes included in a service pack listed individually? If
not is there any way to tell whether or not hotfix 979374 has been applied?
How can W7 be booted without having to change the partition type code of extended partitions every time, is there a newer hotfix that will fix the problem in Windows 7 SP1?
Almost all the references I can find to this problem are at least 2 years old, which suggests it might have been fixed. Does anyone else with an up to date Windows 7 SP1 have this problem with extended partitions. An easy test is to plug in an external
HDD with logical partitions and see if W7 will still boot.
I don't want to convert disk 1 to GPT as that would make XP un-bootable. Also GRUB4DOS only supports MBR, and it is very useful for booting ISO images as well as XP.
Cheers.

Hi Wade,
To be sure that openSUSE, XP, or any other software on my PC isn't part of the problem I decided to do a new install of Windows 7 on a blank HDD. As I don't have a spare one I had to backup everything on disk 1 (MBR) and then wipe it, including the MBR,
with zeros (using AOMEI Partition Assistant).
I unplugged the original disk 0 so that the PC had just single completely blank HDD (previously disk 1), UEFI booted the Windows 7 DVD and installed W7 again. Unfortunately at this first attempt W7 partitioned the blank HDD as an MBR disk and booted
in legacy BIOS mode, even though I had booted the DVD in UEFI mode. So I deleted all the partitions it had just created and converted the disk to a GPT one.
The next time I installed W7 it was a UEFI one, with an EFI system partition. After installing SP1 and re-booting it a few times to make sure it was working OK I plugged in the external HDD with an extended partition before re-booting. The result
was exactly the same as reported above for the main GPT disk: it briefly flashed "Starting Windows" then displayed "Loading files" for a few seconds as the bars progressed; when Startup Repair was launched it failed as well.
After removing the HDD I booted the new W7 and added some missing drivers and installed all the Windows Updates, including the optional ones. Many hours later the result was a new up to date installation of Windows that worked perfectly (no errors in
any log files), with no other software on the PC. However as soon as the external HDD was plugged in it failed to boot, as described previously.
I then ran Bootrec from the DVD, trying all the commands, but the results were exactly the same: everything worked successfully but no Windows installations were found, and it didn't fix the problem.
The documentation on how to use Bootrec describes how to backup the BCD store that is on the C: drive (e.g. "ren c:\boot\bcd bcd.old"). However the BCD store for UEFI based systems is in the EFI system partition, NOT on the C: drive. This suggest
that Bootrec does not apply to UEFI based systems.
Are you sure that the MBR is used when booting in UEFI mode? From what I have read in several places (not MS pages) the protective MBR on the GPT isn't used, but instead the UEFI firmware runs \EFI\Microsoft\Boot\bootmgfw.efi which looks in the BCD store
in the EFI partition. Can you point me to any MS documentation please that explains exactly how UEFI booting works for Window 7, including its use of the MBR.
Do you have a Windows 7 system that can boot from UEFI when an MBR disk with an extended partition is attached. If so how is your installation different from the one I have just set up, i.e. Windows 7 installed on a PC with just
a single empty GPT HDD?
Do you work at Microsoft? If so perhaps you could find out if anybody with a straightforward UEFI booted Windows 7 has problems when an MBR HDD with an extended partition is attached.
Sorry for the delay in responding, but a lot of work was involved.

Windows Server 2012 R2 Will Support for UEFI boot in WDS.

Hi
Currently we had issue in WDS while deploying the image via UEFI boot in the DELL Optiplex 3010. We already deployed the Windows 8 install image and boot image in the Windows Server 2012 R2. After selecting the Network boot its show Start PXE IPV4 and it
will immediately flicker and get back to Network Boot option. Any one please help me out of this.....
But the same is working in Legacy boot and it doesn't activate the Windows 8.

Hi,
As I cannot confirm the exact settings on your side, please see the suggestions provided in following thread:
WDS: EFI BIOS won't PXE boot into EFI mode
http://social.technet.microsoft.com/Forums/windowsserver/en-US/ceca6149-bedd-4860-8a7f-a1c83bf99aa4/wds-efi-bios-wont-pxe-boot-into-efi-mode?forum=winserversetup
The same issue is discussed a lot in this thread and several possible suggestions are provided. See if it is helpful. If there is anything unclear please just let us know.
If you have any feedback on our support, please send to [email protected]

[SOLVED, sort of] Yet another UEFI boot issue

Hello everyone,
Let me start by saying sorry for the long (first) post.
I've ended up with a UEFI boot problem I can't solve. I've searched the forum and internet and I realize I'm not the only one who ran into problems with UEFI. Unfortunately, the problems other have had seem not similar to mine. I've spent almost 2 days now trying to figure this out, and I'm getting nowhere (though I've learnt some more about UEFI, which I guess is good). I was hoping someone here can give me some hints on how to proceed.
So lets start with the background. I recently bought a new computer (Lenovo Thinkpad Edge E530 with Windows 8) and of course I want to run ArchLinux on it (been using ArchLinux for almost 7 years now and no plans on switching). Installation went ok with only a few problems during installation that I managed to solve (or so I thought). I must admit I didn't follow the guide fully. I didn't want to remove the Restore and Windows partitions, so I figured it would be safe to reuse the existing UEFI System Partition, as long as there was enough room, which there was. Anyway, I now have a computer I can boot into ArchLinux and also Windows 8, just the way I want it, almost. There is this one final issue I haven't been able to figure out how to solve.
The problem
Whenever I reset/power on the computer, I must press Enter during the initial screen (showing a Lenovo logo, and a message about pressing Enter to interrupt normal startup). If I don't press Enter before the timeout (a second or so), the screen will go white and that's it. No beep, no message, no nothing but a white screen. A power cycle is the only way to leave this state. Occasionally the screen will be a white bar at the top and random colours below, but I'm guessing this only represents what is in graphics memory at the time (0x00, 0xFF or any other random value).
If i do press Enter however, then I'm presented with a menu where I can select what to boot; rEFInd (which is preselected) along with Windows 8 and some restore and diagnostic entries. Pressing enter will take me to the preselected rEFInd, pressing enter again (or wait for timeout) will boot linux, and I'm in. Nothing weird there. And if I select Windows in rEFInd, then windows boot, just as expected.
There is no difference whether I'm switching from Windows to Linux or Linux to Windows or just reboot the same OS I was using again. The result is the same whatever I choose to boot.
So the question is: Why do I have to select rEFInd manually and go through all these menus? Should I not be able to just power it on and let it boot the preselected rEFInd entry and continue from there, without me helping it?
Trying to solve it
Searching here and on the internet gave me some ideas on what to try, so here is a list of my attempts:
efibootmgr show me there is a rEFInd entry, and that it is the first one in boot order
I copied refindx64.efi to /boot/efi/EFI/Boot/bootx64.efi (replacing an existing entry)
I've updated the EFI firmware (from Lenovo) to the latest and greatest
One other guy had almost the same issue, but with a single boot of Windows. He solved it with Microsoft Boot Manager (there is an Automatic Repair, or something). I even dared trying this, though I must admit I was a bit hesitant about letting some Microsoft program trying to repair my computer. Anyway, it said it couldn't repair my problem, nor did it say I had one, so I am none the wiser.
None of the above gave anything.
So, that's it. I guess I can live with having to press Enter on every power up/reset, but it is very annoying having to do so, and even more so when I forget it because then I'm forced to power cycle it. I hope someone reading this can figure out what's going on, because I am clueless.
Best regards,
Johan
Last edited by 6feet5 (2013-01-08 19:03:50)

WonderWoofy wrote:@srs5694, have you thought about filing a bug report/feature request about the naming scheme here? I would imagine that something coming directly from the upstream developer would be something that they should take into consideration. Also, I imagine that renaming it to refindx64.efi kind of goes against the whole "vanilla packages" thing we tout around here... so it really makes me wonder why it is done in the first place.
I've just done that:
https://bugs.archlinux.org/task/33326
It's not been very important until recently; but I've been putting a lot of effort into the ancillary support scripts (install.sh and mvrefind.sh). They necessarily rely on the files having certain names, so installing them under other names robs users of functionality.
6feet5 wrote:I've decided to try and restore the whole unit, thinking it would take maybe an hour or two. It's been running now for almost 3 hours and only completed 20%.
Good luck with that!
FWIW, it seems that the number of EFI-related bug reports on Linux forums has gone way up recently. No doubt this is because EFI is now pretty much universal on new computers, so problems that used to affect one or two people now affect dozens or hundreds, and some of those post about them.

[SOLVED] UEFI boot configuration using efibootmgr

Hello All,
I've been having a very frustrating time with efibootmgr on my HP Laptop.
I've been searching around for some information regarding the OS Bootmanager in UEFI boot and cannot find anything that works for me.
I'm trying to get efibootmgr to load the boot entries in the order that I specify, but, although it lists exactly what I want in the terminal, when it comes to a reboot, the OS Bootmanager is failing and writing new entries every boot and I cannot fathom why.
Please could someone point me in the direction of a good guide to UEFI boot/OS Bootmanager and it's configuration using efibootmgr? I have read info found in the Archwiki, but was hoping for something focussing on efibootmgr alone as a configuration tool.
Many thanks for your help,
Frazer
Last edited by frazer (2014-03-10 22:21:14)

It's likely that the firmware (or maybe Windows, if you're booting into Windows between boots and haven't mentioned that fact) is changing the boot order. Unfortunately, some EFIs do that, or worse.
I recommend you start by upgrading your firmware. (In some cases, this will wipe out all your boot entries, so be prepared.) If the problem continues, either file a bug report with the manufacturer or return the hardware for a refund and buy something else. The manufacturers have had a long enough time to work out such major problems with their firmware, and returning defective hardware is really the only thing we as consumers can do that will get the manufacturers' attention.
If you must keep the hardware and a firmware update doesn't help, you may just need to find a workaround. If you need advice on doing that, you'll need to provide more details about what your setup is -- in particular, what you want the boot manager's boot list to look like (as in "efibootmgr -v" output once it's configured) and how the firmware is reshaping that when you reboot.

[SOLVED] UEFI-boot on Intel-NUC

Anyone got UEFI-boot working on Intel NUC?
In BIOS i have enabled UEFI and disabled secure boot.
With the latest bootable arch media it boots okay in UEFI-mode.
ls -l /sys/firmware/efi shows a list of files.
If i boot into UEFI shell v 2.0 (from the USB) i can start arch with
fs1:\EFI\arch_grub\grubx64.efi
I have followed the installation guide and created a EFI (fat32) partition on GPT.
I tried to add the entry with both efibootmgr and bcfg, but it doesn't seem like it's being read. I find the entries with bcfg boot dump, but not in intels BIOS under (boot drive order)
It only gives me "a bootable device has not been detected" on startup
Last edited by cybe-arch (2013-08-21 10:29:30)

cybe-arch wrote:
I have followed the installation guide and created a EFI (fat32) partition on GPT.
I tried to add the entry with both efibootmgr and bcfg, but it doesn't seem like it's being read. I find the entries with bcfg boot dump, but not in intels BIOS under (boot drive order)
Please tell us the exact commands you used, and the errors you get, I don't know if I have an answer after that, but now I definitely don't.

B75A-G43 UEFI booting

Similar Messages

Maybe you are looking for