Has anyone successfully updated to Windows Creator in bootcamp on a MacMini late 2014?

It is related to the way Creators Update is installed (using a SysPrep), which does not grandfather the already installed/working Intel GPU driver. Once it is uninstalled, it cannot be re-installed under Creators Update. I suggest lodging complaints/bugs with M$. 😉

Unless the installation process is modified, there is no workaround as of now. If you want to try it, download VMware Fusion, create a VM of Anniversary Update, and then upgrade to Creators Update and check the GPU driver version. You can then try a Winclone restore of the VM to the physical partition.

Add me to the list of those who successfully installed WIndows 10 Anniversary (1607) but cannot receive and successfully upgrade to Creators Update. The installation runs for well over half an hour, seems to near completion but Windows setup then reports that it is being rolled back.

Third attempt...failed this morning.

Where can i get that driver? I have 20xxxx verison driver, I downloaded that 15xxxx version you mentioned, but when I install it, it automatically install version 20.19.15.4703, Instead of the one name to the title of the installer. Thanks

Tokion2 wrote:

I just checked Bootcamp.xml in the USB flash drive after re-downloading BC6 latest driver package.

As you mentioned, as far as contents of Bootcamp.xml, the 20.x versions do not exist.

Yes, see my post with details.

Tokion2 wrote:

But, when I run setup.exe in the USB flash drive's BootCamp folder, Intel Display driver becomes the 20.x version.

Setup.exe sees the 20.x version in DrvStore which is the latest. It is irrelevant how it got there in the first place. No amount of setup.exe executions will work to correct it, unless you use pnputil.exe to remove all intel GPU drivers from DrvStore.

This is a W10 problem and how it handles PID/VID when doing updates for a specific product. It should fail with any update which does not have an exact PID/VID match, instead of the partial match mess it currently has. Forced Updates are a mess as well.

See How to stop Windows 7 automatically installing drivers (also valid for W8+/W10). There are many discussions on this specific subject on ASC.

Create 1607-Boot-USB (For the 1607-Iso, I can't help. I created it a long time ago somehow with the MediaCreation-Tool, but I forgot how).

I removed the LAN-Connection

download the media creation tool: https://www.microsoft.com/de-de/software-download/windows10 and place it on the usb stick

the first time the windows setup start, the Partition-Tabel is empty. - close the setup

when the MAC restart, press alt to open the boot-menü

Select EFI-Boot

On Setup i had select win10 home(because i don't have a pro licence), haven't a key (device is registred on MS-Server) and then format the "Bootcamp"-partition and installed it on it.

I Used the Express-Settings

and create a local use with password

i don't use cortana

Install bootcamp

restart

rightclickt on the Start-Button an open the "system"

on the left side "Erweiterte Systemeinstellungen" - Something like "extended system options"

Tab "Hardware" (Device) > Second option "Geräteinstallationseinstellungen" (device installation options)

set to no - don't download automatic drivers.

Tab > "Computerschutz" (Computer Security?)

Create a Restore-Point

Disconnect the second Monitor. I have now only one Monitor with HDMI

copy the media creation tool from the usb-stick and remove the stick

connect the lan, allow network access

start the Media Creation tool from the desktop and update this pc

I changed in the Energieoption, that the Mac never goes to standby and never disable the monitor.

wait - download (about 20%)

hmmm... during download it seems, that it installed a new graphic driver. (Monitor flicker and "new device" sound)

I check the Gerätemanger (DeviceManager) and the Iris-Grafic-Driver was on 20.x. I decided to click on "vorherigen Treiber" (previous driver) and installed again 10.18.15.4240.

This Version is also mention in the Bootcamp.xml (06/16/2015,10.18.15.4240)

I also checked the "Intel Display-Audio" and reset it to the old one (03/31/2015,6.16.00.3174)

again - download...

After downloading I accept the License

And again - download updates....

I got an error-message, that a device (Iris Graphics 5100) is not compatible..... (don't close the Tool!)

I updated the Grafik-Driver....

I installed the Intel-Driver "WIN64_154036.4703.exe" for 15.40.36.64.4703 ( https://downloadcenter.intel.com/download/26984/Graphics-Intel-Graphics-Driver-f or-Windows-15-40-?product=80939 )

And it installed 20.19.15.4703..... (message in the setup-Box), i don't restart.

In the Media-Creation-Tool I select on the small blue text "Ändern der zu behaltenden Elemente" (Change the remain Elements?) and select all -> this should start a rescan.

install.

I Removed the Lan-cabel during install.

And previous-Version is reinstalled....

removed the lan-cabel and restore the system to the old point, I created before.

I planed it..... but the **** UPDATE CLEARED EVERY THING! It changed the Setting from 4% usage of HDD to 0%....

Ok, the tool again downloaded everything..... I stopped here

I Don't think it will work. The driver from the Intel-Page isn't compatible. It will not work.

I think one of this is True:

* In the Beta of MACOS is a diffrent Driver

* There are diffrent Late2014-Macminis (maybe a small CPU-change because it was cheaper to produce?)

* The MacMini with 4709 is a hoax.

Also this is true for my mac:

* The Driver from the Bootcamp is *INCOMPATIBLE* with Win10 beyond 1607.

* Windows will always replace this driver and this one crash

The MacMini Late2014 is not compatible with win10 any more. And at seems, that Apple has no interesst to change it.

This is a known issue, and it is related to the Intel GPU driver. Unless you really need the Creators Update feature, I suggest staying with the Anniversary Update.

This is squarely at the door of Microsoft. 😉

In Japanese language environment, Intel GPU driver version provided by latest Boot camp driver package is 20.19.15.4531.

After updating MacOs to 13.1, i was able to install 1409 direct! It definitiv fix the problem.