2021 version. There is a problem with build 3048.
2021 version. There is a problem with build 3048.
My computer uses UFEI boot on Windows 10, 2004 version.
2021 version. Create a backup of your computer after installing build 3048.
The computer restarts after attempting to recover.
However, the computer freezes during preparation and does not proceed further.
Clean install Windows and create a backup. Even if you proceed, it does not proceed the same.
I saved a backup copy of my computer on a SATA SSD and connected it there.
My computer is using a 7th generation cpu and motherboard.
But when in 2020 version performed in the same manner after the installation proceeds smoothly to backup and recovery.
Has anyone experienced the same symptoms as me?
I do have exactly same problem using a legacy boot windows 10-system.
2021 version. Create a backup of your computer after installing build 3048.
The computer restarts after attempting to recover.
However, the computer freezes during preparation and does not proceed further.
OP: How are you attempting to perform the Recovery here? It sounds like you are starting this from within Windows instead of using the ATI rescue media to boot your computer in UEFI mode into the offline ATI environment.
Doing a restart from Windows launches a small Linux based OS environment which can give different results to using the 'Simple' WinPE / WinRE boot media.
KB 65508: Acronis True Image 2021: how to create bootable media
KB 65539: Acronis True Image 2021: How to restore your computer with WinPE-based or WinRE-based media
I have a computer with an NVMe drive in AHCI mode set up in BIOS.
TI version 2020 works perfect using Linux USB Bootable Media or even Windows restart version.
TI 2021 with same configuration freezes with Linux Bootable Media and also when restarting Windows to recover.
I can only say that Acronis must have updated the version of Linux used by ATI 2021 from that used on 2020. Please open a Support Case direct with Acronis to report this issue and allow them to investigate if it can be resolved?
The new default for rescue media is to use WinPE / WinRE because of superior compatibility with current / recent hardware.
lanL-s //
Even if no antivirus program is installed
I have the same problem.
Well... thanks for your answer. :)
=====================
Steve Smith //
yes, my computer uses nvme drive.
As you said.
I tried KB 65508 and it failed.
However, B 58006 and KB 65539 did not try.
I have successfully recovered using the 2020 version
If you have work to recover again, I will follow your advice.
Thanks for the advice.
Exactly the same issue, freezes at varying points, same issue with the Linux boot.
Whatever was updated in the last 2021 build, broke it completely
Paragon is looking increasingly attractive after a decade plus with Acronis
Ian, please make your view known to Acronis via in App feedback (click on Help then select Send Feedback) and include a link to this forum topic.
Ian
Same issue with Build 35860.
The computer restarts after attempting to recover. Then it freezes during preparation and does not proceed further.
My computer uses UFEI boot on Windows 10 Enterprise 2019 LTSC. It has a NVMe drive in AHCI mode.
I did an in App feedback.
Recovery in ATI 2021, which is Linux-based, does not work with all or some NVMe SSDs.
This works great in ATI 2020.
There seems to be several issues with the latest build of the ATI 2021 Linux recovery media, for example not working with some (all?) PCs with AMD CPU/APU.
Ian
Ian you're right. I works with a WinPE bootstick.
But when I start a normal system restore in Windows and Acronis restarts, does it boot in a Linux environment? This would explain it.
By the way, the computer is not very exotic:
- Dell OptiPlex 7080
- Intel Core i7-10700
- Windows 10 Enterprise 2019 LTSC
- M.2 NVMe drive in AHCI mode
Andreas Weiss wrote:Ian you're right. I works with a WinPE bootstick.
But when I start a normal system restore in Windows and Acronis restarts, does it boot in a Linux environment?
Yes, that's right.
I've reported my case to the Acronis support. Their answer was simple, the operating system (Windows 10 Enterprise 2019 LTSC) is not supported. I answered that the operating system does not matter in recovery recovery environment and I suspect the reason is the M.2 NVMe drive, but they don't care. The ticket has been closed.
So do we have to change to a different backup software for new computers?
Andreas, the restriction with the Windows 10 LTSC versions is documented in the ATI 2021 User Guide: Supported Operating Systems section.
Acronis True Image 2021 has been tested on the following operating systems.
- Windows 10 (all editions, including the October 2020 Update)
- Windows 8.1
- Windows 8
- Windows 7 SP1 (all editions)
- Windows Home Server 2011
Note
• Beta builds are not supported. See https://kb.acronis.com/content/60589
• Windows Embedded, IoT editions, Windows 10 LTSB, and Windows 10 LTSC are not supported
That said, I too cannot see why this would apply to the rescue media environment provided that the required device drivers for the installed hardware are present in that media?
You mentioned previously that the Windows PE boot media does work for you, and therefore that is the method you would need to use for any Recovery.
Steve Smith, since you are an MVP, could you ask the developers why they don't want to deal with this problem?
VVS wrote:Steve Smith, since you are an MVP, could you ask the developers why they don't want to deal with this problem?
I would love to do so but being an MVP gives me no access to the Acronis developers or anyone else at Acronis. MVP's are basically just experienced users and even our comments and suggestions are ignored!
There is a similar thread in the German forum. After long discussions, the support confirmed that there is a problem. They have promised a fix for one of the next updates. The internal ID is TI-218191.
Andreas Weiss wrote:There is a similar thread in the German forum. After long discussions, the support confirmed that there is a problem. They have promised a fix for one of the next updates. The internal ID is TI-218191.
I submitted a technical support request for this issue on September 6, 2020.
On October 15, 2020, the problem was finally acknowledged. :)
No changes since then. :(
Users here experiencing this issue with Windows LTSC and the Linux based environment should understand that this version of Windows offers no Linux support unless manually installed by the user. I am providing link on how to install Linux support to such version and suggest that this be applied to such installs as a possible remedy. I have not tested this myself however I do believe it may solve the issue.
Bob, please can you expand on why you think that adding Linux support to Windows 10 LTSC would be of benefit here?
The original post for this issue was dealing with issues when rebooting from ATI into the temporary Linux kernel OS environment to perform a restore of the OS started from Windows. As such, nothing in Windows 10 would have any effect here to my knowledge!
Steve,
Sure, version of Windows like LTSC do not receive updates like other versions of Windows and are in fact the last version to do so. Additionally these version do not have Microsoft Store support. Microsoft has changed how Open GNU apps are supported at the kernel level and the aforementioned versions of Windows undoubtedly have not been updated to work with this development. In short, Unix/Linux kernel level support is now accomplished virtually using a Hyper V containerization technique. I am adding a quote below for some further information on this..
You can expect further changes coming in the very near future in the areas of storage, filesystems, etrc. as virtualization is implemented in the Windows platform. For example, the next shoe to drop in storage is expected to be dynamic disk support, should be deprecated with the next version upgrade of Win 10. so if you use dynamic disks at all, you need to make plans to change to something else soon. In MS view storage Spaces will take the place of dynamic disks as both use similar technology.
Microsoft's first foray into achieving Unix-like compatibility on Windows began with the Microsoft POSIX Subsystem, superseded by Windows Services for UNIX via MKS/Interix, which was eventually deprecated with the release of Windows 8.1. The technology behind Windows Subsystem for Linux originated in the unreleased Project Astoria, which enabled some Android applications to run on Windows 10 Mobile.[17] It was first made available in Windows 10 Insider Preview build 14316.[18]
Whereas Microsoft's previous projects and the third-party Cygwin had focused on creating their own unique Unix-like environments based on the POSIX standard, WSL aims for native Linux compatibility. Instead of wrapping non-native functionality into Win32 system calls as these prior systems utilized, WSL's initial design (WSL 1) leveraged the NT kernel executive to serve Linux programs as special, isolated minimal processes (known as "pico processes") attached to kernel mode "pico providers" as dedicated system call and exception handlers distinct from that of a vanilla NT process, opting to reutilize existing NT implementations wherever possible.[19]
Though WSL (via this initial design) was much faster and arguably much more popular than its brethren UNIX-on-Windows projects, Windows kernel engineers found difficulty in trying to increase WSL's performance and syscall compatibility by trying to reshape the existing NT kernel to recognize and operate correctly on Linux's API. At a Microsoft Ignite conference in 2018, Microsoft engineers gave a high-level overview of a new "lightweight" Hyper-V VM technology for containerization where a virtualized kernel could make direct use of NT primitives on the host.[20] In 2019, Microsoft announced a completely redesigned WSL architecture (WSL 2) using this lightweight VM technology hosting actual (customized) Linux kernel images, claiming full syscall compatibility.[3]
Microsoft envisages WSL as "primarily a tool for developers – especially web developers and those who work on or with open source projects".[16] In September 2018, Microsoft said that "WSL requires fewer resources (CPU, memory, and storage) than a full virtual machine" (which prior to WSL was the most direct way to run Linux software in a Windows environment), while also allowing users to use Windows apps and Linux tools on the same set of files.[16]