Unable to boot with UEFI by bootable windows 8.1 DVD

Hi guysUnfortunately when I want to install windows with UEFI from bios, there is no choice for choosing boot from DVD, while my DVD is bootable and it is in my DVD Rom. On the other, by changing UEFI to Legacy support, it can recognize my bootable DVD of windows 8.1. I really cant understand what is the problem. Please help to install new windows through UEFI (((((((((Thanks

I think this is a problem with new laptops (as far as I know), you cannot boot into UEFI using DVD.
(Try disabling / enabling SecureBoot but I dont think that will help either)
You can however create a bootable USB and boot into UEFI.

Similar Messages

[SOLVED] Unable to boot in UEFI System

For several days I have been trying to get Arch to boot on my desktop by following the Beginners' guide and refering to other Arch wiki articles as well as Arch Forum posts for any problems that I had. I have tried a few bootloaders such as GRUB, gummiboot, and rEFInd and they all give the same result when I attempt to boot - a blinking cursor with no menu and then it returns me to the BIOS;. My UEFI motherboard is the ASUS VI Hero. I have disabled secure boot and both fast boots. I use a live USB with UEFI that is able to boot on my system and was created with dd.
Below are the outputs of some commands that might be useful.
root@archiso ~ # lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 223.6G 0 disk
├─sda1 8:1 0 512M 0 part
├─sda2 8:2 0 4G 0 part
└─sda3 8:3 0 219.1G 0 part
sdb 8:16 0 931.5G 0 disk
├─sdb1 8:17 0 487.3M 0 part
└─sdb2 8:18 0 931G 0 part
sdc 8:32 0 232.9G 0 disk
├─sdc1 8:33 0 100M 0 part
└─sdc2 8:34 0 232.8G 0 part
sdd 8:48 1 3.8G 0 disk
├─sdd1 8:49 1 595M 0 part /run/archiso/bootmnt
└─sdd2 8:50 1 31M 0 part
loop0 7:0 0 256.8M 1 loop /run/archiso/sfs/airootfs
loop1 7:1 0 32G 1 loop
└─arch_airootfs 254:0 0 32G 0 dm /
loop2 7:2 0 256M 0 loop
└─arch_airootfs 254:0 0 32G 0 dm /
Windows 7 is on sdc and Arch is on sda (sdb is an extra storage device for Windows). Both sdc and sda are SDDs.
root@archiso ~ # parted /dev/sda print
Model: ATA SanDisk SDSSDHII (scsi)
Disk /dev/sda: 240GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 538MB 537MB fat32 boot, esp
2 538MB 4833MB 4295MB linux-swap(v1)
3 4833MB 240GB 235GB ext4
root@archiso ~ # cat /mnt/etc/fstab
# UUID=0dff590b-24f1-47a2-870e-3f4d2c5bcb6a
/dev/sda3 / ext4 rw,relatime,data=ordered,discard 0 1
# UUID=FA3A-728C
/dev/sda1 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
# UUID=524e2980-d1e6-4948-88f9-c193682d5a9e
/dev/sda2 none swap defaults 0 0
# efibootmgr
BootCurrent: 0003
Timeout: 1 seconds
BootOrder: 0000,0001,0002,0003
Boot0000* grub
Boot0001* Hard Drive
Boot0002* ubuntu
Boot0003* UEFI: General USB Flash Disk
Boot0008 Hard Drive
Ignore ubuntu, that was on my HDD from before but has been removed. The grub option usually disappears after reboot unless I run efibootmgr -O after I install the bootloader. Using efibootmgr -v option, the output is a bit hard to read.
# efibootmgr -v
BootCurrent: 0003
Timeout: 1 seconds
BootOrder: 0000,0001,0002,0003
Boot0000* grub HD(1,800,100000,f9c04628-178b-4c94-9b92-62c04f2a5151)File(\EFI\grub\grubx64.efi)
Boot0001* Hard Drive BIOS(2,0,00)..GO..NO........u.W.D.C. .W.D.1.0.E.Z.E.X.-.0.8.M.2.N.A.0....................A.................................>..Gd-.;.A..MQ..L. . . . .W. .-.D.M.W.3.C.1.F.6.4.5.0.4.6........BO..NO........u.S.a.m.s.u.n.g. .S.S.D. .8.4.0. .E.V.O. .2.5.0.G.B....................A.................................>..Gd-.;.A..MQ..L.1.S.B.D.S.N.F.A.7.1.3.0.7.5. .L. . . . ........BO..NO........o.S.a.n.D.i.s.k. .S.D.S.S.D.H.I.I.2.4.0.G....................A...........................>..Gd-.;.A..MQ..L.4.1.3.4.3.7.0.4.7.0.2.0. . . . . . . . ........BO..NO........u.G.e.n.e.r.a.l. .U.S.B. .F.l.a.s.h. .D.i.s.k....................A.............................B..Gd-.;.A..MQ..L.G.e.n.e.r.a.l. .U.S.B. .F.l.a.s.h. .D.i.s.k........BO
Boot0002* ubuntu HD(1,800,f3a9e,3eaa3162-6352-4ad8-a725-89c738f2b3ad)File(\EFI\Ubuntu\grubx64.efi)
Boot0003* UEFI: General USB Flash Disk ACPI(a0341d0,0)PCI(1d,0)USB(1,0)USB(1,0)HD(1,fc,f800,612a5c68)..BO
Boot0008 Hard Drive BIOS(2,0,00)..GO..NO........o.S.a.n.D.i.s.k. .S.D.S.S.D.H.I.I.2.4.0.G....................A...........................>..Gd-.;.A..MQ..L.4.1.3.4.3.7.0.4.7.0.2.0. . . . . . . . ........BO..NO........u.W.D.C. .W.D.1.0.E.Z.E.X.-.0.8.M.2.N.A.0....................A.................................>..Gd-.;.A..MQ..L. . . . .W. .-.D.M.W.3.C.1.F.6.4.5.0.4.6........BO..NO........u.S.a.m.s.u.n.g. .S.S.D. .8.4.0. .E.V.O. .2.5.0.G.B....................A.................................>..Gd-.;.A..MQ..L.1.S.B.D.S.N.F.A.7.1.3.0.7.5. .L. . . . ........BO..NO........o.G.e.n.e.r.a.l. .U.S.B. .F.l.a.s.h. .D.i.s.k....................A.......................B..Gd-.;.A..MQ..L.G.e.n.e.r.a.l. .U.S.B. .F.l.a.s.h. .D.i.s.k........BO
I mount /dev/sda3 to /mnt and /dev/sda1 to /mnt/boot before I arch-chroot and when I tried grub, I installed with:
# grub-install --target=x86_64-efi --efi-directory=/boot--bootloader-id=grub --recheck
No errors are reported. I then make a config file for grub with:
# grub-mkconfig -o /boot/grub/grub.cfg
Last edited by DetotatedWam (2015-04-01 22:12:06)

Boot\ Secure Boot menu >
Secure Boot state: Disabled
Platform Key (PK) state: Unloaded
OS Type: Windows UEFI mode
I have tried setting "OS Type" to "Other OS" before but that doesn't change anything. I just tried it again and the BIOS freezes upon "Save Changes & Reset".
Boot\ Secure Boot menu\ Key Management >
PK Management: Unloaded
KEK Management: Unloaded
DB Management: Unloaded
DBX Management: Unloaded
The other day, I deleted all of them and backed them up on a USB in order to disable secure boot.
Note: After looking at this menu again I am noticing options to append from file for KEK, DB, and DBX that might help.
Append KEK from File
Allows you to load the additional
KEK from a storage device for an
additional db and dbx loaded
management.
[Yes]
Load the default KEK
[No]
Load from a USB storage device
Append db from File
Allows you to load the additional db
variable from a storage device so
that more custom signed UEFI
executble files can be loaded.
*UEFI executabled files include UEFI
boot loaders, drivers and
applications.
[Yes]
Load the default db
[No]
Load from a USB storage device
Append dbx from File
Allows you to load the additional
dbx variable from a storage device
so that more custom signed UEFI
executble files cannot be loaded.
*UEFI executabled files include UEFI
boot loaders, drivers and
applications.
[Yes]
Load the default dbx
[No]
Load from a USB storage device
Boot\ CSM (Compatibility Support Module)
Launch CSM: Enabled
Boot Device Control: UEFI and Legacy OPROM
Boot from Network Devices: Legacy OPROM first
Boot from Storage Devices: Both, UEFI first
Boot from PCI-E/PCI Expansion Devices: Legacy OPROM first
As a side note: After a reboot, I noticed the Arch boot option disappeared again.
Head_on_a_Stick wrote:Have you managed to boot any other distributions that are not compatible with Secure Boot?
I have been able to boot Windows 7 and ubuntu but I beleive both are compatible with Secure Boot so, no.
Head_on_a_Stick wrote:The Arch live ISO has the EFI applications PreLoader.efi & HashTool.efi included so that will boot up with Secure Boot enabled.
I will try this and post the results.
Edit: Now my BIOS Freezes everytime I try to save & exit.
Last edited by DetotatedWam (2015-04-01 19:59:18)

[SOLVED]Unable to boot in UEFI mode from CD

Hello gents!
Here's the problem:
According to the beginner's guide I followed the instruction to test if I am in UEFI mode:
In case you have a UEFI motherboard, the CD/USB will launch UEFI Shell and display a message that
startup.nsh
script will be launched. Allow the shell to launch it. Then, to check whether you have booted into UEFI mode, load the efivars kernel module (before chrooting) and then check whether there are files in
/sys/firmware/efi/vars/
# modprobe efivars # before chrooting
# ls -1 /sys/firmware/efi/vars/
Well, the thing is that when I boot the CD no UEFI Shell is launched as well as no
startup.nsh
When I try to load the efivars I don't receive any message, so, I assume, the module is loaded; but the, when I invoke ls the message I receive is:
#ls: cannot access /sys/firmware/efi/vars/: No such file or directory
To me it looks that for some reason I am unable to access the UEFI mode when starting the CD iso.
Thank you guys for your courteous attention.
Have a wonderful day!!!
P.S. I've searched already in the following posts:
https://bbs.archlinux.org/viewtopic.php … 84#p148184
https://bbs.archlinux.org/viewtopic.php … 55#p148155
P.S.2
My mobo is an ASUS Maximus V Gene with i3770K on it.
Edit:
Ok guys! Thanks to all of you, but everything was brought about by my scarce knowledge of the mobo. Logging into the BIOS, in the boot section, you have to choose between normal DVD and UEFI DVD. When selecting the last, everything, I mean, the startup phase at least, went well.
Enjoy everybody
Any idea how to close/"solved" this forum tread?
Last edited by guidone (2012-09-11 20:34:21)

guidone wrote:Any idea how to close/"solved" this forum tread?
README: Forum Rules
Simply edit the original post by clicking on the 'edit' button at the lower right corner of it and prepend [SOLVED] to the title.

Unable to boot with MSI X58 PRO-E and OCZ3P1333LV6GK

Hi,
This is my first post in this forum.
I've had this system for about 6 months, and from time to time I kept having instant reboots and once the PC would never start, I think I've sorted that by first flashing an old MB BIOS and then the most recent.
Tree days ago I've had another instant reboot, but now the system stops/reboots when the coloured animation starts to appear above the "Loading windows" message. This happens with both Win7 32 & 64 bits and even with the windows 7 installation DVD !!!
I think I've tried all combinations of the other posts where the MB+memory was the same as mine.
Another strange issue is: the memory PN shown inside the BIOS (OCZ3G1333LV2G) is different from the label on the memory (OCZ3G1333LV6GK)!!
I've already tested with only one memory chip at a time, the result is still the same.
I've only got connected the following: Video board, 1 RAM chip, USB Keyboard & one SATA HD. No over clocking whatsoever !
What else do I need to do to finally boot to windows ?
Thanks in advance for any help.
Paulo
My System:
Mobo: MSI X58 Pro-E, model MS-7522, version 3.1
BIOS: 8.B
CPU: Intel i7 920
RAM: OCZ3G1333LV6GK (6GB)
Video: Sapphire Vapor-X ATI RAdeon HD 4870 2GB
PSU: Combat Power CP 750W
OS: Windows 7 32 & 64 bits

Hi Henry,
Thanks for the help.
"What are your RAM timings? Screenshot of CPU-Z Memory tab and SPD tab."
I've added a few screenshots of the memory, the SPD & CPU-Z tab, plus a MEM86 test with only on memory stick installed. It appears that the memory is OK... or not ?
"Do you have another video card you can try? Those Sapphire Vapor-X cards have been a problem for others in the past."
I wasn't aware of any problems with this video card, I use it mainly to send movies to my big LCD TV through the HDMI port. I don't have access to another video card, sorry...
I don't know what else to do, do you think it's the PSU ?
Regards,
Paulo
--I made it so your images show and are clickable
--Mike

Unable to boot normal, in safe mode or from install DVD

When I walked into my office this morning and hit my keyboard to wake my Mac all I saw on the screen was a white mouse arrow and a black screen. I held down the power button to restart, it starts to boot and then stops at a gray screen telling me to hold down the power button and restart. Doing this brings me to the same screen. I have attempted the following:
Booting while holding the Shift key - this takes a bit longer but takes me to the same gray screen
Booting with the install DVD in and holding the "c" key - DVD spins a bit then gray screen
Booting while holding "option" and selecting the install DVD - DVD spins a bit then gray screen
Booting in Single User mode and ran "/sbin/fsck -fy" it returned - *** FILE SYSTEM WAS MODIFIED ***, ran it again and returned - ** The volume Macintosh HD appears to be OK
I am not sure where to go from here, and advice would be much appreciated.
Thanks,
Bob

I posted in the wrong forum, I am using 10.5, I have reposted this in that forum.

Unable to boot in UEFI mode.

After looking around at the wiki for a few days and playing around with Arch in VirtualBox I went to see if it would boot on my native hardware, and all the turns up is a black screen. Legacy mode is not an option as I am dual booting Windows 8.1 64 bit. I suspect this is related to my issues with Fedora as the Fedora installation media will not boot either, though it once did. Fedora used to work on my machine until it got dropped one day. After the drop I started having some strange issues and tried reinstalling Fedora, only to find that once it hit the bootloader I would face a black screen that never goes away until I power the system down. I sent my laptop in to Lenovo to be serviced and they replaced the optical drive, hard drive and did a reinstall of Windows 8. Fedora still would not boot after I got the machine back. I tried Ubuntu after the drop before sending it off and it worked, and that is what I currently have installed. My knowledge of UEFI is limited. Any ideas? My laptop is a Thinkpad L440 by the way.

Head_on_a_Stick wrote:
Actually, Ubuntu will install and run with Secure Boot enabled (as will the Arch live ISO) -- the blog post is just about making your own Secure Boot keys.
From Ubuntu, post the output of:
# efibootmgr -v
Yeah I know that, but I left it off to save the extra hassle.
Here is the output for the command:
swilliams@speedy:~/Videos$ sudo efibootmgr -v
[sudo] password for swilliams:
BootCurrent: 0014
Timeout: 0 seconds
BootOrder: 0014,0013,0000,0001,0002,0003,0007,0008,0009,000A,000B,000C,000D,0012
Boot0000 Setup
Boot0001 Boot Menu
Boot0002 Diagnostic Splash Screen
Boot0003 Lenovo Diagnostics
Boot0004 Startup Interrupt Menu
Boot0005 Rescue and Recovery
Boot0006 MEBx Hot Key
Boot0007* USB CD 030a2400d23878bc820f604d8316c068ee79d25b86701296aa5a7848b66cd49dd3ba6a55
Boot0008* USB FDD 030a2400d23878bc820f604d8316c068ee79d25b6ff015a28830b543a8b8641009461e49
Boot0009* ATAPI CD0 030a2500d23878bc820f604d8316c068ee79d25baea2090adfde214e8b3a5e471856a35400
Boot000A* ATA HDD0 030a2500d23878bc820f604d8316c068ee79d25b91af625956449f41a7b91f4f892ab0f604
Boot000B* ATA HDD1 030a2500d23878bc820f604d8316c068ee79d25b91af625956449f41a7b91f4f892ab0f605
Boot000C* USB HDD 030a2400d23878bc820f604d8316c068ee79d25b33e821aaaf33bc4789bd419f88c50803
Boot000D* PCI LAN 030a2400d23878bc820f604d8316c068ee79d25b78a84aaf2b2afc4ea79cf5cc8f3d3803
Boot000E* IDER BOOT CDROM ACPI(a0341d0,0)PCI(16,2)ATAPI(0,1,0)
Boot000F* IDER BOOT Floppy ACPI(a0341d0,0)PCI(16,2)ATAPI(0,0,0)
Boot0010* ATA HDD 030a2400d23878bc820f604d8316c068ee79d25b91af625956449f41a7b91f4f892ab0f6
Boot0011* ATAPI CD 030a2400d23878bc820f604d8316c068ee79d25baea2090adfde214e8b3a5e471856a354
Boot0012* PCI LAN 030a2400d23878bc820f604d8316c068ee79d25b78a84aaf2b2afc4ea79cf5cc8f3d3803
Boot0013* Windows Boot Manager HD(2,1f4800,82000,e2e20688-f616-4344-9acc-e7ae20c772e3)File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
Boot0014* ubuntu HD(2,1f4800,82000,e2e20688-f616-4344-9acc-e7ae20c772e3)File(\EFI\ubuntu\shimx64.efi)

PXE Boot with UEFI. WDS not sending WinPE wim

I am trying to test PXE booting on devices that only have UEFI and no CSM support.
We are running Windows Server 2008 R2 in our environment.
On the DHCP server, we have option 66 and 67 set. If I change option 67 to SMSBoot\x86\wdsnbp.com and boot a traditional BIOS system (non UEFI) the SCCM server responds and gives me the option to hit F12 and PXE boot. This works without issue and can deploy
images.
I then change option 67 to SMSBoot\x64\wdsmgfw.efi and use a machine that is pure UEFI (meaning UEFI without any legacy support / CSM). The system appears to successfully download the wdsmgfw.efi and font file via TFTP as shown in the WDS logs. However, it
then goes to the next sreen where it is trying to contact the WDS server. AFter retrying for a while it will error out with error 0x102 which I believe translates to ERROR_TIMEOUT
The SMSPXE.log repeats the following:
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820352" ServerName="" ServerRemoteName=""><Machine><ClientID>8908f9c4-c345-49ba-b137-af7b0b983584</ClientID><NetbiosName/></Machine></Identification><PXEBootAction
LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="GAS20043" OfferIDTime="7/24/2013 3:12:00 PM" PkgID="GAS00037" PackageVersion="" PackagePath="<a href="http:///SMS_DP_SMSPKG$/GAS00038">http://<IVE
REMOVED THIS>/SMS_DP_SMSPKG$/GAS00038" BootImageID="GAS00038" Mandatory="0"/></ClientIDReply>
SMSPXE 7/24/2013 7:14:58 PM 7724 (0x1E2C)
00:50:56:01:00:82, DF6A0C42-F909-B518-7B44-3150B662200B: found optional advertisement GAS20043 SMSPXE 7/24/2013 7:14:58 PM 7724 (0x1E2C)
Looking for bootImage GAS00038 SMSPXE 7/24/2013 7:14:58 PM 7724 (0x1E2C)
Any idea what may be going on?

Hey,
I am having the following situation:
DP1 = Windows Server 2008 R2 SP1 (Standalone Primary Site Server SCCM 2012 SP1 CU2)
DP2 = Windows Server 2012
UEFI Client: Microsoft Surface Pro (with Microsoft Surface Network Adapter)
BIOS Client: HyperV Virtual machine with Legacy network adapert
DP1; DP2 and DHCPServer all in Subnet1.
(IP Helper is set for DHCPServer for DHCP and for DP1 & DP2 for DHCP and BootP - I checked serveral times if everything is right here)
UEFI Client and BIOS Client in Subnet2.
Situation1 -- Using no DHCP Options and both DPs(DP1 and DP2) WDS running:
UEFI Client - Boots perfectly (contacting Server DP2)
BIOS Client - Boots perfectly (contacting Server DP2)
Situaion2 -- Using no DHCP Options and WDS just running on DP1:
UEFI Client - Does not boot (no error information is provided)
BIOS Client - Does not boot (no Bootfilename recieved)
Situation3 -- Using DHCP Options(Option 66="IP of DP1" Option 67="SMSBoot\x86\wdsnbp.com") and WDS just running on DP1:
UEFI Client - Does not boot (no error information is provided)
BIOS Client - Boots perfectly (contacting Server DP1)
Situation4 -- Using DHCP Options(Option 60="PXEClient" Option 66="IP of DP1" Option 67="SMSBoot\x86\wdsnbp.com") and WDS just running on DP1:
UEFI Client - Boots perfectly (contacting Server DP1)
BIOS Client - Does not boot (taking hours to recieve dhcp options..)
My problem is i am having a lot of location with 2008 R2 SP1 server only (this is why situation 1 is not enough for me :-( ).
Based on this article:
http://ccmexec.com/2013/05/configmgr-2012-uefi-and-pxe-boot-support/
x64 UEFI Devices should work with Server 2008 R2 SP1 (not only Server 2012).
Interesting is I am having ALL files on Server 2008 R2 SP1 like they are on Server 2012 (in SMSBoot\x86 folder, too!)??
Some more ideas?
Thank you for help

Linux-3.10.10 fails silently when booting with UEFI

This problem has occured for me on several occasions in the past (with 3.10.2 and 3.10.8) but that has been with kernels in [testing]. With 3.10.10 dropping to [core], this is the first time this has happened for me with an official release.
Though the linked-to thread is marked as "Solved", the only solution found was downgrading and waiting for a new kernel to be released that did not have the issue (3.10.3 and 3.10.9). I am using UEFI with gummiboot, but I have no idea why this is happening (and since the boot fails silently it's rather difficult for me to provide helpful logs). Is anyone else experiencing this issue? Have you found any workable solution that isn't just waiting? Can anyone else guide me in some troubleshooting?
All the best,
-HG

srs5694 wrote:
Booting directly from the firmware and via gummiboot are basically the same, in the sense that they both rely on the EFI stub loader. The problem under discussion in the thread to which I linked appears to be a bug in the EFI stub loader that interacts with the firmware version -- it affects many Lenovo computers, but few others. It appears when using the EFI stub loader directly, from rEFInd, or from gummiboot; but it's a highly inconsistent bug. It can go away by switching from gummiboot to rEFInd, from rEFInd to gummiboot, from one version of rEFInd to another, from either of these to a direct boot from the firmware, etc. It also comes and goes with the exact kernel version, with different people reporting problems with different kernels.
As I said, there's no real fix. The precise cause hasn't been nailed down; if it had been, chances are there'd be a fix by now.
Fascinating. I wonder what's going wrong with it.
If SYSLINUX is getting you further into the boot process, then I recommend you try to debug what's happening with SYSLINUX. Try posting details of any error messages you see.
Fair enough. Then, here's my plan. Given that this thread appears to be a duplicate of the thread srs5694 linked to, it should probably either be merged in or closed (I don't necessarily have any preference, and since there has been no new discovery made in it, it doesn't seem as though there is any inherent advantage one way or another). And, I will shortly open a new thread on troubleshooting syslinux.
Thank you for your guidance srs! You've been a huge help.
All the best,
-HG

HPE-510t does not boot with AMD FirePro W5000 (Windows 8.1)

I just purchased an AMD FirePro W5000 (TDP = 75 W) to replace my nVidia Quadro 600 (TDP = 40 W) in my 2011 HPE-510t (i7-2600, 12 GB RAM). Dell U2913WM monitor.
My machine will not start with the new card inserted. I upgraded the stock 300 W power supply to a 450 W Antec VP450F, but that didn't change the startup situation. I tried DisplayPort and Dual-Link DVI-D.
Anyone been able to get the AMD FirePro working in an HP desktop of this generation?
Thanks,
Mike
This question was solved.
View Solution.

Hi Mike,
I am glad that you finally have success. The issue is probably that the PC BIOS level is too low.
The passmark numbers look very good.
BTW -- I had the ASUS P8P67 motherboard and donated it another forum member. It wouldn't support an EVGA UEFI BIOS based graphics card. I ended up replacing the ASUS P8P67 with the ASUS Z87.
HP DV9700, t9300, Nvidia 8600, 4GB, Crucial C300 128GB SSD
HP Photosmart Premium C309G, HP Photosmart 6520
HP Touchpad, HP Chromebook 11
Custom i7-4770k,Z-87, 8GB, Vertex 3 SSD, Samsung EVO SSD, Corsair HX650,GTX 760
Custom i7-4790k,Z-97, 16GB, Vertex 3 SSD, Plextor M.2 SSD, Samsung EVO SSD, Corsair HX650, GTX 660TI
Windows 7/8 UEFI/Legacy mode, MBR/GPT

PXE boot with UEFI

I get this everytime I try to PXE a UEFI device. I have even moved my PXE to server 2012. Changed to IP helpers.
Windows failed to start. A recent hardware or software change might be the cause. To fix it... <blahblah>
File:\Windows\System32\boot\winload.efi
Status: 0xc0000359
Any ideas?
Thanks,
Jason

Here it is...
Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
SMSPXE 1/13/2014 12:28:09 PM 732 (0x02DC)
78:45:C4:C6:B1:74, 4C4C4544-0037-5210-8047-C7C04F525431: device is not in the database. SMSPXE 1/13/2014 12:28:09 PM 732 (0x02DC)
Getting boot action for unknown machine: item key: 2046820352 SMSPXE 1/13/2014 12:28:09 PM 732 (0x02DC)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820352" ServerName=""><Machine><ClientID>8f2e8c16-543f-4204-a65a-701cc4c40f3f</ClientID><NetbiosName/></Machine></Identification><PXEBootAction
LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="BSD200F7" OfferIDTime="1/9/2014 1:11:00 PM" PkgID="BSD000AB" PackageVersion="" PackagePath="http://sccm-dp04.HIDDEN/SMS_DP_SMSPKG$/BSD00001"
BootImageID="BSD00001" Mandatory="0"/></ClientIDReply>
SMSPXE 1/13/2014 12:28:09 PM 732 (0x02DC)
78:45:C4:C6:B1:74, 4C4C4544-0037-5210-8047-C7C04F525431: found optional advertisement BSD200F7 SMSPXE 1/13/2014 12:28:09 PM 732 (0x02DC)
Getting boot action for unknown machine: item key: 2046820352 SMSPXE 1/13/2014 12:28:12 PM 732 (0x02DC)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820352" ServerName=""><Machine><ClientID>8f2e8c16-543f-4204-a65a-701cc4c40f3f</ClientID><NetbiosName/></Machine></Identification><PXEBootAction
LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="BSD200F7" OfferIDTime="1/9/2014 1:11:00 PM" PkgID="BSD000AB" PackageVersion="" PackagePath="http://sccm-dp04.HIDDEEN/SMS_DP_SMSPKG$/BSD00001"
BootImageID="BSD00001" Mandatory="0"/></ClientIDReply>
SMSPXE 1/13/2014 12:28:13 PM 732 (0x02DC)
78:45:C4:C6:B1:74, 4C4C4544-0037-5210-8047-C7C04F525431: found optional advertisement BSD200F7 SMSPXE 1/13/2014 12:28:13 PM 732 (0x02DC)
Looking for bootImage BSD00001 SMSPXE 1/13/2014 12:28:13 PM 732 (0x02DC)
Looking for bootImage BSD00001 SMSPXE 1/13/2014 12:28:16 PM 732 (0x02DC)
Looking for bootImage BSD00001 SMSPXE 1/13/2014 12:28:16 PM 732 (0x02DC)

Dual boot with (or without) UEFI

Hello,
I want to add arch to a windows box, but I dont really know how to deal with the UEFI bootloaders.
Can I just install plain old grub and do it as i'm used to? I don't know if windows 7 actually uses a UEFI bootloader or not, but in the past I could just put grub on the MBR of my linux drive and add a entry to windows from there. If i choose a UEFI bootloader, will this still be possible?
-Dan

justdanyul wrote:do you know of any way to check if windows 7 is booting with uefi or not? (google have proved rather unhelpful on this matter so far)
May be off-topic wrt Linux, but to do this boot into Windows, open "cmd" (as Administrator), and then type "bcdedit". If the "path" variable under "Windows Boot Loader" shows "winload.exe", then its BIOS-MBR boot, if it is showing "winload.efi", then its UEFI-GPT boot.
C:\Windows\system32>bcdedit
Windows Boot Loader
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {bootloadersettings}
recoverysequence {dbd20116-b38a-11e1-826f-be71072f298b}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {dbd20114-b38a-11e1-826f-be71072f298b}
nx OptIn
numproc 2
usefirmwarepcisettings No
bootlog Yes
sos Yes
Last edited by the.ridikulus.rat (2012-10-22 09:47:25)

Unable to boot windows side

I've been running windows 7 (64bit) via bootcamp for several months and this evening I got to the selection screen I selected Windows and it froze I've tried multiple times with no luck I ran a hardware test with my OSX install disk no problems detected unable to boot with windows 7 disk same thing happens it just freezes.
Anyone know how to fix this?

http://manuals.info.apple.com/en/bootcampinstall-setup.pdf

I purchased a new computer with windows 8 and unable to sync with itunes

I am unable to sync with itunes, since getting Windows 8

Check this article about syncing to a new computer:
Syncing to a "New" Computer or replacing a "crashed" Hard Drive
If you just updated Windows, did you make sure to have the latest updates for your computer?
Did you try to reinstall iTunes and all related Apple software?
Also check this article again:
iTunes for Windows Vista, Windows 7, or Windows 8: Fix unexpected quits or launch issues

890FXA-GD70 no boot with Razer Naga (on the latest 2 biosses)

With the 890FXA-GD70 I had no problems well still have no problems but if I run on either the latest bios 1.12 (1.C) or the one before that 1.11 (1.B) the mobo will hang on initialising USB controllers if you have the Razer Naga (and from what I heard other razer mouses as well). On the BIOS I'm running now 1.10 (1.A) I have no problems so I'm kind off wondering what you guys changed to the latests 2 BIOS that makes the motherboard unable to boot with the Razer mice.
If you need other info you can have it but as I'm sure this is not a hardware problem but a BIOS problem I doubt any other info would be of use to solving the problem.
I checked with multible power option (EuP/CPU Phase/DDR Phase/Cool & Quiet/C1E) but even with those disabled the motherboard still hangs on initialising USB controllers.
On Fail-safe defaults the motherboard also hangs on initializing USB controllers.
If I plug the mouse in after Windows has started the whole computer just freezes (on the 1.11 or 1.12 BIOS).
If I need to forward this to support do tell as it seems quite weird that 2 bios updates where nothing much has changed besides:
1.11:
- Update CPU AGESA code.
- Update RAID option ROM.
- Improved memory compatibility.
1.12
- Update CPU module.
Cause the BIOS/motherboard to hang on initialising usb controllers.

PSU has nothing to do with it, but it's a 1500W MaxRevo (Gold 94% efficiency).
Processor is a Phenom II X6 1100T
Memory is also supported memory which is Kingston KVR1333D3N9 4x => 16GB
After I flash the BIOS I always clear the CMOS actually twice since the first time I try to save the BIOS options (AHCI=on and no bootlogo etc.) the system does not boot XD but that might be because I don't unplug the powercord while I clear the CMOS though the computer is completely turned off. After I clear the CMOS a second time it will be able to save the options and normally boot.
A CMOS clear shouldn't be required actually since the BIOS update (DOS-WAY) destroys the CMOS checksum doing the same as a CMOS clear except for keeping the date (all other BIOS options are reset).
For kicks I've tried the in the BIOS 1.12 (1.C) I've put the Razer Naga in the USB2 slot I normally put it on the back = no boot, USB3 slots = no boot, front panel USB = no boot. Hell the first thing I do is trying usb-ports or different ports if something does not work like the Adaptec Raid Cards in the EFI mobo's.
I've been in IT for like 6 years now and I've never had problems with my Razer mouse(s) as I had an Razer Imperator before the Razer Naga. The 790FX-GD70 motherboard I had never had problems with it (besides it dying of old age ;P). Apperantly since the latest update the mouse also works on the 990FXA-GD80 motherboards without problems in the BIOS anymore.
Like I said the weird thing to me is that it happens with the 1.11 (1.B) and the 1.12 (1.C) bios while the 1.10 (1.A) bios (which is the one I'm on now) works perfectly. Which in logical sence makes the next 2 biosses bad as something is programmed in there differently than the 1.A bios and cause the Razer Naga (and most likely other gaming mice with own firmware) to fail. This should not be that way seeing as the if the only thing that is added to the bios (from 1.A on) is better cpu support, more memory support and the raid option rom not that I'm into bios programming but if the code was continued from the previous bios code and not rewritten completly the motherboard would still boot with the Naga period.

OfficeJet 6700 - "Unable to communicate with printer" message after install

I am on a hybrid network with Windows 7, 64-bit. Printer is hard-wired to the router (ethernet) but laptops are wireless. Installation doesn't allow for a hybrid option, just wireless or wired, so I installed as wired.
I just installed the OfficeJet 6700 - installed OK. I also updated software/firmware during the install process.
Windows' "Devices & Printers" recognizes the HP as being installed.
Printer is able to produce the network configuration page, etc. so we know the printer is functional, but when I try to print I get an "Unable to communicate with printer" message.
Windows' "Devices and Printers" troubleshooter thinks the driver is not installed, but as I mentioned, I just installed software from the CD.
UPDATE: I was able to install & print without problems on my wife's Win7, 64-bit laptop. Something about mine seems to be the issue. Also, HP Print & Scan Doctor reports that everything checks out OK, but when I try to print a test page at the end of the good doctor's diagnosis, I am still "unable to communicate with printer."

Sorry this is so long, but I tried to be through in my testing.
Followed your suggested steps.
I had previously set a static IP address, but just to be thorough, re-set it again with the same address.
I unplugged the USB cord from the laptop.
I began with the device labeled "HP OfficeJet 6700 (Copy 1)," which was set as the default printer.
After entering the IP address & clicking Next, it searched the network and returned this message:
Additional port information required
The device could not be identified.
The device is not found on the network. Be sure that:
1. The device is turned on.
The network is connected.
The device is properly configured.
The address on the previous page is correct. (re: the page where the IP address is entered)
If you are sure the address is correct, select the device type below.
I selected Standard (Generic Network Card) and clicked Next.
Summary dialog appeared and I clicked Finish.
Clicked OK/Apply.
Attempted to print. Like before, it sent the file to print queue - then nothing.
Right-clicked on the "Copy 1" device and selected Troubleshoot. Returned the message: Make printer "Fax HP OfficeJet 6700 the default printer" - even though this copy is already the default printer. (Usually when the original copy is set as the default, this copy is automatically re-named "Fax HP OfficeJet 6700.") I chose "Apply this fix."
Summary page said "Troubleshooting has completed." I closed the troubleshooter and attempted to print. I closed the Devices & Printers window so it could refresh. Re-opened Devices & Printers. Now the default printer is named "Fax HP OfficeJet 6700." The other device is grayed out and is simply named "HP OfficeJet 6700."
Attempted to print. (I'm testing w/ Notepad and .txt files)
I have 3 choices in the Notepad's printer dialog box but only 2 devices showing in the Devices & Printers window:
~ "Fax HP OfficeJet 6700" - This is the default printer in the Devices and Printers window. I clicked on Print & rec'd an error message: "Send Fax - HP Officejet 6700. There is a problem communicating with the Printer. Check your USB connection & verify that the printer is ready." Notepad's print dialog box shows status as Offline. I canceled all documents in the print queue.
~ "HP OfficeJet 6700." When I choose this printer option, Notepad's print dialog box shows status as "Paused - Offline." I clicked on "Print" anyway, and like before, it sent the file to print queue - then nothing. This is the printer that shows as grayed out in the Devices & Printers window. I canceled all documents in the print queue.
~ "HP OfficeJet 6700 (Copy 1)." There is no printer by this name in the Devices and Printers window even tho' it shows in Notepad's print dialog box. Notepad's print dialog box shows status as "Ready." In Devices & Printers, when I right-click on the one labeled "Fax OfficeJet 6700" (the default device) and choose "See what's printing," 2 HP devices are listed - the one labeled "Copy 1" and the one labeled "Fax." I clicked on "Print" and like before, it sent the file to print queue - then nothing. I canceled all documents in the print queue.
I plugged in the USB cord again and re-ran the same series of tests.
~ "Fax HP OfficeJet 6700" - This is still the default printer in the Devices and Printers window. Notepad's print dialog box shows status as "Ready." The fax window opened, waiting me to enter the recipient's name, add a cover sheet, etc. I closed the fax window. The .txt file was in the print queue for the "Fax" device, so I canceled all documents in the print queue.
~ "HP OfficeJet 6700." When I choose this printer option, Notepad's print dialog box shows status as "Paused - Offline." I clicked on "Print" anyway, and like before, it sent the file to print queue - then nothing. This is grayed out in the Devices & Printers window. I canceled all documents in the print queue.
~ "HP OfficeJet 6700 (Copy 1)." Again, there is no printer by this name in the Devices and Printers window even tho' it shows in Notepad's print dialog box. This is one of 2 choices in the device labeled "Fax" - the default device. Notepad's print dialog box shows status as "Ready." I clicked on "Print" and like before, it sent the file to print queue - then nothing. I canceled all documents in the print queue.
Next, I used the printer's touch screen interface and turned the wireless connection off, leaving the USB cord plugged in.
~ "Fax HP OfficeJet 6700" - Status: Ready. The fax window opened, same as before. I closed the fax window & canceled all documents in the print queue.
~ "HP OfficeJet 6700 - Status: Paused - Offline. I clicked on "Print" anyway, and like before, it sent the file to print queue - then nothing. This one shows as grayed out in the Devices & Printers window. I canceled all documents in the print queue.
~ "HP OfficeJet 6700 (Copy 1)" - Status: Error. I clicked Apply, then Print. Again, this is one of 2 choices in the device labeled "Fax" - the default device. Like before, it sent the file to print queue - then nothing. I canceled all documents in the print queue.
Reconnected to the wireless network & verified that the IP address had not changed.
Tried again to print using "HP OfficeJet 6700 (Copy 1)" - Status: Ready. I clicked Print and again, it sent the file to print queue - then nothing. This is still listed as one of 2 choices in the device labeled "Fax" - the default device." Like before, I canceled all documents in the print queue.
Next, I right-clicked on the one labeled "Fax OfficeJet 6700" (the default device) and choose "See what's printing" and selected the device labeled "HP OfficeJet 6700 (Copy 1)." In the print queue window, when I click on "Printer, one of my options is "Set as Default Printer." As soon as I did that, the device in the Devices & Printers window was renamed as "HP OfficeJet 6700 (Copy 1)" - no longer named "Fax." I tried to print again. Once again, file was sent to the print queue but never printed.

Unable to boot with UEFI by bootable windows 8.1 DVD

Similar Messages

Maybe you are looking for