Windows 10: Cannot make system image - VSS error 12289

Hmm, hard to say what that is. What AV program do you use and did you install any other program that could throw a monkey wrench into VSS.

Did you ever try the Wbadmin command:

wbadmin start backup -backupTarget:X: -include:C: -AllCritical -quiet

You have to replace "X" with the volume letter of your backup device.

 

Here is disk management. It is indeed an apple drive. The first 3 partitions are EFI, OSX and OSX recovery. The 4th is Windows. I'm not doing EFI boot - the mbr partition table I posted earlier.

 

AV is defender. I've no third party backup software installed - I did a clean install a couple of days ago. wbadmin gives same error (on Processing PreFinalCommitSnapshots) as recimg and creating restore point...

 

Try tis just for grins and giggles:
turn off System Protection,
turn off hibernation,
make the page file static 3072 MB,
chkdsk /f Win10 drive,
restart

If there are any ramdisks or network shares, remove them - turn on System Protection and try to manually create a Restore Point.
Investigate any errors that produce event entries - see if the more info on the event actually gives you more information.

I'm not familiar with MacWindows - but was wondering how the disk was initialized - by the Mac side or the Win10 install? I know you've reinstalled ate least once trying to get this resolved..

I'll also ask if Windows 8.1 was ever running on the Mac - in other words is this related to 9926 or is it something else. I really don't know, so I ask questions.

Bill
.

 

Hi Bill, I tried these steps (only the page file one I hadn't tried) but no luck. For your information I made the partitions under OSX and formatted the windows one NTFS as part of the Windows install process. It is a standard BIOS type install with everything on the C: drive.

I had 8.1 before and backup etc worked. I upgraded to 10 and it stopped working. I'm not sure what build as I didn't check and as I thought the cause was me breaking authority trying to fix another VSS error I then did a clean install of 9926.

I'd try to debug VSS but I don't know how (I tried turning on tracing but haven't managed to get any output yet) so I'll have to wait and hope it gets fixed in a later build. It is quite annoying not to be able to make a backup (macrium, arcronis etc all use VSS under the covers) but hopefully it will resolve itself.

 

FYI - your partition scheme doesn't appear the same as mine (even taking into account the Mac drive) - you're missing the recovery partition and the System Reserved Partition (there are some unlabeled partitions on yours, but I don't know which is which).
Mine has:
- System Reserved, 350 mB NTFS, Healthy (System, Active, Primary Partition), 90% free
- C:, 41.35 gB NTFS, Healthy (Boot, Page File, Crash Dump, Primary Partition, 39% free
- 450 mB, Healthy (Recovery Partition), 100% free

The System Reserved Partition has 4 folders and 5 files in it.
Folders:
$WINDOWS.~BT
Boot
Recovery
System Volume Information

Files:
$WINRE_BACKUP_PARTITION.MARKER
bootmgr.{CLSID in here}
bootmgr.{another CLSID in here}
BOOTNXT
BOOTSECT.BAK

Please note that the System Reserve partition is named as such, and it is labelled as using the NTFS partition - your system doesn't have this. Nor does it have the recovery partition. My research doesn't state if this partition is required in Win8 or 10, but it wasn't required in Win7. Please check to see if any of your partitions have these files/folders.

The next time that I see a Boot Camp system at work, I'll take a look in DiskMgmt.msc and will post the results back here.



I had no problems with creating a System Restore point, nor with the recimg command
I didn't try the wbadmin command as I don't have a external drive handy, and I'm not real keen on adding extra drives to my Win10 virtual machine.

My VM is nearly unmodified (I've only added updates, have made a Windows Update shortcut on the desktop, and have set it for autologin). It's build 9926.

As you've reinstalled this build, my suspicions are:
- the installation media may be corrupted
- the system may have a device that is incompatible with Win10
- the Win10 installer may not be fully featured for different installation scenarios

As I'm a BSOD specialist, I'd like to ask for a look at the BSOD reports. Maybe I can find something awry in the reports (even though there aren't any BSOD's).
Please provide this information so we can provide a complete analysis (from the Pinned Topic at the top of the forum):
Solved BSOD - Posting Instructions - Windows 10 Forums

 

Hi John,

I've enclosed the BSOD reports.

As for partitions this is what I think (but I really am only guessing here - I'm not an expert).

When you install windows in BIOS mode on an unformatted disk it will make a 350MB or so partition which contains the boot files and the WinRE.wim. This partition will be marked active. If you format it first your boot files and the recovery directory (containing WinRE.wim) are put on the C:\ drive and the C: will be marked active. So a BIOS installed windows will have either 1 or 2 partitions depending if you format it first during you windows install. What you have in your reserved partition I have in C: (see picture). I think this is normal.

An EFI install (which I didn't do as my EFI firmware doesn't support windows) will create a 200MB EFI partition (containing the boot files), a 195MB Microsoft reserved partition (containing nothing) and then your C: drive. And maybe a recovery partition as well.

Now I could make some new partions and copy the relevant stuff in as a test. This is quite fiddly though as I have to maintain my GPT and MBR partition tables separately. At the moment they are the same except I'm not showing windows the EFI partition (it is type EE GPT reserved in the mbr): PHP Code: C:\>gdisk64.exe 0:
GPT fdisk (gdisk) version 0.8.10

Partition table scan:
MBR: hybrid
BSD: not present
APM: not present
GPT: present

Found valid GPT with hybrid MBR; using GPT.

Command (? for help): r

Recovery/transformation command (? for help): o

Disk size is 236978176 sectors (113.0 GiB)
MBR disk identifier: 0x5D3CF3FA
MBR partitions:

Number Boot Start Sector End Sector Status Code
1 1 409639 primary 0xEE
2 409640 106802351 primary 0xAF
3 106802352 108071887 primary 0xAB
4 * 108072960 236976127 primary 0x07

Recovery/transformation command (? for help): p
Disk 0:: 236978176 sectors, 113.0 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 9730D1EA-8014-43FD-A713-9AB93CD62EBE
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 236978142
Partitions will be aligned on 8-sector boundaries
Total free space is 3093 sectors (1.5 MiB)

Number Start (sector) End (sector) Size Code Name
1 40 409639 200.0 MiB EF00 EFI System Partition
2 409640 106802351 50.7 GiB AF00 Yosemite
3 106802352 108071887 619.9 MiB AB00 Recovery HD
4 108072960 236976127 61.5 GiB 0700 Windows10

Recovery/transformation command (? for help):q

 

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 *Smile

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. . .*Smile

 

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[/quote] 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:oSnapshotSet_failure_block] [19:26:31.809 P:1FFC T:1D54 CORSNPSC(0850) COORD] Abort detected while commiting the snapshot set 0x80042306[/quote]

 

Unfortunately, there's not a large number of MacBooks running BootCamp with Win10 for us to check on.
I only get 1 or 2 a month at work. with 8.1 installed.

There's a large number of Windows Update failures in the WER section of MSINFO32
Have you checked for updates recently?

The only thing that I spotted in the reports that I'm not familiar with is the EMET toolkit (Enhanced Mitigation, Experience Toolkit).
Have you tried removing that?

Beyond that, I'd be interested in seeing if you can run the commands on a completely fresh install of 10 using a new copy of the installation media. That'll help to rule out the OS itself and the installation media.

Good luck!