Cant backup 8.1 using system image backup! Error 0x80780119, Cant optimise system partition, (this is why i cant backup) please read. . .

Anonymous
2013-10-19T14:16:48+00:00

I am having this issue, cant optimise the system partition 350mb. 8.1 official release,

This is also causing a huge problem, the optimise option in windows 8.1 allows me to optimise the c: drive but not the system partition this prevents a system image backup...!!

Due to the system partition being out of space for a shadow copy to be placed onto it the backup fails every time with this error code, -- 0x80780119 --.

Backups are a huge factor in operating systems and since upgrading I cant backup my system using windows image backup, if I could optimise the system partition and straighten out the file structure within it (free up some space) for the shadow copy then the volume shadow copy could be placed onto the drive but it cant...

This all worked fine in 8.0 but not now...please fix this problem!?

Not being able to backup your system is not good enough...

here is my my issue again in pictures...

1.system volume needs optimising

but pressing the optimise for this does nothing at all.. current status remains "Needs optimisation".

The way an ssd reclaims drive space is to use the optimise function, this not working prevents the reclaim for files/data to be written to space where files have been deleted previously. Giving the impression the drive/partition is full when really its not full just needs optimising/trimmed.

 

  1. initiate the system image backup

  1. both volumes to be backed up

  1. error message due to insufficient space on the system partition for shadow copy. 

 

  1. finally here is a capture of the current disk setup on my system, notice the system partition only has 17mb free space and according to the above error message I need atleast 50mb free for the volume shadow copy !? Due to this I cant create a backup of my system using windows 8.1 !

(system partition has no drive letter assigned to it 350mb)

PLEASE HELP !! Thanks for reading.

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2013-10-20T20:19:10+00:00

I have found a way around this getting Windows System Image Backup working again. I did this on my laptop and desktop confirming that I could recover from the images. It is actually pretty easy but should not be necessary. The reason that the backup would not work was because the recovery partition was using 284MB of the 300MB available. There was not 50MB available for shadow copy. Here are the steps I took on an EUFI GPT disk:

Note: All commands are without quotes. 

Disclaimer: I would recommend backing up all of you important data as any time you mess with partitions, there is the possibility to lose data. This process was done one both my laptop (Win8.1 Home) and desktop (Win8.1 Pro). I cannot take responsibility if this causes any damage. With that being said, I hope this helps.

Download and install MiniTool Partition Wizard http://www.partitionwizard.com/free-partition-manager.html Note that none of the changes will take effect until you hit apply. I am sure others may work but this is the one that I used and it is free. 

You should have 3 Windows partitions; Recovery - 300 MB, EFI System - 100 MB, and your system Volume to start off with. 

  1. Once installed, Open Partition Wizard and Shrink your system volume, C: in my case, by 101MB at the beginning of the partition. (I had to put 101MB as when I tried 100 it said that the space was too small when doing the next step) To do this, Right Click the C: Drive, select, Move/Resize, and the put 101 in box named "Unallocated Space Before:" and click OK.
  2. Copy the EFI System partition (100 MB FAT32) to this new Free Space by right clicking, selecting copy, and then selecting the unallocated space. Then next the OK.
  3. Delete the 100MB EFI System Partition after the Recovery Partition. 

After this is done, you will see 100MB unallocated space after the Recovery Partition. 

  1. Right click on Recovery partition and select Extend. Drag the bar to take up all of the extra free space. This will change the recovery partition from 300MB to 400MB allowing for enough space (50MB) for the shadow copy. Click OK. 
  2. Next Click Apply. I received an error stating that it could not make changes due to C: being in use. I clicked restart. 

When the computer restarts, Partition Wizard will do its thing. Once it is done you should boot into Windows again.

