How-To: Hide Vista Partition from XP!


Recommended Posts

One of the biggest problems that faces dual-booters is data corruption on many different fronts. While using proper dual-boot techniques and going by the book can avoid most forms of data corruption, there are some things that you can’t just work around, especially if it’s considered a “feature” by Microsoft… One such “feature” is that those dual-booting Windows XP and Windows Vista will find that every time they boot into XP, they’ll lose all their Vista system restore points - because XP “intelligently” detects them as being corrupt XP system restore profiles. So much for painless dual-booting. Even Vista’s “Complete Backup” feature is decimated by the very existence of XP on the same computer - and having them on separate hard drives doesn’t help!

Unfortunately, there is no solution to this. Microsoft acknowledges the issue - but provides absolutely no hint, clue, or even whiff of a hotfix though it would seem that this isn’t something difficult for them to patch. The advice has been to either not dual-boot at all, run XP in a virtual machine, or else encrypt the Vista hard drive - a feature that has more bugs than the rest of Vista put together. But don’t worry, we have a (free and easy!) solution for you!

1. If you don’t already have it, download and install EasyBCD.

2. Run EasyBCD and go to the “Add/Remove Entries” screen.

3. Delete any and all “Windows XP” entries in the list you see. Simply select them, and press the delete button.

4. Click the “NeoGrub” tab, and select “Install NeoGrub” from the screen.

5. Once NeoGrub is installed, hit the “Configure NeoGrub” button.

6. Notepad will open, and you’ll be presented with the NeoGrub configuration file, called “menu.lst” NeoGrub provides a bunch of very nifty options that will help us hide the Vista drive from Windows XP, in a very safe, simple, and straight-forward manner. Copy and paste this code over the existing menu.lst file. Replace everything:

# NeoSmart NeoGrub Bootloader Configuration File
#
# This is the NeoGrub menu.lst file, and should be located at C:\menu.lst
# Please see the EasyBCD Documentation for information on how to create/modify entries
# http://neosmart.net/wiki/display/EBCD

default 0
timeout 0

title Boot XP - Hide Vista
hide (hd0,1)			# SET THIS TO THE VISTA DRIVE
# Optionally repeat the above entry for all the Vista drives
chainloader (hd0,0)/ntldr	# SET THIS TO THE BOOT PARTITION
boot

# Optional section
#  If you include this section, you will see a second bootloader menu!
title Boot XP - Unhide Vista
unhide (hd0,1)			# SET THIS TO THE VISTA DRIVE
# Optionally repeat the above entry for all the Vista drives
chainloader (hd0,0)/ntldr	# SET THIS TO THE BOOT PARTITION
boot

Read “Drive Letters and Numbers” to figure out which (hdx,y) sequence you need to use. Hard drive and partition counts start at 0. Tip: You can see a full list of drives and partitions by going to the “Linux/BSD” tab of the “Add/Remove Entries” section in EasyBCD.

7. Save it, and exit notepad.

8. Optional: Go to the “Configure Boot” screen and rename the entry from “NeoGrub Bootloader” to “Windows XP” or another name of your choice.

9. Exit EasyBCD & reboot to test.

Original Article: http://neosmart.net/blog/2007/hide-vista-partition-from-xp/ (reproduced with permission)

EasyBCD Download: http://neosmart.net/dl.php?id=1

NeoGrub Documentation: http://neosmart.net/wiki/display/EBCD/NeoGrub

This should take care of the problem with Windows XP deleting the System Restore images for Windows Vista and shadow copies on Longhorn Server. If you have multiple Vista partitions, you will need to repeat the hide/unhide lines for each.

Hope this helps!

Link to comment
https://www.neowin.net/forum/topic/564681-how-to-hide-vista-partition-from-xp/
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Everyone else has said it. I'm gonna say it - you don't know what you're talking about. I do. I have two laptops. One work, one personal. I have access to two more laptops - both personal. At home I manually update my personal laptop when I see on Neowin that there is an update - I carry on and only apply the updates when I am ready. My work one only updates when my workplace decides to send it - I carry on and only apply the updates (when they actually arrive, which is usually days after the release) when I switch off the laptop at the end of the day as usual. The two other personal laptops only get updated when I get to it which is rarely - the people who own them carry on using them until I get to it and update them. All of the browsers on all laptops are configured to restore the tabs when launched. Google and Microsoft have changed from 6 weeks to 4, and it looks like it's going to move to 2. None of these changes affect how any of these browsers on the laptops are used. Not one jot. My advice to you is stop panicking whenever you see an update. Just carry on with what you're doing. This even benefits you in a way - from your comment you sound like you don't like the changes or the frivolous new features - great - then carry on as before!
    • AMAZON needs to take total accountability for this.
    • Server Summit had a heap of announcements, ADCS changes are baller.
    • Nice, hope they *finally* fixed the issue with the NTFS driver where the system would completely brick during large file copies using the built in driver. It's been broken for years requiring me to use the older, slower, NTFS-3G FUSE driver.
    • Windows 11 KB5094126 BSODing, freezing, forcing BitLocker lockout, breaks OneDrive, and more by Sayan Sen Microsoft released Windows 11 KB5094126 and KB5093998 last week as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. While Microsoft has so far not acknowledged any major problems with the release, some users online are running into problems. These range from OneDrive and Dropbox access issues, BitLocker recovery lockouts, to blue screens and BSODs. The most common one seems to be happening with HP systems wherein affected users say they hit 0xc0430001 BSOD (blue screen of death) error code after the KB5094126 update. We wonder if this could be related to the recent bug we covered on HP devices wherein the ongoing Secure Boot certificate updates are leading to similar issues. While we are not certain, users affected by this issue likely need to ensure that the boot.stl file is included on the installation media (such as a USB installer or ISO), if the above-mentioned dynamic updates are deployed. If this file is missing, computers may fail to boot from the installation media and could display the error 0xc0430001. This STL file is used by Secure Boot to verify that the boot files are trusted, so it must match the same Windows version and system architecture. To ensure the file is included, Microsoft recommends using the Update WinPE script, which automatically updates the image and handles the required files. Alternatively, you can manually copy the boot.stl file from the Windows\Boot\EFI folder on a Windows device and place it in the matching folder on your installation media before deploying the updated image. Aside from blue screening some users also note their systems have been freezing following the update. This could be happening to Lenovo PCs specifically. In the case of the OneDrive and Dropbox access issues, a user figured out that there could be a conflict with UAC. He explained: "Okay, so I did some digging, and in our environment KB5094126 breaks OneDrive and Dropbox in Explorer. I went through all our GPOs and found out that the combination of disabling UAC and having my user being a local admin breaks OneDrive in Explorer. ... If I enable UAC again, then it works, even with KB5094126 still installed." Hopefully, Microsoft will look into these issues. Source: Microsoft forum (link1, link2, link3, link4), Reddit (link1, link2, link3, link4)
  • Recent Achievements

    • Week One Done
      Jeroen Wilms earned a badge
      Week One Done
    • Week One Done
      rolfus earned a badge
      Week One Done
    • One Month Later
      Leroy Jethro Gibbs earned a badge
      One Month Later
    • Conversation Starter
      flexorcist earned a badge
      Conversation Starter
    • One Month Later
      AndreaB earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      508
    2. 2
      +Edouard
      197
    3. 3
      PsYcHoKiLLa
      138
    4. 4
      ATLien_0
      90
    5. 5
      Steven P.
      80
  • Tell a friend

    Love Neowin? Tell a friend!