Cannot make system image - VSS error 12289

Thanks for the update adam,

Here are some disk references:

FAQs: GUID Partitioning Table disk architecture
Understanding Disk Partitions
Recommended BIOS-Based Disk-Partition Configurations
Recommended UEFI-Based Disk-Partition Configurations

How was Win8.1 installed? Was it pre-installed on the machine or did you install it?

Install Windows 8.1 on a Mac - Windows Help

You probably already visited these Windows on Mac (WoM) pages:

Boot Camp - Apple Support

Boot Camp 5.1: Frequently asked questions about installing Windows 8 - Apple Support

• Things that stood out as I scanned the page, I have no idea if they apply or not.
• On one of the pages it recommends Boot Camp 5.1 - make sure you're MAC is up-to-date. I didn't see any other important updates on the download page, but you'd be a better judge of that. I'm sure you run the Mac Update periodically.
• To install Windows and the Boot Camp Support Software, you need a flash drive or other USB media, which must be formatted for the FAT file system. But later it discusses using an ISO for Windows ??????
• Thunderbolt devices ???

How to install Windows using Boot Camp - Apple Support

Set up a Windows partition on your Mac - Apple Support

• Things that stood out as I scanned the page, I have no idea if they apply or not.
• If you have more than one internal drive and the drive you're partitioning is not in the first drive bay, remove the drives in the lower-numbered bays, then reinstall them after installing Windows.
• If the installer says that it couldn't create a new partition or locate an existing one, disconnect any Thunderbolt storage devices connected to your Mac

That's about all I can think of - hope it helps or points you in the right direction.

Good luck,

Bill
.

Thanks Bill. I installed 8.1 on one partition (which is fine and supported according to your technet links as long as you don't want to use bitlocker) and upgraded that to 10. Then I wiped and did a clean install on the same partition. Your links confirm that there is no requirement to have a separate system partition.

I've always installed windows using mbr on macs using one partition and it has been fine.

The question is about system images - while the partitioning could be an issue it wasn't at eight so something has changed (either a bug or a requirement change I've not seen).

I may try creating another partition but it isn't trivial as mbr only supports 4. I'd have to move the OSX recovery partition next to the EFI and extend the GPT protective partition to cover it before I could create another. I'd also have to manually create the contents of the system partition as the windows installer wouldn't do it. I guess that would work but according to technet installing BIOS based windows on 1 partition is OK anyway.

Thanks again for the feedback - yep, I understand the issue is about System images, specifically VSS.

I asked Lee to see if the issue exists on her machine (Windows on Mac) and to weigh in on your thread if the same issue occurs or if the issue is not present.

I wouldn't bother trying to create a another partition - the next Win10 release will be here soon, it might be 'fixed'.

Did you feed MS the information?

Glad you were able to confirm things, sorry it didn't help much.

I tested System Image on my setup and one thing I noticed is that it picked a partition that was too small, I had to change it to one that could contain the image. That begs the question: Where are you storing the image?

Also, please launch an elevated Command Prompt and type
reagentc /info
exit
Post what Windows thinks about the Recovery Environment.

Thanks,

Bill
.

I'd certainly be interested if someone else running 10 on a mac (not in a VM) can make a restore point. It would be good to rule that out.

For recimg and restore points I was using C: which is 80% free. I also tried a backup to a 32GB SD card (more than big enough) and it failed with the same error.

I'll report on the feedback app also - I was hoping to be able to put more than "it doesn't work" though :)

Here is the reagent info. Partition 4 is my C: drive

PHP Code:

C:\>reagentc /info
Windows Recovery Environment (Windows RE) and system reset configuration
Information:

    Windows RE status:         Enabled
    Windows RE location:       \\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE
    Boot Configuration Data (BCD) identifier: 79f196fe-c34e-11e4-8aa0-97095480a43b
    Recovery image location:
    Recovery image index:      0
    Custom image location:
    Custom image index:        0

REAGENTC.EXE: Operation Successful.


C:\> 


Thanks, hopefully Lee will drop by.

VSS tracing is out of my league, but these references might help:

