Skip to main content

Backup from bootable USB Stick not working - license error

Thread needs solution

Hello,

i have full 1 PC version of True Image 2018. I have created successfull 2 bootable usb sticks some month ago:

Rescue medium, Universal restore medium

Now I had to reset /reinstall windows on my Computer and now I want to make a Backup from USB Boot.

When I boot from this USB sticks I can also start Backup, but then (when I press "finish") an error show me:

"You can not do this with trial license". Same shows, when I boot from Acronis CD.

What can I do?

 

Best Regards

 

Rene

0 Users found this helpful

René, welcome to these public User Forums.

I would suggest signing in to your Acronis account and downloading a copy of the Rescue Media as an .ISO (CD media) image.  Provided your ATI 2018 product is registered to your account, then this should be the full version of the bootable media to allow you to backup your data or system.

If you still see the trial version warning, then please send a private message to Ekaterina and ask her to verify your serial number for ATI 2018 and send you a link to a working download.

Hi and thanks Steve,

 

I think, thats a missunderstanding. I have no CD / DVD Drive at this PC, cause its a Laptop ;-)

So i can't use the ISO from account.

So I have uses these 2 functions within Acronis some month ago to create a USB-stick:

Create Rescue medium, Create Universal restore medium

And: I can successfully boot from this resulting stick. Thats not the problem. But then - only when I try to make a Backup - I get the license error ;-(

Many thanks

 

René

René, you can easily convert the downloaded .ISO image to be used from a USB stick using a free utility such as Rufus or ISOtoUSB which will both create a working, bootable USB stick to use.

Hi Steve,

That's right, I could have tried that too.
But if there is a feature in the software that creates such a USB directly, is it actually better? Or is it a known bug here?
So you think that the ISO from the download area is different and that the function "Create Rescue medium" / "Create Universal restore medium" does not work? That would be really bad.

But I've probably just found a solution by accident, but I do not really understand it.

So far I had done the following:

1st attempt:
- Format the stick
- Create Rescue medium on USB
- boot with it - ok
- License error with backup function

Second attempt
- Format the stick
- Create Universal restore medium to USB
- boot with it - ok
- License error with backup function

Now I've done the following:
- Format the stick
- Create Rescue medium on USB
- Create Universal restore medium to then same USB
- boot with it - ok
- Backup function without license error - it works now :-)

Is it possible that you have to execute "Create Universal restore medium" and "Create Universal restore medium" one after the other - on the same stick?
I now have a working stick. But I would also like to understand why it works all at once. Somehow, the functions for USB creation do not seem to be very well programmed.
If there is such a function, it should work for my understanding...it is not a free software - so all functions should work fine normally?!

Best Regards

René

 

Only as info:
If the error occurred, then you have seen this after booting from the stick directly in the software already in the top right under "Help -> About". Here was then "this is an unlicensed version ..." - such a nonsense

René, the integrated Acronis Rescue media builder tool is the recommended method to use here but in your initial post for this topic you said:

Now I had to reset /reinstall windows on my Computer and now I want to make a Backup from USB Boot.

My assumption, possibly incorrect, is that you did not have a working system to use for creating the USB rescue media from, hence the focus on getting a working USB stick by other means.

There is no reason why you should need to jump through hoops to create the standard then the universal versions of the media just to get this to work properly!

A question that I should have asked earlier is what build version of ATI 2018 you have installed here?  The latest build is #12510 which should be shown on your Account page in the ATI GUI.

See KB 60820: Acronis True Image 2018: how to create bootable media

Hello,

ah, now I understand. Ok - first my version is also build 12510.

And I have a second - PC- where another acronis 2018 is installed - same build. Here i have made the USB Rescue stick, which does not work on my laptop.

