'Install or remove windows 7 or later version' option greyed out

Repairing the partition map might erase disk0s1, proceed? (y/N) y

Started partition map repair on disk0

Checking prerequisites

Checking the partition list

Adjusting partition map to fit whole disk as required

Checking for an EFI system partition

Checking the EFI system partition's size

Checking the EFI system partition's file system

Checking the EFI system partition's folder content

Checking all HFS data partition loader spaces

Checking booter partitions

Reviewing boot support loaders

Checking Core Storage Physical Volume partitions

The partition map appears to be OK

Finished partition map repair on disk0

** Checking volume.

** Checking the container superblock.

** Checking the EFI jumpstart record.

** Checking the space manager.

** Checking the object map.

** Checking the APFS volume superblock.

** Checking the object map.

** Checking the fsroot tree.

** Checking the snapshot metadata tree.

** Checking the extent ref tree.

** Checking the snapshots.

** Checking the APFS volume superblock.

** Checking the object map.

** Checking the fsroot tree.

** Checking the snapshot metadata tree.

** Checking the extent ref tree.

** Checking the snapshots.

** Checking the APFS volume superblock.

** Checking the object map.

** Checking the fsroot tree.

** Checking the snapshot metadata tree.

** Checking the extent ref tree.

** Checking the snapshots.

** Checking the APFS volume superblock.

** Checking the object map.

** Checking the fsroot tree.

** Checking the snapshot metadata tree.

** Checking the extent ref tree.

** Checking the snapshots.

** Verifying allocated space.

** The volume /dev/rdisk1 appears to be OK.

Started APFS operation

Aligning shrink delta to 36,123,070,464 bytes and targeting a new physical store size of 84,999,999,488 bytes

Determined the minimum size for the targeted physical store of this APFS Container to be 39,182,127,104 bytes

Resizing APFS Container designated by APFS Container Reference disk1

The specific APFS Physical Store being resized is disk0s2

Verifying storage system

Using live mode

Performing fsck_apfs -n -x -l /dev/disk0s2

Checking volume

Checking the container superblock

Checking the EFI jumpstart record

Checking the space manager

Checking the object map

Checking the APFS volume superblock

Checking the object map

Checking the fsroot tree

Checking the snapshot metadata tree

Checking the extent ref tree

Checking the snapshots

Checking the APFS volume superblock

Checking the object map

Checking the fsroot tree

Checking the snapshot metadata tree

Checking the extent ref tree

Checking the snapshots

Checking the APFS volume superblock

Checking the object map

Checking the fsroot tree

Checking the snapshot metadata tree

Checking the extent ref tree

Checking the snapshots

Checking the APFS volume superblock

Checking the object map

Checking the fsroot tree

Checking the snapshot metadata tree

Checking the extent ref tree

Checking the snapshots

Verifying allocated space

The volume /dev/disk0s2 appears to be OK

Storage system check exit code is 0

Shrinking APFS Physical Store disk0s2 from 121,123,069,952 to 84,999,999,488 bytes

Shrinking APFS data structures

Shrinking partition

Modifying partition map

4096 bytes per physical sector

/dev/rdisk0s3: 70532224 sectors in 1102066 FAT32 clusters (32768 bytes/cluster)

bps=512 spc=64 res=32 nft=2 mid=0xf8 spt=32 hds=255 hid=166426624 drv=0x80 bsec=70549504 bspf=8616 rdcl=2 infs=1 bkbs=6

Mounting disk

1 new disk created or changed due to APFS operation

Disk from APFS operation: disk0s3

Finished APFS operation

/dev/disk0 (internal, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *121.3 GB
disk0

1: EFI EFI 209.7 MB
disk0s1

2: Apple_APFS Container disk1 85.0 GB disk0s2

3: Microsoft Basic Data BOOTCAMP 36.1 GB disk0s3

/dev/disk1 (synthesized):

#: TYPE NAME SIZE IDENTIFIER

0: APFS Container Scheme - +85.0 GB disk1

Physical Store disk0s2

1: APFS Volume Mac 34.9 GB disk1s1

2: APFS Volume Preboot 38.0 MB disk1s2

3: APFS Volume Recovery 519.0 MB
disk1s3

4: APFS Volume VM 2.1 GB disk1s4

/dev/disk2 (external, physical):

#: TYPE NAME SIZE IDENTIFIER

0: FDisk_partition_scheme *8.0 GB disk2

1: DOS_FAT_32 WININSTALL 8.0 GB disk2s1

/dev/disk3 (disk image):

#: TYPE NAME SIZE IDENTIFIER

0: CCCOMA_X64FRE_EN-US... +4.7 GB disk3

/dev/disk4 (disk image):

#: TYPE NAME SIZE IDENTIFIER

0: Boot Camp +2.8 GB disk4

Do I now boot in EFI Boot and check if it works?

The installation was complete, and it said to restart. I clicked restart now, and it showed the windows logo, then the screen turned black. This happened before, and I have a video and another explanation here: high sierra - Bootcamp: Black screen shows after windows 10 installation - Ask Different

I disconnected from the WiFi, and reinstalled W10, and it showed something about volume 4 and windows 10, but I didn’t see it, because it didn’t let me choose. It then switched to a blank screen again, and after a couple minutes, it showed the windows logo, then turned to a blank screen again.

/dev/disk0 (internal, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *121.3 GB
disk0

1: EFI EFI 209.7 MB
disk0s1

2: Apple_APFS Container disk1 80.0 GB disk0s2

3: Microsoft Basic Data 41.1 GB disk0s3

/dev/disk1 (synthesized):

#: TYPE NAME SIZE IDENTIFIER

0: APFS Container Scheme - +80.0 GB disk1

Physical Store disk0s2

1: APFS Volume Mac 31.5 GB disk1s1

2: APFS Volume Preboot 38.0 MB disk1s2

3: APFS Volume Recovery 519.0 MB
disk1s3

4: APFS Volume VM 1.1 GB disk1s4

/dev/disk2 (external, physical):

#: TYPE NAME SIZE IDENTIFIER

0: FDisk_partition_scheme *8.0 GB disk2

1: DOS_FAT_32 WININSTALL 8.0 GB disk2s1

Loner T wrote:

Which implies that Windows installer is providing a bad GPU driver.

I did turn off my wifi, unless I'm supposed to do something else.

Loner T wrote:

I assume the reboot to start the Windows installer, not the completion of Windows installation, correct?

Wait, what? The black screen showed after it asked to restart the computer, also after the W10 said it restarted, and after the windows logo showed up a second time to start up the computer.

Loner T wrote:

Do you have a Time Machine backup of your macOS installation?

Um, if you mean a backup of my mac version of the computer on Time Machine, then yes. But what do you mean by backup of my macOS installation?

-rwxr-xr-x
1 *name*
staff
5875479 Jul 16
2016 setupapi.offline.20160716_044743.log

-rwxr-xr-x
2 *name*
staff
176958 Jul 17
2018 setupapi.offline.log

-rwxr-xr-x
2 *name*
staff
237439 Jul 17
2018 setupapi.setup.log

I looked at it, and its giant. I see something about installing drivers, class installers, and a bunch of other stuff. I used cmd + f and searched gpu, no results. Searching Intel came up with Intel WiDi Audio Device and

dvi: DevDesc - Intel(R) HD Graphics 5000

dvi: Description - [Intel(R) HD Graphics 5000]

In that section, there are these errors:

Device class {4d36e968-e325-11ce-bfc1-08002be10318} is not configurable.

Driver list already built

DeleteFile: FAILED!

Error 2: The system cannot find the file specified.