Skip to main content

INACCESSABLE_BOOT_DEVICE after upgrade to Acronis True Image 2017 from 2016 win 10 x64

Thread needs solution

HP Envy 17

Windows 10 x64 

SSD 500gb samsnug pro 460 ( I think) NTFS

had diskdirector 12 and trueimage home 2016

upgraded to Trueimage 2017 NG

after install noticed that 2016 version was still showing up and when I run True image 2016 comes up 

but I could see both true image 2016 and 2017 in installed apps in windows. 

I did not have any additional parts like secure zone etc installed from trueimage.

in the change and remove programs > uninstalled 2016 version

still 2017 would not load.

uninstalled 2017 and reboot ... 

disaster!!!

 

 

Blue screen 

INACCESSABLE_BOOT_DEVICE 

 

from recovery

tried system restore .. could not restore 2 of the points I had  after many tries

tried start up repair ... no luck

sfc /scannow didnt find any issues but I was not sure if it is checking the correct windows install so I would poit it to c:\windows offline check and it would say it can not check it

 

DISM offline would not run 

seams like they did not have permission to access the c:\windows folder , even though I could access it via the recovery comand line, or hirein boot cd or linux boot cds

 

chkdsk /r /x  found some files but did not do anything 

 

bootfix mbr   did not help

 

loaded hiering bootcd > regedit PE> loaded the registry from c:\windows and removed all traces of snapman, snapap and acronis 

 

nothing works

 

I have many apps installed , expensive programs activated and some I am not sure if I can find the key for them so I would really like to revive this windows install.

 

tried upgrade installing win 10 from recovery but it only does windows upgrade install from inside windows... any other way I lose my installed apps..

 

this might be a simple fix that I just dont know  but it id defnitly related with acronis

 

please help 

 

 

 

 

0 Users found this helpful

per

 

https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/d…

 

Dism /image:c:\windows /cleanup-image

 

gives

Error : 2

Unable to access the image

 

here is the log it saved 

 

https://pastebin.com/sWKBRtw3

 

===========

 

dism /Cleanup-Mountpoints

 

did not fix anything either

DISKPART att clear 

went through this to make sure there is no read only or head partition or volume.. 

again it did not change anything 

I do not understand why DISM and SFC do not have access to the c:\windows image

Far Z, welcome to these user forums.

I am sorry to hear of this critical problem following your upgrade from ATIH 2016 to 2017.

Do you have a full disk backup of your Windows OS drive created with ATIH 2016 that you can use to recover your system?  If you do, then that would appear to be the best way forward, but you may wish to make a further backup of the OS drive to capture any updated user data that a recovery would overwrite with older copies.

If you want to try to recover the computer as it is, then I would strongly advise to open a Support Case directly with Acronis Support and allow them to work with you on this problem.

Just have to say this...

 

after 10 days  of dealing with this and manytechnician hours could not figure it out 

Acronis was very useless..

 

 

I came to acronis to save a backup of my working data.. I ended up with a disaster of losing my windows and apps because of acronis.

 

there tech support was a useless indian guy across the globe with copy paste data and a promise for contact from high tier tech support by email which never happened 5 days later 

 

SHAME! ACRONIS WILL NEVER BE INSTALLED ON MY COMPUTER AGAIN BEWARE

INACCESSABLE_BOOT_DEVICE errors can usually be fixed by applying Acronis Universal Restore and supplying the driver for the controller that the Windows hard drive is attached to.

In reply to by truwrikodrorow…

so I should make am image of the drive with acronis and then restore it as a universal restore? to the same harddrive?

 

my apps setting will be safe?

You should be able to just boot from the Universal Restore media and let it find your existing OS then let it prepare this to work with the hardware where it is installed.  There should be no need to image the drive then restore it back again - Universal Restore is not used to restore images, only to prepare what was restored (or is already there).

As Paul advised above, AUR may ask for the device drivers for the disk storage controller where the OS is found.