Did you do any software installation, filesystem maintenance, or partition adjustments just prior to the problem occurring? It could be that your installation relies on a hybrid MBR (as do all Boot Camp installations), and that your hybrid MBR has become damaged or replaced with a standard GPT protective MBR. If so, the solution is to re-build the correct hybrid MBR -- but there are risks to doing this if you've adjusted your partitions recently. In particular, if you've used Windows tools to resize partitions, your GPT and MBR data will be dangerously out of sync, and recovering a consistent and correct set of partitions will require careful attention to detail. If the hybrid MBR has been replaced with a protective MBR or damaged in a less dangerous way, re-creating it with gdisk, gptsync, or some other tool should be relatively straightforward.
You can check the current state of the disk with gdisk:
$ sudo gdisk /dev/disk0
GPT fdisk (gdisk) version 1.0.0
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Command (? for help):
This example shows a GPT disk (GPT: present) with a standard protective MBR (MBR: protective). A hybrid MBR disk will show MBR: hybrid. You can type p to show the (GPT) partitions, which you can review as a sanity check. Then, use v to check for GPT/MBR consistency (and other partition table problems):
Command (? for help): v
No problems found. 990 free sectors (495.0 KiB) available in 1
segments, the largest of which is 990 (495.0 KiB) in size.
Your details will differ, of course. If you uncover problems, edit your question to include the details and add a comment to my answer so I notice your reply.
A caveat: Some people install Windows 8 and later on Macs in EFI mode rather than using Boot Camp. You specified the latter, but if that detail was in error, you definitely do not want to add a hybrid MBR to your disk, since it will make matters worse.
EDIT:
You could have pasted your output into your original question by editing it. Adding four spaces to the start of each line will preserve formatting, helping legibility.
Before you try to adjust your hybrid MBR, I recommend looking for Windows EFI boot files. It could be that you've unknowingly installed Windows in EFI mode, in which case adjusting your hybrid MBR will be a waste of time that you'll have to undo later. You can check for Windows EFI boot files by mounting your ESP in OS X:
mkdir /Volumes/ESP
sudo mount -t msdos /dev/disk0s1 /Volumes/ESP
The Windows EFI boot loader files will normally be in /Volumes/ESP/EFI/Microsoft/Boot, given the /Volumes/ESP mount point I specified. If you find files there (bootmgfw.efi is the main file, but there are a number of support files), don't try adjusting your hybrid MBR; instead, investigate possible EFI boot troubles for Windows on Macs.
In fact, your partition list makes me suspicious that you did perform an EFI-mode installation of Windows, although I'm not 100% positive of that.
If you don't see any Windows boot files on your ESP, you can create a hybrid MBR by following the instructions on the gdisk hybrid MBR page. You'll need to decide which partitions to include in the hybrid MBR. Your Windows boot partition is the most critical (your partition #5), but it looks like you've got two other Microsoft partitions (#4 and #6).
Best Answer
So after trying several more items, I decided toying with the registry was the last resort. The issue here is that almost every post or tutorial suggested that i use the original machine, which in this case was not an option.
So i opened the
defaulthive from the Windows 2000 machine on my Windows 8 machine. After this, I followed a tutorial that mentioned to merge many keys into the registry under theCurrentControlSetsubkey. However, again, not possible, so i merged them intoControlSet001. I also had to create most of them manually.However, once this painful process was finished, the VM booted as expected. Link to tutorial