Skip to main content

ATI 2018 Bootable Media Update 2 (9850) "Error occured while opening Registry Subkey"?

Thread needs solution

Hi,

I have ATI 2018, I used the Update 2 (9850) to create a bootable CD. I backed up to a USB 3 External HDD. I needed to restore the Partition image. I used the disk I created to Restore. The Dialog said Restore succeeded, but when I looked at the log it said that "An Error occurred while opening Registry Subkey". I am now not sure if the Restored Partition image is flawless or not.

I buy this software every year exclusively to make bootable CD's and used it to back up all my machines? Is the error due to the build (9850), is this a hardware issue, or something else?. To me the experience was disappointing as I am uncertain whether my Windows 10 Pro 1709 (Fall Creator) image which was corrupted has been replaced by a good backup image.

Can anyone illuminate the meaning of the error message or tell me if the Operation succeeded message is correct?

Advice Welcomed

 

P.S.

I set the Validate option on the restore process

0 Users found this helpful

Do you have a copy of the log from the rescue media where this message is shown in context of the operations performed?  This would need to have been saved before restarting from the rescue media?

Without more information, such as what registry subkey was mentioned, if known, it is difficult to guess what this error was about?

I have not seen any other similar reports of errors involving the registry when restoring using the rescue media.

Given that the registry is just a series of files stored on disk then perhaps running a CHKDSK /R for the restored disk partition may help show whether there are any underlying disk issues at work here.  Other than this, SFC /SCANNOW to check the OS system integrity and simply booting into Windows to show whether any issues arise?

You may want to open a Support Case direct with Acronis to investigate this issue, assuming that you either have the log from the rescue media, or the issue is reproducible?

Could be an invalid registry key left from an app uninstall prior to when the backup image was created.

Hi Steve,

thanks for your post, I didn't save the log file as I was unaware that any more information was saved in it than what I was seeing on the screen. The Operating System Loaded OK. I was able to update Kaspersky and install a the new build (after restart), I was also able to do all the Windows Updates since the backup was made. The machine did all this after a restart.

It seems OK...

As you advised, I ran check disk, it found no errors, I just used the graphical windows version (after right click on computer, tools).

I ran sfc /scannow as Administrator, Windows Resource Protection did not find any integrity violations.
 

I will remember to save the log in the future.

I will have to use the machine and see if everything works OK, this is not a great option as the image I overwrote had only a couple of problems and I expected this restore to be a better image than the one I had. I now I am questioning whether restoring backups is a better option than fixing a flawed image.

any other advice welcomed

Hi Enchantech,

The backup was made using the 2018 Update 2, 9850 bootable media, there were no uninstalls that required a restart before booting to the Acronis Disk to make the Backup. The backup succeeded and in it's log no errors were reported. Also I validated the restore before doing it.

Any other ideas?

Hi,

I have been using the Validate on creating a Backup, and doing a Restore ever since I first used Acronis. Can someone explain what these options actually do? My understanding was that if the restore does not validate the restore fails. Is this true?

If anyone has a recipe for backing up and restoring which has a greater chance of working successfully I would be grateful!

 

 

Hi,

I have looked at the reliability log on the machine, it had not seen the Backup device before I plugged it in, to backup to. The drivers for the external HDD were therefore installed just before booting Acronis. Could this be the cause of the Registry Restore issue?

Any ideas anyone?

Validation reads through the backup .tib file and recalculates the checksum for the file and compares this to the value stored within the file to ensure that the file is exactly the same as when created / written to disk.

Validation cannot guarantee that the contents of the file will result in a perfect restore / recovery as that depends on what state the data was in when the backup was made.  A disk backup works at a sector level and just takes what is shown in occupied sectors and stores this in the backup .tib archive file.  If there were any problems with file integrity before the backup was created, then those problems would be present when the backup is restored.

If all your backup and restore activities are performed using the ATI 2018 build #9850 Rescue Media, then there are no additional device drives being installed here - that is a function of using Windows where such drivers are installed when a new drive is plugged in.  With the Rescue Media, only the drivers already included in that media are available to be used, and this in turn depends on the type of Rescue Media being used here?

With ATI 2018 the new default when creating Rescue Media by the Simple method is to create Windows PE media using files taken from the Windows Recovery Environment, which would included drivers specific to that computer.  If you use the Advanced method to create the media, then both the older Linux media and Windows PE media based on the Windows ADK can also be built, where both can have different device drivers.

Regarding the Registry restore, these are simply files stored on disk captured during the sector backup process and restored as the same.  Nothing done using the Acronis Rescue Media can affect these Registry files.

Hi Steve,

thanks for the explanation. I today tried to restore the original flawed image as my problem is either with Kaspersky or the last Patch Tuesday update or a combination of these things. When making the backup I rebooted after plugging in the WD USB 3 External HDD (so the Registry should not have a problem with the new drivers) When I made the Backup with verification and this succeeded and I checked the log and there were no errors in it.

Today having reproduced the BSOD on my 2 week ago Backup I restored the flawed image. This said it had completed successfully but, I had the same error opening registry subkey message in the log file which I attach.

I ran Chkdsk in windows straight after the Restore, it said there were errors and I repaired them. I ran sfc /scannow, it reported no problems.

Any ideas about what is going wrong here?

Advice Welcomed

Attachment Size
434464-141715.log 2.18 KB

