How to fix “Error mounting EFI on disk /dev/disk” errors

Verify that the EFI partition is on slice 1 by running the following command: diskutil list (note that the EFI partition is disk0s1) Verify that the EFI partition can be mounted by running this command in Terminal as an Admin: sudo diskutil mount disk0s1 (if your bootcamp partition is on a disk different from disk0,…

READ MORE

Make Legacy Bootable in Winclone 9 or later

Windows can boot in EFI mode or Legacy mode, depending on the Windows version and the type of Mac. Winclone will detect which boot mode to use during restore. This option will force the Mac to boot Windows in Legacy mode. “Select Volume” will show any currently attached volume that is NTFS formatted and has…

READ MORE

Make EFI Bootable in Winclone 9 or later

Windows can boot in EFI mode or Legacy mode, depending on the Windows version and the type of Mac. Winclone will detect which boot mode to use during restore. This option will force the Mac to boot Windows in EFI mode. “Select Volume” will show any currently attached volume that is NTFS formatted and has…

READ MORE

Inject Boot Camp Drivers in Winclone 9 or later

Overview Migrating a Boot Camp partition from a older, non-T2 Mac can result in a blue screen with the error message (stop code) Inaccessible Boot Device. Winclone 8.2 or later can inject the Boot Camp drivers to resolve this issue. Visit our product page to download the latest version of Winclone. Instructions To inject the…

READ MORE

Resolving INACCESSIBLE_BOOT_DEVICE Error after restoring Winclone image

When migrating Windows between different hardware or hard drives, Windows may start up with an INACCESSIBLE_BOOT_DEVICE error. This error is caused by the lack of the correct mass storage device driver. To resolve this issue, the correct mass storage device driver can be injected into Windows. This document outlines what is needed to inject the…

READ MORE

System Integrity Protection in Winclone 7 (or later)

Apple has implemented a new security feature, System Integrity Protection (SIP), starting with OS X 10.11.  SIP prevents anyone from altering the contents of files in key System folders and is designed to protect System files from malware and viruses.  SIP also affects third-party apps like Winclone that need to write to files now under protection of SIP.  If you are getting a message that the boot sector cannot be updated, or that SIP needs to be disabled, this article may help.

READ MORE

Extracting a Winclone Image from a Package

If you created a Winclone package but no longer have the original Winclone image, you can extract the image from the package by following these steps: Control-click on the package in Finder and select “Show Package Contents” A new Finder window will open showing a Contents folder: open that folder, then the Resources folder The…

READ MORE

Windows Boot Issues after Winclone Restore

After restoring a Windows image with Winclone, try these steps if the Windows image does not boot: Verify that the version of Windows is supported on your hardware. Windows 7, earlier versions of Windows, and 32-bit versions of Windows are not supported on newer hardware. See this article for more information:https://support.apple.com/en-us/HT205016 Try switching between Legacy…

READ MORE

Run CHKDSK on Boot Camp

As a maintenance practice, you should always run chkdsk in Windows prior to making a Winclone image, as well as when shrinking or expanding the Boot Camp file system. Chkdsk is an internal Windows maintenance utility that checks for disk errors and repairs bad blocks. Running chkdsk should be part of routine Windows maintenance. Follow…

READ MORE

Sysprep Issues

If Sysprep fails to complete, there are several possible causes: Windows Media Player Network Sharing Service may interfere with Sysprep. The solution is to stop or disable Windows Media Player Network Sharing Services in Services. Sysprep may fail with a “fatal error” message if the Windows system has run Sysprep multiple times previously. As a…

READ MORE