cannot mount Boot Camp in Disk utility in Mojave

HaggaBon wrote:

Hi,

After replacing the 2018 version of AppleControlPanel.exe, now I can select re-boot to macOS of Win10 within WIndows 10! That's a relief! Tks!! Half of the issue solved. Only that the 2018 version of AppleControlPanel does not have the keyboard back light settiing as in the 2017 version. ;-(

Unfortunately, this is the side effect of using a different Model's Control Panel.

Thanks for directing me to the other discussion on "BootCamp not showing up in StartUp Disk" and "cannot mount Boot Camp Parition" within Disk Utility.

3. My Mojave was an upgraded from Sierra. I used to have Paragon NTFS for Mac when I was running Yosemite. Is this the reason for 2. ? How can I uninstall it? Will it solve the problem?

Paragon NTFS will cause issues with Startup Disks. See https://kb.paragon-software.com/article/204 for reference.

HaggaBon wrote:

default 06:57:41.000907 +0800 kernel NTFS-fs error (device /dev/disk0s3, pid 668): ntfs_boot_sector_parse(): Mft record size (1024) is smaller than the sector size (4096). This is not supported. Sorry.

default 06:57:41.000909 +0800 kernel NTFS-fs error (device /dev/disk0s3, pid 668): ntfs_mount(): Unsupported NTFS file system.

default 06:57:41.000910 +0800 kernel NTFS-fs error (device /dev/disk0s3, pid 668): ntfs_mount(): Mount failed (error 45).

During this test, were there any references to Paragon? I assume you tried a Mount operation from Disk Utility and these are messages which are time-stamped after your Mount attempt.

HaggaBon wrote:

Not sure if that MFT size is adopted by Win10?

It is supported and W10 will work, but the read-only NTFS driver that Apple supplies will not be able to mount it.

If you have a disk which can be erased for testing purposes, then

• Boot into Windows
• Format this disk as NTFS in Windows
• Check if it mounts correctly in Windows
• Post the output of fsutil fsinfo
• Switch to macOS, try to mount the same external disk and test
• The disk should support 4K block sizes

FYI, Apple support contacted me today and said they believe the version of this problem I’m seeing is fixed in macOS Catalina. I haven’t tried it yet, but I thought I’d pass that along. Although check if any software you rely on is compatible before upgrading. (I may have to wait for some updates.)

Can you repeat these steps? Do you still see references to the Paragon software?

• Click on Applications -> Utilities -> Console logs
• In Disk Utility, click on the NTFS file system, and click on Mount. It may fail
• In the Console window, type 'NTFS' without quotes, and click on Search. If you see any error messages, can you post them?

HaggaBon wrote:

I found the MacBookAir 2019 Boot Camp Apple Control Panel is the same version number as my current installed one - 6.0.6100.0 Should I use 2018 model then?

This is what I have on a 2018 rMBP.

2. Will that for iMacPro or other models work?

Try the 2018 Model one.

3. Any difference between running "SetUp.exe" and just replacing the AppleControlPanel.exe ?

If you run setup.exe, it will try to install all 2018 drivers, which may not be valid. I recommend not using setup.exe.

Did the uninstaller ask you to reboot?

As a test...

• Click on Applications -> Utilities -> Console logs
• In Disk Utility, click on the NTFS file system, and click on Mount. It may fail
• In the Console window, type 'NTFS' without quotes, and click on Search. If you see any error messages, can you post them?

Can you post the output of

diskutil info / | grep “Block Size”

from the macOS side?

On https://www.microsoft.com/en-us/software-download/windows10ISO , in the Select Edition drop down, select Windows October 2018 release.

Post the output of diskutil list.

Install macOS Catalina on an external disk, and test before you commit to Catalina.

This is a bit convoluted. You can re-install Paragon, which will also provide the Uninstaller. Run the Uninstaller, which should clean up properly.

The latest instructions are at https://kb.paragon-software.com/article/4500.