Archive for the ‘DriveImage XML’ Category

I upgraded to Windows 7 and now I can not see any of my drives in your software!

Wednesday, October 28th, 2009

Q: After upgrading to Windows 7, I can not longer see my drives in any of your software.

A: This is due to the UAC that Windows Vista and Windows 7 have in place. In order to bypass this, you can simply right click on the icon of the program you are running and selecting “Run as administrator”. You will then have access to the physical drives at this point.

You must do this even if you are the administrator of the computer. If you have any questions regarding this, feel free to contact us.

Why is there no “verify” in DriveImage XML?

Saturday, September 19th, 2009

Many user are asking us if there is a “verify” for a backup created in DriveImage XML. There isn’t, and this is for good reasons.

Let’s think for a second what a verify should do. It should confirm that the content of a backup is identical with the original data. It should also confirm that the backup files were written correctly to the media.

A backup program doing a verify can only compare what it thinks the data is to what it thinks the data in the backup is. Suppose the backup program makes a mistake when it first writes the backup. It will make the same mistake again once it verifies the backup. Therefore, you should never trust a backup program’s own verify. The only proper and recommended way to verify a backup is to restore it to a new disk.

Comparing backup and original data is not even possible because DriveImage XML uses VSS “hot-imaging”. This means the data is no longer the same an instance after the backup started.

As for the verification the backup files being written without error to the hard drive, with today’s hard drive technology it makes no sense to re-read data written to a disk, as this is verified on a hardware level. There is no need for a program to engage in such a time-consuming task.

You should only trust a backup you have been able to restore, and where a compare of the original drive with the restored drive is satisfactory.

Fixing Error 8000FFFF in DriveImage XML

Thursday, April 2nd, 2009

We have created a video tutorial regarding error 8000FFFF and how to fix it on YouTube. Here is the list of files that are needed to be run from the command prompt and they need to be run from the Windows\System32 folder. A high quality version of the movie can be found here (WARNING!! This file is 100MB in size).

  • Net stop vss
  • Net stop swprv
  • regsvr32 ole32.dll
  • regsvr32 vss_ps.dll
  • Vssvc /Register
  • regsvr32 /i swprv.dll
  • regsvr32 /i eventcls.dll
  • regsvr32 es.dll
  • regsvr32 stdprov.dll
  • regsvr32 vssui.dl – (For Windows 2003 only)
  • regsvr32 msxml.dll
  • regsvr32 msxml3.dll
  • regsvr32 msxml4.dll
  • Net start vss
  • Net start wsprv

Big update to DriveImage XML…

Friday, July 18th, 2008

There is a new version of DriveImage XML available today. We now have a new option on compression and we have made the software much faster.

Lets have a look. This was the old version backing up a 10GB NTFS partition that has 5.93GB of data on it. We were backing the data up to the My Documents folder on the C drive.

As you can see, it took about 12 and a half minutes to complete the backup.

The backup size of the dat and xml file was 5.28GB

Now we backed up the same data on an external drive with the same settings as :
It only took about 20 seconds longer, but this is a small drive with not a lot of data. Had this been 100 or 200GB of data, the extra time would have been substantial.

There are some new options on the new version. You have the ability to choose if you want fast or good compression. Fast is much much faster. Good is still pretty slow but it does a good job. We recommend that you always use the fast option.

So now we took the new version and backed up the same drive with the fast option and saved the data and xml in My Documents
Only 3 minutes and 15 seconds!
The file size is only slightly larger as well, but this will be different on everyone’s computer:

Now we will take the same settings as above and save the data to a USB 2.0 External drive:
Still only 4 and a half minutes!

A few things about the slow compression:
The slow compression is still faster than the old version by two minutes in our internal test.
The size is about 500 MB smaller than the fast compression, however this will again vary with the types of files you have and how many files you have.

!!IMPORTANT!! There are a few issues with the new version. The image you make on the new version is not compatible with the old version. If you have a BartPE with the old version, rebuild it with the new version as the image will not restore with the old software.