Thats my problem. I want to understand why it works only with my described terrible steps ;-(

Best Regards

 

René

 

René, did the USB media work correctly on your second PC where you made it, or did it give the same 'not licensed' issue on both that and your laptop?

I have never had any license issues with any of the rescue media I have created.

Further check, what is the status of your ATI 2018 as shown on the Account page in the ATI GUI?

One last question, are you using an Administrator account when creating the rescue media?

When you make the rescue media on a computer where ATI is in trial mode, the rescue media will be in trial mode. When you make the recue media on a computer where ATI is licensed, the license data from the Windows registry is added to the rescue media and then it will be licensed.

Hi,

I have tried to answer all questions:

René, did the USB media work correctly on your second PC where you made it, or did it give the same 'not licensed' issue on both that and your laptop?
--> The license error has occured on both - Laptop and PC (on which I create the stick)

Further check, what is the status of your ATI 2018 as shown on the Account page in the ATI GUI?
--> Yes, I have made a link to the account in the installed Software at the PC --> Status means everything ok - Licensed and Up to date (latest Updates)

One last question, are you using an Administrator account when creating the rescue media?
--> My current user is not the "Administrator" but a user with admin-rights. But the last version of my stick (which is working - 3. attempt), I have created with the same account.

When you make the rescue media on a computer where ATI is in trial mode, the rescue media will be in trial mode. When you make the recue media on a computer where ATI is licensed, the license data from the Windows registry is added to the rescue media and then it will be licensed.
--> I have definetly made the stick not in trial mode. Could there be any bug, which made a problem at move of the "license data from the Windows registry to the rescue media "?

 

Best Regards

 

René

René, thank you for the answers to the questions asked.

Please download the standalone MVP Log Viewer tool (link below in my signature), and check what messages are shown in the ti_media_builder log that the viewer can show?  Hopefully this may help throw some more light on this issue?

The only other suggestion here would be to create a new Administrator level account and try creating the rescue media from that account.

Hello Steve,

really nice of you that you give so much effort. Maybe we should not spend so much time anymore. I have a working stick now. I just do not know for sure, it works on the next build too.
In addition, it really makes me crazy if I can not find the cause of the error or can not reproduce the error. So here's the log - unfortunately in German - maybe it will be useful?!:

 

06.12.2018 19:55:54: +01:00 8388 I00000000: GetDisplayInfo succeeded: DPI: 96, scaling: 100%. Monitors: Resolution: 1920x1080, work area: 1920x1040, physical DPI: 76.
06.12.2018 19:55:54: +01:00 8388 I00000000: EnableHiDpiScaling - use system scaling.
06.12.2018 19:56:36: +01:00 8680 I00180000: Typ des Boot-Mediums: WinPE-basiertes Medium mit Acronis Software
Zielmedium: Wechsellaufwerk
06.12.2018 19:56:36: +01:00 8680 I00180000: Quell-WIM-Datei wird kopiert...
06.12.2018 19:56:37: +01:00 8680 I00180000: WIM-Datei wird gemountet...
06.12.2018 19:56:49: +01:00 8680 I00180000: Inhalte der WIM-Datei werden aktualisiert...
06.12.2018 19:56:51: +01:00 8680 I00180000: Registry wird aktualisiert...
06.12.2018 19:56:51: +01:00 8680 I00180000: Dateien werden aktualisiert...
06.12.2018 19:56:51: +01:00 8680 I00180000: Regionale Einstellungen werden aktualisiert...
06.12.2018 19:56:51: +01:00 8680 I00180000: Zusätzliche Pakete werden installiert...
06.12.2018 19:56:51: +01:00 8680 I00180000: Treiber werden aktualisiert...
06.12.2018 19:56:51: +01:00 8680 I00180000: .wim-Datei wird gespeichert...
06.12.2018 19:57:30: +01:00 8680 I00180000: Dateien werden kopiert...
06.12.2018 19:59:32: +01:00 8680 I00180000: Die Aktion wurde abgeschlossen.
06.12.2018 20:22:33: +01:00 2148 I00000000: GetDisplayInfo succeeded: DPI: 96, scaling: 100%. Monitors: Resolution: 1920x1080, work area: 1920x1040, physical DPI: 76.
06.12.2018 20:22:33: +01:00 2148 I00000000: EnableHiDpiScaling - use system scaling.
06.12.2018 20:22:48: +01:00 11884 I00180000: Typ des Boot-Mediums: Acronis Boot-Medium
Zielmedium: Wechsellaufwerk
06.12.2018 20:22:48: +01:00 11884 I00180000: Das Medium wird vorbereitet...
06.12.2018 20:22:48: +01:00 11884 I00180000: Das Medium wird konfiguriert...
06.12.2018 20:22:48: +01:00 11884 I00180000: Dateien werden zusammengestellt...
06.12.2018 20:22:58: +01:00 11884 I00180000: Dateien werden auf das Medium geschrieben...
06.12.2018 20:25:10: +01:00 11884 I00180000: Die Aktion wurde abgeschlossen.

Start: 06.12.2018 19:55:54
Stop: 06.12.2018 20:25:10
Total Time: 00:29:16

René, thank you for the log information - all looks to be normal with no indication of an issue, so guess that we are at an impasse at present.  Good that you have got a working USB stick that hopefully will continue to work for as long as you need it to!

Hello Steve,

yes, thanks for the support.
If I have to make a new stick in the future due to an update etc., then I will use the log tool in case of problems.
Otherwise, I'll just try it again on my way:
first create Rescue Medium, immediately afterwards Universal Boot Medium
If necessary, I will write again in the community.
For now it was important for me, to find out if the license error is normal at backup function.
But you have confirmed to me here that the backup function of a full boot stick should work on any device.

Best Regards and happy Christmas days

René