Using Universal Restore returns "...the following file is missing or corrupt: System32\Drivers\Ntfs.sys"
I am testing the UR add-on by attempting to restore an image from a HP NC8000 to a HP DV7 and have run into some problems:
Firstly, I have created an image of an HP NC8000 with XP SP2 via Acronis BR 10.0 Workstation with UR and am attempting to restore the image to the same machine. BRUR returns successful after the restore process, however, the machine fails during the boot sequence displaying the error message:
"Windows could not start because the following file is missing or corrupt:
System32\Drivers\Ntfs.sys".
Next, I get exactly the same result when restoring the NC8000 image to a HP DV7. So it is not a "bad memory" issue.
Then, interestingly, I tried restoring the NC8000 image back to the NC8000 a second time - this time without using the Universal Restore option - and the image restored and booted successfully. So the image itself is fine.
In my searching I came across this thread on the old forum (http://www.wilderssecurity.com/showthread.php?t=90920), however, it was never properly resolved there.
I have also tried the microsoft suggestion of restoring the specific file (Ntfs.sys) from the original boot CD, but to no avail - it returned the same error message again.
NB. I've been able to successfully restore an image to dissimilar hardware for Windows 2003 Server Std. ed and for Windows 7 using the same settings in BRUR 10.0, so it's strange that XP doesn't work. My next step is to attempt to restore an XP image from a Dell Precision M6400 to the NC8000. Failing that I'll try a different XP installer altogether. Otherwise, I'm a bit stuck.
So, my main question is: What would cause this to occur and how can this be rectified?
Regards,
Jarrad.

- Log in to post comments

UPDATE : Also tried re-backing up the image with the "sector by sector" option selected, but failed again with the same error message on boot when using the UR add-on.
- Log in to post comments

UPDATE: Tried with completely different XP (SP3) installer and it works without issue when using UR (both to itself and dissimilar hardware). On further investigation (when md5-ing files in \windows\system32\drivers) it looks like the custom XP installation has changed most of the .sys files (including ntfs.sys)
I suspect that Universal Restore is replacing some of these custom files with it's own version and breaking the system.
Does anyone know if that is how UR works?
Is it possible to get UR to use these custom files instead?
Thanks in advance,
Jarrad.
- Log in to post comments

Hello Jarrad,
Thank you for choosing Acronis Backup & Recovery 10.
Universal Restore is responsible for HAL level drivers replacement (to make your system bootable in case of dissimilar hardware recovery). It's not necessary to choose this option when you recover to the same hardware. The important thing is that Universal Restore cleans up all drivers from your old system, probably corruption occurred after this process. File ntfs.sys is a driver for your filesystem.
Probably the corruption occurred during the backup itself. Is it possible for you to completely recreate archive from another computer and check the results?
We are looking forward to hearing back from you at your earliest convenience.
Thank you.
- Log in to post comments

Hi Alexander,
thank you for your reply. The answers to your post can mostly be found in my previous posts (above). In short I've verified that: it is not an image problem; it is not a hardware problem; And it is not a 'missing or corrupt file' problem (at least in the conventional sense).
I could be wrong, but at the moment I am convinced that it's just an additional operation Universal Restore does that I'm not aware about - which I'm sure can be easily overcome with an additional setting or a workaround of some sort. But to do that I need to know a little more about how UR works.
When you say "Universal Restore cleans up all drivers from your old system", do you mean that it deletes or replaces all the .sys files in the \Windows\System32\Drivers\ directory? What dirvers and/or directories does UR 'clean'?
Also, what do you mean by "Universal Restore is responsible for HAL level drivers replacement", can you provide more technical details please?
Thanks again for your efforts,
Jarrad.
- Log in to post comments

After another phone conversation (and some pointed questions) with one of the technicians (called Gurprakash) I have finally begun to get some answers. I was informed that:
1. When the UR option is selected, it will delete the system32 directory, and replaces it with it's own or a provided system32 directory/files.
2. However if no serarchable locations were provided it will still perform the Universal Restore operation but will retain the directory and files on the image.
I was also given an address to go to for more information on the HAL (http://kb.acronis.com/content/2149), however, while looking useful this didn't actually answer any of my questions. I was then informed that:
3. The boot CD doesn't contain any generic hals or drivers.
Up to that point all this looked quite helpful ...the third point seemed odd - maybe I just didn't hear him correctly. When I tested these things this afternoon, they all failed in exactly the same way as before: "...\Ntfs.sys missing or corrupt". Back to square one.
To test point 1:
- I Copied the ..\Windows\System32 directory from another working system with identical hardware AND OS onto USB.
- And during the restore process selected Universal Restore > Use (option)
- And selected the Search folder > Change... (option) and chose the path to the copied directory.
- Selected the validate backups and check file system options in the Additional settings dialogue (as per ususal)
- And told it to start. It returned "Succeeded with warnings" (as it alwasy does when using UR) and on boot it failed.
NB. When I asked specifically if this would work, the technician said 'yes'.
To test point 2:
- During the restore process I selected Universal Restore > Use (option)
- And set the Search removable media option to OFF.
- I then selected the validate backups and check file system options in the Additional settings dialogue (as per ususal)
- And told it to start. It returned "Succeeded with warnings" (as it alwasy does when using UR) and on boot it failed again.
So in the end it looks like I was either:
1. Lied to and told what I wanted to hear
2. The technician has no idea of how UR works
3. Or there's another way to overwrite the problematic driver files (which I still believe is mostly in the system32 directory) that I haven't been told about.
At this point - having received little-to-no support - I am very disappointed with Acronis.
- Log in to post comments

Hello Jarrad,
Thank you for using [[http://www.acronis.com/enterprise/ | Acronis Corporate Products]]
To find the exact reason of the malfunction we need the AUR debug log. But first of all, please recover the archive using the latest build of Acronis Bootable Rescue Media based on ISOLINUX. We have implemented the possibility to download the appropriate ISO file after logging in to your account (the serial number should be registered). Please log in to your account, go to the Registered products section -> Bootable media. Download the file and create the CD.
You can find more information on how to burn an ISO image to a CD here and here.
After that please restore the archive (the step-by-step guide is available here) and see if the issue remains.
Please post the results and let me know about it via PMs.
Thank you.
- Log in to post comments