Anonymouse is not saying the ISO is at fault in any way but did have the same problem with it from (2) separate ISO downloads of the MAR 2018 [USB 3.0] re-pack.
Each time it was burned to DVD at 6x and an attempt to install it on a virgin Ryzen 1700/ASRock X370 Taichi/RX 560/Samsung 960 EVO/Flair-X DDR4 rig came up with the exact same error;
illegal partition table - drive 02 sector 0
illegal partition table - drive 03 sector 0
illegal partition table - drive 04 sector 0
illegal partition table - drive 05 sector 0
illegal partition table - drive 06 sector 0
Error reading partition table drive 07 sector 0
That's as far as the setup will run attempting to install the OS to the NVMe SSD drive, which isn't even an option at that stage.
An older build of WIN7 worked good, up to the point of formating a drive and injecting needed drivers, so the equipment hardly seems like the problem.
The repack has all the "SP2" (cumulative) updates, which is why Anonymouse is trying to install from it.
Drives 1 & 2 are Lite-On iHAS124-14 ATAPI optical drives.
Drives 3-6 are unformatted Hitachi 2TB SATA III drives
Drive 9 is the Samsung 960 EVO m.2 NVMe (PCI-e) drive
Drive 11 (yes, there is an IDA+SATA II PCI-e adapter card in this rig) is a formated and previously used 1TB Seagate SATA II drive.
IF Anonymouse is understanding those error messages right, 1 DVD burner, all (4) 2TB SATA III drives, & a non-existant Drive 7 are all having partition table error problems.
Unformatted drives is maybe understandable, but an ATAPI drive & a non-existant drive 7 having partition table errors?
Granted it's been several years since Anonymouse retired from the compooter building business, but Ryzen, USB 3.0, & NVMe aren't THAT big of a departure from the AMD 64 X2 with 8 HDDs build this is being sent from.
Injecting drivers during setup goes back to WINNT 4.0 & W2k fer kreist sake & this cheeky virgin does have USB 2.0 ports to inject from and a ready 64GB USB 2.0 stick with all the needed drivers on it.
It's making Anonymouse feel like a n00bie all over again, which is a weird place to find oneself after nearly 2 decades of building and fixing machines for other peeps & surrounded by 6 more at his workstation.
(One each for 9X, W2k, XP, Vista, WIN7, & W10.)
Jist mentioning this issue in case someone wants to investigate it before the next repack comes out, not because any help is needed.