Cannot make system image - VSS error 12289

Page 2 of 4 FirstFirst 1234 LastLast

  1. whs
    Posts : 1,935
    Windows 7
       #11

    How about your Provider. Is that "System"
      My Computer


  2. Posts : 803
    10 Pro Preview x64
    Thread Starter
       #12

    whs said:
    How about your Provider. Is that "System"
    Yes it is. I've only got the one (see first post) and I checked registry in case of any leftovers but it was clean. (This is a fresh install).
      My Computer


  3. Posts : 459
    Windows 8&10
       #13

    I see some things in your posts I can't understand. You have a comment about using GPT with a hybrid MBR partition, but Windows 10, you mention, is installed in the legacy mode. Is the drive an Apple drive?

    A Disk Management picture might help, but your configuration may not lend itself to creating a recoverable system image using the Windows utility.
      My Computer


  4. whs
    Posts : 1,935
    Windows 7
       #14

    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.
      My Computer


  5. Posts : 803
    10 Pro Preview x64
    Thread Starter
       #15

    Saltgrass said:
    I see some things in your posts I can't understand. You have a comment about using GPT with a hybrid MBR partition, but Windows 10, you mention, is installed in the legacy mode. Is the drive an Apple drive?

    A Disk Management picture might help, but your configuration may not lend itself to creating a recoverable system image using the Windows utility.
    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.
    Attached Thumbnails Attached Thumbnails Cannot make system image - VSS error 12289-disk-management.png  
      My Computer


  6. Posts : 803
    10 Pro Preview x64
    Thread Starter
       #16

    whs said:
    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.
    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...
      My Computer


  7. Posts : 3,502
    Win_8.1-Pro, Win_10.1607-Pro, Mint_17.3
       #17

    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
    .
      My Computer


  8. Posts : 803
    10 Pro Preview x64
    Thread Starter
       #18

    Slartybart said:
    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.
      My Computer


  9. Posts : 230
    10
       #19

    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
      My Computer


  10. Posts : 803
    10 Pro Preview x64
    Thread Starter
       #20

    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 (gdiskversion 0.8.10

    Partition table scan
    :
      
    MBRhybrid
      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 identifier0x5D3CF3FA
    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 sectors113.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):
    Attached Thumbnails Attached Thumbnails Cannot make system image - VSS error 12289-c.png  
    Cannot make system image - VSS error 12289 Attached Files
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 05:21.
Find Us




Windows 10 Forums