My Windows 8.1 doesn’t like the NTI Echo 3 cloning utility..

Published on: Author: Mike Hall 6 Comments

When attempting a clone of one drive to another, the program being used did not like the ATAPI bridge that I was using, in actual fact claiming that it didn’t like any ATAPI bridge.

So, when I saw somebody recommend NTI Echo 3, I thought that I would give it a go. The software was downloaded, paid for and installed, and it duly started with no issues. I closed it down, not wanting to do the clone at that time, and all appeared well.

Between then and now, I have upgraded Windows 8 to 8.1 and, after having done so, found no obvious incompatibilities with stuff I ran daily. So the day comes to use NTI Echo and a double click did nothing.

NTI support assured me that it had been tested with Windows 8 and a clean installation of Windows 8.1 and found to have no problems. NTI must test during the night because I was quick to install 8.1 as soon as it was released, and equally quick to want to clone my primary drive.

After a variety of suggestions from NTI, I clean booted Windows 8.1, Echo appeared to start ok, but closed with the error..

“The instruction at "0x00c6bade" referenced at memory "0x00000000". etc etc

Needless to say, NTI Echo 3 is still not working..

I assured NTI support that the only change to the system was the upgrade to Windows 8.1, but it is insisted that I have a program running in the background which is upsetting Echo 3. That’s as maybe, but what I have running I want running, and if that means that Echo 3 won’t run, so be it. I used Aomei partition manager to clone the drive in the end, without issues, without having problems with single user activations, a nice clean process..

My advice re NTI Echo 3.

  1. If you want a utility which you can use on multiple machines if the need to clone a boot drive is required, forget Echo 3 because NTI don’t want or allow you to do that.
  2. Approach it with caution if you are presently running Windows 8 and intend to upgrade to Windows 8.1 in the near future. You may have better luck than I did, but don’t count on it.
  3. There are free utilities which do the job, and which can be installed on as many computers in your home as you have, and the utility should work, even via ATAPI bridges. Aomei is a good choice.

As NTI Echo is still activated on this machine, I will wait awhile until a newer version of the utility appears, download it and see what happens. In the meantime, I would like to hear from others who have experience with NTI Echo 3.. 

6 Responses to My Windows 8.1 doesn’t like the NTI Echo 3 cloning utility.. Comments (RSS) Comments (RSS)

  1. I can confirm that NTI Echo doesn’t work for me under Windows 8.1 either. I downloaded the free version for the Toshiba SSD and it worked just fine under Windows 7.

    Under Windows 8.1 it doesn’t open. It requests administrator privs and then nothing. So, my solution was to install the free AOMEI Partition Assistant. It worked just fine.

    I did have to “repair” the Windows 7 install that I’d moved. I’d copied the “boot loader” partition (100 MB) and the main partition with Windows 7 on it and then had to boot up with the Windows 7 installer CD to let it automagically repair the boot loader… easy enough.

  2. Same scenario here. NSI Echo 3 downloaded from site, with provided serial nbr, doesn’t open on Windows 8.1 x64. Frustrating experience and negative marketing issue for Toshiba SSD.

  3. Mr. Hall,

    After you contacted us we found that a flash memory card reader with empty slots will prevent Echo form opening.

    To work around it you can disable the drives associated with your memory card reader’s slots and Echo will open and run. This happens on more than just Windows 8.1 because it is not a compatibility issue with Windows 8.1.

  4. Well, I didn’t have a card reader installed at the time as I remember, and I certainly would not entertain use of a utility where I have disable parts of the computer hardware in order to get it working.

    Sorry NTI, but you lost out to a free application where the user does not have to disable anything. That you admit to it failing on other operating systems further reduces credibility in the product.

    To get people like me on board/back on board, you are going to have to do a lot better, and be a lot less dogmatic when a user tries to find an operating system upon which an NTI utility will actually run..

Leave a Reply