EFI Update v2.6 breaks Windows dual boot

The EFI Update MBA51.00EF.B02 has broken WIndows on my MacBook Air 2012
Bootcamp Dual boot using OSX Lion & WIndows 7 was working fine prior to the EFI update.
Since then, the WIndows initial boot screen displays, but as soon as the GUI starts there is a blank notebook screen.
Using an external monitor connected via Thunderbolt > VGA adapter, the Windows GUI Logon & desktop shows on the external monitor, but Control Panel display manager cannot see the MBA own lcd screen as a display option.
This makes it unusable as a portable WIndows M/C, as instead of fixing WIndows it has broken it.
Can I regress ?
Is there a fix to this issue ?
Please Help

vintherine wrote:
the.ridikulus.rat wrote:
@vintherine: Everything you mentioned in the 1st post is correct. In your case the correct commands should be:
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=arch_grub --recheck
grub-mkconfig -o /boot/grub/grub.cfg
Thanks. I've tried that, get now a single line with Windows, which does not work
EDIT: Are you able to boot Windows independent of GRUB, ie. directly from the firmware boot menu?
I've tried F12 key, found a menu, started on the HD, found a new menu corresponding with the EFI directories (arch_grub, Microsoft....). Microsoft entry sent me on... grub menu
EDIT: Can you try (note the extra line : "set gfxpayload=keep")
It's time for diner (i'm in France). I'll see this in the next hour.
Many thanks
Seems like the actual Windows bootmgfw.efi was overwritten by grubx64.efi or something else. In the boot menu Windows's entry (created by Windows installer) is usually titled "Windows Boot Manager".
EDIT:
Try this. Copy the files from Windows's C:\Windows\Boot\EFI to <EFISYS>/EFI/Microsoft/Boot/ . Overwrite any exisitng files, and make sure <EFISYS>/EFI/Microsoft/Boot/BCD file exists. That is the Windows equivalent of grub.cfg (although BCD cannot be read easily since it is not a text file). Try your menuentry again.
Last edited by the.ridikulus.rat (2013-09-27 18:29:09)

Similar Messages

Upgrading to lion: concern currently i amMac OS X 10.6.8 (10K549) with a windows dual boot (boot camp)

Upgrading to lion: concern currently i am running Mac OS X 10.6.8 (10K549) with a windows dual boot (boot camp) on a imac, hardward configuration is good. my question is if i upgrade to lion will it effect my boot camp windows environment in any manner shape or form or will it stay pristine and I will be able to access it with no problem. as for the upgrade does it give you a clean install and upgrade options
any insight would be appreciated.
Also has anyone, added another partition and installed lion in their leaving the snow leopard partion intact.

I would ask myself these questions first
What features am I hoping to benefit from by upgrading?
What apps do I have on OSX that I need to still fucntion? (research that they will)
Just a cautionary note - I have had problems, but only upgraded to see what was new - needed nothing, lost a lot

EFI partition deleted after removal of dual boot of OSX10.8 and Ubuntu/Linux Mint - using rEFIt