We do not offer any support for this software since it is free, however if you have an issue that you feel needs to be looked at, let us know.

Some information about DriveImage and dealing with drives with hidden partitions…

Friday, July 13th, 2007

Kenneth writes:

First off, DriveImage XML is awesome. Absolutely the easiest product I’ve used to date. Good work.

I used it to copy a system drive from a Dell Laptop to a new drive. Apparently Dell puts a small partition with utilities on all primary hard drives. So when I restored my Windows system partition image to the new drive in which I made a single active primary partition, the boot.ini file was slightly off.

When I booted off of the hard drive the first time the normal windows boot menu came up. I let it do the default os boot, but it said that it could not read from the drive.

But when I looked at the drive in a different computer I could read everything. It dawned on me that I should look at the boot.ini. Upon looking at it I found that the default boot was:

multi(0)disk(0)rdisk(0)partition(2)WINDOWS=”Windows XP Professional” /fastdetect /noexecute=optin /numproc=2

Changing it to:

multi(0)disk(0)rdisk(0)partition(1)WINDOWS=”Windows XP Professional” /fastdetect /noexecute=optin /numproc=2

…did the trick.

DriveImage XML – Could not flush write buffer

Friday, July 6th, 2007

We get email all the time about DriveImage XML. One of the main ones is the error “Error – Could not flush write buffer …..”.

Users say that they have more than enough room on the drive but the backup fails every time after copying about 4GB. The problem is that you are copying to a FAT32 drive. FAT32 does not allow files to be larger than 4GB.

You can find more information about this at You have two solutions to this problem, the first one is to format the drive to NTFS which is preferred by Windows XP, or you can just turn on the Split Large Files option in the software.

If you have any DriveImage XML issues you would like to see answered, let us know by emailing us at

Creating a Bart PE CD

Thursday, May 31st, 2007

We get email all the time with people having problems with the creation of a Bart PE CD.

Since we do not make the Bart PE software, we do not support it. However here is a video tutorial of making a Bart PE CD. If you have any questions, email us at

Data Encryption in Data Recovery and DriveImage XML…

Friday, May 11th, 2007

Here is a questions we get all the time, “Why can’t I extract a working copy of my encrypted data from my recovery or my DriveImage?

Recovering encrypted data with GetDataBack…

This can be answered with a question: Why did you encrypt your data? The answer induces anger in most people because they do not think it through before they encrypt their data. The answer is ‘because I do not want anyone getting access to my data’. That is the entire point of encrypting your data, so no one can get access to it. Computers do not have self awareness, they do not look through their own monitor and say “Oh, its my owner, give them access to the data.“, Once you lose a partition table, or suffer file system damage, GetDataBack can not recover encrypted data because of the exact reason you encrypted it in the first place, so someone can not get access to your data, including yourself. You might be able to send the drive to a hardware recovery company like DriveSavers and have them do it by hand and recover the encryption key and apply the key to the files and recover them.

Extracting encrypted data with DriveImage XML…

When you are using DriveImage XML and trying to extract a file that is encryted, it will give you the message telling you it can not extract encrypted data. This is because the software does not look for the encryption key, it just does not let you copy the data. However if you restore the image to a drive and boot from it, you can have access to that data again because the key is restored and the data matches the key as it did when you made the image.


If you decide to encrypt your data, keep a backup of it in a safe place. You can not use DriveImage if you want to extract files from the image at a later time without restoring the entire drive. Put it on an external drive that you keep in a safe or keep it on a CD or DVD that you can hide someplace as well. If you need data recovery for encrypted data, it will be expensive and time consuming.

DriveImage XML

Tuesday, April 3rd, 2007

Because DriveImage is free, we do not offer support for it, however there are plenty of places to find the information you need. Here are a few of them: (a user’s tutorial) user’s tutorial)

You can also watch our video tutorial here: