Windows 1809 ISO and Boot Camp Issue

[saulinpa]

I got my ISO from the official Microsoft download page - was the re-release last week. English 64-bit. The one page did say that some images require a DL DVD so I didn't think anything was wrong. I can boot and install Windows from it. I will try again to see if it comes through as a different size.
[doublepost=1542745782][/doublepost]Went to Microsoft's page again and the file to download was still the bigger 4.7GB
Went to Microsoft's page using Microsoft Edge - it downloaded an installer first then gave me a 4GB file but with a different size and name than you have.

5030264832 Nov 14 05:26 Win10_1809Oct_English_x64.iso
4068671488 Nov 20 15:12 Windows.iso​

Both have file dates from 10/29. First has times of 7:45PM and 7:49PM. Second has times of 7:32PM and 7:47PM.

It is Microsoft. Nothing else to say.

 

[Synchro3]

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

Here is my ISO (64 Bit): 'Deleted'

 

[bookemdano]

I got my ISO from the official Microsoft download page - was the re-release last week. English 64-bit. The one page did say that some images require a DL DVD so I didn't think anything was wrong. I can boot and install Windows from it. I will try again to see if it comes through as a different size.
[doublepost=1542745782][/doublepost]Went to Microsoft's page again and the file to download was still the bigger 4.7GB
Went to Microsoft's page using Microsoft Edge - it downloaded an installer first then gave me a 4GB file but with a different size and name than you have.

5030264832 Nov 14 05:26 Win10_1809Oct_English_x64.iso
4068671488 Nov 20 15:12 Windows.iso​

Both have file dates from 10/29. First has times of 7:45PM and 7:49PM. Second has times of 7:32PM and 7:47PM.

It is Microsoft. Nothing else to say.

