Whatever I do I'm entering windows boot menu

I'm trying to install Windows 7 (UEFI mode) on HP Envy 6-1210sw (previously there was windows 8 installed). Installation went ok, but by mistake I installed from wrong dvd so I don't have a key for it. So, I tried to re-install from the right dvd.
Now the issue: whatever I do now I'm always entering windows boot menu. I tried:
-- ESC -> Startup Menu pops up -> F9 (should be boot device options) -> instead windows boot menu starts
-- ESC -> Startup Menu pops up -> F10 (shoud be bios setup) -> instead windows boot menu starts
-- ESC -> Startup Menu pops up -> F11 (should be recovery app.) -> instead windows boot menu starts
-- F9 -> (should be boot device options) -> instead windows boot menu starts
-- F10 (shoud be bios setup) -> instead windows boot menu starts
In short: I cannot boot enthing else then windows 7.
Is there a way to enforce bios or boot menu ?
Regards,
Michal

Michal765 wrote:
I'm trying to install Windows 7 (UEFI mode) on HP Envy 6-1210sw (previously there was windows 8 installed). Installation went ok, but by mistake I installed from wrong dvd so I don't have a key for it. So, I tried to re-install from the right dvd.
Now the issue: whatever I do now I'm always entering windows boot menu. I tried:
-- ESC -> Startup Menu pops up -> F9 (should be boot device options) -> instead windows boot menu starts
-- ESC -> Startup Menu pops up -> F10 (shoud be bios setup) -> instead windows boot menu starts
-- ESC -> Startup Menu pops up -> F11 (should be recovery app.) -> instead windows boot menu starts
-- F9 -> (should be boot device options) -> instead windows boot menu starts
-- F10 (shoud be bios setup) -> instead windows boot menu starts
In short: I cannot boot enthing else then windows 7.
Is there a way to enforce bios or boot menu ?
Regards,
Michal
Hi,
Have you tried to re-flash the BIOS or even upgrade it to the latest version (if possible)?
Dv6-7000 /Full HD/Core i5-3360M/GF 650M/Corsair 8GB/Intel 7260AC/Samsung Pro 256GB
Testing - HP 15-p000
HP Touchpad provided by HP
Currently on Debian Wheeze
*Please, help other users with the same issue by marking your solved topics as "Accept as Solution"*

Similar Messages

Toshiba Satellite C645-SP4145L enters windows boot manager and reboots[solved]

Toshiba Satellite C645-SP4145L
Problem description:
When the laptop is turned on, it goes for about less than a second to the Windows Boot Loader Screen, then it reboots itself, this loop repeats continously.
If you press the enter key quickly, the system boots to windows normally.
If you press the tab key it will allow you to execute memtest
If you try to boot from a cd or a usb, either changing the boot order in the BIOS menu or by choosing the option in the boot loader menu (F12), the laptop will crash and start beeping.
The problems persist either if the ac adpater if connected or disconnected. The problem persist if you remove the battery and work only with AC.
Tried solutions
1) Windows 7 reinstallation: Reinstalled windows (not booting from the cd, but from the older windows version). The problem persist
2)Reflashing BIOS: Download the Toshiba Boot Flashing tool, I upgraded the BIOS version, but the problem persist
3) Pressing F8 and trying to repair the laptop: It enters Advanced Boot Options, I have tried with al the options.
Startup Repair
System Restore
System Recovery Image (there is none)
Memtest
But the problem persist
4)Diagnostics performed
memtest: shows everything is ok
chkdsk c: shows no problem on the disk partition
Additional Info: Checking the OEM partition the recovery folder seems to be empty
Solved!
Go to Solution.

Satellite C645-SP4145L
When the laptop is turned on, it goes for about less than a second to the Windows Boot Loader Screen, then it reboots itself, this loop repeats continously.
If you press the enter key quickly, the system boots to windows normally.
Well done so far and good reporting. So Windows' loading sequence is messed up.
Try a System Restore from Windows first.
   What is System Restore?
If that doesn't fix things, burn a system repair disc (you should make that in any case) and use it to access the recovery environment.
   Create a system repair disc
   What are the system recovery options in Windows?
Try first a Startup Repair and let us know what happens.
-Jerry

Laptop won't load OS, won't enter BIOS/Boot Menu.

I recently installed Windows 7 Professional on my Compaq CQ56 PC, on a 260Gig HHD partition. I then installed Opensuse linux on the remainind 60Gig. However half way through installation my PC ran out of power and dhut down. I tried booting and changing the Boot Device menu, so that I complete installation, but it won't allow me to go into the boot menu (simply stops on the compaq start screen - fan and cd-rom will be working.) Is there a way for me to rectify this without losing my data?

It sounds as if you were never warned to always do an OS installation or anything that has to do with partitioning while on external power.
Please identify your notebook with more than just the model type. You have given an incomplete picture of your hardware configuration while reporting an extreme hardware/firmware issue. IT would help to remove the battery and take a look at the service tag. Please post the p/n (product number) here in your thread
There are a few things to try.
Remove the hard disk. Connect the power adapter and press the power button. Does the BIOS screen appear and warn that it can not find a bootable disk?
If it does not, then try a hard reset.
Try a hard reset as follows:
1) Remove the battery and unplug the DC power adapter.
2) Press and hold the power button for more than fifteen seconds.
3) Plug in the DC power adapter (leave the battery out for now)
4) Press the power button
Please post your positive or negative results here in your thread.
You can put the hard disk in an external housing and connect it to another PC to try torecover your data. What you will see will depend on the operating system of the PC that you use for data recovery.
****Please click on Accept As Solution if a suggestion solves your problem. It helps others facing the same problem to find a solution easily****
2015 Microsoft MVP - Windows Experience Consumer

X61 Windows setup [ems aktiviert] - how to deactivate in boot menu?

I have a x61 thinkpad with Vista. Recently I installed Win 7 via a bootable USB stick. For this I had to set the boot menu so that the computer starts from the USB stick. After installing Win 7 I reset the Boot order to default.
Now everytime I start my computer a boot selection appears:
1. Win 7 Professional
2. Windows Setup (EMS aktiviert)
This is very annoying as I dont want to enter the windows setup. How can I deactivate this selection so that the computer directly starts Win 7 without entering the boot menu?
Thanks for any help!

Thanx for the rapid response. I had tried that prior to posting and it didn't help. I went to System preferences>Desktop & Screen saver and there is was sitting in Desktop, the image of Windows boot manager screen. No clue as to how it got there ut changing the desktop image cleared it from my screen.
Thanks again for trying to help.

