Skip to main content

How to exit ATI 2021?

Thread solved

I cannot find any way to exit True Image 2021 when it is not in use.  There is no "Exit" or "Quit" command in the GUI or in the pop-up menu from the tray icon, and it is not even possible to quit the application by killing the process in Task Manager.

Am I missing something?

0 Users found this helpful

Obviously, I have tried clicking the "X" in the upper right corner of the ATI window, but this only hides the program window -- the ATI tray icon is still present, and all of ATI's processes are still running (as revealed in Task Manager).

My need to use ATI is limited to imaging a disk 1-2 times at year max, so I don't need or want ATI to run continuously.  Is my only recourse to uninstall the software and reinstall it each time I need to create a disk image?

J K, the ATI 2021 GUI can be closed by clicking on the X in the top right corner or else click on the icon in the top left corner to see other options.

Steve,

Thank you for pointing out the little top left icon.  However, selecting "Close" only seems to hide the window.  After "closing" the program, ATI still has a presence in the system tray, and 13 processes still running in the background (including "Acronis True Image 2021").

J K, you are only able to close the ATI GUI, the system tray notifications icon will stay there as will all the background services and processes which run all the time that Windows is active.

See KB 65464: Acronis True Image 2021: Windows services and processes - for details of all these and help to decide if you want to set an Services to Disabled start via the Services Control panel, i.e. Non Stop Backup and Sync Agent plus the 2 Mobile Backup services if not being used.

That's quite a mess of services and background processes (most of which I have zero need for)!  I am inclined to uninstall ATI 2021, and just run True Image from Acronis bootable media whenever I need to image or restore a disk or partition (since I anticipate needing to do this only infrequently, at most 1-2 times annually).  Would there be any substantive issues with routinely using ATI this way (via bootable media) instead of via the bloated Windows app? 

J K, there should be no significant issues in just using the Acronis Rescue Media to create regular offline backup images other than that there would be no updates for this media unless you have ATI 2021 installed on this or another PC to recreate the rescue media after any new builds are released.  There is normally a new 'sticky' forum topic to announce new updates / builds with details of some of the issues that were resolved by the same.

Thank you.  I will probably try this approach.  However, I've only been able to successfully create the simple Linux-based bootable media.   When I first installed ATI 2021 on this computer, I attempted twice to create "WinPE-based media with Acronis software" on an external USB flash drive, and the operation failed.  Now that I have the log viewer, I found the following error messages:

8/22/2020 11:24:36 AM: -04:00 12324 I00180000: Activating media...
8/22/2020 11:24:36 AM: -04:00 12324 I00180000: Copying files...
8/22/2020 11:24:36 AM: -04:00 12324 E00180000: Error 0x180023: Unable to copy the product files.
| line: 0xaa76ebb96e715536
| file: c:\jenkins_agent\workspace\579\products\imager\home\builder\logic\impl\utils_winpe.cpp:2148
| function: TrueImage::MediaBuilder::WinpeRemovableMediaBuilder::MakeUsb
| line: 0xaa76ebb96e715536, c:\jenkins_agent\workspace\579\products\imager\home\builder\logic\impl\utils_winpe.cpp:2148, TrueImage::MediaBuilder::WinpeRemovableMediaBuilder::MakeUsb
| $module: ti_managers_vs_30290
|
| error 0x180023: Failed to copy file or folder 'bootmgr.efi.mui'.
| line: 0xaa76ebb96e715390
| file: c:\jenkins_agent\workspace\579\products\imager\home\builder\logic\impl\utils_winpe.cpp:1726
| function: `anonymous-namespace'::CopyDirRecursive
| line: 0xaa76ebb96e715390, c:\jenkins_agent\workspace\579\products\imager\home\builder\logic\impl\utils_winpe.cpp:1726, `anonymous-namespace'::CopyDirRecursive
| $module: ti_managers_vs_30290
|
| error 0x4000a: Error occurred while creating the file.
| line: 0xf35f747b3b21f903
| file: c:\jenkins_agent\workspace\579\core\file\windows\winnt_dir.cpp:506
| function: winnt_dir::OpenFile
| line: 0xf35f747b3b21f903, c:\jenkins_agent\workspace\579\core\file\windows\winnt_dir.cpp:506, winnt_dir::OpenFile
| function: CreateFileW
| path: \\?\D:\bg-BG\bootmgr.efi.mui
| $module: ti_managers_vs_30290
|
| error 0xfff0: The parameter is incorrect
| line: 0xbd28fdbd64edb8f1
| file: c:\jenkins_agent\workspace\579\core\common\error.cpp:307
| function: Common::Error::AddWindowsError
| line: 0xbd28fdbd64edb8f1, c:\jenkins_agent\workspace\579\core\common\error.cpp:307, Common::Error::AddWindowsError
| code: 0x80070057
| $module: ti_managers_vs_30290
 

Any advice?

J K, your log has 2 entries:

path: \\?\D:\bg-BG\bootmgr.efi.mui
| $module: ti_managers_vs_30290

Is D: the drive letter for your USB drive you were using to create media?

The log is dated back in August 2020 using the first public build of ATI 2021 #30290 which was quickly superseded by later builds.  Please test the media builder with the latest #35860 build installed.

The size of the USB media used should be 32GB or smaller in size, down to 2GB size and be formatted as FAT32.  Media creation should be performed from an Administrator account without any interference from any installed security applications such as antivirus.

Yes, the D: drive was the external USB that was the target for the bootable media.  I believe all preconditions were met (<32 GB, FAT32, etc.).

I will update to the latest version and try again.  If it fails again, I will start a new forum topic, so that I can mark this thread solved.  Thank you for your help with this and my other questions.