Skip to main content


The Boot Manager (BOOTMGR) is the bootloader of the Windows 7, Windows Vista, and Windows Server 2008 operating systems (OS). The computer's BIOS loads the program upon startup and will start the bootloader for the OS and other required programs. The NTLDRpreceded it on older versions of the Windows OS.
What Problems Can Occur with BOOTMGR?

Unfortunately, the BOOTMGR may display a number of errors due to varying circumstances. Some of the common BOOTMGR errors are a result of operating system upgrade errors, corrupt hard drive sectors, a damaged IDE cable, and an outdated BIOS. Another common cause of BOOTMGR errors is a computer trying to startup from a flash/disk drive that is not configured to be a boot disk.
How to Fix BOOTMGR Errors

Step 1 – Check the CD/DVD drive for a disk, as it could be triggering the error when the computer starts up. If a disk is found, remove it.

Step 2 – If there was no disk in the drive, insert the Windows repair CD/DVD into the computer's disk drive and click “Next” on the subsequent menu prompt.

Step 3 – Select “Repair your computer” on the subsequent window, then click “Next.”

Step 4 – Click “Startup Repair” to initiate the systen's installation repair process and restart the computer when prompted. If the System Repair application is opened from the MS DOS prompt, then the command for running the repair application is “bootrec /fixboot.”

Step 5 – If the computer still has the BOOTMGR error after repairing and restarting, check if there are any damaged IDE cables. If so, replace them.

Step 6 – If none of these steps fix the error, get a professional to examine the hard drive to see whether a hard drive replacement is needed in order to solve the BOOTMGR error.

Popular posts from this blog


The BCD registry file controls which operating system installation starts and how long the boot manager waits before starting Windows. Basically, it’s like the Boot.ini file in earlier versions of Windows. If you need to edit it, the easiest way is to use the Startup And Recovery tool from within Vista. Just follow these steps: 1. Click Start. Right-click Computer, and then click Properties. 2. Click Advanced System Settings. 3. On the Advanced tab, under Startup and Recovery, click Settings. 4. Click the Default Operating System list, and edit other startup settings. Then, click OK. Same as Windows XP, right? But you’re probably not here because you couldn’t find that dialog box. You’re probably here because Windows Vista won’t start. In that case, you shouldn’t even worry about editing the BCD. Just run Startup Repair, and let the tool do what it’s supposed to. If you’re an advanced user, like an IT guy, you might want to edit the BCD file yourself. You can do this

DNS Scavenging.

                        DNS Scavenging is a great answer to a problem that has been nagging everyone since RFC 2136 came out way back in 1997.  Despite many clever methods of ensuring that clients and DHCP servers that perform dynamic updates clean up after themselves sometimes DNS can get messy.  Remember that old test server that you built two years ago that caught fire before it could be used?  Probably not.  DNS still remembers it though.  There are two big issues with DNS scavenging that seem to come up a lot: "I'm hitting this 'scavenge now' button like a snare drum and nothing is happening.  Why?" or "I woke up this morning, my DNS zones are nearly empty and Active Directory is sitting in a corner rocking back and forth crying.  What happened?" This post should help us figure out when the first issue will happen and completely avoid the second.  We'll go through how scavenging is setup then I'll give you my best practices.  Scavenging s

AD LDS – Syncronizing AD LDS with Active Directory

First, we will install the AD LDS Instance: 1. Create and AD LDS instance by clicking Start -> Administrative Tools -> Active Directory Lightweight Directory Services Setup Wizard. The Setup Wizard appears. 2. Click Next . The Setup Options dialog box appears. For the sake of this guide, a unique instance will be the primary focus. I will have a separate post regarding AD LDS replication at some point in the near future. 3. Select A unique instance . 4. Click Next and the Instance Name dialog box appears. The instance name will help you identify and differentiate it from other instances that you may have installed on the same end point. The instance name will be listed in the data directory for the instance as well as in the Add or Remove Programs snap-in. 5. Enter a unique instance name, for example IDG. 6. Click Next to display the Ports configuration dialog box. 7. Leave ports at their default values unless you have conflicts with the default values. 8. Click N