Yeah super weird. I just went to the Win10 Download page (https://www.microsoft.com/en-us/software-download/windows10ISO) and downloaded the x64 English ISO (Win10_1809Oct_English_x64.iso). File size: 5075539968

 

[Squuiid]

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.

This seems to be related to MP51.0087.B00 firmware or injected microcode modified firmware only. I cannot find any evidence of anyone getting a brick on any other ‘vanilla’ firmware.
Please correct me if I am wrong but I think we need to be cautious of spreading FUD.

As I have mentioned before I, and many others, have been running Windows 10 in UEFI mode since it was released and have upgraded both firmware and OS over the past few years without issue.
And yes, I was fortunate enough to skip MP51.0087.B00 and did not manually inject any microcodes into my firmware.

 

[tsialex]

This seems to be related to MP51.0087.B00 firmware or injected microcode modified firmware only. I cannot find any evidence of anyone getting a brick on any other ‘vanilla’ firmware.
Please correct me if I am wrong but I think we need to be cautious of spreading FUD.

As I have mentioned before I, and many others, have been running Windows 10 in UEFI mode since it was released and have upgraded both firmware and OS over the past few years without issue.
And yes, I was fortunate enough to skip MP51.0087.B00 and did not manually inject any microcodes into my firmware.

Seems you and I have different opinions about this. You think that because you never had a problem, it's safe, but I'm seeing various BootROMs with all sort of problems into the NVRAM volume and every time has a SecureBoot certificate inside.

I don't have enough data to affirm that is Windows installed into UEFI that causes this, but for know it's a possible probability and everyday I'm getting more data about this. Maybe I can confirm this in the future, maybe not, but Apple never supported Windows installed into UEFI mode with Mac Pro 5,1.

 

[Speedstar]

Ok so far, I tried to install Efi-64-win10 on my SSD in bay4 (other MacOS drives disconnected)
It quits setup with 0xc0000005 error on ntfs formatted partition
SSD Crucial CT525MX

GPT 200MB
NTFS 250GB (empty for win 10)
Bootcamp250GB (working win7 winclone )

I tried to format with Win10DVD-advanced options
And I tried to format with
Paragon Manager, and Tuxera NTFS,
In all cases win10efi refused to install either GPT or mixed GPT+MBR

Now my question
Can EFI and CMS/legacy boot
Coexist on one Drive ?
Can I install 2 different versions of Windows 7/10 on one GPT hard disk and
if I can how to boot them with Mac alt-key boot manager?
Booting last partition and jump via boot.ini to second partition win10?

My rig McP 5.1 2012 with
Efi GTX Evga 680 ME.
3 Raid toshibas
1 SSD
Boot-ROM 140.0.0
From MacOS 14.1

Ideal - way would be to
Choose between w10 and w7
With alt-key without lilo or eRfi

Is there a way ?

 

[Squuiid]

SSD Crucial CT525MX

That’s a Crucial MX300 drive, correct?
What firmware version is it on?
Those things are buggy as hell if not running the latest version.
Could definitely be a big part of your problem here.
Update here:

http://www.crucial.com/usa/en/support-ssd-firmware

 

[DearthnVader]

Ok so far, I tried to install Efi-64-win10 on my SSD in bay4 (other MacOS drives disconnected)
It quits setup with 0xc0000005 error on ntfs formatted partition
SSD Crucial CT525MX

GPT 200MB
NTFS 250GB (empty for win 10)
Bootcamp250GB (working win7 winclone )

I tried to format with Win10DVD-advanced options
And I tried to format with
Paragon Manager, and Tuxera NTFS,
In all cases win10efi refused to install either GPT or mixed GPT+MBR

Now my question
Can EFI and CMS/legacy boot
Coexist on one Drive ?
Can I install 2 different versions of Windows 7/10 on one GPT hard disk and
if I can how to boot them with Mac alt-key boot manager?
Booting last partition and jump via boot.ini to second partition win10?

My rig McP 5.1 2012 with
Efi GTX Evga 680 ME.
3 Raid toshibas
1 SSD
Boot-ROM 140.0.0
From MacOS 14.1

Ideal - way would be to
Choose between w10 and w7
With alt-key without lilo or eRfi

Is there a way ?

Installing Windows via Bootcamp converts a GPT disk, to a Hybrid MBR GPT disk, that's likely your issue, I don't think the Windows 10 installer knows how to handle Hybrid disks.

 

[Speedstar]

I managed to install Windows seven in last partition Mult-GPT-mbr, boot it on bootcamp , format first visible partition (second after Efi ) via Windows 7 to ntfs and install win10 legacy mbr NOT EFI on first visible partition primary.(formatted in win 7 as primary ntfs)

Now I have two windows versions on one SSD drive they are bootable via metro boot manager that I can choose between windows 10 and seven , in EFi-(alt key menu I just can choose one bootcamp partition )

Now my problem paragon ntfs Hides these boot partitions in preference pane .

Again I choose boot camp then my first partition starts with an boot menu and there I can choose which windows version

No Fisk or gpart pain

 

[1151105]

ummm, i just checked sys info on my win10 install and it says my BIOS mode is uefi... except i installed using the DVD. does anyone know why this is?
and can someone please point to the binwalk tut/walkthrough? having trouble finding it...

 

[bookemdano]

ummm, i just checked sys info on my win10 install and it says my BIOS mode is uefi... except i installed using the DVD. does anyone know why this is?
and can someone please point to the binwalk tut/walkthrough? having trouble finding it...

You need to hold the "c" key when you hear the boot chime--that should boot the DVD in legacy BIOS mode, which will install Win10 in the same mode.

 

[1151105]

You need to hold the "c" key when you hear the boot chime--that should boot the DVD in legacy BIOS mode, which will install Win10 in the same mode.

hrrmmm, is there a way to tell if this has worked or not before you start installing? because i am certain i was pressing c when i did it.

since i have efi installed, when were people experiencing the bricks? just one day it randomly stopped working?

 

[bookemdano]

hrrmmm, is there a way to tell if this has worked or not before you start installing? because i am certain i was pressing c when i did it.

since i have efi installed, when were people experiencing the bricks? just one day it randomly stopped working?

Maybe someone else knows a better way, but my observation is that when booting in legacy mode the resolution of the Windows boot logo screen is lower than it is when booting in EFI mode. That could just be my vid card/monitor though.

 

[Speedstar]

When installed in uefi I heard there might be or are serious problems with certificates (microkernelupdate) which load into vram.
And the boot camp control penal in Windows can not boot into uefi installations.

But how to install Windows 10 into a SSD-module on PCIe NVme card ? It is external "yellow" icon in Mac boot menu screen/ boot-picker so it is impossible to make Boot Camp on it with legacy compatibility mode ???

 

[1151105]

When installed in uefi I heard there might be or are serious problems with certificates (microkernelupdate) which load into vram.
And the boot camp control penal in Windows can not boot into uefi installations.

But how to install Windows 10 into a SSD-module on PCIe NVme card ? It is external "yellow" icon in Mac boot menu screen/ boot-picker so it is impossible to make Boot Camp on it with legacy compatibility mode ???

I am currently going through this right now. you can lok through my posts to see what I've tried.
I'm thinking its a problem with initialization in the win installer, or the drive isn't supported [mioght have to try a Samsung]
what nvme are you trying to install?

 

[Jayson A]

When installed in uefi I heard there might be or are serious problems with certificates (microkernelupdate) which load into vram.
And the boot camp control penal in Windows can not boot into uefi installations.

But how to install Windows 10 into a SSD-module on PCIe NVme card ? It is external "yellow" icon in Mac boot menu screen/ boot-picker so it is impossible to make Boot Camp on it with legacy compatibility mode ???

You cannot boot from PICe cards unfortunately with Windows. I’ve tried many times. Also, even if my Mac drive is on PCIe, I still have problems booting into Windows. I finally figured out that it was the PCIe SATA 3 adapter I was using and when I got rid of it, everything worked seamlessly

 

[1151105]

You cannot boot from PICe cards unfortunately with Windows. I’ve tried many times. Also, even if my Mac drive is on PCIe, I still have problems booting into Windows. I finally figured out that it was the PCIe SATA 3 adapter I was using and when I got rid of it, everything worked seamlessly

i was able to boot into win10 no problem when it was EFI on the nvme. but i couldn't use bootcamp to switch so i tried osx on the nvme and legacy on the ssd. i can boot into either no problem. but i still have the switching problem
managed to install BC on win10, but it doesn't recognize the osx install

wouldn't it be nice to just be able to load grub or something and just boot all 3 systems from there?

 

[Spacedust]

You cannot boot from PICe cards unfortunately with Windows. I’ve tried many times. Also, even if my Mac drive is on PCIe, I still have problems booting into Windows. I finally figured out that it was the PCIe SATA 3 adapter I was using and when I got rid of it, everything worked seamlessly

I'm running a PCIe card for Windows 7 and it boots great with 16 GB SSD for just boot manager.

 

[bookemdano]

i was able to boot into win10 no problem when it was EFI on the nvme. but i couldn't use bootcamp to switch so i tried osx on the nvme and legacy on the ssd. i can boot into either no problem. but i still have the switching problem
managed to install BC on win10, but it doesn't recognize the osx install

wouldn't it be nice to just be able to load grub or something and just boot all 3 systems from there?

I have the exact same setup (Mojave on nvme and Win10 Legacy on SATA SSD) with no issues switching back and forth. To be able to switch back to Mojave from Win10 you must use Boot Camp 6.1 from the iMac Pro (and maybe other brand-new models). You can get the iMac Pro specific package by using Brigadier. If you have any earlier version installed than that version it will not see your APFS-formatted Mojave drive.

 

[1151105]

I have the exact same setup (Mojave on nvme and Win10 Legacy on SATA SSD) with no issues switching back and forth. To be able to switch back to Mojave from Win10 you must use Boot Camp 6.1 from the iMac Pro (and maybe other brand-new models). You can get the iMac Pro specific package by using Brigadier. If you have any earlier version installed than that version it will not see your APFS-formatted Mojave drive.

when you were using brigadier, were there any long pauses for you? i type in the first command and it says its downloading then it just sat there for 30mins before i pressed ctrl-c. then it seemed to resume but crashed trying to install 7-up and had no files in the download folder.
[doublepost=1543361300][/doublepost]i think i found the issue. when using terminal if you click on the screen it pauses whatever it was executing [that is the behaviour mine is showing].

in any case the files did not download the first two times i did it and it is now working. sooo, thanks for your patience and help!

 

[Jayson A]

I'm running a PCIe card for Windows 7 and it boots great with 16 GB SSD for just boot manager.

After fighting with it for so long and wondering why sometimes my computer just wouldn't boot into Windows, I finally just took out the PCIe SATA adapter and everything went back to normal. Haven't had an issue booting since.

Edit: After doing some research, I realized that the PCIe adapter I was using had a warning that it will not work with boot camp. https://eshop.macsales.com/item/OWC...Vg4TICh2NMQcMEAQYASABEgKwkPD_BwE&gclsrc=aw.ds "Not compatible as a Windows boot drive on a Mac"

Even though, I was using Windows on a normal drive and the macOS installation was on the PCIe card, I still had Windows boot issues. Sometimes it would boot, sometimes it would simply freeze. Taking out the adapter was the only thing that worked.

 

[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.

Apparently I'm running MP51.88Z.0084.B00.170808058, which looks like it's older than the revision you mention.

 

[hknatm]

There is a post here to make pcie adapter as internal with a kext. I did it. Tried to install win10 with bootcamp, it worked. But after that i cant reboot it. It stucks at bsod.

I had MP 4.1 > 5.1
Flashed gtx680 for mac

I came up with this uefi not compatible thing now. Will try to install with dvd.

I have kingston predator 960gb . I am thinking i may have trouble with pcie ssd’s firmware problem maybe that is why i can not boot afterwards. Will frsh install and try to check firmware and will install bootcamp 6.1

 

[thornslack]

I run win 10 uefi on a sata6 ssd mounted on an apricorn solo x2 pcie sled without issue. Be aware that if you run OS X in soft raid it will crash windows however.

 

[hknatm]

I run win 10 uefi on a sata6 ssd mounted on an apricorn solo x2 pcie sled without issue. Be aware that if you run OS X in soft raid it will crash windows however.

Then normally mine should work. Will dig into it. Someone suggested me a tutorial. Will try it. And download a proper version from microsoft.