The log doesn't give us any more information here than you have already shared in this topic.

I think that at this point, the best way forward would be to open a Support Case direct with Acronis and ask for their help with understanding what this log file is telling you?  There may be some way to turn on additional logging on the restore that could provide more detailed information in the log?

It sounds like you found some errors using chkdsk which you allowed to be repaired.  Such errors are in the file system itself and can exist in a backup image if the image was created from a disk having such error to begin with.  These must have been minor errors as in most cases True Image will error out when disk/file system corruption exists prior to creating the backup.

Since you fixed these errors I would not be overly concerned at this point.  It is prudent to run chkdsk prior to making a backup of an OS disk to check for corruption. 

Hi Steve and Enchantech,

I will take your advice and always run CHKDSK before backing up.

I may not have made it clear but I always create bootable media by downloading the iso file from the Acronis site. My understanding is that this iso burned onto a CD contains a set of drivers which allow access to the USB 3 EX HDD. I was under the impression that these drivers are independent of the windows 7 machine I burn the cd on. Is this true?

I did the restore again and when completed on reaching the boot menu chose reporting tool. I attach the files it produced. I hope someone can interpret them.

Advice welcomed

Attachment Size
434567-141810.txt 286.14 KB
434567-141812.txt 385 bytes
434567-141813.txt 13.79 KB
434567-141815.txt 2 KB

Looking at the text files you posted, I see the following details:

Disk 1 size 1.8TB SATA using GPT / NTFS with a UEFI, OS and 3 Windows Recovery partitions.

Disk 2 size 1.8TB USB Elements drive using GPT / NTFS with 1 partition.

I do not see anything else to suggest any problems, and nothing related to any registry errors.

In reply to by truwrikodrorow…

I have the same problem - I made a backup using the bootable media, and later when I went to restore it (with a the verify first option selected), right at the very end I got the "error occurred wile opening registry subkey" error message, immediately followed by a restore successful message (!).

This begs the question: why, after a sector by sector restore, does True Image need to look at or modify the registry at all?

I did save my log, but it isn't helpful:

<?xml version="1.0" encoding="UTF-8" ?>
<logs>
<log build="12510" product="Acronis True Image" task_name="Recover" uuid="7F3D580F-5B09-2943-3D87-1F3B481A8EAA" version="22.5">
    <event code="0" id="1" level="2" message="Operation &quot;Recover&quot; started." module="100" time="1533507296" />
    <event code="1026" id="2" level="2" message="&lt;bold>Validate Backup Archive&lt;/bold>&lt;endl/>&lt;tabpoint value=30>&lt;indent value=4>Location:&#9;&lt;indent value=10>&lt;textcolor value=&quot;navyblue&quot;>&quot;\\192.168.7.77\homes\sylerner\Backups\Druk - Deployed - No Office\Druk - Deployed - No Office_full_b1_s1_v8.tib&quot;&lt;/textcolor>&lt;/indent>&lt;indent value=4>&lt;endl/>&lt;/indent>&lt;endl/>" module="11" time="1533507296" />
    <event code="504" id="3" level="2" message="Pending operation 4 started: 'Validate Backup Archive'." module="1" time="1533507296" />
    <event code="1020" id="4" level="2" message="&lt;bold>Recover Backup Archive&lt;/bold>&lt;endl/>&lt;tabpoint value=30>&lt;indent value=4>From file:&#9;&lt;indent value=10>&lt;textcolor value=&quot;navyblue&quot;>&quot;\\192.168.7.77\homes\sylerner\Backups\Druk - Deployed - No Office\Druk - Deployed - No Office_full_b1_s1_v8.tib&quot;&lt;/textcolor>&lt;/indent>&lt;indent value=4>&lt;endl/>Recovery of:&#9;&lt;indent value=10>&lt;textcolor value=&quot;navyblue&quot;>Disks&lt;/textcolor>&lt;/indent>&lt;indent value=4>&lt;endl/>&lt;/indent>&lt;endl/>" module="11" time="1533510387" />
    <event code="504" id="5" level="2" message="Pending operation 20 started: 'Deleting partition'." module="1" time="1533510387" />
    <event code="504" id="6" level="2" message="Pending operation 14 started: 'Recovering partition sector by sector'." module="1" time="1533510387" />
    <event code="74" id="7" level="4" line_tag="0xF23788D3F6D588B2" message="Error occurred while opening registry subkey." module="190" time="1533512521">
        <field name="$module" type="TIdentifier">trueimg_home_media_glx_12510</field>
    </event>
    <event code="252" id="8" level="2" message="Recover operation succeeded." module="100" time="1533512521" />
</log>
</logs>

Any help in figuring out what's going on would be appreciated.

Welcome to these User Forums.

From looking briefly at your log information, it looks that you have done this Validation & Recovery from the Windows ATI 2018 application, not by using the Acronis Rescue media, and as there is no indication that a computer restart was required, that you were recovering a non OS partition or disk?

As this was done within Windows, then the message:  "Error occurred while opening registry subkey." is most likely related to the recovery task writing information to the Acronis Database and looking for information in the registry for this reason. You would need to open a Support Case with Acronis to get a full confirmation of this but if the recovery was successful, as indicated in the log, then this message can be ignored.

I would recommend using the MVP Log Viewer tool (available from the Community tools link below) to read and copy log details, as this renders the information much easier to read than seeing the raw XML data format.