If I am right and the \boot\BCD is OK there is no need of a windows 7 install disk or of a PE, *anything* that can copy (on NTFS) the /Windows/Boot/PCAT/bootmgr Now we need to boot to *something* (like a CD/DVD or USB stick). Possibly with a more recent version of grub4dos we could try a few more tricks, but I believe that version being a very old one it simply misses a number of needed commands. If this is the case the \boot\BCD is still OK, and all it is needed is to *somehow* copy the BOOTMGR from the second partition to the first one. Some past reference on the matter for historical reasons (including a few that were not solved due to OP leaving early the I don't think it is a modified version, it is simply a very old (never recommended) about the matter, it is likely that the issue is that the BOOTMGR that is chainloaded from the Windows directory on (hd0,1) tries to load the \boot\BCD from the same partition (while in reality it is in (hd0,0)). You should thank Tinybit (one of the Authors of grub4dos) for this nice, clean -edx=0x0080 trick and cdob for the finding about the existence of a working copy of bootmgr in \Windows\boot\PCAT\. first disk or (hd0), in a nutshell this set of commands:Ĭhainloader -edx=0x0080 /windows/boot/pcat/bootmgrĪ similar situation may arise from other "rogue" or "improper" installs of grub4dos, particularly when the embedded menu.lst has been edited, it seems like some other crappy programs/loaders/whatever can create a similar issue, the good news is that attempting to run the above set of commands won't alter anything on the system, in the worst case it won't boot. You do this by adding a parameter to the chainloader command -edx=0x0080 which basically overwrites a registry with the appropriate values, in the 0x0080 the 00 means first partition (or the second 0 in (hd0,0)) and the 80 means BIOS disk 0x80 or disk drive 128 decimal, i.e. In these case you need to "force" the assignment of the boot partition, otherwise the chainloaded bootmgr will attempt to find the \boot\BCD on the same (hd0,1) partition from which it is booted and fail. However the "default" install on Windows 7 on a new hard disk/system creates two partitions, a first one ((hd0,0) in grub4dos notation) containing only the bootmgr and the \boot\BCD (which is the active partition in the MBR partition table or "boot" partition, called by MS "system", that normally has not a drive letter assigned) and a second partition ((hd0,1) in grub4dos notation) containing the rest of the operating system (which everyone would call "system", but that the goof MS guys call "boot", that normally has the drive letter C: assigned). the "system" and "boot" partition are the same volume, typically (hd0,0) in grub4dos notation. The above will only work if the Windows 7 has been installed on a single partition, i.e. after having pressed "c" for the prompt issuing the commands:įind -set-root /windows/boot/pcat/bootmgr In these cases there is a way out by chainloading a copy of the bootmgr that is normally present in \Windows\boot\PCAT\, i.e. What has been increasingly reported is that also chainloading the bootmgr does not work (it is very possible that this happens because of a concurrent different issue, such as malware or similar, no way to know the exact reason). In some cases what does not work is the chainloading of bootmgr_, but there is still a good copy of bootmgr so all it is needed is to press "c" to get to a grub4dos command prompt and issue the commands: Several people have reported that the provision does not work. MakeactiveEvidently *somehow* the program makes a copy of bootmgr renaming it to bootmgr_ and as long as this works everything works. The screen comes from a now obsolete version of grub4dos grldr, the 0.4.3, that is renamed to shldr and has the internal embedded menu.lst modified as follows: Windows Vista/7None of which when chosen leads to have your system booted. You are presented with a screen (white text on black background) with three choices:
However if you are reading this most probably you either installed on your system the trial or are a moron less experienced user that actually paid good money for it and you are now stuck with an unbootable system.
Spyhunter is a program by Enigma Software intended to be a remover for crapware/malware/etc.īesides whether it works or not for the intended scope, it has been reported in the past to overcharge customers that bought a license for it and to renew subscriptions billing the credit card without authorization.Īdditionally, we had a number of reports that in some cases it can effectively make a Windows 7 unbootable.