How to: VSS Tracing - Ask the Core Team - Site Home - TechNet Blogs

Using Tracing Tools with VSS (Windows)

Hi guys. . . Hopefully this will help. 1.) I use VMWare for the Mac or Parallel for running different OSs. 2.)I also use Boot Camp in which I am running windows 7 at the present time. Now if someone is unable to run windows 10 they could attempt to load up windows 7 or 8 in boot camp then try to do an upgrade to either one of those OSs with win 10. As to doing a clean install with Windows 10 in Boot Camp I have yet to try. . .sorry wasn't planning on doing so until the final hits the street. 3.) Now you could go over to Mac Rumors: Apple Mac iOS Rumors and News You Care About, and then to the Boot Camp forum to see if maybe someone can help you out there. Haven't have time as of yet to explore it, will try to make time later this eveinging. . .good luck. . .:)

I've got 2 MBP - one with clean install of 9926 one with 8.1 upgraded to TP (also now on 9926). Both have the same issue in bootcamp (native Windows boot) I've not tested with VMs as I rarely use OSX but I will set one up today. I asked on the mac forum also.

Thanks to Bills links I managed to download the SDK and make a trace of creating a restore point and recimg using this command vsstrace.exe +f 0xffff -o C:\temp\recimg.txt. The trace files are huge and I don't know where to start looking really. I've uploaded them in case anyone else knows what to look for. There is some stuff about it writing OK to the backup location but then messages about aborting.

Code:

[19:26:31.803 P:1480 T:1EE4 INCICHLH(0200)    IOCTL] Opening a handle to \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy7 (access = 0x00000000, share = 0x00000003)
[19:26:31.803 P:1480 T:1EE4 INCICHLH(0300)    IOCTL] The object '\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy7'. was opened under the device handle 0x000001e4
[19:26:31.803 P:1480 T:1EE4 INCICHLH(0451)    IOCTL] IOCTL sent: 53019c on device \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy7
 Input buffer size: 0, Output buffer size: 4096
[19:26:31.803 P:1480 T:1EE4 INCICHLH(0549)    IOCTL] IOCTL 53019c succeeded on device \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy7 - 0x000001e4. 
 Output buffer: size received = 108

Code:

[19:26:31.808 P:1FFC T:1D54 CORSOFTC(0163)    COORD] EXIT[CVssSoftwareProviderWrapper::Release] Time spent: 00:00:00-0000; total: 0; HRESULT: 0
[19:26:31.808 P:1FFC T:1D54 CORSNPSC(1217)    COORD] EXIT[CVssSnapshotSetObject::ThawWriters] Time spent: 00:00:00-0015; total: 0xf; HRESULT: 0x80042306
[19:26:31.808 P:1FFC T:1D54 CORSNPSC(0828)    COORD] HRESULT exception caught: hr: 0x80042306
[19:26:31.808 P:1FFC T:1D54 CORSNPSC(0831)    COORD] ENTER[CVssSnapshotSetObject::DoSnapshotSet_failure_block] 
[19:26:31.809 P:1FFC T:1D54 CORSNPSC(0850)    COORD] Abort detected while commiting the snapshot set 0x80042306

John, Everything is up to date in Windows update. I uninstalled EMET but the issue is the same. I'll download a fresh copy of 9926 and try it again without installing anything at all.

Thanks all for keeping suggesting things as I sure would like to be able to make backups...

The cause is the Apple HFS driver applehfs.sys.

This happens with bootcamp version 3.2 (driver creation date 10/15/2010) and 5.1 (creation date 1/31/2014).

If the driver is disabled through Autoruns for Windows then after reboot system image, recimg and restore points all work. I've tested this on 2006 core 2 duo running the old driver version and 2012 MacBook pro running the new one and in both cases disabling this driver is sufficient. Note that enabling this driver will delete all restore points you may have made.

It does mean you can't see HFS partitions which is a bit of a bugger but there we are. Perhaps Apple will make a Windows 10 compatible driver one day.

Thanks for the input everyone - there is no Windows error here.