Best method to upgrade Boot Camp partition from Windows 7 to Windows 10? Intel HD Graphics 4000 incompatibility?

Disk Utility calls it "MacOS Extended (Journaled)", but I know it's HFS+, with the GUID partitioning scheme. OS is 10.12.6 Sierra. There are no SSDs in my system - all spinners.

Thanks yet again - your advice has been invaluable during this process.

And there's more...

In terminal, I entered "diskutil list" and got:

/dev/disk0 (internal, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *1.0 TB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_HFS My Mini 780.0 GB disk0s2

3: Apple_Boot Recovery HD 650.0 MB disk0s3

4: Microsoft Basic Data MinDoze 219.3 GB disk0s4

Looking from the MacOS (which CAN read the Win10 NTFS partition), both AppleHFS.sys and AppleMNT.sys are located in the Windows\System32\drivers\ folder. I'll have to re-boot to see if either is running in Services.

After rebooting to Windows, I opened the Task Manager to see if the AppleHFS service is running - it isn't.

I then used the USB Flash drive I had created with BootCamp Assistant on the MacOS, and ran the Bootcamp installer again, choosing "Repair". A short time after starting, I got a "Windows Installer has stopped working" message with no indication as to which installer was meant, and no other option than to quit it. After doing that, the Bootcamp installation continued, and the machine restarted.

The HFS+ partition is still not available in "This PC". I confirmed that the version of Bootcamp installed is 6.0.6201. If I knew where to find the appropriate Error log, I could possibly see which installer crashed during the Bootcamp Repair...

I ran the Boot Camp installer from my Boot Camp Assistant created USB Flash Drive in "Repair" mode. As before, about a fifth of the way into the process (as shown by the progress bar) i got an error message stating that the Installer had crashed and I should quit the process. I made a note of the time. I allowed the rest of the drivers to be re-installed and the finished without re-booting. I immediately wento to C:\Windows\INF\setupapi.dev.log to see if the crash was mentioned in that log, or indeed anything helpful from the time of the Installer crash or shortly thereafter.

There doesn't appear to be anything useful, in that it shows that all listed processes ended with "Exit Status: SUCCESS". Those listed with timestamps close to when the Installer crash happened included those for keymagic64.inf, bcmwl63.inf and bcmwl6.inf, which ended with SUCCESS as mentioned.

I looked in the Event Viewer for Error messages from around the time in question, but it's rather bewildering without knowing just where to look. There were several Errors listed, but they appear to be network or font cache problems - there is nothing I oculd find that specifically mention Installer errors.

Searching for a remedy for the inability of my Win10 1809 installation to mount the HFS+ volume, I came across a post that suggested that installing the drivers (AppleHFS.sys and Apple MNT.sys) from Boot Camp version 5, and gave a link for their download.

I followed the instructions that came with the file - renaming the existing drivers that my BC 6.0 install had put there, running a Registry entry that removed the access for these file, re-started, removed the old now renamed AppleHFS and MNT drivers, replaced them with the v.5 ones from the package and ran a Registry entry which restored the Regirtry's connection to them.

Bottom line? Didn't work - in much the same way that the version 6.0 drivers didn't work, and probably for the same reasons, whatever they may be...

Looking around at other posts it seems that a lot of people believe that Apple is quietly removing support for this feature, as it only ever worked for HFS+ formatted partitions, and those without the Core Storage designation. It's looking like this function simply cannot be enabled in Win10 - so much for progress!

I was able to restore my system to its state before I tried any of this, thanks to a Winclone backup.

I'm now wondering if installing Paragon's HFS+ for Windows will even work on this machine (or for that matter, MacDrive).

Does anyone have any experience with Paragon or MacDrive in Windows 10 v1809 64 bit Pro?

After a week of searching for solutions to my Win10 installation's inability to grant Read-Only access to HFS+ formatted partitions, I've decided to start all over again, wipe the Windows partition and install from a USB Flash Drive created by Apple's Boot Camp Assistant.

BCA offers the option to create a drive from a downloaded ISO file from Microsoft, or to create a drive holding all the drivers and Apple software required by my computer - or both. I'm thinking that this last option is the way to go, in that it seems to be the best option that could allow the HFS driver/software to be installed correctly.

I'm having a problem with BCA, however. When I tick the two checkboxes for both the ISO loading and the Apple Software loading, it gets going and the progress bar proceeds to a point just short of half way, where it lingers for about twenty minutes with no apparent activity. Then, I get an error message in BCA, stating that my UBS Flash drive has insufficient space, and the only option is to quit.

I'm using a 16 GB Sandisk Cruzer Glide. I have two more just like this one, one holding the expanded files from the Win10 ISO, the second holding the downloaded files from Apple. Examining both of these, I see that the ISO drive has barely 4 GB on it, while the Apple software drive as less than 2 GB, so it would appear that a 16 GB drive should be sufficient, but nonetheless, is not...

Mac OS is 10 12.6 Sierra.

Boot Camp Assistant is version 6.1.0.

I'm using the MS ISO for Win10 v1809.

The computer is a Late 2012 Mac Mini (version 6.2).

Yes, Alan Jenks, I believe you're correct - some file in there exceeds the 4 GB file size limit, and there's no way to change which formatting is used by Sierra's BCA. An upgrade to Mojave is not in the cards just now, mostly because of all the other changes that come with Mojave - file system, non-64 bit programs nag, etc.).

Loner T, I have seen mentions of the 1511 ISO in other forums as a solution to this issue, but finding one online means going through a bunch of dodgy looking websites that I've never heard of before. I'll ask my friends...

I have some apprehension about going the Paragon route, but it's more because of the potential for, ahem, operator error, than any problem with the software. But to be sure, how about making the HFS+ Volume Read-Only?

If I understand things correctly, the method is to use "diskpart" within Windows' Command Line editor:

Start Button > "cmd.exe" > Run as Administrator >

Once it opens type:

diskpart

select disk 0

list volumes

select volume 1

attribute volume set readonly

exit

exit

Then reboot the computer.

Hopefully the Mac volume will now be visible but write protected within Windows, and the EFI and Apple System Recorvery partitions will not be visible or mounted.

Thoughts?

Thanks Loner T.

I was afraid of that (the subsequent updates would remove HFS+ reading capability). I'm beginning to feel that the only way forward for me now is to use Paragon, or to use MS-DOS formatted flash drives to carry things to Windows from the MacOS. A p.i.t.a. to be sure, as I'm always sure to forget one key item, necessitating a re-boot, followed by a re-boot...

Any comments about my proposed action with "diskpart" in Windows? Will trying to set the HFS+ partition to read-only status do more harm than good?