"EISA Configuration" partition won’t go away
Monday, 20 April 2009
The symptom is typical: you check out the partitions on your hard drive in Windows Disk Manager only to find out that there’s a weird, inaccessible partition that’s of the type “EISA Configuration.” What is it? Can I get rid of it?
What is it?
It has become standard practice for manufacturers to include recovery data or utilities on the hard drive to save them the costs of creating separate recovery disks for your computer. The benefit is that you can always restore your computer without worrying about losing your restory disks, but the downside is that it’s taking space on your hard drive, and if your hard drive died, you don’t have any restore disks at all.
The “EISA Configuration” partition is not really an EISA Configuration partition. EISA is an obsolote IBM bus architecture. What’s really going on is that this partition is a regular FAT32 or NTFS partition, except that its identifier in the partition has been changed to 0xDE, which codes for “EISA Configuration.” This way, Windows doesn’t try to mount it so you won’t accidentally mess with the files there.
How do I get rid of it?
Just delete it. You may be able to delete this partition and then expand your regular Windows partition to fill the gap using Windows Disk Management MMC snap-in. Just right-click on “My Computer” and select “Manage…” and find “Disk Management.”
Personally, I recommend using an Ubuntu live CD. With it, you can boot into Ubuntu, run GParted (a partition editor), delete the EISA Configuration partition and expand the Windows partition to fill in the remaining space. Just be careful with your data. Make a backup.
It won’t go away!
You may experience an issue where, after deleting your “EISA Configuration” partition, you boot your computer only to find out that another partition has magically turned into an “EISA Configuration” partition. What happened here was that the manufacturer (Acer has been known to do this) put a small program in the Master Boot Record (MBR), the first 512 bytes of your hard drive. Every time you boot that hard drive, their program runs and blindly changes the first (usually it’s the first one) partition on the hard drive to 0xDE, which codes for “EISA Configuration.” Bad.
What you need to do is write in a new MBR to get rid of this program. Be careful, because the MBR stores the partition table, without which your computer won’t know what partitions exist on your hard drive. There are several tools that can do this; I won’t go into detail on each one.
- fixmbr.exe—on the XP or Vista Recovery Console
- MbrFix.exe—for Windows
- ms-sys—for Linux. This guide to ms-sys might be helpful.
Now my computer won’t boot!
If Windows displays an error message saying that “hal.dll” could not be found (Windows XP) or that “rundll32.exe” could not be found, then what likely has happened is that your partition numbers have changed and Windows can’t find itself anymore. On XP, if you know what you’re doing, you can edit the “boot.ini” file to point to the new partition number. On Vista, you’re best off just running the automated recovery on the Vista Recovery Console disc until it’s fixed. It might take several tries.
My drive C: and D: got switched!
It’s a regrettable problem when Windows, which originally was on the C: drive, suddenly gets switched to the D: drive. You’ll find that a lot of things don’t work like this, but unfortunately, you can’t go into Disk Management and change the drive letters because you’re currently running Windows off that drive letter. Microsoft has a KB article detailing the procedure to switch them back, but the process is simple.
Fire up regedit.exe and navigate to HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices, and rename the \DosDevices\C: and \DosDevices\D: keys around. Or, you can delete all the keys in MountedDevices and Windows will automatically enumerate the partitions and reassign drive letters.