Boot menu - holding down 'option' issues

Hi,
I thought I would share an issue which had me confused but I figured out how to fix. I bought an Apple keyboard with the extended number pad and when trying to get to the boot menu by holding down 'option' it won't work. I had to switch to the default mini keyboard (without number pad) and hold down 'option' to get access to it.
This was frustrating when trying to sort out some bootcamp issues.
I hope this issue is addressed in future updates.
Thanks,
Greg

I too have a really weird issue with the boot menu. It's only started happening recently (that and numerous other problems with this **** 17" MBP!).
I hold down the 'Option' key to enter the boot menu... which it does, and it shows me boot options of OSX and Windows 7. Now the really weird thing is, when I select one and hit the enter key nothing happens... nothing!! It just sits on the boot menu screen... still allowing me to switch between the two but no response when enter is pressed. I've tried unplugging all external devices but to no avail.
I've just reinstalled Snow Leopard (although without formatting the hard drive) and I totally scrubbed Windows 7 and reinstalled and it still has the same issue... sometimes... not always though.... aagghh!
I've had more problems with this Mac than I've had with my old PC I hate to say.

Boot menu show alone at start

hello, today to start my macbook pro 15 "with dualboot (Win 8.1) instead of from disk default (windows) went to the menu screen to boot. I rebooted and everything is back to normal. What could have happened?

That was not my question: I know how to enter on boot menu. The problem is that instead of starting Windows, the notebook is positioned immediately on boot menu

Efibootmgr & gummiboot replaced UEFI entry for Windows Boot Manager