so, i recently installed ubuntu to check out the advances in the linux world since i last looked into them 10+ years ago... very impressed, but when i tried to delete ubuntu and remove the various partitions (which i was able to do just fine using gparted) reFIT still displayed the **** linux logo from the install i deleted....
OSX still boots fine... a install of Linux Mint i have on another partition(s) still boots fine ... everything appears to work... but i want to know what the possible issues are so i can be prepared...
this is frustrating...
so i went in and looked around with the remaining partitions and noticed the EFI partition which hadn't shown before i mistakenly tried to install another distro over ubuntu after wiping the partition it was on...
so i erased the EFI partition hoping that this would remove the g-damned hold out linux boot logo in reFIT... it didn't... now i suppose i can go back in and create a new EFI partition through gparted but that stupid linux logo will still be there... and i'll have another problem of getting the proper information back onto the EFI partition, which i am unsure of how to do, or where to even dig up the proper information...
i want to edit my boot mbr or grub or whatever the eff apple comps use as a boot record so that (or i am using as a boot record since i'm using reFIT) to get rid of this **** logo, so i can install another distro of linux and probably windows without having the **** supernumerary logo...
i would rather not wipe the whole drive (aka the primary partition the recovery partition) and do a fresh new install of os x (mountain lion) because i have OSX set up just the way i want it for personal use and work use... all my various tools and so on...
i don't use time machine and can't do a "restore" from a previous back up...
some one please help me out here, what are my options? am i going to have to bite the bullet and do a wipe of the entire drive and all its partitions to get my MBP back to 'normal'???
PS - using a macbook pro late 2011, standard specs, 13"...

stqn wrote:
Expi1 wrote:Thanks, I'm mostly struggling with how to partition for Arch and then how to do the bootloader. I'm using Win8 64-bit and from what I understand a Legacy BIOS bootloader. I'm not entirely sure what I should be partitioning the C: into, I've done partitions before, just not for Arch and then I'm not sure whether to use GRUB or syslinux, or if I even need those. Or if I need to use GPT or MBR?
Your disk is already partitionned so you don’t have to choose between GPT or MBR, the choice is already made.
You don’t partition “C:”, that is the name of a Windows partition. You partition a drive.
Grub or syslinux, use whatever the beginners guide tells you to. Personally I think syslinux is simpler which is why I’m using it (but I’m not dual-booting, if that matters).
You’re not saying what your problem is with partitionning, so it’s hard to help.
Thanks for getting back to me, I'm not sure if I just create one large partition for Archlinux or if I have to create multiple? Where I'm also confused is with the Creating Filesystems part of the guide. I don't understand how I'd do this in Windows, or what /dev/sda1 is referring to.
As for the bootloader part, the Beginner's Guide gives you a choice between syslinux and grub, what I'm not sure about is which to use considering I'm dualbooting. How it will affect my windows bootloader, do I disregard that and use GRUB now? I'm unclear on how that works.
I'm also aware I need to disable Secure Boot, I just searched my BIOS options and couldn't find anything remotely relating to that, so I'm assuming it's not an issue since this computer was originally on Windows 7 anyway?
Thanks again, Expi.
Last edited by Expi1 (2014-03-06 19:54:30)

WLAN module is sleeping from Windows Dual boot cannot Install

Hi I'm having problems installing from the Core installation disk due to Windows 7 or the Windows 7 Wifi driver for my computer shutting off the Wifi module when it restarts or powers off. I was wondering if anybody had any idea about that if so. How do I wake WLAN in Linux Dual-boot so I can have wireless internet access in Linux. I run an ASUS Laptop. My wifi driver is a Ralink 80211n Network adapter.

This is possibly due to windows having trouble to establish a wireless connection, then it shuts down the wireless card to save power.
Unfortunately on some systems, bios/efi doesn't re-enable the card at next boot.
I've encountered cases where the card stayed disabled, and the only way to get it back was use the network troubleshooter to get it activated gain.
That trick however only worked until windows lost wireless connection for whatever reason.
The only way to solve this permanently if found is to deny windows the option to shut down the wireless card at all.
To make this work however you need to change the wireless adapter settings :
In windows configuration panel, look for 'device management'.
In the tree, select the physical wireless adapter, choose properties .
you should see 4 tabs then, one of them (think it's called driver details) allows you to set many driver settings.
Look for an option called something like : "windows is allowed to shut down this device to save power" and disable it.
Edit : tried to make it more readable
Last edited by Lone_Wolf (2013-09-01 12:57:29)

T400s Linux/Windows dual boot with Linux from Esata Flash Drive

This project is about a dual boot Windows/Linux system without using the normal dual boot changes in the bootloader of the windows hard drive. When I started this I found bits and pieces of information on the web but no complete description so I wrote this post.
I have done a dual boot system on my previous Thinkpad where I had partitioned the hard drive between Linux and windows. For this project I wanted to leave the windows hard drive absolutely intact and unaltered, and boot Linux from a flash drive in the esata port on the back of the T400s. Obviously this uses the F12 boot list function key to boot from the flash. The advantage of this is that Windows is totally unaltered and when I need Linux, I plug in the esata flash drive, hit F12 during the boot cycle and select booting from the esata flash drive. The reason for Esata rather than USB is simply speed. I have a nice fast Linux installation.
I used the OCZ esata flash drive but suspect any of the alternatives will work. It did not need the accessory usb cable because the Thinkpad powered the esata flash directly.
To boot from the esata drive I had to make the following changes in the bios
    I left the esata flash plugged in as I went into the bios
    Bios>config>Serial ATA and changed the Sata controller mode option to compatibility
    Restart and back into the Bios
    Bios>startup>boot - in my case the esata flash drive showed up as ATA HDD2 and was excluded from the boot order so I had to un-exclude it and move it to the point in the boot order that I wanted.
Next I downloaded a linux installation iso and put it on a CD - in my case opensuse. Then booted from the CD
From now on this instructions are specific to opensuse and yast but can be generalized to whatever Linux is being used.
In my case yast came up with a good set of suggestions for automatically partitioning the flash drive but then crashed during the partitioning itself. So I rebooted and specified the partitions manually.
    A fat32 partition left as a partition which both windows and Linux could see (in my case about 20% of the drive) (/dev/sdb1)
    An extended partition with the remainder of the drive (/dev/sdb2) which contains the following logical partitions
    A linux Swap partition of 2GB (/dev/sdb5)
    A linux /home partition –the remainder of the drive (/dev/sdb6)
    A linux /root partition of 8GB (/dev/sdb7)
Yast automatically suggested mount points of C,D,E for the windows partitions. Unfortunately because of the way the Thinkpad hard drive was laid out Yast had C assigned the ThinkPad Service partition and D assigned to the SW_Preload (or main windows partition). However there was an edit function that allows for the reversal of those mount points so that the windows C drive is mounted in Linux as Windows/C thereby avoiding confusion. I had already backed up and removed the Thinkpad factory install data so I did not have to deal with that. Yast suggested Windows/E for the mount point of the FAT32 partition on the flash drive, which I accepted.
The yast install configurator made all this manual selection easy, and after the manual configuration the partitioning worked perfectly.
Next step was Linux user configuration which went fine
Next was booting.
In the section management tab
    delete the windows 1 and 2 options (since we are not dual booting directly)
In the boot loader installation tab
    uncheck boot from mbr ( this stops the install from installing Grub and dual boot on the windows c drive
    check boot from root partition (this installs grub and all associated files in the Linux root partition (/dev/sdb6)
I believe that the correct procedure at this point is to click Boot Loader installation details which will bring up the Grub device map. In the device map there will be a line for the fixed hard drive (aka the windows drive) and a line for the esata flash drive. When the installer started up these were in hard drive and esata drive order. However when we boot directly from the flash the esata drive will be grub drive hd0 and the fixed hard drive will be grub hd1. The device map order needs to be changed to reflect this ie the esata drive should be first not second.
I did not do this and ended up initially doing Grub command line editing to boot and later manually editing the grub files using information I had previously learned the hard way and through google.
At this point let the installer go ahead and install Linux. After doing this it should come back and tell you to reboot. Do not do it yet because we need to install the MBR into the flash drive.
I suspect that there is a way of doing this in Yast running from the Live CD but it was not obvious to me so I used the manual method that I have used before.
Open a root terminal
Mount /dev/sdb6 to /mnt/sdb6 (my linux root)
Touch /mnt/sdb6/boot/grub/flag
The purpose of this is when we go looking later at the grub command prompt we need an easy to find unique file
Start grub and do the following
#grub
            grub> find /boot/grub/flag
                (hd1,5)    -- the result of the find in my example
            grub> root (hd1,5)   -- using the result of the find in my example
            grub> setup (hd1)   -- install mbr -- my example parameters - if you get this wrong you will trash some other drive!!!
                  hopefully grub announces success
            grub> quit
Reboot and select the flash drive. In my case I still had the grub devicemap wrong and had to edit the grub commands during boot to tell grub how to find the correct partition and then edit them again after booting
Typical linux install issues that we all always seem to have and can be solved with a little (or a lot of) google research.
As I said at the beginning I now have an untouched windows installation and a nice fast Linux installation. I hope that this will be of some use to someone.

Hi chrissh
i tried this exact procedure... on the exact same notebook (T400s). However, as soon as I set the
   Bios>config>Serial ATA to "compatibility", I cannot use my default Windows installation! I immediately get the "blue screen of death".
I doubt I did anything differently since this is the first step of your procedure and my laptop is brand new!
any idea?

[SOLVED]Windows dual boot

Here's my fdisk -l
Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x495d01ab
Device Boot Start End Blocks Id System
/dev/sda1 * 1 3060 24579418+ 7 HPFS/NTFS
/dev/sda2 3061 4365 10482412+ 7 HPFS/NTFS
/dev/sda3 4366 16832 100141177+ 83 Linux
/dev/sda4 16833 19457 21085312+ 5 Extended
/dev/sda5 16833 18137 10482381 83 Linux
/dev/sda6 18138 18790 5245191 83 Linux
/dev/sda7 18791 19312 4192933+ 83 Linux
/dev/sda8 19313 19326 112423+ 83 Linux
/dev/sda9 19327 19457 1052226 82 Linux swap / Solaris
and here's my menu.lst
# Config file for GRUB - The GNU GRand Unified Bootloader
# /boot/grub/menu.lst
# DEVICE NAME CONVERSIONS
# Linux Grub
# /dev/fd0 (fd0)
# /dev/hda (hd0)
# /dev/hdb2 (hd1,1)
# /dev/hda3 (hd0,2)
# FRAMEBUFFER RESOLUTION SETTINGS
# +-------------------------------------------------+
# | 640x480 800x600 1024x768 1280x1024
# ----+--------------------------------------------
# 256 | 0x301=769 0x303=771 0x305=773 0x307=775
# 32K | 0x310=784 0x313=787 0x316=790 0x319=793
# 64K | 0x311=785 0x314=788 0x317=791 0x31A=794
# 16M | 0x312=786 0x315=789 0x318=792 0x31B=795
# +-------------------------------------------------+
# general configuration:
timeout 5
default 0
color light-blue/black light-cyan/blue
# boot sections follow
# each is implicitly numbered from 0 in the order of appearance below
# TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
# (0) Arch Linux
title Arch Linux
root (hd0,7)
kernel /vmlinuz26 root=/dev/disk/by-uuid/e20fd940-03ae-48c4-a666-790e9be9e5d5 ro vga=792
initrd /kernel26.img
# (1) Arch Linux
title Arch Linux Fallback
root (hd0,7)
kernel /vmlinuz26 root=/dev/disk/by-uuid/e20fd940-03ae-48c4-a666-790e9be9e5d5 ro vga=792
initrd /kernel26-fallback.img
# (2) Windows Vista
title Windows Vista
rootnoverify (hd0,0)
makeactive
chainloader +1
Yet when I select Vista from the grub, all I get is an error saying that my windows boot manager needs to be fixed and I should put in my Windows CD etc....
I want the grub to be in the MBR...I just need to be able to access the Windows OS as well. Is there something wrong in my menu.lst file ?
Last edited by Inxsible (2009-02-13 07:33:36)

Funny, I have an HP Laptop that dual-boots Vista and Arch x86_64. I don't seem to recall having a problem. I installed Vista first (system restore disk <yech!>), then used gparted to resize the Vista partition, then did a standard Arch install.
# cat /boot/grub/menu.lst
default 0
timeout 30
color light-gray/black light-gray/blue
title Arch Linux
root (hd0,5)
kernel /boot/vmlinuz26 root=/dev/disk/by-uuid/fbece3b5-a239-4f40-91b6-d82986108e2d ro
initrd /boot/kernel26.img
title Arch Linux Fallback
root (hd0,5)
kernel /boot/vmlinuz26 root=/dev/disk/by-uuid/fbece3b5-a239-4f40-91b6-d82986108e2d ro
initrd /boot/kernel26-fallback.img
title Windows
root (hd0,0)
chainloader +1
makeactive
# fdisk -l /dev/sda
Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x9c5a55bb
Device Boot Start End Blocks Id System
/dev/sda1 * 1 6374 51199123+ 7 HPFS/NTFS
/dev/sda2 18396 19457 8522752 7 HPFS/NTFS
/dev/sda3 6375 18395 96558682+ 5 Extended
/dev/sda5 6375 6501 1020096 82 Linux swap / Solaris
/dev/sda6 6502 9051 20482843+ 83 Linux
/dev/sda7 9052 18395 75055648+ 83 Linux
Partition table entries are not in disk order
I'd be happy to send you any parts of my laptop configuration that might help.
Last edited by airman99 (2008-12-24 14:19:52)

Re: Windows dual-boot

Hi,
I have Windows Vista on my laptop that not longer available after Xp instalaltion. I want to have dual-boot Vista with Xp. How to do it? Do I have reinstall Vista?
Any help appreciated.
Thanks

Hi,
Recommended to install Windows Xp before Vista. Because, Windows Xp erases the Vista bootloader, therefore, you need to recover it. Recovering isn't complicated procedure.
I think the steps bellow will assist you:
1. Boot up the Windows Xp, Insert Windows Vista disk, find the bootsect.exe ? in the ,,BOOT,, folder. Get know the path to bootsect.exe. For example: F:\boot\bootsect.exe where F is dvd drive.
2 Run Command prompt and type in
F:\boot\bootsect.exe /nt60 all press Enter
Now, the bootsect.exe is recovered. but it's still not avalible in boot selection menu
3 Type in
Bcdedit /create {ntldr} /d "Microsoft Windows XP" press Enter
Bcdedit /set {ntldr} description "Microsoft Windows XP" press Enter
Bcdedit /set {ntldr} device partition=C: press Enter
Bcdedit /set {ntldr} path \ntldr press Enter
Bcdedit /displayorder {ntldr} /addlast press Enter
That's all. Note, if you want to change the OS boot up timeout in selection menu, you can type in:
Bcdedit /timeout XX where XX is timeout, for example 10 sec instead of 30 sec by default.

How to run solaris 10 and windows, dual booting.

I installed solaris 10 first and then windows 2000 on my celeron pc. Nopw every time i start pc, it starts windows, coz of windows mbr.
how to set at startup before booting the option which ask for solaris or windows? suggest me a easy way as i am a new user of solaris.

The procedure to reinstall the Solaris boot sector
(along with lots of info on dual booting) can be
found here: http://multiboot.solaris-x86.org
Another approach is to use the Windows 2000/XP boot
menu. Assuming your S10 DVD is on D:\, type at a
command prompt:
copy
d:\Solaris_10\Tools\Boot\usr\lib\fs\ufs\mboot
c:\bootsect.solThen add the following line at the end of the
C:\boot.ini file:
C:\bootsect.sol="Solaris"(google "boot.ini" for more info on the above)
Now Windows will display a boot menu where you can
choose between Win2K and Solaris.
BlaiseThe menu appears as you mentioned but there is another problem it tells me that there is no active partitions.
i have to hards in my system, and it seems i screwed the booting thing during installation since this is the first time i install solaris.
regards
firas nemer

[SOLVED] Dual Boot Window 7 & Arch on a Uefi system.

From the Wiki
Windows 7 x86_64 versions support booting in x86_64 UEFI mode from GPT disk only, OR in BIOS mode from MBR/msdos disk only. They do not support IA32 (x86 32-bit) UEFI boot from GPT/MBR disk, x86_64 UEFI boot from MBR/msdos disk, or BIOS boot from GPT disk.
I don't understand this. As stated in the title I have a ueif system so that means I have to create a GPT disk ? I already have a gpt disk which I confirmed by running Arch Live USB. Under type it said GPT. I don't understand this at all
However if Arch is installed in BIOS-GPT in one disk and Windows is installed in BIOS-MBR mode in another disk, then the BIOS bootloader used by Arch CAN boot the Windows in the other disk, if the bootloader itself has the ability to chainload from another disk.
Note: If Arch and Windows are dual-booting from same disk, then Arch SHOULD follow the same firmware boot mode and partitioning combination used by the installed Windows in the disk.
In the Note above it says both Arch and Windows follow the same boot mode if they are dual booting from same disk. I DO NOT want to do this. I have already decided to partition my drive with 200 Gb going to Windows and 500 Gb going to Arch. Does this mean that I should install both in different modes i.e. Arch in Bios-GPT and Windows in Bios-MBR.
The recommended way to setup a Linux/Windows dual booting system is to first install Windows, only using part of the disk for its partitions. When you have finished the Windows setup, boot into the Linux install environment where you can create additional partitions for Linux while leaving the existing Windows partitions untouched.
UEFI systems
Both Gummiboot and rEFInd autodetect Windows Boot Manager \EFI\Microsoft\Boot\bootmgfw.efi and show it in their boot menu, so there is no manual config required.
For GRUB(2) follow GRUB#Windows_Installed_in_UEFI-GPT_Mode_menu_entry.
Syslinux (as of version 6.02 and 6.03-pre9) and ELILO do not support chainloading other EFI applications, so they cannot be used to chainload \EFI\Microsoft\Boot\bootmgfw.efi .
Computers that come with newer versions of Windows often have secure boot enabled. You will need to take extra steps to either disable secure boot or to make your installation media compatible with secure boot.
Being a beginner should I go with Gummiboot then. GRUB made a mess last time.
Also my secure boot is NOT enabled so is that good.
I have read the FAQs, Beginner's guide, Installation Guide, Dual Boot wiki entry but I just don't understand the above concepts. But it looks this this is the main thing in dual booting. Almost everything else is doable but this I have to get right on account of what happened the last time I installed Arch without getting the above right.
Last edited by Some Arch Lovin (2014-06-14 08:53:14)

A few issues with the dual boot setup
Hello again, I lost my dual factor authentication grid from lastpass. Opensuse was acutally overwriting new pdf files over my old pdf files so now that grid pdf is actually an Arch cheat cheet with the name last_pass_grid.pdf. And the gmail account I used to register to Arch forums is also in last pass.
This is why I created another account. I am some arch lovin.
The installation went smoothly but I could not dual boot Windows7 with Arch because my Win7 image is not UEFI bootable so had to dual boot win8(not a fan at all) and arch.
Almost everything is working correctly. I have a few issues that aren't affecting how the system is working but they still need sorting out.
I'll do them one at a time but I want to know from the admins if I should start a new thread? Because in a way this thread accomplished it job i.e. win7 and arch dual booting in uefi system.
If the answer is yes I should create a new thread depending upon the issue then I will do that but in case its a no since I have only 2-3 problems I am going to ask help for the first one.
My gummiboot is not working on startup. I have to press f12 and use bios booting menu to boot. The problem with that is if I put Windows at the top of the boot priority the bios does not show F12 and F2 at the time of booting up so I can't access the boot menu. I have to boot into Windows and crash it by holding the power button and then the F12 options shows up and I am able to boot into Arch. If I put Arch at the top then Windows keeps restoring back to an earlier version due to start up options.
NOTE : I can't be sure but one it did work(only once). I checked the images online to compare with what I saw and its very similar. An all black screen with three bootloading options
Windows
Arch
Opensuse(don't know why I created a completely new GPT partition table)
This is what I did while installing Gummiboot
# mount -t efivarfs efivarfs /sys/firmware/efi/efivars
# pacman -S gummiboot
# gummiboot install
I tried going through the gummiboot to see if I can do something but it very difficult to comprehend as a beginner. All I get is the characters gummiboot understands but thats all.
Last edited by Archer61 (2014-06-11 13:48:56)

[SOLVED] How to dual boot windows on separate drive with syslinux

I'm trying to follow the directions from the arch syslinux wiki to add a windows dual boot option to my current syslinux.
I have two hard drives: sda (windows MBR) and sdc (arch linux GPT). My BIOS is set to boot sdc, and syslinux is currently installed fine to boot arch linux off of sdc. I would like to add an entry to boot windows.
I added an entry to /boot/syslinux/syslinux.cfg that looks like
LABEL windows
MENU LABEL Windows
COM32 chain.c32
APPEND mbr:0xf00f1fd3 # my actual identifier for sda from fdisk is here
When I rebooted, I saw the new entry in the syslinux menu. When I went to arch linux, it booted fine. When I rebooted again and selected windows, it hung with a blinking underscore. The next time I rebooted, it didn't even get to the syslinux menu and just hung with a blinking underscore.
I booted from my rescue arch usb drive. In fdisk, sdc's partition table now mirrored sda's! In other words, it looked like I had windows partitions on my linux drive, and it had the same MBR identifier even though it was supposed to be GPT. I ran gdisk /dev/sdc, it detected both GPT and MBR, and I asked it to use the GPT table and wrote out the partitions, and my drive looked normal again. I ran arch-chroot, syslinux-install_update, and everything was fine the next time I booted.
Any advice on how I can set up windows dual boot with syslinux?
Last edited by mikemintz (2013-08-17 18:25:46)

I am assuming that you use Bios and not UEFI (I am not that quite familiar with UEFI).
1) You must configure the Bios to boot from the disk where syslinux is installed, having a correct mbr and with syslinux correctly installed.
2) The disk where windows reside must be bootable by itself with a valid mbr.
It may be possible that windows try to boot from the linux disk (and of course fails), try to add the swap option to the chain command.
To check if Windows is correctly installed, try to boot it directly from the Bios.
The mbr of the syslinux disk should be gptmbr.bin:
dd if=/usr/lib/syslinux/gptmbr.bin of=/dev/sd<letter of the linux disk> bs=440 count=1
Warning: Be very careful with what you do with dd, it is very easy to destroy all your data!
Last edited by olive (2013-08-17 08:31:44)

Windows steals boot flag in dual boot

I have installed windows on sda1, boot on sda2, mostly replicating what is suggested in the windows dual boot article. On arch setup, I flag 2 as bootable and 1 as not bootable. However, when windows runs, it flags sda1 as bootable and the next time I restart, I go immediately into windows. Is there a way to stop windows from doing this outside of windows OS?

Like jowilkin said, the bootable flag does not matter as long as Windows can boot its ok to leave it as it is.
When you are dual booting with Windows, its easier to have grub installed to the MBR so that it overwrites Windows' bootloader. Grub can boot to just about anything.

MacBook Pro Retina EFI Update 1.0 taking a long time

Does the MacBook Pro Retina EFI Update 1.0 take a long time - mine is just saying "Waiting..." after 20 minutes. Updating from the App Store. Thanks

hi, i wasnt able to find the EFI update in my App store. My computer is also MBPro Retina Mid 2012.
would you mind telling me your boot rom version after you successfully installed this EFI updated? (Anyone?)
mine is:
Boot ROM Version: MBP101.00EE.B02
Although i dont remember installing this EFI update. After I installed 10.8.2, i was only able to see the iphoto update, and
after that, nothing. Until now, there's no update from App Store.

[SOLVED] Dual boot with Windows 8, problems after updating Windows

Hi all,
I have been maintaining a dual boot of arch and Windows 8 for some time. I recently updated Windows to 8.1, and found that the update process had two side effects:
1) The update added a new partition in the middle of my file table, so my /etc/fstab which referenced "/dev/sda6" was wrong because that partition is now "/dev/sda7."
2) The default boot device was switched to the Windows Boot Loader instead of grub. But, this is not a problem because I can work around this by using the "Choose boot device" feature of my bios at start up.
So, neither of these problems are critical for me at the moment. I can fix my fstab and just press a hotkey at startup.
EDIT: I have avoided the /etc/fstab issue by referencing my partitions using UUID as specified in https://wiki.archlinux.org/index.php/Fstab.
How do I set the default boot device back to grub? There is some weirdness here, I think windows is using UEFI booting and my grub uses the old booting system.
Last edited by bjmnbraun (2014-05-14 19:00:36)

Rex: I tried that command, got some warning messages regarding blocklists, but no dice.
Loqs: You are right about windows using a ESP and UEFI while my linux is not booting using UEFI. My bios is configured to try "Legacy boot" first before trying UEFI. Getting linux to boot using UEFI seemed like a pain, so...
I went into my BIOS settings and found that the Windows Boot Manager boot device was listed in front of my hard disk (which boots linux). I don't think this used to be the case, so something about the update caused my BIOS to reorder the boot devices (probably because the partitions changed).
Switching my hard disk to be above the Windows Boot Manager in the boot device list now makes me boot into linux by default, and I can boot into windows by pressing a hotkey at bootup and selecting the windows boot manager.

HT3986 i made a dual boot of windows 7 and mac os x lion in my macbook pro .i installed microsoft support software also. now, can i install windows updates? do i turn on the automatic updating of updates?

i made a dual boot of windows 7 and mac os x lion in my macbook pro .i installed m icrosoft support software also. now, can i install windows updates? do i turn on the automatic updating of updates?

yes you need the updates and patches.
Only some of the drivers that Windows will automatically install at times
and always make sure to insure it is using restore points
do all the maintenance andsuch as normal
use MS Security Essentials for AV is really top notch
Clean disk space
Use WinClone new program to inisure you have a restore image

I made a dual boot of windows 7 and mac os x lion in my macbook pro .i installed m icrosoft support software also. now, can i install windows updates? do i turn on the automatic updating of updates? does hot fix of microsoft helps in stop freezing?

i made a dual boot of windows 7 and mac os x lion in my macbook pro .i installed m icrosoft support software also. now, can i install windows updates? do i turn on the automatic updating of updates? does hot fix of microsoft i.e, " support.microsoft.com/kb/979491" helps in stop freezing in dual boot mechanism?

Windows has a software updater built into Windows and when you install the Boot Camp drivers then it will install an Apple software updater also. I believe Windows is set to automatically download and install your updates as does the Apple software Updater. They both will update the individual files it needs to periodically.
"Microsoft updates" and "Windows updates" are basically the same thing in Windows. Are you talking about the "Windows support software" when downloading from Boot Camp Assistant? Apple installs a software updater for it's Boot Camp drivers in Windows 7 so you can do it manually or automatically.
The "Hot Fix" your referring to is only for certain motherboards built from other Windows only computer manufacturers and does NOT pertain to any Apple computers.
If you have a problem with your computer then it's best to ask a specific question so we can help better.

EFI Update v2.6 breaks Windows dual boot

Similar Messages

Maybe you are looking for