Issues after resizing Bootcamp using Minitool

For ecverything you want to do with a bootcamp partition you should use BootcamAssistant ONLY.

The best way to do now is using BootcamAssistant to delete the compromised Windows partition and setup a new Windows partition.

Yes. Can you follow Windows 7 Vanished after Yosemite update... help? and download Testdisk (http://www.cgsecurity.org/wiki/TestDisk_Step_By_Step) and GPT Fdisk (http://sourceforge.net/projects/gptfdisk/) and start a Testdisk scan (example - http://imgur.com/a/PjmnK) . The gap between GPT3 and GPT4 indicates a 'lost' NTFS header. Minitool does not keep MBR and GPT in sync.

Please post the output of sudo fdisk /dev/disk0 for the record.

Please re-post the fdisk output. 😉

This is table for partition verification. Can you please post the output of sudo fdisk /dev/disk0 for cross-validation?

The MBR has also been corrupted. Can you scroll down to the following partition

>D MS Data 783175680 1000214520 217038841

and use 'P' to list files. We are looking for something similar to the following...

Install GPT Fdisk (aka gdisk). Leave your Testdisk display and start a new Terminal Window. You need to use the following steps. If you see any error messages during the following steps, please stop and post back here with the error message. The following steps have values from your Testdisk output (and you can verify) in Steps 7 and 8. Please notice the'+' sign in step 8 (this is called offset notation). The text in parentheses is for informational purpose to describe the action being taken. Gdisk has one-character commands except when entering numbers.

Rebuild GPT4 using start/end offsets

1. Sudo gdisk /dev/rdisk0
2. P (print the full list of parts)
3. D (delete)
4. 4 (part 4)
5. N (new part)
6. 4 (part 4)
7. 783175680 ( - Start offset in sectors or the start point for Bootcamp part)
8. +217038841 ( - Size offset, as opposed to End offset)
9. 0700 (Windows part type)
10. P (print list of all parts just to see what changes will be made)
11. W (Write the new GPT)
12. Y (Yes! really write the new GPT)

This will delete and re-write the GPT partition info for /dev/disk0s4.

Rebuild MBR to match the new GPT information thus resetting the Hybrid MBR. Use defaults for other questions (like partition codes). The only values that need modifications are the Boot flags and step 10. Accept all other defaults that Gdisk offers. Please see thesample Q&A as an example. These steps can be repeated if you make a mistake before you get to Step 12, otherwise start from Step 1 for these steps. Step 6 has numbers which are typed with a space between the numbers.

1. Sudo gdisk /dev/rdisk0
2. P (Print list of parts)
3. R (Recover)
4. O (print current Hybrid MBR)
5. H (chooses Hybrid)
6. Partitions numbers to be hybridized: 2 3 4
7. Y (Good for GRUB question)
8. N (part 2 boot flag)
9. N (part 3 boot flag)
10. Y (part 4 boot flag make NTFS bootable partition)
11. O (print current Hybrid MBR)
12. W (Write the new MBR)
13. Y (Yes! write the new MBR)
14. Reboot

Here is sample Q&A for this section. Please notice the Press Enter/Return.

Place EFI GPT (0xEE) partition first in MBR (good for GRUB)? (Y/N): Y

Creating entry for GPT partition #2 (MBR partition #2)

Enter an MBR hex code (default AF): Press Enter/Return

Set the bootable flag? (Y/N): N

Creating entry for GPT partition #3 (MBR partition #3)

Enter an MBR hex code (default AB): Press Enter/Return

Set the bootable flag? (Y/N): N

Creating entry for GPT partition #4 (MBR partition #4)

Enter an MBR hex code (default 07): Press Enter/Return

Set the bootable flag? (Y/N): Y

Test 1 - Does Bootcamp Volume show up in Finder?

Test 2 - Can you see files in Bootcamp Volume?

Test 3 - Can you select Bootcamp in System Preferences -> Startup Disk?

Test 4 - If Test 3 is successful, select Bootcamp and Click Restart.

1. Please post the output of

sudo gpt -vv -r show /dev/disk0

sudo fdisk /dev/disk0

2. Do you have any third-party NTFS software (Tuxera, Paragon, NTFS-3g or variants..)?

3. Which tests in the test list fail?

Yes, Parallels does have an NTFS driver which has been known to interfere with Apple's NTFS driver. It can cause conflicts. In OS X Finder, do you see all your files, including Documents?