About Contribute Disclaimer Contact News
Disclaimer
The information on this site is offered in good faith and no responsibility can be accepted for misuse that leads to loss of data or damaged hardware.
Help Us Improve
Have you spotted an error, or found something confusing or ambiguous? Help us improve our articles......


Google Advert Links
-
-
tech insight guyTech Talking
Trying to put it into plain language.
spacer Multibooters.com

Recover from a Changed Windows Drive Letter.


My Computer Drive C: Icon When you move a Windows operating system, either by cloning partitions or drives, or even by just restoring a backup image, it can happen that on first bootup a Windows install will swap drive letters and assign itself a different letter to the one it originally had. This usually results in either a hang and failure to boot, or various error messages that you have to click through just to get to a changed and limited desktop, or you may even get cross-linked operating systems where you can be booted into a different Windows install to the one it appears you are.


The Problem.
The main cause of all this trouble is the way a WinNT operating system remembers drive letters and stores this information in its registry. During bootup the registry is consulted to determine the drive letter a partition had been assigned, so that the same letter can be reassigned. A Windows install that has been moved to a different partition will on bootup look for its original partition and if found assign it the letter that is held for it in the registry, usually C:, thereby removing it from being available to be assigned to its new partition. Another factor that can have a bearing is if the partition Windows now finds itself on has already been recorded as having its own drive letter, which then may be given precedence over the correct allocation of the C: drive letter. Whatever the reason a Windows install is not re-allocated the same drive letter as it was originally assigned with during its install to a machine, the results are going to be problematic. For much more on how drive letters are assigned and maintained see this article.

Prevention.
Avoiding drive letter problems is one of the main things we have to consider when cloning and moving Windows and there are a few measures we can take before hand to prevent such issues from arising. For example we can hide partitions from Windows so that letter allocation won't take place, or we can delete Window's memory of previously allocated drive letters so the old associations don't come into play. This is partly covered below, but is more fully explained in this article and so if the recovery procedures detailed on this page fail for you then perhaps a bit of prevention may help in any following attempts you have at moving Windows. There are of course other boot issues to be overcome when moving a new-generation Windows operating system and knowing a bit about the new boot files is key to an understanding of those.




Making Corrections.
If you do have trouble with a cloned or restored Windows being assigned the wrong drive letter you should still be able to eventually boot to a limited desktop or to just a blank light blue screen, (for 2K/XP see box below). You may be able to affect repairs directly from there, but if you have problems getting any of the following procedures to work then you should try again from Safemode. Our goal is to reset the Windows drive letter to what is should be and so we need to access and edit the registry. Once Windows has booted as far as it's going to then press Ctrl+Shift+Esc or Ctrl+Alt+Del to open Task Manager and then click New task... and type in and run diskmgmt.msc and wait until the Disk Management utility has fully opened and then determine which drive letter has been assigned to your cloned or restored Windows install, which you should be able to identify by simply knowing which partition it is on.

Once you have your wrong drive letter then New task ... again and this time type in and run regedit and navigate to the key described in the screenshot below. Right click on the \DosDevices\ entry that has your letter and choose rename and change the letter to the one you think it should be (usually C:). If the registry already has that letter assigned to another DosDevices entry you will need to change that one first to free up the required letter. You can make it anything for now that is not currently in use as you can change or remove it later from Disk Management once you are fully into Windows.

HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices
mounted devices key screenshot
Note that the amount of entries in MountedDevices can range from several to dozens and for our purposes here we are only interested in the lines that start...   \DosDevices\

If you just can't get Disk Management or Regedit to open for you in the steps detailed above, even in safemode, then try 'Safemode with Command Prompt'. Note that from Win7 in safemode you have to tick the option 'Create this task with administrative privileges'. If you still can't get Disk Management to open but regedit works then you can make an educated guess as to which DosDevice entry is your desired target and change its letter and try rebooting. If you don't have success first time then repeat the process with each DosDevice entry until you get the right one.

Another option you can try is to just delete entire lines in the MountedDevices key, which will force Windows to completely rebuild them on reboot. You can in fact delete the entire contents of MountedDevices (except the first line) and this may well do the trick, as in the absence of any previous letter allocations it is normal procedure for Windows to make its own partition the C: drive. Clearing out the MountedDevices key is something that can be done in a fully functioning Windows install in order to try and cure certain letter allocation problems, or as a preemptive step before moving Windows so that letter allocation problems are avoided. Please be acutely aware however that in normal circumstances changing or deleting items in the MountedDevices key should not be tackled lightly and it is only safe under certain conditions. In our case here with an already non-booting operating system we have little to lose and we should still be able to recover things manually by changing each line individually till we get it right and give our partition the correct letter.




XP/2K logos

Previous generation of Windows NT operating systems.


With XP or Win2K and their server derivatives we won't make it to any kind of desktop but instead just be left hanging at one of the startup or welcome screens. To get easy access to the registry of an unbootable OS will require having to be able to boot into another Windows operating system from where we can use its regedit tool to make our drive letter alterations as described above. We can do this from another OS on the same machine, or from Windows on a bootable external/removable device, or we can connect our problem drive up to another Windows machine by USB or SATA.

up arrowTop of page....
spacermultibooters.com:- March 2014


Advertisement:
www.hostgator.com
Windows7 logo
Building a Hackintosh:
A new Intel motherboard that is compatible with 'Any OS'?
www.techspot.com


multibooters logo multibooters.com
creative commons licence

All product and company logos, icons and images that are reproduced on this site are the property and trademarks of their respective owners and are used here merely to illustrate their products, NOT to indicate or infer any endorsement or partnership unless otherwise stated. We have endeavored not to reproduce copyrighted images or graphics or infringe upon the rights of any trademark or copyright holder. If you believe or suspect we may have breached the permissible use of copyrighted material then please bring it to our attention. The reproducing or copying of original material from this site is currently allowed for non commercial purposes with the provision that your source is clearly indicated and that a back-link to the referenced information is included. Thank You. See our full  Terms of Use.  Material on this site is not guaranteed to be free of errors.   Multibooters.com   2012 - 2013

Home Sitemap Privacy-Policy About Contact/Feedback Donate Copyright/Legal