Windows 1809 ISO and Boot Camp Issue

[rolltide4life]

Here is the issue I am currently experiencing: I have downloaded the full ISO of windows 10 1809 tonight
and used it on a flash drive. For some reasons, its forced to format as NTFS that MAC can not read it during
the first boot up screen. it needs to be using FAT32, the big issue here is that install.wim inside the ISO is more than 4.2 GB that fat32 cant support.

Any advice how to workaround this issue?

Thanks for your help!

EDIT:

I used the media tool (https://www.microsoft.com/en-us/software-download/windows10)
to create and install the media (thumb drive) and it is forced to use NTFS instead of FAT32

 

[tsialex]

Here is the issue I am currently experiencing: I have downloaded the full ISO of windows 10 1809 tonight
and used it on a flash drive. For some reasons, its forced to format as NTFS that MAC can not read it during
the first boot up screen. it needs to be using FAT32, the big issue here is that install.wim inside the ISO is more than 4.2 GB that fat32 cant support.

Any advice how to workaround this issue?

Thanks for your help!

EDIT:

I used the media tool (https://www.microsoft.com/en-us/software-download/windows10)
to create and install the media (thumb drive) and it is forced to use NTFS instead of FAT32

For start, don't install Windows 8.1/10 UEFI with an EFI Mac Pro, it's not supported and we have numerous cases of BootROM corruption caused by multiple SecureBoot certificates. Burn a DVD and install as CSM mode.

 

[MisterAndrew]

I burned 1809 to a DVD and it doesn’t want to boot. I suggest if you have a Windows 7 DVD (or 8, or other 10 that boots fine) then install that first. Then install Win 10 1809 from within that. You can use Disk Cleanup to remove the old Windows installation.

 

[Draeconis]

For start, don't install Windows 8.1/10 UEFI with an EFI Mac Pro, it's not supported and we have numerous cases of BootROM corruption caused by multiple SecureBoot certificates. Burn a DVD and install as CSM mode.

What? I’ve used Windows 10 UEFI on my Mac Pro for over 2 years with no issues whatsoever? How does this issue come about?

 

[tsialex]

What? I’ve used Windows 10 UEFI on my Mac Pro for over 2 years with no issues whatsoever? How does this issue come about?

Mac Pro 5,1 is not a UEFI machine, it's EFI. Windows 8.1/10 installed with UEFI mode saves SecureBoot certificates and makes havoc into the NVRAM volume/BootROM.

We found that some Mac Pros got the BootROM corrupted after MP51.0087.B00, some got trouble booting, some become bricks because of UEFI Windows.

Do a BootROM dump and binwalk the dump, if you have multiple SecureBoot certificates, you have a problem.

 

[Project Alice]

Mac Pro 5,1 is not a UEFI machine, it's EFI. Windows 8.1/10 installed with UEFI mode saves SecureBoot certificates and makes havoc into the NVRAM volume/BootROM.

We found that some Mac Pros got the BootROM corrupted after MP51.0087.B00, some got trouble booting, some become bricks because of UEFI Windows.

Do a BootROM dump and binwalk the dump, if you have multiple SecureBoot certificates, you have a problem.

I've never heard of this until now. I've also seen many installations of windows 10 on EFI with 2009+ macs working without an issue.
Apple does support EFI windows in newer models, I think 2012 or so use it automatically.
Windows 10 will work perfectly fine on a 4,1 or 5,1 in EFI mode. If it's a 3,1 or older, use CSM. It wasn't until 2009 when apples EFI implimentation was more compatible. Windows 10 works great in my 2009 MacBook under full EFI mode.
CSM is a HUGE bottleneck for windows 10. Windows will be stuck in IDE emulation mode, and it will boot a lot slower. So if you have a 2009 or newer, don't use CSM.
That aside I'm pretty sure that 1809 was pulled. So go with 1803 if you can.

 

[tsialex]

I've never heard of this until now. I've also seen many installations of windows 10 on EFI with 2009+ macs working without an issue.
Apple does support EFI windows in newer models, I think 2012 or so use it automatically.
Windows 10 will work perfectly fine on a 4,1 or 5,1 in EFI mode. If it's a 3,1 or older, use CSM. It wasn't until 2009 when apples EFI implimentation was more compatible. Windows 10 works great in my 2009 MacBook under full EFI mode.
CSM is a HUGE bottleneck for windows 10. Windows will be stuck in IDE emulation mode, and it will boot a lot slower. So if you have a 2009 or newer, don't use CSM.
That aside I'm pretty sure that 1809 was pulled. So go with 1803 if you can.

Seems you need to follow the BootROM thread, we are talking about this on and off for the last two months since I found the BootROM corruption with multiple SecureBoot certificates…

BTW, Apple never supported UEFI with Mac Pro 5,1.
[doublepost=1542280528][/doublepost]Windows 10 1809 was re-released two days ago: https://support.microsoft.com/en-in/help/4464619/windows-10-update-history

 

[Draeconis]

Mac Pro 5,1 is not a UEFI machine, it's EFI. Windows 8.1/10 installed with UEFI mode saves SecureBoot certificates and makes havoc into the NVRAM volume/BootROM.

We found that some Mac Pros got the BootROM corrupted after MP51.0087.B00, some got trouble booting, some become bricks because of UEFI Windows.

Do a BootROM dump and binwalk the dump, if you have multiple SecureBoot certificates, you have a problem.

Don’t think I’m running that revision. I’ll check later today and post. Was the version that High Sierra launched with.

 

[Jayson A]

I've been running Windows 10 on my Mac Pro 5,1 without a problem. I first installed Windows 7 Pro, and upgraded to Windows 10 from there. That method seems to work the best for me.

 

[tsialex]

I've been running Windows 10 on my Mac Pro 5,1 without a problem. I first installed Windows 7 Pro, and upgraded to Windows 10 from there. That method seems to work the best for me.

Windows 7 installs with CSM mode, so your Windows 10 still runs as it. BootCamp/CSM mode works, UEFI got bricks for lots of people.

 

[Jayson A]

Windows 7 installs with CSM mode, so your Windows 10 still runs as it. BootCamp/CSM mode works, UEFI got bricks for lots of people.

Excuse my ignorance, but what exactly is CSM. Also my Windows 10 partition runs great.

 

[tsialex]

Excuse my ignorance, but what exactly is CSM. Also my Windows 10 partition runs great.

CSM = Compatibility Support Module

Basically a way that permits UEFI OSes to install into BIOS and EFI computers. BootCamp is a CSM for EFI Macs, like MP5,1.

 

[Jayson A]

CSM = Compatibility Support Module

Basically a way that permits UEFI OSes to install into BIOS and EFI computers. BootCamp is a CSM for EFI Macs, like MP5,1.

So basically that's why I always had trouble installing just Windows 10 vs, just installing windows 7 and upgrading afterwards?

 

[tsialex]

So basically that's why I always had trouble installing just Windows 10 vs, just installing windows 7 and upgrading afterwards?

Probably, but maybe your problem could have another cause.

 

[Project Alice]

Seems you need to follow the BootROM thread, we are talking about this on and off for the last two months since I found the BootROM corruption with multiple SecureBoot certificates…

BTW, Apple never supported UEFI with Mac Pro 5,1.
[doublepost=1542280528][/doublepost]Windows 10 1809 was re-released two days ago: https://support.microsoft.com/en-in/help/4464619/windows-10-update-history

I know they didn't, I meant some of the other models 2012? or later did support it.

Anyways, I read through a bit of that thread. That is interesting for sure, and unexpected. I suppose if we were to somehow disable secure boot within windows, it wouldn't do this anymore?

 

[tsialex]

I know they didn't, I meant some of the other models 2012? or later did support it.

Anyways, I read through a bit of that thread. That is interesting for sure, and unexpected. I suppose if we were to somehow disable secure boot within windows, it wouldn't do this anymore?

Mac Pro 5,1, even the 2012, is more a 2009 era Mac than anything. Practically all 2012 Macs support UEFI, some better than others.

With SecureBoot disabled we probably won't have problems, but with UEFI we miss the functionality of StartUp Disk. If you have a Mac EFI GPU, you can live with just boot selector, but people with RX-580 and others will have to use workarounds that for me don't worth the hassle.

 

[PianoPro]

So basically that's why I always had trouble installing just Windows 10 vs, just installing windows 7 and upgrading afterwards?

Just download the Win 10 iso and convert it to a cdr (else it won't boot) with Disk Utility and burn to DVD. It will boot in BIOS Legacy mode just fine and install Win 10 in BIOS legacy mode. You don't even need a video card that supports boot screens to do that. I don't understand why people want to install Win 7 and upgrade. It's such a waste of time.

In the BIOS legacy mode the Startup Disk preference pane will work (if you want to use it), or you can boot Win 10 using a bless script, or one of the Boot Manager apps. And if you install the BootCamp 6 drivers you can use the Bootcamp Control Panel in windows to boot back to an APFS Mojave disk.

 

[crjackson2134]

Just download the Win 10 iso and convert it to a cdr (else it won't boot) with Disk Utility and burn to DVD. It will boot in BIOS Legacy mode just fine and install Win 10 in BIOS legacy mode. You don't even need a video card that supports boot screens to do that. I don't understand why people want to install Win 7 and upgrade. It's such a waste of time.

In the BIOS legacy mode the Startup Disk preference pane will work (if you want to use it), or you can boot Win 10 using a bless script, or one of the Boot Manager apps. And if you install the BootCamp 6 drivers you can use the Bootcamp Control Panel in windows to boot back to an APFS Mojave disk.

This is exactly my process as well, easy peasy most of the time.

 

[bookemdano]

I know they didn't, I meant some of the other models 2012? or later did support it.

Anyways, I read through a bit of that thread. That is interesting for sure, and unexpected. I suppose if we were to somehow disable secure boot within windows, it wouldn't do this anymore?

What's interesting is running msinfo32 from within Windows 10 installed in UEFI mode, it actually said Secure Boot was disabled, which should be correct (since the cMP doesn't support it anyway). So I have no idea why MS tries to place certificate(s) in the cMP's NVRAM.

 

[1151105]

anyone manage to get this working?

Just download the Win 10 iso and convert it to a cdr (else it won't boot) with Disk Utility and burn to DVD. It will boot in BIOS Legacy mode just fine and install Win 10 in BIOS legacy mode. You don't even need a video card that supports boot screens to do that. I don't understand why people want to install Win 7 and upgrade. It's such a waste of time.

In the BIOS legacy mode the Startup Disk preference pane will work (if you want to use it), or you can boot Win 10 using a bless script, or one of the Boot Manager apps. And if you install the BootCamp 6 drivers you can use the Bootcamp Control Panel in windows to boot back to an APFS Mojave disk.

how did you go about making the cdr file? [the 1809 file is too big for a standard dvd]

has anyone tried installing windows in another windows box and then moving the SSD to the mac pro?

i haven't been able to install windows for about 8 months now. i've tried pretty much everything. if anybody could provide any assistance that'd be great. i'm on the 2009 upgraded to 5,1 using high sierra [MP51.0089.B00].
tomorrow i will install a pulse 580 and try to install mojave and 141 [or whatever we're at right now]. maybe that'll help?

 

[PianoPro]

anyone manage to get this working?

how did you go about making the cdr file? [the 1809 file is too big for a standard dvd]

I can't believe how many WRONG ways I found on the internet. As I said you MUST convert an iso to a cdr if you want to use Disk Utility to create a bootable DVD. Here's the correct procedure:

(Just double click the iso to open it in the left column of Disk Utility. Then choose Convert and proceed as described below. Do NOT burn the iso. That will NOT boot. )

https://discussions.apple.com/thread/5132196

 

[saulinpa]

I've found the latest 1809 distribution to be buggy. Starting with the fact that it won't fit on a standard DVD. Go back to the 1803 distribution and most problems go away. Then upgrade to 1809 through the normal upgrade when it gets pushed out.

 

[Synchro3]

I've found the latest 1809 distribution to be buggy. Starting with the fact that it won't fit on a standard DVD. Go back to the 1803 distribution and most problems go away. Then upgrade to 1809 through the normal upgrade when it gets pushed out.

The Windows 1809.ISO I downloaded last week did fit on a DVD. I burned it with the CloneCD application on a DVD.

4’091’936’768 Byte.

 

[saulinpa]

The Windows 1809.ISO I downloaded last week did fit on a DVD. I burned it with the CloneCD application on a DVD.

4’091’936’768 Byte.

More reasons to hate Windows. My download was 5030264832 Nov 14 05:26 Win10_1809Oct_English_x64.iso

 

[bookemdano]

More reasons to hate Windows. My download was 5030264832 Nov 14 05:26 Win10_1809Oct_English_x64.iso

I wonder why the discrepancy? Was your ISO of the original release in October or the re-release in November? What page did you dl from?