TLDR
I am now in Windows 7 and dual boot with Arch is working fine.
But before I update Arch, I would like to understand what happened, as in why adding an efibootmgr entry for Arch replaced/deleted the Windows Boot Manager entry although I followed the BG.
The status of my UEFI boot menu was, before the installation of Arch:
Windows Boot Manager
AHCI HDJ... (hard drive 1)
AHCI ST... (hard drive 2)
While working through the BG, I decided to use gummiboot=> https://wiki.archlinux.org/index.php/Be … #Gummiboot. So:
pacman -S gummiboot
gummiboot install
pacman -S efibootmgr
gummiboot install
[some error ocurred, as mentioned in red box]
efibootmgr -c -L "Gummiboot" -l /EFI/gummiboot/gummibootx64.efi
nano /boot/loader/entries/arch.conf
title Arch Linux
linux /vmlinuz-linux
initrd /initramfs-linux.img
options root=/dev/sdb3 ro
[CTRL + X, Y, Enter]
exit
umount /mnt/{boot,home,}
reboot
I then saw a new list of the UEFI boot order:
Gummiboot
AHCI HDJ... (hard drive 1)
AHCI ST... (hard drive 2)
Chose Gummiboot and it brought up a gummiboot menu with entries
Arch Linux
Windows Boot Manager
EFI Shell something
Selected Arch Linux and it went to a message something along "boot device ' ' not found" and I was in a shell which was, I think, rootfs.
I rebooted via the button on my desktop and out the Arch Linux USB drive back. After mounting the partitions:
gummiboot remove
efibootmgr
[0000: Windows Boot Manager
[0001: Arch Linux
[0002: AHCI HDJ...
[0003: AHCI ST...
exit
umount /mnt/{boot,home,}
reboot
Now I booted into a black screen with white text which said something "Reboot and select proper Boot device"
=> Inserted Win 7 64-bit DVD, repaired the boot sector. Rebooted, saw I had these entries again:
Windows Boot Manager
AHCI HDJ... (hard drive 1)
AHCI ST... (hard drive 2)
The boot into Windows worked fine. Rebooted, chrooted into my install again and:
efibootmgr
[0000: Arch Linux
[0001: Windows Boot Manager
[0003: AHCI HDJ...
[0003: AHCI ST...
efibootmogr -b 0 -B
Then I used the EFISTUB method:
efibootmgr -c -L "Arch Linux" -l /vmlinuz-linux -u "root=/dev/sdb3 ro initrd=/initramfs-linux.img"
efibootmgr
[0000: Windows Boot Manager
[0001: Arch Linux
[0002: AHCI HDJ...
[0003: AHCI ST...
exit
umount /mnt/{boot,home,}
reboot
On reboot, 'Windows Boot Manager' was again replaced by 'Arch Linux'.
=> Inserted Win 7 64-bit DVD, repaired the boot sector.
Rebooted, I have now Windows Boot Manager + Arch Linux and dual boot works now.
My questions:
What is going on with efibootmgr replacing/deleting the Windows entry? Is there something wrong with my UEFI menu?
In connection with 1., I would like to sync the EFISTUB Kernel (wiki entry) before I run pacman -Syu. Can I do that now?
Can I uninstall gummiboot now?
Last edited by jones (2013-07-11 12:30:55)

henrik wrote:So in light of your post, I decided to ditch EFISTUB + gummiboot and try out GRUB. Thanks for clearing it up a bit. Which is what confuses me a great deal more, as GRUB/gummiboot obviously do not meddle with Microsoft's EFI files. Right?
EFI relies on two things to boot:
Boot loader program files on the ESP (or occasionally elsewhere).
NVRAM entries pointing to the boot loader files.
Your own problems seem to be with the NVRAM entries, not with the boot loader files themselves. Unfortunately, managing those NVRAM entries has proven to be problematic because of bugs in specific EFI implementations, bugs in efibootmgr and other tools that manipulate the NVRAM entries, poor documentation, and other factors.
To answer your question, though, no boot loader should mess with another's files. Such things can happen, though. The number of bugs that cause Microsoft's boot loader (EFI/Microsoft/Boot/bootmgfw.efi) to be treated deferentially have provoked some tools to use it as a target location for other boot loaders. (Ubuntu's Boot Repair tool does this in a rather overzealous way. So does my own rEFInd installer script, but only under certain narrow circumstances.) Also, the EFI/BOOT/bootx64.efi file is a special case; it's the fallback bootloader that's used when NVRAM entries are missing or don't work, and various boot loader installation procedures place copies in that location, so it can be overwritten and could contain just about anything.
However, the whole thing happened again with GRUB. So I did the whole "repairing Boot problems" with the Windows DVD rescue thingy again and deleted all non-Microsoft files from the EFI partition, /dev/sda1.
Then I formatted / (root) and installed arch again and followed the Beginners' Guide which suggest mounting /dev/sda1/ to /mnt/boot (in contrast to the GRUB entry where the ESP should be mounted to /mnt/boot/efi).
I strongly advise against doing a complete re-installation just to overcome a boot loader problem. Instead, figure out what the problem is and fix it. Doing a complete re-installation is not likely to fix anything, and depending on precisely how you do it, you could end up with a more complex problem. The reason is that the re-installation is not likely to erase the NVRAM entries from the old installation, so you could find that you've got additional stray NVRAM entries. If you do happen to fix the problem by re-installing (say, because you selected a different installation option), you're not likely to know what changed to fix the problem, so you could end up in the same boat should you need to re-install again in the future.
But it did not show this line
Found Windows 7 (loader) on /dev/sda1
... how come??
I've given up trying to understand GRUB's configuration scripts. You could try creating an entry manually by editing /etc/grub.d/40_custom; or you could forget about using the GRUB scripts and create a hand-crafted grub.cfg; or you could forget about using GRUB at all. I'm not a fan of GRUB, so my personal choice is the final one.
So for all the headache and time ... should I delete the EFI partition and recreate it maybe? I think it's possible using the Windows 7 DVD.
But somehow using efibootmgr on my UEFI list somehow invalidated the Windows entry.
Reviewing your posts, it seems that you want to use the EFI stub loader directly, but you're having problems with that because when you add it to the NVRAM entries, Windows drops off your boot manager's boot options. The obvious solution to this problem is to forget about adding the EFI stub loader directly to the NVRAM entries, and instead add a boot manager that can handle either a Linux kernel or the Windows boot loader. (IMHO, this is the superior solution anyhow; I disagree with the Arch wiki's emphasis on using the EFI stub loader "raw.") It seems you were trying to do this with GRUB but had problems booting Windows. Earlier you tried gummiboot but had problems booting Linux. My suggestion is to either go back to gummiboot and fix its problem or try rEFInd. The "device not found" error you reported with gummiboot is usually caused by either a missing (or incorrectly-specified) initrd file or by an incorrectly-specified "root=" option passed to the kernel. Check those possitilities, and if you need help, report what happens in more detail. If necessary, take a digital photo of the screen and post it here. (Make sure it's legible, though!)
You can try rEFInd with minimal disk by using a CD-R or USB flash drive image. Boot with that and your NVRAM and ESP won't be affected at all. If you can get rEFInd working from the flash drive, you can then install it to your hard disk and it should continue working. Note that you probably won't be able to boot Linux directly from rEFInd with your current configuration without adding a "root=" specification to the kernel command line. You can do this by hitting F2 or Insert twice rather than launching Linux by pressing Enter. Alternatively, you can create a refind_linux.conf file in the directory that holds your kernel. That file's contents are described in the rEFInd documentation.

[Forum FAQ]How to customize Windows 7 & Windows 8.1 dual boot menu

Scenario 1:
When you install Windows 8.1 on Windows 7 based computer, the default boot option is Windows 8.1 boot options menu which is shown as Figure 1:
If you want to use the old Windows 7 boot menu, follow these steps:
Start the computer and then go into
Windows 8.1 boot options menu which is shown as Figure 1.
Click
Change defaults or choose other options, and Options menu appears which is shown as Figure 2.
Click
Choose a default operation system option.
Click
Windows 7 Enterprise option to set Windows 7 as the default operating system in the Choose a default operating system menu which is shown as Figure 3.
Restart, and it will be changed to
Windows 7 boot options menu which is as shown as Figure
Scenario 2:
If you have Windows 7 and Windows 8.1 dual-boot configuration, and the default boot menu is Windows 7 boot options menu which is shown as Figure 4.
If you want to get the GUI as Windows 8.1 style, follow these steps:
Boot into Windows 8.1 computer, open the
command Prompt (Admin).
Type the following command
bcdboot c:\Windows and press Enter.
Restart, and you'll see the Windows 8.1 boot options menu which is as shown Figure 1.
Scenario 3:
When you have dual-boot system, one of the system disappear from the boot menu. We could follow these steps to get it back:
Boot the computer from the installation media (Here my example is Windows 7) that works fine system.
Go into
System Recovery Options menu, which is as shown as Figure 6.
Click
Command Prompt link to open the command prompt window
Use the
diskpart and list volume commands to confirm the OS boot drive, the commands are shown as Figure 7.
Backup the bcd file, rename it.
Rebuild a new bcd file. It will scan all disk to confirm all Windows installation on your computer and ask if you want to add them to boot list.
Type
Y to agree with adding to boot list. In next boot, you will get all boot options back in the boot menu.
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Since you've selected as default OS as Windows 8.1 you can go to disk management console and format the drive as required.
You can remove the Win 7 entry from boot loader:
To launch msconfig:
Click Start
In the Search text box, type msconfig
Launch msconfig by selecting it from the search results above the search text box.
After msconfig is launched:
Go to the Boot tab
Slect the boot entry you want to delete.
Click the Delete button and then click OK.
Arnav Sharma | http://arnavsharma.net/ Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading
the thread.

Arch & Windows 8 Dual Boot -- Windows Boot Loader loads grub-rescue

Arch works fine,but as it always happens Windows boot went down. Both OS are EFI.
Note that boot secure and fast boot were disabled for Windows 8.
I used os-prober, but did not fix anything; so, I removed it. I tried to hack things out using boot-repair from Ubuntu, but it requires a repository, grub-efi, from Ubuntu that Arch doesn't have.
I am trying to modify files in grub.d and grub.cfg and hopefully fix something.
Exact description:
- archgrub loads and shows 3 entries. Two for Arch that load the sys succesfully and one for Windows 8 that fails.
- When I try to execute Windows from grub, it brings me to a grub rescue>
and shows error /boot/grub/x86_64-efi/normal.mod not found
As far as I am concerned this .mod is from Linux, so I don't know why it is being called into Windows loading procedures.
lsblk returns:
[jav@localhost ~]$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 931.5G 0 disk
|-sda1 8:1 0 1000M 0 part
|-sda2 8:2 0 260M 0 part
|-sda3 8:3 0 1000M 0 part
|-sda4 8:4 0 128M 0 part
|-sda5 8:5 0 605.3G 0 part
|-sda6 8:6 0 5.4G 0 part /boot/efi
|-sda7 8:7 0 25G 0 part
|-sda8 8:8 0 20G 0 part
|-sda9 8:9 0 244.1G 0 part /
`-sda10 8:10 0 29.3G 0 part
sr0 11:0 1 1024M 0 rom
Here's the output of fdisk. Another weird thing is that sometimes ubuntu would show on my terminal. See the first line below, "jav@ubuntu"?!
[jav@ubuntu ~]$ sudo fdisk -l
[sudo] password for jav:
Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: [i deleted this]
Device Start End Size Type
/dev/sda1 2048 2050047 1000M Windows recovery environment
/dev/sda2 2050048 2582527 260M EFI System
/dev/sda3 2582528 4630527 1000M unknown
/dev/sda4 4630528 4892671 128M Microsoft reserved
/dev/sda5 4892672 1274335231 605.3G Microsoft basic data
/dev/sda6 1847777280 1859151871 5.4G EFI System
/dev/sda7 1859151872 1911580671 25G Microsoft basic data
/dev/sda8 1911580672 1953523711 20G Windows recovery environment
/dev/sda9 1335775232 1847777279 244.1G Linux filesystem
/dev/sda10 1274335232 1335775231 29.3G Microsoft basic data
And, bootinfoscript output:
Boot Info Script 0.61 [1 April 2012]
============================= Boot Info Summary: ===============================
=> No boot loader is installed in the MBR of /dev/sda.
sda1: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:
sda2: __________________________________________________________________________
File system: vfat
Boot sector type: Windows 7: FAT32
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /efi/Boot/bkpbootx64.efi /efi/Boot/bootx64.efi
/efi/ubuntu/grubx64.efi
sda3: __________________________________________________________________________
File system: vfat
Boot sector type: Windows 7: FAT32
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /efi/Boot/bkpbootx64.efi /efi/Boot/bootx64.efi
/efi/ubuntu/grubx64.efi /bootmgr /boot/bcd
sda4: __________________________________________________________________________
File system:
Boot sector type: -
Boot sector info:
Mounting failed: mount: unknown filesystem type ''
sda5: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /bootmgr /Boot/BCD /Windows/System32/winload.exe
sda6: __________________________________________________________________________
File system: vfat
Boot sector type: SYSLINUX 6.02 ... :..(:,:0:4:8:....D:H:L:[.T:[.\:`:d:[.l:p:t:x:|:.:.:.:.:.:.:.:.....................
Boot sector info: Syslinux looks at sector 99102 of /dev/sda6 for its
second stage. SYSLINUX is installed in the /syslinux
directory. No errors found in the Boot Parameter Block.
Operating System:
Boot files: /grub/grub.cfg /syslinux/syslinux.cfg
/syslinux/ldlinux.sys
sda7: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:
sda8: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:
sda9: __________________________________________________________________________
File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Arch Linux ()
Boot files: /etc/fstab
sda10: _________________________________________________________________________
File system: ext4
Boot sector type: -
Boot sector info:
Operating System:
Boot files:
============================ Drive/Partition Info: =============================
Drive: sda _____________________________________________________________________
Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Partition Boot Start Sector End Sector # of Sectors Id System
/dev/sda1 1 1,953,525,167 1,953,525,167 ee GPT
GUID Partition Table detected.
Partition Start Sector End Sector # of Sectors System
/dev/sda1 2,048 2,050,047 2,048,000 Windows Recovery Environment (Windows)
/dev/sda2 2,050,048 2,582,527 532,480 EFI System partition
/dev/sda3 2,582,528 4,630,527 2,048,000 -
/dev/sda4 4,630,528 4,892,671 262,144 Microsoft Reserved Partition (Windows)
/dev/sda5 4,892,672 1,274,335,231 1,269,442,560 Data partition (Windows/Linux)
/dev/sda6 1,847,777,280 1,859,151,871 11,374,592 EFI System partition
/dev/sda7 1,859,151,872 1,911,580,671 52,428,800 Data partition (Windows/Linux)
/dev/sda8 1,911,580,672 1,953,523,711 41,943,040 Windows Recovery Environment (Windows)
/dev/sda9 1,335,775,232 1,847,777,279 512,002,048 Data partition (Linux)
/dev/sda10 1,274,335,232 1,335,775,231 61,440,000 Data partition (Windows/Linux)
"blkid" output: ________________________________________________________________
Device UUID TYPE LABEL
/dev/sda1 CE62D9F062D9DCF1 ntfs WINRE_DRV
/dev/sda10 150a8788-6049-45ed-85af-ded92a2c0801 ext4
/dev/sda2 16DC-8816 vfat SYSTEM_DRV
/dev/sda3 7CDD-0403 vfat LRS_ESP
/dev/sda4
/dev/sda5 40E4E0CFE4E0C7EC ntfs Windows8_OS
/dev/sda6 9C3F-2A9E vfat
/dev/sda7 7240E43740E40427 ntfs LENOVO
/dev/sda8 422CE5EA2CE5D945 ntfs PBR_DRV
/dev/sda9 1a765403-f251-43d8-8edf-c191475d3837 ext4
================================ Mount points: =================================
Device Mount_Point Type Options
/dev/sda6 /boot vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/sda6 /boot/efi vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/sda9 / ext4 (rw,relatime,data=ordered)
============================= sda6/grub/grub.cfg: ==============================
# DO NOT EDIT THIS FILE
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_gpt
insmod ext2
set root='hd0,gpt9'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt9 --hint-efi=hd0,gpt9 --hint-baremetal=ahci0,gpt9 1a765403-f251-43d8-8edf-c191475d3837
else
search --no-floppy --fs-uuid --set=root 1a765403-f251-43d8-8edf-c191475d3837
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
fi
terminal_input console
terminal_output gfxterm
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Arch Linux, with Linux core repo kernel' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-true-1a765403-f251-43d8-8edf-c191475d3837' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod fat
set root='hd0,gpt6'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt6 --hint-efi=hd0,gpt6 --hint-baremetal=ahci0,gpt6 9C3F-2A9E
else
search --no-floppy --fs-uuid --set=root 9C3F-2A9E
fi
echo 'Loading Linux core repo kernel ...'
linux /vmlinuz-linux root=UUID=1a765403-f251-43d8-8edf-c191475d3837 rw quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux.img
menuentry 'Arch Linux, with Linux core repo kernel (Fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-fallback-1a765403-f251-43d8-8edf-c191475d3837' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod fat
set root='hd0,gpt6'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt6 --hint-efi=hd0,gpt6 --hint-baremetal=ahci0,gpt6 9C3F-2A9E
else
search --no-floppy --fs-uuid --set=root 9C3F-2A9E
fi
echo 'Loading Linux core repo kernel ...'
linux /vmlinuz-linux root=UUID=1a765403-f251-43d8-8edf-c191475d3837 rw quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux-fallback.img
### END /etc/grub.d/10_linux ###
## Attempt at fixing grub
# insmod fat
# set root='hd0,gpt6'
### BEGIN /etc/grub.d/30_os-prober ###
#menuentry 'Windows Boot Manager (on /dev/sda2)' --class windows --class os $menuentry_id_option 'osprober-efi-16DC-8816' {
# insmod part_gpt
# insmod fat
# set root='hd0,gpt2'
# if [ x$feature_platform_search_hint = xy ]; then
# search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 16DC-8816
# else
# search --no-floppy --fs-uuid --set=root 16DC-8816
# fi
# chainloader /EFI/Microsoft/Boot/bootmgfw.efi
menuentry "Windows 8 UEFI" {
set root='(hd0,gpt2)'
chainloader /EFI/Microsoft/Boot/bootmgfw.efi
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
### BEGIN /etc/grub.d/60_memtest86+ ###
### END /etc/grub.d/60_memtest86+ ###
========================= sda6/syslinux/syslinux.cfg: ==========================
# Config file for Syslinux -
# /boot/syslinux/syslinux.cfg
# Comboot modules:
# * menu.c32 - provides a text menu
# * vesamenu.c32 - provides a graphical menu
# * chain.c32 - chainload MBRs, partition boot sectors, Windows bootloaders
# * hdt.c32 - hardware detection tool
# * reboot.c32 - reboots the system
# To Use: Copy the respective files from /usr/lib/syslinux to /boot/syslinux.
# If /usr and /boot are on the same file system, symlink the files instead
# of copying them.
# If you do not use a menu, a 'boot:' prompt will be shown and the system
# will boot automatically after 5 seconds.
# Please review the wiki: https://wiki.archlinux.org/index.php/Syslinux
# The wiki provides further configuration examples
DEFAULT arch
PROMPT 0 # Set to 1 if you always want to display the boot: prompt
TIMEOUT 50
# You can create syslinux keymaps with the keytab-lilo tool
#KBDMAP de.ktl
# Menu Configuration
# Either menu.c32 or vesamenu32.c32 must be copied to /boot/syslinux
UI menu.c32
#UI vesamenu.c32
# Refer to http://syslinux.zytor.com/wiki/index.php/Doc/menu
MENU TITLE Arch Linux
#MENU BACKGROUND splash.png
MENU COLOR border 30;44 #40ffffff #a0000000 std
MENU COLOR title 1;36;44 #9033ccff #a0000000 std
MENU COLOR sel 7;37;40 #e0ffffff #20ffffff all
MENU COLOR unsel 37;44 #50ffffff #a0000000 std
MENU COLOR help 37;40 #c0ffffff #a0000000 std
MENU COLOR timeout_msg 37;40 #80ffffff #00000000 std
MENU COLOR timeout 1;37;40 #c0ffffff #00000000 std
MENU COLOR msg07 37;40 #90ffffff #a0000000 std
MENU COLOR tabmsg 31;40 #30ffffff #00000000 std
# boot sections follow
# TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
LABEL arch
MENU LABEL Arch Linux
LINUX ../vmlinuz-linux
APPEND root=/dev/sda3 rw
INITRD ../initramfs-linux.img
LABEL archfallback
MENU LABEL Arch Linux Fallback
LINUX ../vmlinuz-linux
APPEND root=/dev/sda3 rw
INITRD ../initramfs-linux-fallback.img
#LABEL windows
# MENU LABEL Windows
# COM32 chain.c32
# APPEND hd0 1
LABEL hdt
MENU LABEL HDT (Hardware Detection Tool)
COM32 hdt.c32
LABEL reboot
MENU LABEL Reboot
COM32 reboot.c32
LABEL poweroff
MENU LABEL Poweroff
COM32 poweroff.c32
=================== sda6: Location of files loaded by Grub: ====================
GiB - GB File Fragment(s)
================= sda6: Location of files loaded by Syslinux: ==================
GiB - GB File Fragment(s)
============== sda6: Version of COM32(R) files used by Syslinux: ===============
syslinux/cat.c32 : not a COM32/COM32R module
syslinux/chain.c32 : not a COM32/COM32R module
syslinux/cmd.c32 : not a COM32/COM32R module
syslinux/config.c32 : not a COM32/COM32R module
syslinux/cptime.c32 : not a COM32/COM32R module
syslinux/cpuid.c32 : not a COM32/COM32R module
syslinux/cpuidtest.c32 : not a COM32/COM32R module
syslinux/debug.c32 : not a COM32/COM32R module
syslinux/disk.c32 : not a COM32/COM32R module
syslinux/dmitest.c32 : not a COM32/COM32R module
syslinux/elf.c32 : not a COM32/COM32R module
syslinux/ethersel.c32 : not a COM32/COM32R module
syslinux/gfxboot.c32 : not a COM32/COM32R module
syslinux/gpxecmd.c32 : not a COM32/COM32R module
syslinux/hdt.c32 : not a COM32/COM32R module
syslinux/hexdump.c32 : not a COM32/COM32R module
syslinux/host.c32 : not a COM32/COM32R module
syslinux/ifcpu.c32 : not a COM32/COM32R module
syslinux/ifcpu64.c32 : not a COM32/COM32R module
syslinux/ifmemdsk.c32 : not a COM32/COM32R module
syslinux/ifplop.c32 : not a COM32/COM32R module
syslinux/kbdmap.c32 : not a COM32/COM32R module
syslinux/kontron_wdt.c32 : not a COM32/COM32R module
syslinux/ldlinux.c32 : not a COM32/COM32R module
syslinux/libcom32.c32 : not a COM32/COM32R module
syslinux/libgpl.c32 : not a COM32/COM32R module
syslinux/liblua.c32 : not a COM32/COM32R module
syslinux/libmenu.c32 : not a COM32/COM32R module
syslinux/libutil.c32 : not a COM32/COM32R module
syslinux/linux.c32 : not a COM32/COM32R module
syslinux/ls.c32 : not a COM32/COM32R module
syslinux/lua.c32 : not a COM32/COM32R module
syslinux/mboot.c32 : not a COM32/COM32R module
syslinux/meminfo.c32 : not a COM32/COM32R module
syslinux/menu.c32 : not a COM32/COM32R module
syslinux/pcitest.c32 : not a COM32/COM32R module
syslinux/pmload.c32 : not a COM32/COM32R module
syslinux/poweroff.c32 : not a COM32/COM32R module
syslinux/prdhcp.c32 : not a COM32/COM32R module
syslinux/pwd.c32 : not a COM32/COM32R module
syslinux/pxechn.c32 : not a COM32/COM32R module
syslinux/reboot.c32 : not a COM32/COM32R module
syslinux/rosh.c32 : not a COM32/COM32R module
syslinux/sanboot.c32 : not a COM32/COM32R module
syslinux/sdi.c32 : not a COM32/COM32R module
syslinux/sysdump.c32 : not a COM32/COM32R module
syslinux/vesainfo.c32 : not a COM32/COM32R module
syslinux/vesamenu.c32 : not a COM32/COM32R module
syslinux/vpdtest.c32 : not a COM32/COM32R module
syslinux/whichsys.c32 : not a COM32/COM32R module
syslinux/zzjson.c32 : not a COM32/COM32R module
=============================== sda9/etc/fstab: ================================
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda9
UUID=1a765403-f251-43d8-8edf-c191475d3837 / ext4 rw,relatime,data=ordered 0 1
# /dev/sda6
#UUID=9C3F-2A9E /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
UUID=9C3F-2A9E /boot vfat defaults 0 2
UUID=9C3F-2A9E /boot/efi vfat defaults 0 1
============== sda9: Version of COM32(R) files used by Syslinux: ===============
boot/syslinux/cat.c32 : not a COM32/COM32R module
boot/syslinux/chain.c32 : not a COM32/COM32R module
boot/syslinux/cmd.c32 : not a COM32/COM32R module
boot/syslinux/config.c32 : not a COM32/COM32R module
boot/syslinux/cptime.c32 : not a COM32/COM32R module
boot/syslinux/cpuid.c32 : not a COM32/COM32R module
boot/syslinux/cpuidtest.c32 : not a COM32/COM32R module
boot/syslinux/debug.c32 : not a COM32/COM32R module
boot/syslinux/disk.c32 : not a COM32/COM32R module
boot/syslinux/dmitest.c32 : not a COM32/COM32R module
boot/syslinux/elf.c32 : not a COM32/COM32R module
boot/syslinux/ethersel.c32 : not a COM32/COM32R module
boot/syslinux/gfxboot.c32 : not a COM32/COM32R module
boot/syslinux/gpxecmd.c32 : not a COM32/COM32R module
boot/syslinux/hdt.c32 : not a COM32/COM32R module
boot/syslinux/hexdump.c32 : not a COM32/COM32R module
boot/syslinux/host.c32 : not a COM32/COM32R module
boot/syslinux/ifcpu.c32 : not a COM32/COM32R module
boot/syslinux/ifcpu64.c32 : not a COM32/COM32R module
boot/syslinux/ifmemdsk.c32 : not a COM32/COM32R module
boot/syslinux/ifplop.c32 : not a COM32/COM32R module
boot/syslinux/kbdmap.c32 : not a COM32/COM32R module
boot/syslinux/kontron_wdt.c32 : not a COM32/COM32R module
boot/syslinux/ldlinux.c32 : not a COM32/COM32R module
boot/syslinux/libcom32.c32 : not a COM32/COM32R module
boot/syslinux/libgpl.c32 : not a COM32/COM32R module
boot/syslinux/liblua.c32 : not a COM32/COM32R module
boot/syslinux/libmenu.c32 : not a COM32/COM32R module
boot/syslinux/libutil.c32 : not a COM32/COM32R module
boot/syslinux/linux.c32 : not a COM32/COM32R module
boot/syslinux/ls.c32 : not a COM32/COM32R module
boot/syslinux/lua.c32 : not a COM32/COM32R module
boot/syslinux/mboot.c32 : not a COM32/COM32R module
boot/syslinux/meminfo.c32 : not a COM32/COM32R module
boot/syslinux/menu.c32 : not a COM32/COM32R module
boot/syslinux/pcitest.c32 : not a COM32/COM32R module
boot/syslinux/pmload.c32 : not a COM32/COM32R module
boot/syslinux/poweroff.c32 : not a COM32/COM32R module
boot/syslinux/prdhcp.c32 : not a COM32/COM32R module
boot/syslinux/pwd.c32 : not a COM32/COM32R module
boot/syslinux/pxechn.c32 : not a COM32/COM32R module
boot/syslinux/reboot.c32 : not a COM32/COM32R module
boot/syslinux/rosh.c32 : not a COM32/COM32R module
boot/syslinux/sanboot.c32 : not a COM32/COM32R module
boot/syslinux/sdi.c32 : not a COM32/COM32R module
boot/syslinux/sysdump.c32 : not a COM32/COM32R module
boot/syslinux/vesainfo.c32 : not a COM32/COM32R module
boot/syslinux/vesamenu.c32 : not a COM32/COM32R module
boot/syslinux/vpdtest.c32 : not a COM32/COM32R module
boot/syslinux/whichsys.c32 : not a COM32/COM32R module
boot/syslinux/zzjson.c32 : not a COM32/COM32R module
======================== Unknown MBRs/Boot Sectors/etc: ========================
Unknown GPT Partiton Type
e7afbfbf4fa38a449a5b6213eb736c22
========= Devices which don't seem to have a corresponding hard drive: =========
sdb
=============================== StdErr Messages: ===============================
cat: /tmp/BootInfo-p9ML2Cte/Tmp_Log: No such file or directory
cat: /tmp/BootInfo-p9ML2Cte/Tmp_Log: No such file or directory
/dev/cdrom: open failed: No medium found
/dev/sdb: open failed: No medium found
No volume groups found
mdadm: No arrays found in config file or automatically
Any ideas?
Here's my grub.cfg:
# DO NOT EDIT THIS FILE
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_gpt
insmod ext2
set root='hd0,gpt9'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt9 --hint-efi=hd0,gpt9 --hint-baremetal=ahci0,gpt9 1a765403-f251-43d8-8edf-c191475d3837
else
search --no-floppy --fs-uuid --set=root 1a765403-f251-43d8-8edf-c191475d3837
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
fi
terminal_input console
terminal_output gfxterm
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Arch Linux, with Linux core repo kernel' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-true-1a765403-f251-43d8-8edf-c191475d3837' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod fat
set root='hd0,gpt6'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt6 --hint-efi=hd0,gpt6 --hint-baremetal=ahci0,gpt6 9C3F-2A9E
else
search --no-floppy --fs-uuid --set=root 9C3F-2A9E
fi
echo 'Loading Linux core repo kernel ...'
linux /vmlinuz-linux root=UUID=1a765403-f251-43d8-8edf-c191475d3837 rw quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux.img
menuentry 'Arch Linux, with Linux core repo kernel (Fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-fallback-1a765403-f251-43d8-8edf-c191475d3837' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod fat
set root='hd0,gpt6'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt6 --hint-efi=hd0,gpt6 --hint-baremetal=ahci0,gpt6 9C3F-2A9E
else
search --no-floppy --fs-uuid --set=root 9C3F-2A9E
fi
echo 'Loading Linux core repo kernel ...'
linux /vmlinuz-linux root=UUID=1a765403-f251-43d8-8edf-c191475d3837 rw quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux-fallback.img
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Windows Boot Manager (on /dev/sda2)' --class windows --class os $menuentry_id_option 'osprober-efi-16DC-8816' {
insmod part_gpt
insmod fat
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 16DC-8816
else
search --no-floppy --fs-uuid --set=root 16DC-8816
fi
chainloader /EFI/Microsoft/Boot/bootmgfw.efi
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
### BEGIN /etc/grub.d/60_memtest86+ ###
### END /etc/grub.d/60_memtest86+ ###
Last edited by knowNothing23 (2013-12-30 00:17:02)

Hi,
New to this forum, joined today in anticipation of trying an install of AL...For whatever this may be worth:
I have an HP Pavillion desktop that came with Windows 8 (now 8.1), & has, of course, a UEFI boot system. I tried earlier to install Ubuntu Studio (which I currently run) on the same disk as Windows (/dev/sda), I made (I believe) a huge mistake in trying to install as LVM/ext4... wiped out my Windows install & made the UEFI unavailable... I had to do a complete re-install of Windows (fortunately, I did the recommended system backup, using 4 DVD's!) so then I tried a (non LVM) install on an external usb 3.0, with the Grub 2 on the external disk (great access time, & it worked fine... IMO)...
One other item: as I have been trying to find the right flavor of Linux for my main purposes, I have been trying various distros. & having to try to learn to negotiate the UEFI, secure/legacy procedures (still learning)... As I was unsure of installing rEFind... I did down load the .iso, burn it to a CD...
http://www.rodsbooks.com/refind/getting.html
& in legacy mode, found that simply putting it (rEFind CD into the CD/DVD player, which in the UEFI it is labeled something like HP/UEFI CD/DVD), & then launching it, rEFind worked for some other distros...that is, I was able to boot into my Linux distros, even bypassing Grub), as well as having the option of booting Windows. It may seem trivial that I say this (it maybe is), but I have not seen anywhere (I have scoured the internet rather well) this mentioned as a possibility (though it, of course, would not make such a good permanent solution, especially for computers like mine that have only one CD/DVD player).
HenryP

MDT 0xc0000098 The windows boot configuration data file does not contain a valid OS entry

hello,
i installed WDS+MDT for OS deployment. all was working fine.
Now i need our branch office to be able to deploy OS as well.
I installed a new Win 2008R2 server, and installed the WDS service on it.
When reading about this on the internet i saw i need, on the MDT at our main office, to make a link, under "Advanced Configuration" - "Linked Deployment Shares" to the new WDS server (I used this: http://www.balm.se/?p=115")
when doing so i entered the UNC path to the new server and then, on the created link, i right click and choose "Replicate now".
after doing so, i tried booting a laptop just to see if there is any impact, and now, I'm getting this error:
Windows failed to start. A recent hardware or software change might be the cause. To fix the problem:
1. insert your windows installation disk and restart your computer
2. choose your language, and then click "Next"
3. Click "Repair your computer"
If you do not have this disc, contact your system administrator or computer manufacturer for assistance.
File: \Boot\BCD
Status: 0xc0000098
Info: The windows Boot Configuration Data file does not contain a valid OS entry.
I know that usually when I'm getting this message, it means that a previous MDT installation was started and did not finished correctly, and the are some [stuff] on the HD, so i do a partition erase and start over and all working fine.
Now it's not working. I tried several computer, even new ones, and NADA.
someone know the cause?
I know I read something, i don't remember where or how to find it, that when doing the steps I did, it alter\change some ini or xml, or something like this. is that true? any one know on what file do i need to look and see if something is misconfigured?
thanks a lot for your help

hello,
i installed WDS+MDT for OS deployment. all was working fine.
Now i need our branch office to be able to deploy OS as well.
I installed a new Win 2008R2 server, and installed the WDS service on it.
When reading about this on the internet i saw i need, on the MDT at our main office, to make a link, under "Advanced Configuration" - "Linked Deployment Shares" to the new WDS server (I used this: http://www.balm.se/?p=115")
when doing so i entered the UNC path to the new server and then, on the created link, i right click and choose "Replicate now".
after doing so, i tried booting a laptop just to see if there is any impact, and now, I'm getting this error:
Windows failed to start. A recent hardware or software change might be the cause. To fix the problem:
1. insert your windows installation disk and restart your computer
2. choose your language, and then click "Next"
3. Click "Repair your computer"
If you do not have this disc, contact your system administrator or computer manufacturer for assistance.
File: \Boot\BCD
Status: 0xc0000098
Info: The windows Boot Configuration Data file does not contain a valid OS entry.
I know that usually when I'm getting this message, it means that a previous MDT installation was started and did not finished correctly, and the are some [stuff] on the HD, so i do a partition erase and start over and all working fine.
Now it's not working. I tried several computer, even new ones, and NADA.
someone know the cause?
I know I read something, i don't remember where or how to find it, that when doing the steps I did, it alter\change some ini or xml, or something like this. is that true? any one know on what file do i need to look and see if something is misconfigured?
thanks a lot for your help
For a branch solution I would use DFS(R) rather than linked deploymentshares.
If there is infrastructure at the remote sites you could use the MDT environment at your main site, and then at each other site use an existing server or build a new server (VM is available). Create a Deploymentshare on each sever
and copy the contents of the MDT environment from the first site into this share. Next you will have to add the WDS service to each site's server. For WDS add the boot image. Of course as Keith noted ensure that you
have the same versions of MDT and the WAIK/ADK on all systems
You can use DFS to replicate to all of the other sites, but you will still have to create a deploymentshare, and install WDS at each site. So each site talks to its own WDS server you can use the DefaultGateway parameter instead -
[Settings]
Priority=Default, DefaultGateway
[Default]
SkipBDDWelcome=YES
[DefaultGateway]
192.168.10.1=Bergen
192.168.20.1=Oslo
[Bergen]
DeployRoot=\\MDT-Bergen\DeploymentShare$
[Oslo]
DeployRoot=\\MDT-Oslo\DeploymentShare$
If this post is helpful please click "Mark for answer", thanks! Kind regards

Windows Boot Manager

Hello all Support Team,
i Have some problem want to know reason and fix it, please help me.
i'm used the HP ProBook 440 G1. My problem is :
1.When i install OS win7 by disc from Microsoft, after first install complete it's reboot and black screen appear with one option to chose is " Windows 7 install [EMS Enable]". I provisional accept the solution from my friend but i still want to know what reason of this issue.
If choose that without remove disc, the laptop will restart and progress installed windows start again from beginning.
If choose that with remove disc, the laptop start to windows normal and everything maybe is fine ( this is my friend's solution).
2.When I reboot this laptop, the screen "Windows boot manager" appear, even only one option to chose is Window 7, then I check in "Boots" by open msconfig, I see only one OS and it's already default OS. But every time I restart the laptop the screen "Windows Boot Manager" always appear, how can i remove this screen and take my laptop enter directly to window ?
That's all my ploblem, please help me fix it.
Thanks and Best Regards,
Katori.

Remove the disk unless you want to install Windows.
"When I reboot this laptop, the screen "Windows boot manager" appear, even only one option to chose is Window 7, then I check in "Boots" by open msconfig, I see only one OS and it's already default OS. But every time I restart the laptop the screen "Windows Boot Manager" always appear, how can i remove this screen and take my laptop enter directly to window ?"
If you remove the password you are using, then the notebook will boot right into the operating system. That is not a good practice as there is no security at all.
****Please click on Accept As Solution if a suggestion solves your problem. It helps others facing the same problem to find a solution easily****
2015 Microsoft MVP - Windows Experience Consumer

Keyboard in a Windows boot partition.

I have a windows boot partition. Can I use my wireless keyboard in this environment? Is there a place to download drivers or whatever? Alternatively, is there a USB keyboard or whatever I can buy to work with my iMac in this partition environment?

Penguin555 wrote:
Penguin555 wrote:
where can I get windows 7 keyboard and mouse drivers for bootcamp?
I have installed Windows 7 in a boot camp partition. I can only use usb keyboard and mouse by booting Windows intyo safe mode, and I am totally unable to use my Apple wireless keyboard and mouse. How do I resolve this?
I'm running Lion - 10.7.2. Boot Camp Assistant fails to download drivers - that issue has been going on for some time, and has been reported by others as well.
But that answers your question. You get the drivers by using BCA to download them. Your inability to download the drivers is a separate issue than not being able to use your wireless keyboard.
While some people may have issues downloading the drivers, many others have successfully downloaded the drivers. I have downloaded them fine on several different Macs. It may take a long time, depending on the speed of your internet connection. Mine took over 3 hours.
Regardless, you need to download the drivers using Boot Camp Assistant. Try again, and if you still have problems, start a new thread and provide as much details as possible to describe what your seeing so that we don't have to go through this back-and-fourth, and you'll get your answer quicker.

After restore windows boot manager says windows failed to start. CQ57 notebook

Had a problem with the FBI scareware. Took it to a cmputer repair place. They wanted $250 to fix it and now it won't boot up at all. It did the HP system restore but when it rebooted the Windows Boot Manager says "Windows failed to start". It wants an installation disc. THen :
File: \Boot\BCD
Status: 0xc000000f
Info: An error occurred while attempting to read the boot configuration data.
Is it trying to boot from the wrong partition?

Enter BIOS setup by tapping/holding the F10 key immediately after powering on the laptop.Use Diagnostics to test your hdd.
If you haven't burned a Recovery Disk set, phone HP to order one.Usually around $17. Choose your country here>> Contact HP
******Clicking the Thumbs-Up button is a way to say -Thanks!.******
**Click Accept as Solution on a Reply that solves your issue to help others**

[SBS 2011] USB drive 3 TB and Windows Boot

Attached new USB drive to the SBS server. The previous one, 2 TB, died. This one is 3 TB. When I reboot the server, I see the message 'Windows is starting' briefly and then it halts with an error. Can't make a screenshot, but it's something with UEFI
boot. Didn't know what caused this, so I tried starting Windows in safe mode. Same error. O dear. What has changed recently... ah, them USB drive. Unhooked it from the server and Windows booted just fine.
I didn't have this problem with the previous USB drive. The BIOS / UEFI setup of the server is set to boot from harddisk, then CD/DVD. The USB drive isn't coming into play at the boot stage. And it doesn't since I briefly see the message 'Windows starting'.
When Windows starts, it somehow does something to the USB drive and then decides it can't start. How do I prevent Windows from checking them USB drive at startup?
Simon

None of them answers are correct. I don't use the drive for Windows Backup. Tested the drive and it's OK. I rebooted the machine so I could create a screenshot. When Windows starts, it displays the text "Windows is loading files...."
and a progress bar at the bottom of the screen. When that bar is full, the machine stops with an error. It looks like this error is triggered by the BIOS, since it displays:
BIOS rev 2.3.3
A system restart is required.
The system detected an exception during the UEFI pre-boot environment.
Press Enter on the Serial Console for detailed exception info.
Type: General Protection Fault (13) Source: Software (UEFI0011)
Then a bunch of numbers and the line:
-->rip C023D04C bootmgfw.efi <--Crash occurred here
Reading this, I wonder if it's a Windows problem or some BIOS / UEFI thing?
Simon

Windows Boot failure

1) HP Pavilion g6-1b67 cl Notebook PC
2) Windows 7
3) "An error occurred while attempting to read the boot configuration data"
4) Stored all information on a USB Flashdrive before wiping computer.
5) Laptop experienced repeated crashes: Went to blue screen and restarted or the computer would simply stop responding and then restart itself. In the most recent instance of this, I was taken to an HP restart screen or something along those lines. I was given about 6 options for what to do. 3 were under immediate help. The first said something along the lines of "load from a previous date" and that had worked when this happened opnce before so I gave that a try again, but it said there were no previous dates to load from. So I backed up my files on a flashdrive and chose the third option which was to restore the computer to factory settings, thinking this would load everything how it was when I first got it. I was dismayed when I turned the PC back on after the process completed and saw the windows boot manager come up. It looks like this:
"Windows failed to start. A recent hardware or software change might be the cause. To fix the problem:
1. Insert your Windows installation disc and restart your computer.
2. Choose your language settings and then click next.
3. click "repair your computer"
If you do not have this disc, contact your system administrator or computer manufacturer for assistance.
File: \Boot\BCD
Status:0xc0000225
info: an error occurred while attempting to read the boot configuration data."
then it says i can press enter to continue or esc to exit, both of which take me back to this screen after the hp logo flashes and the option comes up for the startup menu.
Please help me out, i cant afford to lose another laptop, im a college student so this is vital to me right now.
Thank you,
Josh

please run sytem daignostics in start up menu to check if there are any Hardware problem.
it seems that you need to run system recovery to bring it back to its default settings
▬JM▬

Whatever I do I'm entering windows boot menu

Similar Messages

Maybe you are looking for