Unable to create System Image Backup > 0x80780119. Now OS won't Boot.

Hello,

Windows 10 Pro installed on an SSD running on a Dell Inspiron.

I wanted to create a System Image Backup. I attached a 1TB drive to contain the backup but kept getting the 0x80780119 error pop up telling me: "The Backup Failed, There is not enough space to create the volume."

I reformatted the 1TB backup drive and tried again.
I made sure the "Volume Shadow Copy " service was running.
I tried this link to turn ON System Protection for Drive C: (The drive containing the Win 10 OS, it was turned off)
I tried this link to Extend System Reserved Partition.

My System Reserved Partition is the first partition on the disk and is only 50MB in size. Actually I used EaseUs Partition Master to move the C: drive (containing the OS) to the right and thus free up 950MB more space that I was then going to allocate to the System Reserved Partition. EaseUS appeared to repartition the drive ok. And I booted back into Win 10 and all was well. Then I used the Disk Management tool to "Extend Volume" on the System Reserved Partition. After this the screen froze and when I tried rebooting it won't boot anymore.

I then used a Win 10 bootable ISO I had and tried to "Repair" and that ran for a few minutes but then it said it "Could not Repair" it. The I googled a bit and tried these commands from the command prompt:

bootrec.exe /FixMBR
bootrec.exe /FixBoot <-- This would not run, I got permission denied?
bootrec.exe /RebuildBcd

Then I rebooted and still it would not boot however I actually have two hard disks in my laptop and was able to boot in to the other drive which also has Win 10 on it... I had recently cloned that (optical) drive on to the SSD drive.

THEN... I tried running the System Image Backup tool again and found it DID run? But it was running on the few days older Win 10 installation on the Optical drive that also has a System Reserved Partition of 50MB.

My questions:
1. Is there a way to get the SSD drive booting Win 10 again or will I have to clone the Win 10 Optical drive installation back over to it again?
2. Why was System Image backup not working for me on the Win10 installation on the SSD (when its System Reserved Partition was 50MB)?
3. Why did the System Image backup work for me on the Win10 installation on the optical drive (when its System Reserved Partition is also 50MB)?

Thank you,

Flex

Is the 1TB drive formatted properly?

Ahm.. yes.

Because I used that same 1TB USB drive to successfully save a System Backup Image that I created from the Win 10 installation on my other regular spinning disk hard drive.

By the way.. I tried booting into Ubuntu Live CD and I cannot mount or view the files on the OS partition on the SSD. This is the drive that will not boot anymore since I used the Win 10 Disk Management tool to resize it's System Reserved Partition. I get the same thing when I try to view that drive from Windows (I have the regular drive and SSD drive in the same laptop)... I get the error: "[drive] is not accessible. The volume does not contain a recognized file system".

So maybe the SSD has become corrupt? But I was able to boot into that SSD AFTER I used EaseUS on it. I didn't get problems until I used the Win 10 Disk Management tool to expand the System Reserved partition to use up the additional 950MB of free space I freed up from the C: drive using EaseUS.

Any help with answers to my questions above much appreciated!

Cheers,

@Ghot

When I say "optical drive" I am talking about a regular spinning disk hard drive.

I can't post a screen shot of EaseUS now because I had installed that on to Win 10 on my SSD which now won't boot. Here is a screenshot of the Disk Management tool as run from the other spinning disk drive also running Win 10 that I have in the same laptop.



Disk 0 is the SSD that won't boot. It is actually a clone from Disk 1 that is a regular spinning hard disk. I increased the size of Drive D: from 50MB to 999MB using EaseUS. I just moved drive G: to the right to free up space to its left to expand drive D: . Then I guess EaseUS cropped the size of drive G: because it was over 900MB so it got reduced to some unallocated space and then I used EaseUS to further reduce the size of drive G: to make that 500GB unallocated space.

Windows booted up fine from the SSD after EaseUS did its thing but after I right clicked on drive D: in Disk Management to expand drive D: from 50MB to 999MB then Windows froze and would not reboot.

Can I rescue Windows on this SSD? In my first post above I mentioned that things I tried.

Thank you for your help,

Did you try running

chkdsk /f G:

Is this something to do with the G: partition now being formatted as "RAW" instead of NTFS?

I am following instructions at this link and have downloaded Disk Genius(r). When I select "Load Current Partition Intelligently" from the Tools menu nothing appears on the screen. So maybe all data is lost on drive G? I can see the contents of Drive D: and also the Disk 0 "Recovery Partition" when I boot into Linux Live CD but I can't mount drive G:

So I'm wondering what went wrong? Maybe it was EaseUS that messed things up just it was a delayed effect? Or maybe I expanded drive D: by clicking something wrong in Disk Management?

So many questions? Like why was I not able to create a System Image from Win 10 on the SSD but I AM able to from a clone of that installation on Disk 1 .. the spinning disk drive?

Thank you,

- - - Updated - - -
@SIW2

When I try that from elevated command prompt I get this...

Code:

C:\Windows\system32>chkdsk /f G:
The type of the file system is RAW.
CHKDSK is not available for RAW drives.

- - - Updated - - -

@Ghot

Do I need to ask @NavyLCDR or did/can you maybe let him know?

Thank you.