Black screen when trying to install Windows 10 w/ Bootcamp

Question

Level 1

13 points

Black screen when trying to install Windows 10 w/ Bootcamp

I seem to be running into a problem installing Windows 10 on my MacBook Pro 13,3.

Using the official Windows 10 1803 ISO from Microsoft, I run Bootcamp on macOS perfectly fine. The hard drive gets partitioned, the Windows support software downloads perfectly normal, and the computer restarts. It takes me through the whole Windows installation process, and then restarts again. This is where I run into problems.

After I go through the Windows installation and the computer restarts, I boot back up to get a lit black screen. The Windows mouse cursor is showing and can be moved around, but resets to the middle of the screen every couple seconds or so, as if stuck in a loop of some sort. I did not get into Windows 10 at all yet. The computer went from the Windows 10 installation, to reboot, to black lit-up screen with the Windows cursor that resets every couple of seconds.

When going into startup manager, there are two drives named "Windows" and the normal "Macintosh HD" drive. One of the Windows drives takes me back to the black lit-up screen, and the other takes me back into the Windows installation process, which immediately freezes upon starting up.

Here is some info on my system:

Macbook Pro 13,3 (15", Late 2016)

macOS High Sierra 10.13.5

Bootcamp 6.1.0

SSD: APPLE SSD SM0512L 500 GB

GPU: Radeon Pro 460 4 GB

Trying to install Windows 10 1803

Any help in getting Windows 10 working would be appreciated.

MacBook Pro (15-inch, Late 2016), macOS High Sierra (10.13.5)

Posted on Jul 2, 2018 5:48 PM

Reply

Answer 1

Loner T

Level 9

59,536 points

Jul 3, 2018 9:00 PM in response to Nunnuh

Looks clean.

Do you have access to a PC? If yes, can you use Windows Media Creation Tool to create a USB installer. Once the regular installation fails, without deleting the existing partition, connect this USB, and reboot and hold Alt/Option, select EFI Boot from the USB, and select the existing BC partition, and try to install Windows.

Reply

Answer 2

Loner T

Level 9

59,536 points

Jul 4, 2018 5:55 AM in response to Nunnuh

Can you use W10 1607 instead of 1803 and test?

Reply

Answer 3

Loner T

Level 9

59,536 points

Jul 3, 2018 4:28 AM in response to Nunnuh

You seem to have a bad AMD GPU driver. If the first restart is causing problems, I suggest you download AMD drivers from bootcampdrivers.com and install them before the BC drivers are installed.

Reply

Answer 4

Loner T

Level 9

59,536 points

Jul 3, 2018 4:06 PM in response to Nunnuh

I suggest installing W10 1607, but run a SMC/NVRAM Reset before you do.

Reply

Answer 5

Loner T

Level 9

59,536 points

Jul 3, 2018 5:18 PM in response to Nunnuh

Nunnuh wrote:

The MD5sum in Terminal resulted in:

MD5 (/Users/[My Username]/Downloads/en_Windows_10_1607_build_14393_x64_dvd.iso) = 88b98698600511dcd69596df92b242e5

The MD5sum I have is

openssl md5 Win10_1607_English_x64.iso

MD5(Win10_1607_English_x64.iso)= 88b98698600511dcd69596df92b242e5

which matches. Your ISO seems to be fine.

From macOS Terminal, can you post the output of

diskutil list

Reply

Answer 6

Loner T

Level 9

59,536 points

Jul 3, 2018 5:55 PM in response to Nunnuh

You currently have disk0s1, 0s2 and 0s4. If you reboot, do you have the same sequence? Is/was there an OSXRESERVED partition on Disk?

Do you get an error, if you run BCA and click on Remove/Restore? If you choose to remove the BC partition, can you run

diskutil repairDisk disk0

and post the output.

Reply

Answer 7

Loner T

Level 9

59,536 points

Jul 3, 2018 6:11 PM in response to Nunnuh

Run

diskutil mount disk0s1

This will mount the EFI partition. In Finder, look at this volume and check if there is a Microsoft directory.

Reply

Answer 8

Loner T

Level 9

59,536 points

Jul 3, 2018 7:56 PM in response to Nunnuh

Run

sudo fsck_apfs -n -l /dev/rdisk1

and post the output.

Reply

Answer 9

Loner T

Level 9

59,536 points

Jul 4, 2018 1:37 PM in response to Nunnuh

Let us install it without the AMD drivers first. Windows should use the Generic VGA driver, which will make your screen look abnormal in terms of size and fonts.

Reply

Answer 10

Loner T

Level 9

59,536 points

Jul 4, 2018 8:14 AM in response to Nunnuh

Look for a file called setupapi.dev.log in the Windows (or folders under it). It has a lot of information. You are only looking for errors. You do not need to post the contents of logs, but a few lines of errors are all we need to look at.

Reply

Answer 11

Loner T

Level 9

59,536 points

Jul 3, 2018 4:47 PM in response to Nunnuh

If you are using a W10 ISO, can you post the name of the file and it's MD5sum?

Reply

Answer 12

Loner T

Level 9

59,536 points

Jul 4, 2018 9:27 AM in response to Nunnuh

See Build your own Windows 10 Bootcamp USB Installer .

Reply

Answer 13

Loner T

Level 9

59,536 points

Jul 3, 2018 2:06 PM in response to Nunnuh

You will need to download the driver to a USB2 flash drive. You should be prompted for the BC drivers installation. Leave it at the prompt, install the other driver and then allow the BC driver installation to run.

Reply

Answer 14

Nunnuh Author

Level 1

13 points

Jul 4, 2018 7:40 AM in response to Loner T

I attempted to install W10 1607 w/ Boot Camp, and after the Windows setup, got the same "CRITICAL_PROCESS_DIED" that usually results from that ISO.

I then booted into the EFI Boot USB and attempted to install W10 from the USB. This resulted in the lit-up black screen that usually results from W10 1803. Windows repair tools didn't help. I tried installing again from the USB, but with formatting the BOOTCAMP drive in the Windows setup before the install. Same result, a black lit-up screen.

Reply

Answer 15

Nunnuh Author

Level 1

13 points

Jul 4, 2018 8:48 AM in response to Loner T

Actually, I did find an error in setupapi.offline.20160716_044743.log. Here is what it says:

! sto: Device class {5175d334-c371-4806-b3ba-71fd53c9258d} does not exist. Error = 0x00000002

inf: Error Control = 1

inf: Error Control = 0

inf: Error Control = 1

inf: Error Control = 0

inf: Error Control = 1

inf: Error Control = 0

inf: Error Control = 1

inf: Error Control = 0

inf: Error Control = 1

! sto: Device class {5175d334-c371-4806-b3ba-71fd53c9258d} does not exist. Error = 0x00000002

inf: Error Control = 1

sto: Unable to unload hive key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}d:/rs1.bin.amd64fre.dep/mergedcomponents /images/staged/client/Starter/Windows/System32/config/SYSTEM' loaded by another process. Error = 0x00000005, Time = 0 ms

sto: Unable to unload hive key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}d:/rs1.bin.amd64fre.dep/mergedcomponents /images/staged/client/Starter/Windows/System32/config/SOFTWARE' loaded by another process. Error = 0x00000005, Time = 0 ms

sto: Unable to unload hive key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}d:/rs1.bin.amd64fre.dep/mergedcomponents /images/staged/client/Starter/Windows/System32/config/DRIVERS' loaded by another process. Error = 0x00000005, Time = 0 ms

Reply

Black screen when trying to install Windows 10 w/ Bootcamp

Similar questions