OK, just deleted it. Shutting down now.
Thanks for all your patience.
Trouble Making Image Backup with Acronia True Image 2016 -- apparent misread of space
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
I have been trying for days now to make a backup image of my internal Windows 10 hard drive, fully updated to current Windows 10 level May 2020. I have been using Acronis True Image 2016, as I always do. I have been backing up to an external, USB2 connected hard drive with 160 GB of free space on it (a 320 GB hard drive), the same drive I normally backup to. This is a Gateway laptop, NE56R from 2012, which shipped with Windows 8.
I have been trying to backup all partitions, including the C, and recovery partitions (including the Push Button one, which is about 15 GB) and whatever others are there. In total, they are about 109 GB. So I ought to have plenty enough free space.
I have checked all partitions to back up with True Image. It runs the whole backup, takes a good five hours. At the end, it throws up amessage saying ther eis not enough space for the image.
I have never had this problem before. The machine is booted from the True Image disk, so that should rule out some issue wiht my Widows 10 OS. I am doing a full disk backup, and I am even using Maximum Compression, which is what I always use, so I should need something lessthatn 109 GB of free space. and Ihave 160 GB of free space on the external drive.
I have a backup of Win 10 I made in April, shortly before the new OS level cam out on the drive -- I always keep two, just because. I deleted the older of the two on there, so now have only the one. I certainly don't want to delete the one on there, and still have this problem but no backup at all. But Ihave more free space than shudbe needed.
The external drive has been used only for backups since I started using it brand new, and I make a backup once or twice a year -- and I have been using it no more than four years. So, the external drive has very little, hardly any actual use on it, it is not far from brand new.
I read something this morning about a real problem found in the new Win 10 update, something to do with Storage Space, that is some sort of function in the OS now. I don't know what that is, or what it does. But the story said if your drive is not showing as RAW, then it should be OK, not affected. I checked Disk Management, and none of my volumes nor the external drive are marked as RAW. So, that should mean that issue is not the case here.
I have done enough backups in the past four years using the Acronis True Image 2016 software. It has always worked fine, and actually with less free space (I had another item on the drive too, but have deleted it. I also have deleterd about 32 GB of stuff from my C drive in an attempt to make this backup fit, but to no avail -- that is, my last two backups were actually larger than this one, and they fit fine.)
So, why do I keep getting the message about not enough space? I should have way more than enough.
Windows for home | Windows 10 | 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.
270 answers
Sort by: Most helpful
-
Anonymous
2020-08-01T04:16:03+00:00 -
Anonymous
2020-08-01T04:16:01+00:00 That looks great with HarddiskVolume5 in it. Keep going. Fingers crossed.
-
Anonymous
2020-08-01T04:14:28+00:00 Will check out for the night now, and pick up in the morning. I did not proceed to erase that BCD line, because part 5 is not listed as R there, it is listed as your is. Its easy enough to do it again and delate the line if there is some reason.
- I did not mean it is D in Advanced Startup, but otherwise. I can fix those, later. Deal with that R for now.
- I already tried right click — it does not offer the option to Change Drive Letter. Don’t know why yours does and mine doesn’t. Maybe a difference between machine makers?
- yes, I saw a LOT of Windows Boot Loader. Don’t know what iti s.
OK, I will delete that line, then check out. :) Will check the results in the morning when I boot up.
-
Anonymous
2020-08-01T04:01:46+00:00 (1) OK, I haven't tested it in a while, but when I last removed a letter from my Recovery partition in Advanced Startup, it came back the next time I went. And I had tried it multiple times. All the other letters I changed or deleted remained as I left them. It was a big mess at first. But -- as you say -- it just isn't important enough to fret over. Well, except -- surely C: should be C:, though. Definitely do that one, is all. And I do like the DVD-ROM to be D:. I know you said yours already is that.
(2) "I have checked Disk Management. I see no way to set any partition letters there."
Right-click a partition, & select "Change Drive Letter...". But it is grayed out for the EFI & Recovery, except maybe when one already has a letter.
(3) "It definitely was before we Reaget'd it. I already was surprised to see the R was still on it before we did that or as we did that."
Hmm, that could mean forcing a rewrite of the BCD won't be a fix because I think it was ReagentC that did that. But try it anyway, it will be harmless.
(4) "Confirm that that is what we want to do, and I will do it now. I see we would first take the R off, then delete one unimportant line and BCD will rewrite, so you say. And hopefully the R will be gone as it will not be on part 5 when BCD rewrites. Restart."
It's worth a try. You've got a lot of junk in your BCD like...
Windows Boot Loader
identifier {4677ba16-45a9-4007-9e32-a87e737c0b41}
device unknown
path \Windows\system32\winload.efi
description Windows
osdevice unknown
systemroot \Windows
nx OptIn
That's a useless entry because it refers to "unknown". Once it would boot Windows & "device" would say where it was -- but there's nothing it can ever do now. You've got a lot of those, & I don't know why. The entire entry (all of those lines) will be deleted by...
BCDEdit /Delete {4677ba16-45a9-4007-9e32-a87e737c0b41} <<< Delete a useless entry
Hopefully, when the BCD is rewritten, it will be without R: in it. Then maybe it'll be gone from the partition too. Try it, yes, while in Windows.
-
Anonymous
2020-08-01T03:16:26+00:00 I proceeded as far as starting BCD, and am holding there until I hear. Last thing in that last ispart5, no R, says like your's. Should I proceed?
Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 0 D Vid UDF DVD-ROM 5588 MB Healthy
Volume 1 Recovery NTFS Partition 400 MB Healthy
Volume 2 C Gateway NTFS Partition 681 GB Healthy Boot
Volume 3 R Recovery To NTFS Partition 826 MB Healthy
Volume 4 Push Button NTFS Partition 15 GB Healthy
Volume 5 ESP FAT32 Partition 300 MB Healthy System
DISKPART> Select Vol=R
Volume 3 is the selected volume.
DISKPART> Remove Letter=R
DiskPart successfully removed the drive letter or mount point.
DISKPART> Exit
Leaving DiskPart...
C:\WINDOWS\system32>BCDEdit /Enum All
Firmware Boot Manager
identifier {fwbootmgr}
displayorder {bootmgr}
timeout 2
Windows Boot Manager
identifier {bootmgr}
device partition=\Device\HarddiskVolume3
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {2d25babd-c701-11ea-bc80-f9e613436a82}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30
Firmware Application (101fffff)
identifier {6333995d-208d-11e7-86b3-806e6f6e6963}
description MATSHITADVD-RAM UJ8C0
Firmware Application (101fffff)
identifier {6fd14a79-c6c7-11ea-896a-806e6f6e6963}
description ST750LM022 HN-M750MBB
Firmware Application (101fffff)
identifier {79a37f86-c6c0-11ea-8968-806e6f6e6963}
description WDC WD3200AAJB-00TYA0
Firmware Application (101fffff)
identifier {8c530f8d-d8ac-11e5-833c-806e6f6e6963}
description WDC WD3200AAJB-00TYA0
Firmware Application (101fffff)
identifier {8f472f02-059e-11ea-88fe-806e6f6e6963}
description WDC WD3200AAJB-00TYA0
Firmware Application (101fffff)
identifier {98e580f8-cd40-11ea-898d-806e6f6e6963}
description BRCM MBA Slot 0200 v15.0.11
Firmware Application (101fffff)
identifier {db84bcc4-69a1-11e6-84ca-806e6f6e6963}
description MATSHITADVD-RAM UJ8C0
Windows Boot Loader
identifier {06a7379d-d1bb-11ea-8997-b888e3b1b2f5}
device ramdisk=[\Device\HarddiskVolume5]\Recovery\WindowsRE\Winre.wim,{06a7379e-d1bb-11ea-8997-b888e3b1b2f5}
path \windows\system32\winload.efi
description Windows Recovery Environment
locale en-US
inherit {bootloadersettings}
displaymessage Recovery
osdevice ramdisk=[\Device\HarddiskVolume5]\Recovery\WindowsRE\Winre.wim,{06a7379e-d1bb-11ea-8997-b888e3b1b2f5}
systemroot \windows
nx OptIn
bootmenupolicy Standard
winpe Yes
Windows Boot Loader
identifier {current}
device partition=C:
path \WINDOWS\system32\winload.efi
description Windows 10
locale en-US
inherit {bootloadersettings}
recoverysequence {06a7379d-d1bb-11ea-8997-b888e3b1b2f5}
displaymessageoverride CommandPrompt
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \WINDOWS
resumeobject {2d25babd-c701-11ea-bc80-f9e613436a82}
nx OptIn
bootmenupolicy Standard
Windows Boot Loader
identifier {4677ba16-45a9-4007-9e32-a87e737c0b41}
device unknown
path \Windows\system32\winload.efi
description Windows
osdevice unknown
systemroot \Windows
nx OptIn
Windows Boot Loader
identifier {49275add-50fb-4501-8b3b-7df483700c94}
device unknown
path \Windows\system32\winload.efi
description Windows
osdevice unknown
systemroot \Windows
nx OptIn
Windows Boot Loader
identifier {5661a75d-fc4d-4f90-8f77-af1385f5c102}
device unknown
path \Windows\system32\winload.efi
description Windows
osdevice unknown
systemroot \Windows
nx OptIn
Windows Boot Loader
identifier {591efade-37b3-42f3-b325-d3380c9352e5}
device unknown
path \Windows\system32\winload.efi
description Windows
osdevice unknown
systemroot \Windows
nx OptIn
Windows Boot Loader
identifier {8a5e4268-a211-447b-9877-f752a8ba97a6}
device unknown
path \Windows\system32\winload.efi
description Windows
osdevice unknown
systemroot \Windows
nx OptIn
Windows Boot Loader
identifier {8c19644b-24f2-4ca4-9d6b-3635eaa6a08d}
device unknown
path \Windows\system32\winload.efi
description Windows
osdevice unknown
systemroot \Windows
nx OptIn
Windows Boot Loader
identifier {95696df0-4c33-11e2-a5a4-b888e3b1b2f5}
device ramdisk=[unknown]\Recovery\WindowsRE\Winre.wim,{95696df1-4c33-11e2-a5a4-b888e3b1b2f5}
path \windows\system32\winload.efi
description Windows Recovery Environment
locale en-US
inherit {bootloadersettings}
displaymessage Recovery
osdevice ramdisk=[unknown]\Recovery\WindowsRE\Winre.wim,{95696df1-4c33-11e2-a5a4-b888e3b1b2f5}
systemroot \windows
nx OptIn
bootmenupolicy Standard
winpe Yes
Windows Boot Loader
identifier {b2d487de-ac52-4262-9678-16b4b484a9d0}
device unknown
path \Windows\system32\winload.efi
description Windows
osdevice unknown
systemroot \Windows
nx OptIn
Windows Boot Loader
identifier {bb8b618a-d59e-4827-98e2-b5975416fd44}
device unknown
path \Windows\system32\winload.efi
description Windows
osdevice unknown
systemroot \Windows
nx OptIn
Windows Boot Loader
identifier {fb49f4c6-d650-45e2-9506-8e7240a61516}
device unknown
path \Windows\system32\winload.efi
description Windows
osdevice unknown
systemroot \Windows
nx OptIn
Resume from Hibernate
identifier {2d25babd-c701-11ea-bc80-f9e613436a82}
device partition=C:
path \WINDOWS\system32\winresume.efi
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
recoverysequence {06a7379d-d1bb-11ea-8997-b888e3b1b2f5}
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
filedevice partition=C:
filepath \hiberfil.sys
bootmenupolicy Standard
debugoptionenabled No
Windows Memory Tester
identifier {memdiag}
device partition=\Device\HarddiskVolume3
path \EFI\Microsoft\Boot\memtest.efi
description Windows Memory Diagnostic
locale en-US
inherit {globalsettings}
badmemoryaccess Yes
EMS Settings
identifier {emssettings}
bootems No
Debugger Settings
identifier {dbgsettings}
debugtype Serial
debugport 1
baudrate 115200
RAM Defects
identifier {badmemory}
Global Settings
identifier {globalsettings}
inherit {dbgsettings}
{emssettings}
{badmemory}
Boot Loader Settings
identifier {bootloadersettings}
inherit {globalsettings}
{hypervisorsettings}
Hypervisor Settings
identifier {hypervisorsettings}
hypervisordebugtype Serial
hypervisordebugport 1
hypervisorbaudrate 115200
Resume Loader Settings
identifier {resumeloadersettings}
inherit {globalsettings}
Device options
identifier {06a7379e-d1bb-11ea-8997-b888e3b1b2f5}
description Windows Recovery
ramdisksdidevice partition=\Device\HarddiskVolume5
ramdisksdipath \Recovery\WindowsRE\boot.sdi
C:\WINDOWS\system32>
C:\WINDOWS\system32>