Talk:Windows Boot Manager

message: Does anyone know where I could find a description of 7's startup process?  If I had one I would go through the article and rewrite it to reflect that it covers win7 as well as vista.
Universalss (talk) 06:09, 31 August 2009 (UTC)
thread_title:  So how does this compare to windows 7? 

message: How exactly does this whole system differ from NTLDR?  It just seems to me like they renamed the binary, changed the configuration file format, and made it compatible with EFI.  Now, the last of those is rather significant, but does it really need a whole article to say "Windows Vista and Windows Longhorn Server will support booting from EFI?"—Kbolino 08:19, 23 September 2006 (UTC)
replies: text: In the new scheme, the "loading" part of the process is handled by a separate file (winload.exe); besides requiring an obvious change of name (since what replaces NTLDR does not "load" any more), it opens wide arrays of new possibilities to branch to other things than just WinLoading, and does not require any more hacks like the use of chain-loading of variants of SetupLdr.bin to launch the recovery console, or the various /win9xxx flags. The design is an order of magnitude more clean. Antoinel 14:24, 19 February 2007 (UTC)

text: I do not understand the question. The new scheme, like the older, certainly can boot Vista (and even recent xp/2003) kernel directly from various partitions, and certainly can chain-load arbitrary boot records, including one that mimics the VBR from another partition. A different problem is to boot a volume which is not marked as active, something which has traditionnaly been difficult with MS booting programs. Antoinel 14:24, 19 February 2007 (UTC)
replies: text:  Maybe the question was whether different boot loader can chainload Vista the same way as it does chainload older versions of MS Windows. And I guess that the answere depends on the particular implementation of chainloading - if it loads NTLDR or VBR. Pheeror (talk) 14:27, 2 July 2008 (UTC)

text: It is certainly possible to boot Vista with a different code in the MBR that the one MS put without asking while installing the operating system. Of course the disk signature should be preserved, but again this is not a new requirement. Antoinel 14:24, 19 February 2007 (UTC)

text: Fact is that with TPCA, the full content of the MBR is part of the chain of trust; so if one OS is in control of the TCPA chip, and registered the OS version of the MBR, it is now impossible to install any other software there without defeating the whole chain. There is nothing specific to Vista here. Antoinel 14:24, 19 February 2007 (UTC)
thread_title:  I'm just a bit confused 

message: i just bought a computer with vista in it. however, i also want xp in it as well. is there a way i can install xp, and still have vista work. it is my understanding that once you install an older operating system on top of a newer one, the newer one stops working. at least that was the case when i installed windows 2000 on top of xp. —The preceding unsigned comment was added by 86.139.242.103 (talk) 11:40, 6 April 2007 (UTC)
thread_title:  multi boot 

message: Can someone add Bitlocker related info? When Bitlocker is enabled, the MBR is verified and if its overwritten or modified by another OS, even a previous Windows version, Vista cries "data integrity compromised". Bitlocker's probably the chief reason Microsoft developed the Windows Boot Manager to replace NTLDR.  —Preceding unsigned comment added by 221.128.181.68 (talk) 18:17, 27 March 2008 (UTC)
thread_title:  Startup process when Bitlocker enabled? 

message: i just found this in the history
http://en.wikipedia.org/w/index.php?title=Windows_Vista_startup_process&oldid=393166375
surely this should be in the article, as it would be useful to people looking for information on fixing issues, which is how i found the article to start with. Ktremain (talk) 00:41, 25 February 2011 (UTC)
replies: text: That was a tutorial, a tip not suitable for an encyclopedia, but the information is almost already there: bcdedit.exe. Maybe the paragraph can be enhanced, and maybe we can consider a wikiversity article. Rursus dixit. (mbork3!) 06:32, 11 July 2011 (UTC)
thread_title:  removed content? re-add to article 

message: If you are using say a Win7 PC to make a bootable win7 install USB stick for a new Win7 PC, you need a 32 bit or 64 bit bootsect.exe file depending on whether bootsect.exe is to execute on on a 32 bit or 64 bit PC to place the boot info on to the stick - refer this article. My question is: Does bootsect.exe then install code that is different for 32 bit and 64 bit systems based on whether bootsect.exe itself is 32 bit or 64 bit? Or is it that a 32 bit or 64 bit bootsect.exe will install boot code that doesn't care what it's going to boot - ie either a 32 or 64 bit bootsect.exe can install boot code that can boot either a 32 or 64 bit Win OS installer. Hope that makes sense.  — Preceding unsigned comment added by 124.191.112.66 (talk) 23:58, 18 June 2012 (UTC)
thread_title: 32 bit vs 64 bit

message: :The following is a closed discussion of a requested move. Please do not modify it. Subsequent comments should be made in a new section on the talk page. Editors desiring to contest the closing decision should consider a move review after discussing it on the closer's talk page. No further edits should be made to this discussion.
The result of the move request was: Moved  BilledMammal (talk) 22:39, 29 March 2023 (UTC)
replies: text: I have performed the move; please copy over the updated content when it suits you. I decided not to do so to ensure that it was properly attributed to you, and to allow those draft pages to be deleted if you desire. BilledMammal (talk) 22:47, 29 March 2023 (UTC)
replies: text: I'll copy over the content. Thanks for moving the pages. – BrandonXLF (talk) 22:56, 29 March 2023 (UTC)
thread_title:  Requested move 20 March 2023