Windows partition no longer bootable

Question

Last night, I was using Bootcamp fine through VMware Fusion, no issue at all.  I shut the VM down correctly and closed VMware.
Later that evening, I was trying to copy files onto my iPad through iTunes and got the warning that I didn't have permissions to view the contents of that file – I checked file info, I do, and also transferred the same file to my iPhone no more than 5 minutes prior.
Just in case, I booted into the recovery partition on 10.9.2 and ran permission and disk checks.  When verifying the entire disk however, I got the error "The partition map needs to be repaired because there's a problem with the EFI system partition's file system".
A repair couldn't be done on the live disk so I booted back into OS X and created a recovery USB.  From this, I ran the repairs to the entire disk, and repaired the permissions and disk for my Mac HD partition, and then checked the disk again in the recovery partition and whilst in OS X – the error is no longer registering.
From here – I no longer have access to Bootcamp (natively, or via VMware).  The partition is mounting in Finder, and viewable in Disk Utility.  It even appears in the "Startup Disk" pref pane, however, selecting the partition here just results in a blank screen on boot.
Before I booted into the recovery partition using the "alt" key, the Windows parition was there.  Since that error, it's no longer available.
I've not resized the partition, nor have I changed any disk sizes.
I did, however, run the following commands following the iTunes issue in an attempt to correct:
sudo chmod a+rx /volumes/*
sudo chflags 0 /volumes/*
I understand I can probably remove the partition and start again, but that defeats the point.  Surely there must be a fix through command line or something?
I'm not a computer novice, but this field is a whole new ballpark for me.  I'm googling for answers, but they may as well be in another language – the common notions seem to be a broken GPT or MBR/GPT out of sync.
Below are the results of various terminal commands – maybe someone could analyze and point me in the right direction?
Kind regards and thanks in advance,
Jamie
// sudo gpt -r -vv show disk0
gpt show: disk0: mediasize=500277790720; sectorsize=512; blocks=977105060
gpt show: disk0: PMBR at sector 0
gpt show: disk0: Pri GPT at sector 1
gpt show: disk0: Sec GPT at sector 977105059
      start       size  index  contents
          0          1         PMBR
          1          1         Pri GPT header
          2         32         Pri GPT table
         34          6        
         40     409600      1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
     409640  876953152      2  GPT part - 48465300-0000-11AA-AA11-00306543ECAC
  877362792    1269536      3  GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
  878632328        632        
  878632960   97755136      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
  976388096     716931        
  977105027         32         Sec GPT table
  977105059          1         Sec GPT header
// sudo fdisk /dev/disk0
Disk: /dev/disk0     geometry: 60821/255/63 [977105060 sectors]
Signature: 0xAA55
         Starting       Ending
#: id  cyl  hd sec -  cyl  hd sec [     start -       size]
1: EE 1023 254  63 - 1023 254  63 [         1 -  977105059]
2: 00    0   0   0 -    0   0   0 [         0 -          0] unused     
3: 00    0   0   0 -    0   0   0 [         0 -          0] unused     
4: 00    0   0   0 -    0   0   0 [         0 -          0] unused   
// diskutil list
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.3 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                  Apple_HFS Macintosh HD            449.0 GB   disk0s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
   4:       Microsoft Basic Data Windows HD              50.1 GB    disk0s4

Answer 1

Hi, me again.
When you found the setupact.log file (from the other thread) did you do a search for "detected boot environment"?