These are unusual, immediately on boot from hard disk:
00:00:05.897233 PIIX3 ATA: LUN#0: disk write error (rc=VERR_WRITE_PROTECT iSector=0xa4d8 cSectors=0x1)
00:00:05.897438 VMMDev: Guest Log: BIOS: int13_harddisk_ext: function 43, error 06 !
00:00:05.897478 PIIX3 ATA: LUN#0: disk write error (rc=VERR_WRITE_PROTECT iSector=0xa4d8 cSectors=0x1)
00:00:05.897662 VMMDev: Guest Log: BIOS: int13_harddisk_ext: function 43, error 06 !
00:00:05.897698 PIIX3 ATA: LUN#0: disk write error (rc=VERR_WRITE_PROTECT iSector=0xa4d8 cSectors=0x1)
00:00:05.897881 VMMDev: Guest Log: BIOS: int13_harddisk_ext: function 43, error 06 !
00:00:06.647656 PIIX3 ATA: LUN#0: disk write error (rc=VERR_WRITE_PROTECT iSector=0x3b7af504 cSectors=0x1)
00:00:06.647857 VMMDev: Guest Log: BIOS: int13_harddisk_ext: function 43, error 06 !
00:00:06.647906 PIIX3 ATA: LUN#0: disk write error (rc=VERR_WRITE_PROTECT iSector=0x3b7af504 cSectors=0x1)
00:00:06.648091 VMMDev: Guest Log: BIOS: int13_harddisk_ext: function 43, error 06 !
00:00:06.648135 PIIX3 ATA: LUN#0: disk write error (rc=VERR_WRITE_PROTECT iSector=0x3b7af504 cSectors=0x1)
00:00:06.648328 VMMDev: Guest Log: BIOS: int13_harddisk_ext: function 43, error 06 !
...
00:00:39.667979 PIIX3 ATA: LUN#0: disk write error (rc=VERR_WRITE_PROTECT iSector=0x32800 cSectors=0x10)
00:00:44.668754 PIIX3 ATA: LUN#0: disk write error (rc=VERR_WRITE_PROTECT iSector=0x32800 cSectors=0x10)
00:00:49.663254 PIIX3 ATA: LUN#0: disk write error (rc=VERR_WRITE_PROTECT iSector=0x32800 cSectors=0x10)
00:00:54.663486 PIIX3 ATA: LUN#0: disk write error (rc=VERR_WRITE_PROTECT iSector=0x32800 cSectors=0x10)
00:00:59.664011 PIIX3 ATA: LUN#0: disk write error (rc=VERR_WRITE_PROTECT iSector=0x32800 cSectors=0x10)
00:01:04.663095 PIIX3 ATA: LUN#0: disk write error (rc=VERR_WRITE_PROTECT iSector=0x32800 cSectors=0x10)
00:01:09.662972 PIIX3 ATA: LUN#0: disk write error (rc=VERR_WRITE_PROTECT iSector=0x32800 cSectors=0x10)
00:01:14.663656 PIIX3 ATA: LUN#0: disk write error (rc=VERR_WRITE_PROTECT iSector=0x32800 cSectors=0x10)
00:01:19.663654 PIIX3 ATA: LUN#0: disk write error (rc=VERR_WRITE_PROTECT iSector=0x32800 cSectors=0x10)
00:01:19.680606 PIIX3 ATA: LUN#0: disk write error (rc=VERR_WRITE_PROTECT iSector=0x5e7970 cSectors=0x8)
00:01:24.679443 PIIX3 ATA: LUN#0: disk write error (rc=VERR_WRITE_PROTECT iSector=0x5e7970 cSectors=0x8)
00:01:29.678874 PIIX3 ATA: LUN#0: disk write error (rc=VERR_WRITE_PROTECT iSector=0x5e7970 cSectors=0x8)
I see that the primary hard disk is a VMDK located at 'C:\Users\PAULD\VirtualBox VMs\PAULD\PAULD.vmdk'.
Windows will not tolerate a read only boot drive.
That is a strange scattering of sector numbers. Is this a raw disk access scenario? [Edit: reviewing the first post, I see that it is. That makes this a rather standard permissions problem with raw access under Win7 and later:
viewtopic.php?f=6&t=38914#p175089. ]
I suggest that you try cloning the VMDK to a VDI. That will eliminate a number of ??? concerning that VMDK. Alternatively (more work, but much more likely to be successful), image the drive using Macrium Reflect Free, and the "restore" the image into a blank VM. Macrium has the ability to make smart images (i.e. ignoring unused sectors). I think it will also cope with a different target drive size, e.g. if you want to make it smaller.