Solved Can't create system image. 0x80780119 error after upgrade

Hello!


I have upgraded my Windows 8 PC to 8.1 yesterday and it seemed like everything is working fine until I tried to create System Image. I got an error 0x80780119 saying that there is to little space on one of the partitions.


I started looking into this problem and indeed one of the partitions does not meet the requirements. There are following partitions on my drive:




Partition 1 has only 13MB free space. Partition 2 has 70MB free space, partition 3 is MSFTRES, partition 4 is my C drive with around 35GB free and partition 5 is not included in system image.
Partitions were create like this during installation of Windows 8 - clean install from scratch. I am using UEFI so the drive is GPT formatted.


So I thought, OK I can resize my C drive a little, move the partitions and expand the 1st one. I tried using GParted but it is not able to move the MSFTRES partition. It does not recognize the file system on it.


So the question is:


Is it possible to "clean up" the 1st partition in anyway?
If not, is there anything special about MSFTRES partition? Or can I just remove it and create it a little further and just flag it as msftres with GParted?

Before you go through all that, I would make the switch to Macrium Reflect Free and see if that works for you. If so, just keep using it!

Macrium Reflect FREE Edition - Information and download

I know about Macrium, but it is annoying and to be honest I would like to keep using Windows Backup...

cichy202 said:

I know about Macrium, but it is annoying and to be honest I would like to keep using Windows Backup...

Click to expand...

OK, someone will be along to help you. Good luck.

I use EaseUS Partition Manager FREE. I have done almost everything with it. I suggest you get a GOOD imaging program and an external drive. I use Thermaletake MAX external drive cases and a Western Digital 640gig sata drive for each of my desktops. Paragon Backup and Recovery is my program of choice.

I have system image already, but how did you move MSFTRES partition exactly? Could you please describe in detail what have you done exactly?

* This applies only to UEFI and GPT installations! *

OK it took me a while to figure out what to do, but I have managed to fix that.


First of all create backup of everything you have on your PC that is valueable. In my case I created only the system image using Macrium Reflect Free.


Secondly I have installed EaseUS Partition Master Free and shrinked the system partition (C. Then I have copied the 128MB MSFT partition closer to the C partition and removed the original one. For some reason the EaseUS Partition Master did not want to copy the EFI partition so I used MiniTool Partition Manager (also free) to copy it just like the 128MB partition. Last I had to expand the Recovery Partition.


After restart I turned out that recovery partition is broken for some reason and Windows does not recognize it. So I booted with GParted live CD to check if it is OK and it was - so no luck here. But I have noticed that the 128MB one does not have proper flag set, so I set it to MSFTRES with GParted.


OK. The only thing left to fix was the recovery partition. I decided to format it and deploy the Windows Recovery Environment again. So I removed the partition just to be sure that I get clean "normal" partition and created it again using EaseUS. Then I have followed this tutorial: Windows Recovery Environment (RE) Explained | sepago . I just had to set proper flags on the volume with DISKPART: gpt attributes=0x8000000000000001.


After reboot and some quick testing I saw that everything works fine, but for some reason the recovery partition is mounted on every boot even though it is hidden. Disk Management showed that the partition should not have any letter assigned, but it was visible in "This PC". I removed the letter using Diskpart and then immediately fixed the MountedDevices registry key using this little tool: USB drive or flash problems? How to cleanup and remove old USB storage drivers - TechSpot Forums .


Now everything is up and running. Windows sees the recovery environment and backup works as charm.