This next part is essential, because, windows now does not recognize the partition that was moved before as an EFI System Partition. If you try and do a backup image now, only the system partition will show and not the Recovery or EFI System

  1. Open a cmd prompt with administrator privileges. Press Start Key, Type cmd, right click, select run as administrator. 
  2. Type diskpart to start windows command line disk manager. 
  3. Find the disk that Windows is installed on by typing List disk. This will be different on each machine but for illustration mine was disk 0
  4. Select that disk by typing the command "select disk" and the disk number.
  5. Next, determine the EFI partition that was moved earlier. This is the partition that was moved earlier and should be 100MB. Type in the command "list part" to see a list of the partitions on the disk. Mine was Partition 3. This may be different on your system. 
  6. Once you have determined the partition number, type "select partition " and your partition number
  7. Next you have to set this partition as an EFI System volume. Type in this command - "set id = c12a7328-f81f-11d2-ba4b-00a0c93ec93b" This changes the partition type to an EFI system volume.
  8. After all of this is done, restart your computer and you should now be able to back up you system using the System Image Backup in File History.

I know some of this may seem a little elementary to some but you never know who needs help and their technical knowledge. 

I hope that this helps and let me know if you have any questions.

Was this answer helpful?

10+ people found this answer helpful.
0 comments No comments

778 additional answers

Sort by: Most helpful
  1. Anonymous
    2013-12-06T20:33:33+00:00

    I upgraded too, they sent me the disks for a small fee and I did a clean install of Win 8, finding this all a bit sinister really,  not a word from the company?  Contacted the BBC watchdog several times recently too,  awaiting a reply hopefully from the BBC.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2013-12-06T20:24:46+00:00

    Unfortunately this is the problem, some have successfully managed to fix this including myself whilst others have relentless issues, I too had problems booting from the image after extending the system partition but eventually figured it all out, used up Alot of my time and now I think this is actually not an error but a purposely built piece of code to limit the full function to people who bought the very cheap 8.0 upgrade... thoughts welcome on this... 

    Does this type of message happen more often on computers that were upgraded to Windows 8 rather than Windows 8 being their original OS?  I could see why people who originally had Windows 7 and upgraded to Windows 8 are having more of a problem than those of us who started with a fresh Windows 8 install.  I upgraded to Windows 8 from 7 on my desktop, but I did a clean install, so perhaps that's why I didn't have any problems with it.  The other two computers came with Windows 8 preinstalled.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2013-12-06T15:23:25+00:00

    Another question that I have is how to check a partition that is not showing - the partitions that are unlettered would be hard to check with CHKDSK.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2013-12-06T12:53:32+00:00

    never used CHKDSK, was never prompted to either sorry, never heard of the  (0x8007045D)\ error either,

    This thread is regarding the  0x80780119  error.

    I hope someone can assist you with this,

    can I quote some of your reply...

     "  I followed the instructions here and enlarged the partition that was too small .  I was able to reboot and my system is running well"

    ok so you enlarged the required partition and your system is working well...

    "(I can also run the Windows imaging program - which is the whole point of this thread.) "

    The whole point of this thread was the system imaging program NOT working.

    But in actual fact you can run the system imaging program until it fails (where in the process does it fail?? near the start?? middle or near the end of the process?? This will give me some indication of the issue once you give me your exact partition layouts.. also are you backing up to an external usb HDD or SSD??

    " The image backup begins fine as the partitions are big enough.  But now there is a different error,  As stated above in my first post there is an I/O error and the error message tells me I can run check disk to attempt to fix the drives that are causing the trouble."

    This sounds to me like a drive inconsistency error, in other words the drive partition that you extended is conflicting with something possibly an overlap? Did you overlap any space from any partition onto the system recovery partition?? the imaging process (volume shadow service) will start and run until it hits an anomaly with the partitions/drives, what size is all your partitions? did you borrow space from 1 partition to add to another?? Extending the system partition would normally use some space from C partition and not any other partition??  

    Is it not the backup location drive you need to run a chkdsk on?? Also make sure it is fully formatted NTFS, seeing how your system runs and boots ok.

    I recommended chkdsk /r on the external USB hard drive... I cant see how this would screw up a HDD or SSD, then again if it does then sorry... :-)

    /f - fixes errors on the disk

    /r - Locates bad sectors and recovers readable information (implies /f)

    Was this answer helpful?

    0 comments No comments