Windows boot manager boots almost fully into windows 8 before letting me select windows 7, at which point it reboots my computer

Hi,
I haven't used my slow HDD with windows 7 on it in a while, but today my SDD with windows 8 on it died. I have kept my old OS in a dual boot setup exactly for this rare possibility. I in fact successfully revived my SSD from windows 7.
During the restore procedure I had to boot into both OSes (7 and 8) several times before I managed to get 8 working. I tried a lot of things before one of them struck. (Is that how the phrase goes?
Me Hungary, no good speak English some times...) I am surprised to have found the following unexpected behavior of the new windows 8 branded boot loader:
The new windows boot manager boots almost fully into windows 8 before letting me select an OS.
If I select windows 7, it reboots my computer and loads windows 7, wasting a lot of time... on the windows 8 portion of the boot process, which is simply thrown away if I happen need windows 7 and not 8.
"This is highly inefficient!" — I almost exclaimed aloud... A boot manager should load just enough of itself so that a simple OS selection menu can be presented to the user with minimal keyboard interaction. Only when a selection is made should
it load an OS. I have no use for the new boot manager's mouse control support, and having it appear on the second screen in my dual screen setup is just plain scary. Use the main laptop monitor where the BIOS messages were displaying, and keep the secondary
off until the OS is done booting! By the time my secondary screen turns on, the boot selection menu disappears anyway.
Yes, I only noticed this problem now because I haven't booted into windows 7 for a long time. (300 MB worth of Windows updates were waiting for me indeed.) My boot selection menu timeout is set to 3 seconds instead of 30 so I don't have to pick windows 8
every time.
I am going to wait at least a week for the forum's input before I switch on my own to a faster, minimalist boot manager. I don't know what to use, I'm familiar with:
some minimalist bootstrap loaders
coreboot/linuxbios (recently learned of it)
bootcamp (not really)
acronis OS selector (discontinued before windows 8 came out, probably doesn't support it)
syslinux/isolinux (Linux only, I think)
old Windows bootmgr
more recent Windows ntldr
then this new "inefficient for dual booting" Windows 8 boot manager
and finally grub
Grub feels like the best option as it keeps the windows boot manager intact and supports mac, windows, and linux. All 3 of which will at one point — or has already — come up as a subject or prerequisite in my university.
I don't know how or why I was able to access windows 8's boot loader while my SSD was dead. Was it installed on the HDD, overwriting the windows 7 boot loader? That too is inefficient. I want to completely boot from my SSD. Don't spin up my HDD while I'm
booting my laptop on the go! The shaking of the vehicle I'm in could seriously damage the disk if I run into a pothole (common in my country) with just the right timing, data could be damaged. The entire reason windows 8 is on an SSD is so that it can boot
without accessing my HDD with all its moving parts. My goal with buying an SSD was for the HDD to remain safely offline while I'm in a shaky environment with potholes! Also, what if I want to disconnect the old HDD in the future... Or what if it dies? Will
the windows 8 boot loader die with windows 7? I want the two kept separately and completely independent from each other for exactly this reason.
In summary:
How can I stop windows 8 from almost fully booting before offering the dual boot OS selection menu? Do I need a better Boot loader?
Why was the boot loader that came with windows 8 still working OK while the SSD with windows 8 on it wasn't accessible? Did it sneak its way onto the old HDD? I want a 100% SSD-based boot process. What is the boot loader doing on a different drive? Its
place is on the SSD, with the operating system it belongs to. Not on the HDD of a different OS. Can I move it?
Sincerely,
Daniel "3ICE" Berezvai
p.s.: For windows 7 I only have a repair disk and hidden RECOVERY partition which I kept (came with the laptop, would rather not use it.) The Windows 8 pro DVD (purchased last year) is fine, but I had it moved to a bootable pendrive so I could remove my
optical drive and replace it with an SSD on which windows 8 is installed now. (I also have a vista ultimate DVD, as they were giving them away for free on a Microsoft conference. Funny story.)
p.p.s.: I am subscribed (☑ Alert me) to this topic and will respond to all questions and try all recommended actions right away.
http://3ice.hu/

Hi,
Thank you for your post.
From your description, I see the issue you are facing is there is no menu to choose OS when booting dual boot(Windows 7 & Windows 8). Please let me know if I have misunderstood anything.
It seems that the Windows 7 entry is missing, currently, we can use a tool –
EasyBCD to get it back. After downloading it, choose the Add/Edit panel item, select the OS you're missing and let the program detect it. Then simply click the Add button to add the missing OS entry.
At the meantime, here is a related link which demonstrates how to keep Windows 7 as the default OS in dual boot, you may use it for a reference.
How to Dual-Boot Windows 8 While Keeping Windows 7 As Your Default OS
http://blog.laptopmag.com/how-to-dual-boot-windows-8-while-keeping-windows-7-as-your-default-os
[Please Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy
of this information.]
Regarding your second questions in your first post, you can refer to the following link to know more about dual boot.
Dual
Booting Explained: How You Can Have Multiple Operating Systems on Your Computer
http://www.howtogeek.com/187789/dual-booting-explained-how-you-can-have-multiple-operating-systems-on-your-computer/
[Please Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy
of this information.]
Hopefully the information is helpful. Please let me know if you have any questions. Thanks for your time.
Best Regards,
Sophia Sun
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.

Similar Messages

  • I just updated firefox TODAY 8/17/11 and after the update i can't open firefox unless i restart my computer or i delete going to windows task manager and process, also i can't open a new window, it won't allow it. please can you help me

    I just updated firefox TODAY 8/17/11 and after the update i can't open firefox unless i restart my computer or i delete firefox going to windows task manager and process, also, i can't open a new window, it won't allow it. please help me, everything works on IE, Google Chrome and Safari, everything went wrong after the update

    Hey Elaine07!
    I have an article here that can help you with that issue. This article will help you make sure you have uninstalled iTunes correctly and help you troubleshoot the launch issues you are seeing:
    iTunes for Windows Vista or Windows 7: Troubleshooting unexpected quits, freezes, or launch issues
    http://support.apple.com/kb/ts1717
    Take care, and thanks for visiting the Apple Support Communities.
    -Braden

  • When I exit Firefox and later load Firefox it says its open, although I can't use, have to go to Windows Task Manager and force it to close before I can load it again.

    Problem is on a Dell Studio XPS desktop with the i7 processor. Current version used is 3.6.13, although the problem occurred with previous version, and only occurs intermittently. Does not seem to be time related. Sometimes, though not always, there will be two copies of Firefox open in the Task Manager "processes". When I close Firefox, and reload, runs fine until the next time.

    https://support.mozilla.com/en-US/kb/Firefox%20hangs (hang-at-exit)

  • 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.

  • Installing Windows 7 using Boot Camp Assistant

    I want to install Windows 7, but my iMac came with Boot Camp 3.0.1. Apple says that I need to update my Boot Camp to 3.1. But when I go to the appropriate support site and download the 3.1 32-bit version, I get a message stating: You have chosen to open BootCamp3.132-bit.exe. Is this the right file? It has an .exe extension and my web browser's download utility (Firefox) doesn't know what to do with this file. Am I doing something wrong?

    Hi,
    I got my first Mac a few weeks ago and I feel into this problem. What you need to do is from your Mac launch Boot Camp Assistant and install Windows 7 (I recommend Windows 7 64bit version) as per the normal Boot Camp process.
    Once you have Windows 7 installed, boot into Windows and then download the latest the Boot Camp Assistant update for Windows i.e. the .exe file you downloaded before, and install on Window 7. Make sure you get the right version as there is a 32bit and 64bit version.
    I short the .exe is only to be installed on your Windows partition and is nothing to do with Boot Camp on your Mac.
    FYI - if like me you find that after a while you have made your Windows partition to big and want to repartition to give some space back to your mac check this Website out - it works a treat, but always remember to backup any data before hand JIC http://www.twocanoes.com/winclone/

  • HP Mini 110-3500 Netbook: How to skip Boot Manager screen when booting into Windows 7 Starter

    Hi,
    As per the topic. I can't seem to deactivate the boot manager screen and it's getting really annoying having to press the enter key each and every time I turn on my netbook.

    First you need to get into the BIOS.  You can accomplish this by holding down the F10 (aka volume up) key located on the top of the keyboard near the right.
    Next hit the right > arrow key (located on the right bottom of the keyboard) 3 times to get you to the System Configuration tab.
    Thirdly, hit the down arrow key (located on the right bottom of the keyboard) 3 times to take you to the Boot Options sub menu and hit Enter
    Hit the down arrow key once to highlight HP Quickweb and hit enter.
    Select Disabled and hit Enter
    Hit F10 (Yes should be selected) and hit Enter
    DONE!!!

  • "Boot Manager failed to find OS loader" - Windows XP

    Hello, I'm new in this community.
    That being said, I have a problem with my Thinkpad SL410. Two nights ago I shut down my laptop. It was working fine at that point. I clicked on shut down, but I think it went to "update and shut down". BAD idea, since now, its stuck on a loop.
    When I try and boot up the laptop, it only brings me to R&R4. Then, after it scans and tries to "fix" the problem, it gives me a message. Unfortunately, the message is in chinese since I bought this laptop in china, so with my rough translation skills, I was able to determine that "Boot Manager failed to find OS loader".
    You would think that that would be easy to fix. I go grab a windows recovery ISO, and put it onto my bootable USB. Problem is, R&R is almost getting in the way of recovery console. When I boot from the usb, there is a black screen with the message "To boot rescue and recovery environment, press f11". I have tried to press f11 and I have tried to wait, but no matter what, it takes me to the thinkvantage rescue and recovery, as opposed to the windows console.
    Essentially, I cannot access the console to type in:
    -fixboot
    -fixmbr
    I have painstakingly translated much of the R&R page (The one that gives you 3 options; restore, backup, reset to factory settings). I don't think there is a way to get to recovery console via that rescue and recovery page. So I do what is most logical. I try and restore to a backup. Technology doesn't seem to like me because after waiting for 30 mins, its at 93% done and there is a message saying something along the lines of "C: doesnt have enough space".
    Great. What other options do I have? I know the hard drive isn't corrupted and my files are still there, since going into "backup" shows me all the files (pictures, documents, etc...). I can't back them all up and factory reset since not only would it take forever, but it would take up wayy too many gigs of space, and I simply can't get my hands on a massive storage system atm.
    This is very frustrating since I only started using this computer after my dell laptop had a hard drive failure. It's a pain trying to get through dell support, only to have my situation a whole lot  more complicated since it was a gift from china, and already registered to someone. Then a perfectly good working computer fails on me again, and this time I can't analyze the problem correctly since the computer is in chinese.
    TL;DR 
    "Boot manager failed to find OS loader error. When I try booting from Windows XP ISO, R&R gets in the way. I also can't do a restore to backup since my C drive apparently doesn't have enough space.

    Hi dizscez, welcome to the forums,
    I can't promise, but something which has worked for me in similar situations is explained in the following KB article. Basically you would be doing the same as running a system restore to a previous point under Windows
    http://forums.lenovo.com/t5/Windows-XP-and-Vista-discussion/XP-System-Restore-When-Normal-And-Safe-M...
    Andy  ______________________________________
    Please remember to come back and mark the post that you feel solved your question as the solution, it earns the member + points
    Did you find a post helpfull? You can thank the member by clicking on the star to the left awarding them Kudos Please add your type, model number and OS to your signature, it helps to help you. Forum Search Option T430 2347-G7U W8 x64, Yoga 10 HD+, Tablet 1838-2BG, T61p 6460-67G W7 x64, T43p 2668-G2G XP, T23 2647-9LG XP, plus a few more. FYI Unsolicited Personal Messages will be ignored.
      Deutsche Community     Comunidad en Español    English Community Русскоязычное Сообщество
    PepperonI blog 

  • SCCM's OSD (not MDT): Task sequence can be tweaked into imaging Windows+VHD Native Boot, but can it go all the way and deploy?

    Hello All,
    What I am trying to do is use SCCM's own OSD Task Sequence / Windows PE to deploy an operating system that boots using VHD Native Boot. (C:\ = VHD File  with Windows, D:\ Data drive with BCDBoot).
    MDT 2013 Can do it I've been told, but I am putting off MDT until Windows 10 if I can get away with it.
    TechNet VHD Native Boot on Windows 8.1:
    http://technet.microsoft.com/en-us/library/hh825689.aspx
    http://technet.microsoft.com/en-us/library/hh825691.aspx
    The good news is it is working up to the "Apply Operating System" phase, but that apply operating system phase is reported as an error even though it completes successfully. It can't clean up the SMSTS folder it's looking for on the C:\ because
    it's been moved over to the D:\ by a diskpart script. We are left with the deployment working but requiring IT staff to deal with the OOBE Personalization wizard and adding each PC to the domain manually. From that point on the SCCM client can do the rest,
    which works for US before we upgrade to Windows 10 with utilizing MDT.
    I am not talking about deploying an OS to a VHD file and putting that file on a network share i.e.
    http://blogs.technet.com/b/configurationmgr/archive/2013/10/31/new-in-system-center-2012-r2-configuration-manager-deploying-an-operating-system-to-a-virtual-hard-drive-vhd.aspx
    I reported getting the diskpart script working first here:
    https://social.technet.microsoft.com/Forums/en-US/ff124f09-1d2e-4fc4-a5b6-63b683f3d208/native-vhd-boot-deployments-from-sccm-2012-r2?forum=configmanagerosd
    Here it is:
    rem work around any USB disk left in or any CDROM detected by PE as drive D
    select volume D
    assign letter=F noerr
    rem select the formatted volume and reassign it's drive letter
    select volume C
    assign letter=D
    rem create and setup VHD file
    create vdisk file=D:\DEV_WIN81.VHD maximum=250000 type=expandable
    select vdisk file=D:\DEV_WIN81.VHD
    attach vdisk
    create partition primary
    active
    format FS=NTFS quick label="Developer Win81 VHD"
    assign letter=C
    rescan
    exit
    (type=fixed is better for performance - we'll surely activate when we have dual boot 8.1 / Windows 10 later for the Win10 VHD's)
    The Task Sequence looks like this:
    I'd like to add a few more steps after apply operating system if I can, but I have to resolve this error with "Apply Operating system before I can go further."
    Question:
    Can an OSD guru tell me if there are any Task Sequence Variables we could throw at this to make the Apply Operating System sequence complete without error so we can do all SCCM OSD Deployment steps?
    If we can, then someone (not me) gets to add a new TechNet blog post about this being possible. It's my understanding presently that only MDT can support deploying WIM files into VHDs on Workstations, that boot them.
    The install image was created using dism to convert a VHD from a Hyper-V host into a wim. I know I'm meant to use SCCM to capture it, but I don't think that's causing this problem because when we are deploying from that image to a HDD without VHD we don't
    get any issues.
    I'm only allowed enough characters to paste the tail end of the apply operating system phase only:
    <![LOG[Execution engine result code: Success (0)]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:929">
    <![LOG[Cleaning Up.]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:675">
    <![LOG[Removing Authenticator]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:686">
    <![LOG[shKey.DeleteValue( c_szRegValue_SecurityToken ), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\ccmutillib\ccmutillib.cpp,1660)]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="ccmutillib.cpp:1660">
    <![LOG[Cleaning up task sequence folder]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="utils.cpp:2329">
    <![LOG[Unable to delete file C:\_SMSTaskSequence\TSEnv.dat (0x80070005). Continuing.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="ccmfile.cpp:1056">
    <![LOG[hr, HRESULT=80070091 (e:\nts_sccm_release\sms\framework\core\ccmcore\ccmfile.cpp,1218)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="ccmfile.cpp:1218">
    <![LOG[Failed to delete directory 'C:\_SMSTaskSequence']LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="2" thread="960" file="ccmfile.cpp:1218">
    <![LOG[(dwRet = ::SetNamedSecurityInfoW ((WCHAR*) pszObjectName, objectType, OWNER_SECURITY_INFORMATION, pOwnerSID, NULL, NULL, NULL)) == ERROR_SUCCESS, HRESULT=80070005 (e:\qfe\nts\sms\framework\tscore\utils.cpp,6675)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="utils.cpp:6675">
    <![LOG[SetNamedSecurityInfo() failed.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="3" thread="960" file="utils.cpp:6675">
    <![LOG[SetObjectOwner() failed. 0x80070005.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="3" thread="960" file="utils.cpp:6687">
    <![LOG[SetObjectOwner (szFName, SE_FILE_OBJECT, c_szAdministrators), HRESULT=80070005 (e:\qfe\nts\sms\framework\tscore\utils.cpp,6772)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="utils.cpp:6772">
    <![LOG[RemoveFile() failed for C:\_SMSTaskSequence\TSEnv.dat. 0x80070005.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="3" thread="960" file="utils.cpp:6816">
    <![LOG[RemoveDirectoryW failed (0x80070091) for C:\_SMSTaskSequence]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="2" thread="960" file="utils.cpp:6900">
    <![LOG[Deleting volume ID file C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ...]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="resolvesource.cpp:506">
    <![LOG[DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\resolvesource.cpp,508)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="resolvesource.cpp:508">
    <![LOG[Deleting volume ID file D:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ...]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="resolvesource.cpp:506">
    <![LOG[DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\resolvesource.cpp,508)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="resolvesource.cpp:508">
    <![LOG[Successfully unregistered Task Sequencing Environment COM Interface.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="environmentlib.cpp:910">
    <![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="commandline.cpp:228">
    <![LOG[Set command line: "X:\sms\bin\x64\TsProgressUI.exe" /Unregister]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="commandline.cpp:731">
    <![LOG[Executing command line: "X:\sms\bin\x64\TsProgressUI.exe" /Unregister]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="commandline.cpp:827">
    <![LOG[==========[ TsProgressUI started in process 8012 ]==========]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="1" thread="8040" file="winmain.cpp:330">
    <![LOG[Command line: "X:\sms\bin\x64\TsProgressUI.exe" /Unregister]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="0" thread="8040" file="winmain.cpp:332">
    <![LOG[Unregistering COM classes]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="1" thread="8040" file="winmain.cpp:204">
    <![LOG[Unregistering class objects]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="1" thread="8040" file="winmain.cpp:495">
    <![LOG[Shutdown complete.]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="1" thread="8040" file="winmain.cpp:512">
    <![LOG[Process completed with exit code 0]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="commandline.cpp:1123">
    <![LOG[Successfully unregistered TS Progress UI.]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="utils.cpp:2903">
    <![LOG[Sending success status message]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:784">
    <![LOG[MP server http://OUR-SCCM.ourcompany.com. Ports 80,443. CRL=false.]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="utils.cpp:5881">
    <![LOG[Setting authenticator]LOG]!><time="18:29:37.785-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="utils.cpp:5903">
    <![LOG[Set authenticator in transport]LOG]!><time="18:29:37.785-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="libsmsmessaging.cpp:7734">
    <![LOG[Sending StatusMessage]LOG]!><time="18:29:37.785-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="libsmsmessaging.cpp:4023">
    <![LOG[Setting message signatures.]LOG]!><time="18:29:37.801-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="libsmsmessaging.cpp:1295">
    <![LOG[Setting the authenticator.]LOG]!><time="18:29:37.801-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="libsmsmessaging.cpp:1325">
    <![LOG[CLibSMSMessageWinHttpTransport::Send: URL: OUR-SCCM.ourcompany.com:80 CCM_POST /ccm_system/request]LOG]!><time="18:29:37.801-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="libsmsmessaging.cpp:8604">
    <![LOG[Request was successful.]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="libsmsmessaging.cpp:8939">
    <![LOG[::RegQueryValueExW(hSubKey, szReg, NULL, NULL, NULL, &dwSize), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\utils.cpp,811)]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="utils.cpp:811">
    <![LOG[RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="2" thread="960" file="utils.cpp:811">
    <![LOG[GetTsRegValue() is unsuccessful. 0x80070002.]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="2" thread="960" file="utils.cpp:842">
    <![LOG[End program: ]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:805">
    <![LOG[Finalize logging request ignored from process 856]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tslogging.cpp:1737">
    <![LOG[Process completed with exit code 0]LOG]!><time="18:29:37.863-420" date="12-26-2014" component="TSPxe" context="" type="1" thread="592" file="commandline.cpp:1123">
    <![LOG[Task Sequence Manager returned code 0x00000000]LOG]!><time="18:29:37.863-420" date="12-26-2014" component="TSPxe" context="" type="1" thread="592" file="tsmediawizardcontrol.cpp:2180">
    <![LOG[Exiting with return code 0x00000000]LOG]!><time="18:29:37.863-420" date="12-26-2014" component="TSPxe" context="" type="1" thread="592" file="tsmbootstrap.cpp:1238">
    <![LOG[Execution complete.]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="bootshell.cpp:693">
    <![LOG[hMap != 0, HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentscope.cpp,493)]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="environmentscope.cpp:493">
    <![LOG[m_pGlobalScope->open(), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentlib.cpp,335)]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="environmentlib.cpp:335">
    <![LOG[this->open(), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentlib.cpp,553)]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="environmentlib.cpp:553">
    <![LOG[::RegQueryValueExW(hSubKey, szReg, NULL, NULL, NULL, &dwSize), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\utils.cpp,811)]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="utils.cpp:811">
    <![LOG[RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="2" thread="760" file="utils.cpp:811">
    <![LOG[GetTsRegValue() is unsuccessful. 0x80070002.]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="2" thread="760" file="utils.cpp:842">
    <![LOG[End program: ]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="bootshell.cpp:725">
    <![LOG[Finalizing logging from process 752]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="tslogging.cpp:1741">
    <![LOG[Finalizing logs to root of first available drive]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="tslogging.cpp:1583">
    <![LOG[Successfully finalized logs to D:\SMSTSLog]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="tslogging.cpp:1640">
    <![LOG[Cleaning up task sequencing logging configuration.]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="tslogging.cpp:584">
    MCSE,MCNE,SCO,Sair Linux/GNU, Open source-enthusiast.

    I have already set it to FALSE. The solution to this will be some different OSD Task Sequence variables or a statement that it can't be made to work.
    I believe that setting defines what volume will be the BOOT / OS Drive Letter. Some people were getting D:\WINDOWS as their boot volume drive letter. Setting to true means whatever was the System Drive letter (usually C) in the image will remain as such
    after it was was applied, setting it to false will make the system have the same drive letter arrangement as what Windows PE detects. In my case I set it to false so that no matter what the new VHD file setup as drive C will be the system drive. I'll set it
    to true on the next deployment but I expect there to be no difference, because in both PE and the WIM the installation volume is the C:.
    We are talking about the DRIVE LETTERS Windows PE SCCM OSD is using for it's temporary files - and how we can manipulate these locations using OSD Task Sequence Variables, so the Apply OS doesn't try and clean up files that are not there
    - and fail with an error if you have added a VHD Native Boot volume.
    This OSDPreserveDriveLetter setting isn't having any effect on the problem here.
    I believe that Format step is setting some task variables used by the OSD Deployment process - telling it where to store it's temporary files. However between the Format Disks and Apply operating system steps the OSD Task Sequence isn't picking up on the
    fact what was the C:\ after Format HDD step is now the D:\ .
    A developer who has an understanding of how the OSD boot process executes in order would be able to see what's going on here.
    MCSE,MCNE,SCO,Sair Linux/GNU, Open source-enthusiast.

  • HP Pavilion dv7-1285dx - No F11, Won't Boot Windows -- Recovery Manager PATH?

    I am repairing an HP Pavilion dv7-1285dx for a friend. I have restored countless other computers but this one has driven me up the wall after 7 hours of trial and error and web searches.
    Here's the deal:
    --The computer came with Windows Vista
    --The owner upgraded it to Windows 7 this past fall
    --The comptuer came in contact with malware and will not boot
    --When booting, the computer will slowly attempt to load Windows, will make it to the "welcome" screen, then restart itself, creating an infinite loop
    --I do have a recovery DVD for the computer; the owner burned it apparently in late 2010
    --I am proficient in MS-DOS and am comfortable using the command prompt
    --The command prompt is the only way I can operate this computer at the moment. I do not have access to Windows of any sort, let alone the web
    --I do have two other computers here that are mine, both are Macs and one dual-boots into Windows; I do have a few flash drives and can burn optical media if necessary
    The F11 key does not work on this computer to bring up the recovery manager. I know why, too--the machine was upgraded to Windows 7, which wiped out the connection between the key and the program.
    My hope is that I can find the path of the recovery manager somewhere. There was a windows.old directory on the drive; I was able to change it to Windows (the existing Windows was renamed windows.scrap).
    This enabled me to at least get to an OS selection screen. There were three options: 7, 7 (recovery), and Vista (recovery). None of them are able to get me into Windows. The Vista option states it is corrupt while both 7s will try to unsuccessfully repair themselves.
    I can, however, access the command prompt through the Windows recovery program (NOT the HP recovery program, which I need to restore anything from either the partition on the D: drive or the DVD).
    I did notice all of the files on the DVD were in .zip format once I got deep enough in a directory. I'm debating about extracting them on one of my other comptuers to see if I can just get them over on another device, but my only external hard drive is Mac formatted so I'll have to use a USB stick.
    There have been queries about this out there referring to making the D: partition active. However, all of these solutions require Windows, which I cannot use. The same is true of downloads.
    My biggest question--where could the recovery program be buried? I would be willing to bring files over on another device IF AND ONLY IF THEY DO NOT REQUIRE WINDOWS.
    The SMINST directory within Program Files (x86) is not present.
    Basically, I need a DOS-compatible, non-Windows, way to restore this computer.
    I have no other Windows installation discs for the machine currently with me. Also, the COA sticker on the bottom of the computer is extremely worn and I can only read a few digits of it, so I can't use that for a restore I guess.
    On a final note--the fan in this comptuer is extremely annoying; any way to turn it off besides just the switch in the BIOS that toggles whether it runs all the time?

    You don't need to be in Windows to mark the D:\Recovery partition Active. Just boot with a utility cd with the disk management capability. If you don't have one_Scroll down on the page and get>> Bootable CD  If you don't have a burning app that can burn an ISO to cd get>> ImgBurn to burn the iso image to cd-a guide on using ImgBurn to write an ISO to a disc is> Here. Once created, boot from it.
    Btw-have you tried booting from his Vista Recovery DVD? With the first disc in the CD/DVD drive power on the laptop and immediately tap Esc to bring up the menu. Then tap F9 Boot options. Use the arrow key to move down & highlight the Optical drive then tap Enter key. (No key is needed with Recovery DVDs)
    ******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**

  • Windows 8.1 not booting : "Boot manager failed to find OS loader"

    Hello all,
    I know this question came up before, but I have being trying to fix this for many days now, without luck and I feel I need some new ideas...
    The short story:
    My Windows 8.1 is not booting, and gets trapped in cycle of Boot Manager until I tell the UEFI to boot from disk or USB
    I can boot up from external CD or USB Windows RE, from which I can get to prompt line
    In the log file in C:\Windows\System 32\LogFiles\Srt\SrtTrail.txt I read: 
    Boot manager failed to find OS loader
    Repair Action File Repair à Failed (err code 0x4001)
    Repair Action Boot Config Data Store Repair à Failed (err code 0x2)
       4. My disk is GPT partitioned, with UEFI Bios
       5. I tried the typical Bootrec commands: FixMbr, FixBoot, ScanOs, RebuildBCD but I always get the error:
    Identified Windows install:0
        6. I tried Bcdedit but I get:
    the boot configuration data (BCD) store could not be opened
        7. I tried to create a new BCD store in the FAT32 partition (temporarily named "v:\") with  
    bcdboot c:\Windows  /l en-gb  /s  v: /f ALL
    but I get:
    Failure when attempted to copy boot files
        8. Finally, I noticed that in
      C:\Windows\System32\
    I DO NOT have the file  winload.efi
    while in: ESP\EFI\Microsoft\Boot\
    I DO have the file   Bootmgfw.efi
       One question I have is: Is it possible to copy a "healthy" winload.efi from somewhere in my PC into C:\Windows\System32\ ?
    Where (which path) could I find it?
    Any other ideas? Please help !!!!
    Many thanks!! This is literarily driving me crazy because I really don't want to reinstall windows....

    Hello Kermit_70,
    What is your current situation?
    Please try the suggestion as aw00t mentioned.
    Additionally, please try to use Automatic Repair to fix problems that keep Windows from loading.
    For more information, please take a look at the following article.
    http://www.eightforums.com/tutorials/2269-system-recovery-options-boot-windows-8-a.html
    Please note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
    Best regards,
    Fangzhou CHEN
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • 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

  • Boot Manager error message on Windows 7 Toshiba Laptop

    Well, I will start with what happened to it, though I don't really know. I was on the internet and it started freezing up horribly, then I didn't know what to do so I walked into the room of the house that doesn't get wireless, and gradually it unfroze. Then I went back to the other room got on again, then it just froze again, only this time walking into the next room didn't work, so I pressed the power button and shut it down. Then when I turned it back on I chose "Start Windows Normally"  and I entered my password at the login screen, then it was on the screen that says "Welcome" and has the blue loading bar next to it, but I waited for at least 10 minutes and it still hadn't loaded. So, I try safe mode and all I get is a black screen with a mouse cursor, in all safe modes. Well, I decide to go to setup by pressing F2 at the Toshiba screen when you first turn it on. So, I did that and I restored the default settings, then exiting saving the settings, and then I turned it on, expecting it to work or at least have the Welcome thing. It went through the Toshiba screen, then it had a black screen for while , then I got an error message:
    WINDOWS BOOT MANAGER
    Windows has encountered a problem communicating with a device connected to your computer.
    This error can be caused by unplugging a removable storage device such as an external USB drive while the device is in use, or by faulty hardware such as a hard drive or CD-ROM drive that is failing. Make sure any removable storage is properly connected and then restart your computer.
    If you continue to recieve this error message, contact the hardware manufacturer.
    File: \Boot\BCD
    Status: 0xc00000e9
    Info: An unexpected I/O error has occurred.
    So then what I did was I plugged in the charger, the mouse ( like on a desktop computer, only I stick this in my laptops usb thing) , my ipod, I put in the last cd I had in the disk drive, and I connected my computer to the modem from the other computer that I sometimes get on.  It didn't do anything, it still gave me that message.
    I would appreciate some help. I just got this computer in December 2009 for Christmas, and I have taken good care of it as far as I can tell. I really can't afford to replace anything right now, but if I have to I will find a way. What makes it worse is that I just got a new video game sent from my grandmother for my birthday....
    Thank you for your help/thoughts/crap

    it looks like a corrupted windows 7 OS or hdd issue , but you might try this one
    Remove all usb devices and make sure that only ac adapter is plugged in your computer.
    Turn on your computer and start tapping on F8. You should see windows advanced option when you do this.
    Select on Safe Mode then Enter. If you can boot to safe mode you can try doing a system restore.
    OR
    On windows advance option. Select Repair my computer
    Just follow the prompt and select system restore.
    OR
    On windows advance option. Select Repair my computer
    Just follow the prompt and Windows Startup Repair
    =========================================================
    the only easy day was yesterday.....
    =========================================================

  • I have macbook pro 13.3 inch. I am installing window 7 in boot camp manager after copying file of window upto 67% it doesn't response and i had forcely shotdown my macbook. Now my macbook doesn't open and stop in black screen with cursor blinking.

    i have macbook pro 13.3 inch. I am installing window 7 in boot camp manager after copying file of window upto 67% it doesn't response and i had forcely shotdown my macbook. Now my macbook doesn't open and stop in black screen with cursor blinking. Now how could i open my macbook pro.

    At startup hold down the Option/Alt key and from the screen that comes up select your OS X partition to start the computer from. Then use the Boot Camp Assistant app to Remove Windows and the partition you reated for it and it will Automatically place the space you allocated for the Windows install back into the OS X partition.
    NOTE:
    Do NOT use Disk Utility to erase the partition that was created for the Windows install. Use the Boot Camp Assistant app again to do that.

  • Corrupt Boot Manager / Missing Windows 8 Pro

    Please assist with the following as I have read too many forums and attempted to resolve without success.
    Problem: unable to boot into Windows 8.0 due to corrupt boot manager or missing boot manager.  
    Observed:  Harddisk is recognized within bios. The disk cable is firmly connected. I hear the disk spinning. Bootrec commands have completed successfully. 
    Attempted to resolve by: 
    1. Bootrec commands (but will still will not boot). 
    2. Factory disk repair command
    3. Ran chkdsk commands (there was some clusters that need to be reorganized).
    My primary concern is that I need to access my data on the drive.  Is there a file that I can download and install that will act as my new boot manager?  Or how can I access the drive?  Pulling it of the computer and installing in an HD dock
    seemingly will not work because I need the bootmanger fixed? 
    Please advise.  Many thanks,

    Hi,
    Firstly, I need to confirm your system edition, as you said unable to boot into Windows 8.0 but your provide this problem at Windows 7 forum.
    About bootrec command to fix the boot manager problem, I would like to suggest you refer to the KB again and try its process for test.
    Use Bootrec.exe in the Windows RE to troubleshoot startup issues:
    http://support.microsoft.com/kb/927392
    If no use, please try to boot system into repair mode and using Startup Repair to fix system startup problem.
    Roger Lu
    TechNet Community Support

  • Windows 7 start up boot manager problem

    I am using inbuilt Windows 7 ( 64 bit , Home Basic ) on my Sony VAIO laptop . For last few days , i am having a very annoying problem during the start up .
    Every time i start my laptop , very soon after the VAIO logo appears , the boot manger prompt appears having "Windows 7" option selected and within fraction of a second it disappears and keep coming till i keep on pressing the ENTER button to start
    the OS . I am only using the Windows 7 OS on the system . To get rid rid of it i tried few options suggested on websites - i changed the BIOS settings , in 'msconfig' tried some alternative options in the boot tab and finally i also formatted my
    laptop but could not get  rid of the issue . Please help me out with this issue .
    Thanks,
    Shantanu 
     

    Hello,
    my problem is similar but all sollutions offered are not working for me.
    The problem: the bootmanager appears showing available OS and gives the chance to select. I can chose and the spezified OS starts. I also can make the selected OS starting with no timeout (so, no chance to select anything). But everything I tryed to make the
    timeout counting back form soemting inbetween 3 and 999 seconds to cero failed. There is just no timeout.
    I tryed to configure timeout via (a) *control panel* > *system & security* > *system* > *advanced system settings* > *advanced* next to *startup & recovery*, then (b) I tryed *msconfig* > *start*, the (c) I tryed to use EasyBCD - but
    all, nothing helps me to bring the timeout to work.
    What I see when I run bcdedit.exe, the timeout is set propperly (see below) - but sill, it is not working while booting - I have to select the OS manually.
    Anybody having an idea, what to do to bring the timeout up and working?
    Thx for your help!
    Jappie
    output of bcdedit.exe:
    Windows-Start-Manager
    Bezeichner              {bootmgr}
    device                  partition=C:
    description             Windows Boot Manager
    locale                  de-DE
    inherit                 {globalsettings}
    default                 {current}
    resumeobject            {9266f3c4-cd82-11e3-bbec-c83fe4796fc1}
    displayorder            {current}
                            {9266f3c8-cd82-11e3-bbec-c83fe4796fc1}
    toolsdisplayorder       {memdiag}
    timeout                 3
    displaybootmenu         Yes
    Windows-Startladeprogramm
    Bezeichner              {current}
    device                  partition=C:
    path                    \Windows\system32\winload.exe
    description             Windows 7
    locale                  de-DE
    inherit                 {bootloadersettings}
    recoverysequence        {9266f3c6-cd82-11e3-bbec-c83fe4796fc1}
    recoveryenabled         Yes
    osdevice                partition=C:
    systemroot              \Windows
    resumeobject            {9266f3c4-cd82-11e3-bbec-c83fe4796fc1}
    nx                      OptIn
    Echtmodus-Startabschnitt
    Bezeichner              {9266f3c8-cd82-11e3-bbec-c83fe4796fc1}
    device                  partition=C:
    path                    \NST\AutoNeoGrub0.mbr
    description             Ubuntu Linux
    EDIT:
    I found a solution by myself:
    (1) via boot-repair I re-installed grub
    (2) via Windows 7 install-disc  I re-installed the Windows bootloader (went into sysrepair tools -> via console with "bootrec /fixmbr" and then "bootrec /fixboot")
    (3) than, back in Windows 7, I used EasyBCD 2.2 community edition, I deleted the old entry for Linux and added a new one pointing to the right place for grub
    (4) finaly, I went into Windows 7 systemsettings to set timeout to 3 second (what was impossible  to be done by EasyBCD for whatever reason)
    Now it works fine - both OS can be started and the timeout is working again.

Maybe you are looking for