Aller au contenu principal

True Image 2016 installs in 32 bit format on Windows 8.1 Pro 64 bit machine?

Thread needs solution

Why does True Image 2016 Home install as a 32 bit program on a Windows 8.1 Pro workstation? It installs in the Program Files (x86) directory and Task Master shows it running in a 32 bit mode. Can True Image 2016 Home be installed to operate in a 64 bit mode?

0 Users found this helpful

Hello, Thomas.
True Image does indeed run in 32-bit mode only, whether it's a 32-bit or a 64-bit version of Windows.

Thanks Dmitry.
True Image 2016 home seems to run as old legacy programs do. As a source is selected there is a big lag with the (program not responding) showing until after a time that source shows up in the source area. Again when the destination is selected the is a big lag, again with the (program not responding) showing until the destination is finally shown in the destination area. When backup now is selected the program runs pretty much normally. This is what I experience with old legacy programs running under compatibility mode. I was hoping there was a more responsive mode available. Guess this will have to do.

Best Regards,

Tom

Dear Thomas,

I think you can run it as 64 bit. You need to boot from recovery USB-stick/dvd then select the 64 bit version.
I dont think its a solution for your problem, but thats how it can be done if needed.

Regards,
Patrick

Thanks Patrick,

I guess it is not really necessary to run it in 64 bit mode. I was just inquiring because I had so much trouble getting it to install properly and run that I thought I was doing something wrong. It now runs and does a backup and I can validate the backup. I had to uninstall the upgrade from 2015 to 2016 and then reinstall 2016 to get the program to make a back up that it would see and validate. I have been able to successfully use the make the rescue media builder to make a USB stick bootable rescue media. However I am having problems creating the universal restore media. I get all the way through the process and the USB stick I am using is not shown as one of the media output selections that I can choose. I am sure it is something I am doing wrong. I just have to spend some time finding where I am making my mistake. That is probably another question I need to post but that is another subject.

Regards,

Tom

Dmitry Nazarov wrote:

Hello, Thomas.
True Image does indeed run in 32-bit mode only, whether it's a 32-bit or a 64-bit version of Windows.

Hi Dimitry...

but WinPE recovery does only support 64bit ? I really cant understand your Roadmaps what is supported and what not....

S22

The Windows installed application is 32 bit and can run on a 64 bit Windows installation. This is so because there are still many 32 bit Windows installations out there in the customer base. The 64 bit seen using the boot media is an option design present for those booting UEFI machines to solve boot issues on those machines. The application is then run under a Linux based OS environment which is still 32 bit.

WinPE recovery support depends on which ADK is used in the creation of the WinPE disk. Again the TI app runs in 32 bit mode.

Thomas, you should try a different brand media in creating your Universal Restore media, Scan Disk flash drives are known to be troublesome in this area and you will need a flash drive of at least 8GB capacity.

[quote=Enchantech]

WinPE recovery support depends on which ADK is used in the creation of the WinPE disk. Again the TI app runs in 32 bit mode.
[quote]

Hi Enchantech...

for ATI2015 and ATI2016 it seems that ATI Plugin for WinPE is only available in 64bit mode....
At least this is statement of Mustang, another MVP:

https://forum.acronis.com/forum/99369

see #5

Did you manage to get a WinPE32 boot medium including ATI2016 running on a 32 bit UEFI system?

S22

No I have not and Mustang is correct. The fact remains that TI is still a 32 bit application and can run on 64 bit Windows and compatible hardware. The WinPE 64 bit applies to the Windows environment of the WinPE disk, not that True Image is a 64 bit application when run under WinPE.

Thanks Enchantech,

I built the Universal Restore media using a non SanDisk USB stick and it worked like a champ. Many thanks. It is amazing that one of the major brands of removable media has this problem. I used a generic Staples USB stick and everything worked as it should. Could you recommend what Windows drivers for mass storage devices I should add to the media. Any help in that area would be appreciated. I don't really understand the WinPE stuff or the UEFI, I just want to be able to restore to my current HDD or similar if it becomes necessary in the future.

You have been a really big help top me.

Thanks,

Tom

Thomas,

Which storage drivers would be necessary is totally dependent on which specific storage controller is used on the new hardware (motherboard) of the target device. In general a different motherboard that uses a controller from the same manufacturer as the existing device may well not need such drivers to boot the restored drive. For the most part the critical issues with a restore to dissimilar hardware are motherboard chipset drivers, mass storage drivers, and USB drivers. Network NIC drivers may be necessary for the new NIC to establish network connection but should not inhibit boot of the device.

I have found that when it comes to mass storage drivers such drivers are necessary only if you are making a change in manufacturer of storage controllers, Intel for Asmedia for example. When staying with the same manufacturer there probably will not be an issue to boot into Windows with current drivers. This is not to say that drivers should not be updated nor that you may not be able to boot the machine. But for most users updating drivers is easier to do from within the Windows environment.

I have also found that performance can vary between mass storage drivers and the rest of the hardware on any given machine. It is possible that an older driver may outperform a newer version depending the rest of the hardware in the device. The best way to determine which is best as far as performance goes is unfortunately through experimentation which most users do not care to do.

Thanks Enchantech. That was a pretty clear explanation that even a casual tech user like myself can understand and use. If I am restoring to my same workstation that the original source drive was backed up in then I am unlikely to need new storage drivers as they will be on my full back up. If I am restoring to a different machine, with a different motherboard and chip set then I would probably need to find the necessary drivers for the new machine to be bootable.

Glad you are around to help the casual user like myself.

Many thanks,

Tom

You are welcome and correct. Universal Restore is not needed unless recovery is done to a device that has had different hardware installed. This in most cases means motherboard replacement to that of something different than what was in place when the backup image being restored was created.

Hi all...

  Odd (related) problem with ATI 2016 #6027, a 32bit app but the serial is being stored in the WOW6432Node registry (only).  This was on a Win10 (x64) clean install of #6027.

  Not sure if this is correct but its throwing off WinPE build/deploy scripts.

Please describe what you mean by "throwing off "?