Acronis (6559) still won't work on my Windows 10 Tablet (WINBOOK)
Well the shutdown problem (Long shutdown) that existed on two of my nine Windows 10 (32bit) computers seems to have been fixed by updating to 6559 today...All PCs that have Acronis installed are now shutting down as normal...
However I had high hopes that 6559 might work on my Windows 10 Pro (32bit) tablet. A WINBOOK TW-801. Previously when I tried using Acronis TI (I have 9 licenses) on the tablet the program would perform a backup but I could not do a restore with with the LINUX BOOT USB Key or the WINPE BOOT USB Key I created with TI. (It would boot but could not find the eMMC 32GB drive in the tablet). Today I installed TI on the Tablet again (6559)...Then did a backup in TI...Created a Recovery USB Key (Linux) and rebooted with high hopes...NOPE...In fact unlike before it would not even boot from the USB Key but instead immediately went to a STACK memory error...It wrote a SYSTEM ERROR Report which I saved....Where do I upload that report?
I don't understand how I can use FREE VERSIONS of MACRIUM REFLECT and CLONEZILLA with my Windows 10 (32bit) tablet fine and they restore without a problem but my PAY VERSION of Acronis TI will not work with the tablet?? The tablet uses UEFI and a eMMC 32GB drive.


- Log in to post comments

Bobbo,
I just checked....No...The Winbook TW-801 does not have LEGACY Mode in the BIOS..
I had to hookup a USB WIRED Keyboard to get into the BIOS as the Wireless FOB for my
wireless keyboard is not picked up at that point...But using the USB Wired Keyboard I was able
to get into the BIOS on boot...There is no LEGACY option in the BIOS on the WINBOOK TW-801...
However as stated both MACRIUM REFLECT and CLONEZILLA both have no problem at all booting
the Winbook Tablet from their created USB recovery keys...It's only Acronis that can't deal with it
(Using either WinPE or Linux recovery key)...With 6027 it would boot into TI but could not find
the drive...With 6559 it didn't even get that far (with the Linux USB Key created)...It just immediately
went to a STACK error and created a SYSTEM REPORT...Where do I upload the SYSTEM REPORT to?
P.S. My Windows 10 is 32bit on my Tablet as well as all my other PCs...The tablet came with Win 8.1 32bit
and I updated it to Win10 32bit last year...It is current.
- Log in to post comments

I had a winbook myself - I had it for 6 days and promptly sent it back due to the bugginess of the hardware and bios. A buddy and I bought one of the 8" with 32GB hard drives when they were on sale for like $70. He returned his shortly after me due to other USB drives not detecting and the same screen waviness that mine was having. That said, I realize that your issues with Acronis are separate from my opinions of the Winbook, but I had all kinds of trouble with it with bootable media and not detecting flash drives with the full size UsB 3.0 port 50% of the time, and only detecting USB drives with a micro USB to full size USB adapter about 65% of the time.
Again, Macrium is completely WinPE based and it supports WinPE 32 and 64bit. Acronis boot media is Linux; however, it supports WinPE as a secondary recovery media builder option. Unfortunately as of 2015, the WinPE builder for Acronis is only 64-bit so it won't boot on a 32-bit only system (you said it did with v6027 - are you sure that was WinPE - it has no 32 bit bootloader so I don't see how that would be possible). The default Linux media has not worked with my Asus T200 in the past either; it would not recognize the eMMC flash drive. WinPE worked fine for me since my system is 64-bit.
As of today's release, so far, the Linux bootable media is reading my eMMMC flash drive for backups. I have not yet had the opportunity to test a restore, but plan to do so later tonight. I still want to confirm on my ASUS T200 if the restore works with my eMMC hard drive though. If it's not working for any eMMC drive, that would certainly be something. If it's not working on your specific system, it could be the media or maybe unique to the winbook. What type of eMMC hard drive is in it? Mine is a hynix.
Questions: 1) Which Linux bootable media are you using - did you download it from your account or create it from within Acronis? Perhaps try the other method as a test to see if you get the same results.
2) What type of media did you create the bootable media too - USB or disc? What brand? Perhaps try a different brand, and/or different type of media to double check it's not a compatibilty issue with the media being used or that it was a bad media creation.
3) Did you verify the checksum of the download to make sure it matches?
I'm only asking because there have been several people using certains disks and/or flash drives that have created "bad media". Just lask week there for no less than 5 of us helping someone and it turned out to be bad discs and a bad flash drive - all of which were verbatim. He switched to a new DVD type and it instantly worked. He then switched to another USB and it also instantly started to work.
As for submitting feedback/reports, well, it used to be right in the application, but I must be blind, it has moved somewhere where I'm missing it, or it is not there - I will look into that. For now, you can still do this from your account though... https://www.acronis.com/en-us/support/feedback.html and can attach a system report with it.
- Log in to post comments

Dave,
Have you tried creating a new WinPE media on the Winbook? I have seen that build 6559 now has a WinPE.zip at C:\Program Files\Acronis\TrueImageHome\WinPE. This version of WinPE.zip has folders for both 32 bit and 64 bit. It is possible that you may get a 32 bit WinPE if you build it on your Winbook.
Prior builds used WinPE.zip at C:\Program Files\Acronis\TrueImageHome\BartPE. That version of WinPE.zip only had 64 bit files that would not work on your WinBook. I've asked Acronis how or if they are deciding to build a 32 bit or 64 bit WinPE. As of now, I haven't received an answer so I don't know if it will work for you or not. In any case, it is worth a try.
- Log in to post comments

Bobbo,
I using that feedback link...They won't take my attachment as it's 12MB and the max you can send via that is 5MB...
But I sent my feedback (Even though after doing that it says they won't respond...
Regarding the LINUX USB RECOVERY...It was on a USB KEY....The same key that I boot MACRIUM REFLECT without a problem (I FORMATTED
the drive again before installing TI Recovery...IT FAILED...I then reformatted it and put MACRIUM REFLECT back on it...Works like a charm...
I also have CLONEZILLA USB recovery KEY (Which IS using LINUX)...It works like a charm...
Only TI cannot boot from a known good USB Key. The previous version 6027 could boot but could not see the eMMC drive (LINUX and WinPE)...
This version 6559 cannot even boot using the LINUX version which I created from within ACRONIS TI 6559 on the WINBOOK.
**Reference my WINBOOK...Sorry you had trouble with yours....Mine has been AWESOME...I've had mine for more than a year now..
The only problem I've had recently is that the latest build of Win10 only my front camera works (Even though I tried reloading the driver)...
it was working before in Win10 but stopped with the latest build...But I don't need the back camera anyway as it's in a FOLIO and I only use
the front camera for SKYPE...Other than that's it's an incredible mini PC for me in it's folio with Bluetooth Keyboard and mouse...I paid $99
for mine and it is the only portable I use now when I'm out and about as it's so small and lightweight (Other laptops stay at home)...It runs
all Windows Software that I can run on a PC (Except for Acronis True Image which runs and backs up fine but can't restore)...
Acronis TI 2016 works fine on all my other LEGACY Windows 10 32bit PCs...It's just the WINBOOK that the recovery does not work.
- Log in to post comments

Mustang,
Thanks...I haven't tried yet with the new 6559..I'll give it a whirl and report back here...
- Log in to post comments

That would be sweet! I can confirm that my system also has the 32-bit version of BartPE now. Unfortunately there is no option to pick 32 or 64-bit PE so it looks like it defaults to what the OS is installed as. DaveI if you can create one and see if it does make a 32-bit WinPE, that would be great to confirm.
I have just successfully booted with the default Linux bootable media v6559 on my ASUS T200 - booted just fine - I even selected the 32-bit version to try and make sure it was as close as possible.
It sees my Hynix 64Gb eMMC drive and backed it up without issue. When I select on recovery, and I get to the point of selecting a disk, it has no issues detecting the drive and letting me select it as a restorable location.
Unless there is a compatibilty issue with your specific drive, this seems to be working fine. What concerns me is that you're not even able to boot the media at all currently, which makes me think it is a bad recovery media creation, or the issues I had with the Winbook where it would drop out the USB devices on the full sized USB 3.0 port and would only work with the usb 2.0 micro UsB port. I would basically have to use a micro USB to full USB adapter, plus a powered USB hub and attach my bootable media flash drive, an external UsB hard drive for the backup and a keyboard/mouse (although my Logitech wireless usb adapter worked fine). I just tested my Logitech unifying device with this version and it picks it up just fine as well.
Are you using the full size UsB 3.0 port on the winbook? If so, I'm going to say that is the issue and suggest you try using the micro USB port and and adapter and hub as that is the only way that we could get external bootable devices to work the majority of the time on the Winbook 8" before it went back. This is the only device I've had such trouble with regarding Acronis bootable recovery media, but it was not limited ot just Acronis.
Attachment | Size |
---|---|
349932-128056.jpg | 647.42 KB |
349932-128059.jpg | 545.43 KB |
349932-128062.jpg | 998.19 KB |
349932-128065.jpg | 724.4 KB |
349932-128068.jpg | 721.62 KB |
- Log in to post comments

Bobbo.
I use the Full Size USB 3.0 port with a USB 3.0 Hub...It's what I use with CLONEZILLA (LINUX LiVE USB) and Macrium Reflect (Win-PE)..It's not the port...
I am in the process of building/testing and will report back...
- Log in to post comments

DaveI wrote:Bobbo.
I use the Full Size USB 3.0 port with a USB 3.0 Hub...It's what I use with CLONEZILLA (LINUX LiVE USB) and Macrium Reflect (Win-PE)..It's not the port...
I'm sure you're right. Ultimately, these tablets work best with WinPE though as it's a known issues that Linux does not have proper 32-bit support for 64-bit processors that have been neutered to 32-bit only capability in the bios. Looking forward to hearing more back about your results with WinPE build with this version and Mustang has asked the engineers to enlighten us more about whether or not 32-bit winpe is back and/or supported again.
Don't rule out that USB completley though. If you could at least test the other port, that would be more definitive. For the 2 of us who had these tablets in my office, it was not just Acronis that the large USB port was an issue with bootable media, again though, these were all Linux based USB boot drives. There are others from the Microcenter forums who are not always successful with Macrium and or Clonezilla either. Some are saying it works if you use an external hard drive, but not a flash drive (I'd probably blame the specific flash drive they were using), others are saying you must format the USB flash drive as GPT (I doubt that, but if it works, hey, why not), others like me say to use the other UsB port- maybe my batch had a faulty one, I don't know.
I'm glad Clonezilla and Macrium are working for you, but I'm just trying to point out a lot of inconstency with these tablets and what does (and doesn't) work.
http://www.mctsol.com/phpBB3/viewtopic.php?f=55&t=912&start=20
- Log in to post comments

OK...So I built a Win-PE USB Recovery with Acronis Plugin (Using the MS ADK which then allows you to build the Win-PE)...This was the same I haddone in 6027 BTW...Once I had that built on the usb key I picked the advanced startup and reboot...At that point on reboot I selected USB CD which is what I do with MACRIUM REFLECT... With the WinPE ACRONIS KEY...It did not find the USB key on boot...OK...So I did it again this time selecting USB HD...Again...It did not find the USB Key...I did it again...I picked USB FD...Again it did not find the Acronis USB Key...I took the same exact Key and
restored Macrium Reflect to it and picked advanced reboot..On reboot I picked USB CD....And Voila...Back in Macrium Reflect with zero problems...
OK...I'm thinking...Let me make an Acronis WinPE DVD (On another PC) and then try to boot the Winbook using an old external USB DVD Drive (Asus) that I have...Unfortunately after making the DVD and then hooking up the external DVD Drive to the Winbook and rebooting the Winbook did not recognize the External DVD drive...
So...I give up...Acronis 2016 latest build does not work with the Winbook TW-801 (At least mine). As orignally stated both Clonezilla (USB LINUX LIVE KEY) and Macrium Reflect (WinPE USB KEY) work perfect. No how no way does either the Acronis Linux Recovery (USB Key) or the Acronis WinPE Recovery (USB Key) work with my Winbook TW-801...Don't know why...But it doesn't work...
So I've done my duty and reported it...Could be a one device problem or a wider problem having to do with UEFI....
- Log in to post comments

I have a couple of observations.
1. Try your USB port without the hub - however I don't think in this instance that will get things working for you.
2..It is possible that Macrium changes the way your USB stick is reported. Windows can react differently if a USB stick reports itself as a HDD rather than a removable drive.
3. Try the following:
a) Insert a spare USB stick - run the Windows Recovery Media option provided by the OS.
b) Select to install bootable media only, don't opt for the Windows files option.
c) Once the stick has been formatted and the Windows booting software has been installed.
d) Make a True Image PE based recovery media selecting WIM as the file type.
e) Replace the boot.wim in the USB stick source folder with the Acronis Windows PE bootable media.
f) Rename the True Image WIM file to boot.wim
The tablet should now boot from the stick.
You can if you have a BCD editor leave the True Image wim file with its original name and point the BCD to that name rather than boot.wim
- Log in to post comments

Also curious to know what the results of creating the WinPE from Acronis was - if it was still 64-bit or actually 32-bit. I don't have a 32-bit only system to test with. However, on my SnapDeploy media (which has 32-bit and 64-bit PE), I have both a bootia32.efi file and a bootx64.efi file. If Acronis is only creating the bootx64.efi file (as it has done with all versions of 2015-2016) before, then it will still be 64-bit only and won't boot.
I could understand better if the drives were detected, but failed to boot for some reason, but the non-detection of the drive as a bootable device at all is more concerning at this point. If it's 64-bit only media, that makes sense. however, the Linux version is most certainly 32 and 64 bit bootable. It should at least show up as bootable drive in the bios. What happens after that may be a different story though.
Trying to get my hands on another generic 32-bit tablet with eMMC flash hard (my buddy has another one from Fry's that is basically the same thing, but with a different manufacturer stamp on the case).
- Log in to post comments

BOBBO,
I recreated the Acronis Win-PE boot USB Key just to see if I could answer your question about 32bit/64bit...
Unfortunately there's no telltale signs with the files created. The two main files bootmgr and bootmgr.efi
when I looked at the properties there was nothing pointing to show whether 32/64...All the other files are
simply language MUI file except for a hidden system volume...But I can't see where they would make it 64bit
as that would do the opposite of what they are trying to accomplish which is make it compatible..32bit is going
to be far more compatible...
COLIN,
You must use a USB Hub when doing this procedure...You have to be able to have an input device hooked up (mouse/keyboard,etc.)...
So when you do this procedure you have the USB Key Connected, The USB External Drive connected, and either a wired or wirless Keyboard
connected (BLUETOOTH is not an option to use because BLUETOOTH at this point does not function).
- Log in to post comments

USB booting may not be possible. The motherboad needs to supply boot rom for USB devices. Is there any USB configuration in the BIOS? If there is, legacy USB support needs to be enabled to support USB booting.
The easy way to tell if WinPE is 32 or 64 bit is to look in the registry after it is booted. Try booting the USB WinPE on a 64 bit UEFI computer. If it is 64 bit, it should boot in both UEFI mode and legacy mode. If it is 32 bit, it will only boot in legacy mode. After it is booted, enter regedit in the command window. Regedit will run. Navigate to HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment. There will be a data value on the right side called PROCESSOR ARCHITECTURE. If the value is x86, it is a 32 bit WinPE. If it is AMD64, it is a 64 bit WinPE.
- Log in to post comments

Mustang,
I boot via USB with the Winbook using WinPE USB Key created in Macrium Reflect without any problem.
I boot via USB with the Winbook using LINUX LIVE USB Key created with Tuxbox and it has Clonezilla on it.
I don't own (or have access to) a 64bit Windows computer. All nine of my computers (including the Winbook) are Windows 10 32bit...I have no need for 64 bit.
- Log in to post comments

OK - I tested with a Fry's Vulcan 16GB eMMC tablet VTA0IE16 that is stricty 32-bit bios (although running a 64-bit baytrail atom processor like the MicroCenter Winbook801) and it is working like a charm.
It immediately boots directly to the UEFI 32 bit menu for Acronis. I select Acronis 2016 and goes straight to the GUI. From there, i would backup without issue. I then selected an existing image that was also attached via a USB hub and another USB hard drive and went through the process to the point of recovery and it sees the 16GB "MMC" drive as a valid recovery location as well.
I'm going to have to say that the issue is specific to the Winbook, the configuration in the bios is the issue, or it could be that particular USB hub, boot drive, or something else. I had tried to Winbook's (mine were actually 802 with a full size USB 3.0 - I believe yours is an 801 with USB 2.0 only?) and had a lot of issues with bootable media being detected in general.
For you, maybe Acronis is not going to work with this particular model - why that would be though, I can't say. Seems to be working on an ASUS T200 with 64Gb eMMC flash hard drive and this Vulcan with 16Gb eMMC flash hard drive though.
Attachment | Size |
---|---|
350276-128101.jpg | 562.05 KB |
350276-128104.jpg | 774.97 KB |
- Log in to post comments

Bobbo,
Thanks for your efforts and the information...
BTW you have it backwards regarding the Winbooks...
The TW-801 has the USB 3.0 port
The TW-802 has the USB 2.0 port
From what I understand they couldn't get the chip that enabled 3.0
for the later TW-802...
I may play around with it some more in the future...THANKS.
- Log in to post comments

Ah, yeah, thanks for the clarification. It's been well over a year since I had one i hand and don't remember the differences between the model #'s - I just remember I had the one with the full sized USB 3.0 port - it was a smoking deal right around the holidays and I had high hopes for it at that price, but the 32-bit bios and the wavey/shakey screen on 2 of those put me off of them.
I moved onto an Acer Aspire Switch 10 from Costco for about twice the price (bigger screen and 64Gb eMMC drive space) and loved it at first. However, also had trouble getting it to boot Acronis media at the time since it was also a 32-bit only bios, but I had Snap Deploy stand-a-long recovery media to fall back on. 2 of those Acer's turned out to be duds (screens went out on both of the) so that's when I gave up on 32-bit tablets and skipped the ASUS T100 and went straight ot the ASUS T200 since it was the only fully 64-bit capable 2-in-1 I could find at the time and it also had 4GB of memory.
Best of luck with the Winbook and Acronis - wish I had a way to test it myself, but don't know anyone who has one and there's no Microcenter in my area. If there was, I'd bring my Acronis boot media with me and test it out in person at the store.
- Log in to post comments

DaveI,
I am going to suggest here that I think your problem here is how the boot image is being created on the USB flash drive that is giving you issue.
I also do not think that you need the WinPE variant of Acronis True Image to boot your machine nor if you are using the latest release version of True Image, version 6559 that a WinPE based boot medium is necessary to see your eMMC device or the USB thumb drive you are booting from.
I am going to outline here for you the steps necessary and the tools required to create a default Linux based boot medium which I am fairly certain will be recognized in your Winbook TW-801.
What you need:
It is best to use a clean unused before USB thumb drive. If you wish to reuse an existing drive you may do so however I recommend that you perform a full format of the thumb drive so that all existing data is removed from the device. The default format and what you need to use is FAT32. This procedure will take some time so kick it off, grab a snack and take a break while the format completes.
You also will need a third pary tool to pull this off. A lot of people recommend Rufus, ISO to USB, Yummy, etc. for performing the writing of a bootable USB thumb drive. I have used them all and they do work but they also fail as well. The one tool I have found that is simple to use and has worked for me every time is Win32DiskImager. The link below is a direct link to SourceForge download of the app.
https://sourceforge.net/projects/win32diskimager/files/latest/download?…
What you need to do:
The first step here is to create an Acronis True Image ISO file. In the TI 2016 version 6559 application GUI on the left side of the screen click on the Tools Icon then select Rescue Media Builder. In the popup window select Acronis Bootable Rescue Media. Next click on ISO file, this will open a Windows Explorer Save As window with the default save location being Desktop. you may select another location if you like just make sure you remember where that location (path) is as you will need it when running the Win32DiskImager app.
Wait for the ISO creation process to complete, you should recieve notification of success.
Next run the Win32DiskImager app. What you will see is a sparse interface with a path bar at the top. To the right of the path bar you will see a folder icon and next to that you will see a drive letter. Make certain that the drive letter is in fact the USB thumb drive you wish to write the ISO file to. Once that is confirmed click on the folder icon and browse to the location where you saved the ISO file you created. Again once you choose the folder browse icon a Windows Explorer window will open and the default file type that is selected here is for .img file types. Since you will be using an ISO file change the file type to *.* (bottom right corner of explorer window). Once you have your ISO file selected in path bar of the Win32DiskImager app the command buttons at the bottom of the interface will become active. Simply choose Write. Again, you will recieve notification when the process has completed. Close out the DsikImager app.
Now attach your newly created USB bootable thumb drive to your Winbook, start the Winbook and I think pressing F5 repeatedly while the machine starts up will get you to a boot options menu. Look for an entry for you thimb drive, select it and True Image should start. Providing that is that I am right of course!
- Log in to post comments

SO............ENCHANTECH.............You got INSIDE INFORMATION?????? At first when I saw your instructions...I figured what the heck...Might as well try it...I took a different USB Key but shortcutted your instructions and just did a fast format to see if it would work quick...D/L'ed the Win32DiskImager (What a great little utility...Gotta be careful with that drive letter)...Wrote the image to the USB Key...Did an ADVANCED RESTART from inside Win10 and rebooted...
What the H*LL...It WORKED!!!.... Wait a minute I'm thinking...It must have been the USB Key I had been using at first...
So I rebooted...And wrote another image to the original USB Key I had been using (It's formatted with 512K clusters...I was thinking maybe that was it)...Advanced Restart and rebooted....IT WORKED AGAIN with the original USB key!!!!!
OK...The final test...Booted back in to Windows 10 and did a FULL BACKUP to an external USB HD...
ADVANCED RESTART and reboot....Now I did a RESTORE from the FULL BACKUP I just created...At the end it reported SUCCESS....Rebooted... YEAH BABY!!!! Acronis Backup worked!!! First time I've been able to Backup/Restore the WINBOOK with ACRONIS since I bought the 9 PC licenses at Christmas....So...The problem (And please correct me if I'm wrong) is that the way that Acronis is putting the image on the USB Key is not correct which is why USB CD did not work before when booting from ADVANCED START....So this procedure lays down a correct format that the USB CD boot in Windows 10 can recognize?? It sounds as if you were pretty sure of this and knew about the issue before...
Does ACRONIS realize this?? MUCHO GRACIAS for resolving this long time issue...MEGA THANKS to YOU and all the others here who have helped.
- Log in to post comments

Sweet! Another utility to add to the IT Utility belt!
DaveI,
Thanks for giving everything a shot so far and helping to test the recommended solutions.
I'm sure you're ready to call it a day now, but you're one of the few with this type of tablet that can help test these scenarios. If you're up for it, could you now select the USB drive in the Acronis Application when creating default bootable recovery media and let Acronis create the USB drive and see if it's still bootable or not? Mabye it was the formatting of the the tool Enchantech recommended that finally did the trick - maybe not? Just seems odd, that other eMMC flash drives are working with the default media creator, but not the Winbook so would like to give it one more go.
If it does work, cool. If it still does not work, what happens if you use the Universal Restore Media builder (not the Acronis application, but the UR media add-on and have it add the Acronis application with it?
Attachment | Size |
---|---|
350416-128107.jpg | 66.06 KB |
- Log in to post comments

Bobbo...No problem...Give me a few minutes....I'm restoring the other thumb drive I had used (My wife's)...I had to use MiniTool Partition Wizard to get he space back on it (Diskmanager in Win10 wouldn't do it)...It a PORTABLE APPS Thumb Drive...I'm restoring the Thumb Drive now and when done
I'll put the original in and try...
- Log in to post comments

OK...So the USB Thumb Drive that was created using Win32DiskManager utility appears in Windows10 as if it is a FAT drive with 0 bytes of 350 MB free with 1.5GB UNALLOCATED.
So when you try to select the Thumb Drive from within Acroni Recovery Media Builder it of course says it has insufficient drive space...Acronis says it wants a drive with 512KB free... I would have to use MiniTool Partition Wizard on it like I did my wife's thumb drive to regain the space...But then it would fail again like before when trying to do it from within Acronis...
- Log in to post comments

DaveI - could you format it with fat32format.exe first to avoid having to use minitool (which by the way is a great tool I also use). This can be done from within Windows. Launch it with admin command prompt and run
fat32format.exe H:\ (replace "H:\" with the actual drive letter of the thumb drive)
http://www.ridgecrop.demon.co.uk/index.htm?fat32format.htm
Then build it in Acronis like normal and test. If it doesn't work, reformat again and rebuild with UR media builder.
- Log in to post comments

I ran fat32format.exe under an Admin Command Prompt on the thumb Drive J:...
It reported everything would be lost....OK...BUT...It still just has 345MB of 345MB free...
Acronis needs 512MB free (I mistakedly said KB before)...So it needs to have that partition resized or deleted and recreated...
fat32format.exe did not do that...
- Log in to post comments


SO...After I deleted the partition using MINITOOL Partition WIzard...I was back to having 1.8GB or so free...
Then I let ACRONIS RECOVERY BUILDER make a RECOVERY USB Thumb Drive...
Advanced restart....USB CD.... IT WORKED!!!!
And now the working USB Recovery thumb drive has 1.3GB of 1.8GB free...
- Log in to post comments

Excellent!
So, I'm wondering if the USB was formatted with multiple paritions before - perhaps by Acronis or Clonezilla or something else before them? Although Linux can create multiple partitions on a "removable" disk, Windows can only see 1 - the first one. Having multiple partitions may also make it unreadable to the Windows Boot manager.
http://www.prime-expert.com/articles/a05/enabling-multiple-partitions-o…
- Log in to post comments

There was only one partition...HOWEVER...Remember this Thumb Drive was a MACRIUM REFLECT Recovery Thumb drive...
Everytime I did build it into an ACRONIS RECOVERY USB Thumb Drive (AFTER Formatting) it would fail...
I would then FORMAT it again in Windows and Make it a MACRIUM REFLECT RECOVERY Thumbdrive and it would work...
I did this several times and each time it would fail as an ACRONIS Recovery thumb drive...Then Format...Make it a MACRIUM REFLECT
Recovery Thumb Drive...And it would work...I had in my mind that "maybe" MACRIUM had set some type of a protected area on it
that was not overwritten by the formatting prior to trying to make it an ACRONIS Recovery Thumb Drive....It wasn't until
I used ENCHANTECH's Win32DiskImage that it finally worked (Because it laid down a new format and possibly blew away whatever
was on it preventing it from working)...I haven't tested that theory because I've deinstalled Macrium Reflect from the Winbook now
and don't have it installed on anything else now....Just an idea...
- Log in to post comments

The issue is what bootloader is used and how that bootloader is written to disk. Most if not all of the other commonly used tools that create a bootable media especially a Linux based media use a Grub2 loader. Acronis Linux variant does not use a Grub2 loader but instead uses it's own custom loader. The Win32DiskImager is intelligent enough to recognize this and write the default custom loader to the media device. The other tools do not do this most of the time. It is possible to use a Grub2 loader to then load another bootloader but few utility tools pull this off successfully.
I think that the advent of EFI has brought changes to this as well because since boot files have been associated with EFI it seems that using a Grub loader to then load a custom loader has been problematic and in general a failure.
If you have a look inside the created Acronis Linux based recovery media you will see the same structure as that of how the Win32DiskImager tool creates the media. That is why it works were others do not. You can also use the Win32DiskImager tool to write .img image files to disk so it is a very handy tool and worth having in ones arsenal.
- Log in to post comments

OK...Thanks for the explanation and THANKS AGAIN for the help in resolving this...I'm now 100 percent backing up my nine Windows 10 (32bit) PCs with Acronis...
- Log in to post comments

Under ATI 2014 I was unable to get my Linx8 Windows 10 tablet to boot the ATI recovery media from a USB stick. I understand this was due to the fact that the Linx8 uses a 32-bit boot loader and the ATI recovery media was 64 bit. With ATI 2016 build 6559, I am able to boot the recovery media from a USB stick BUT the FAQ for ATI 2016 states that tablet recovery is not supported if it requires a reboot of the device (ruling out recovery of the W10 OS). Has this changed with 6559, given that I can now boot into the recovery media?
I have been backing up the tablet using Macrium Reflect (free) for the Linx8's SSD and AOMEI Backupper for the SD card (the free version of Macrium won't backup the SD card) and I would by really pleased if ATI 2016 can now backup and restore the entire device. However, I don't want to waste a ton of time testing this by backing up in both Macrium and ATI and then attempting to restore via ATI, only for it to fail and then have to be recovered by Macrium (which I have already proved will work). Does anyone know for sure whether build 6559 can be used to recover the OS partition on a 32-bit tablet?
- Log in to post comments

Howard,
Like you I was also backing up my TABLET which uses the same TYPE of loader as you with Macrium Free (Clonezilla also worked)...
I can't say anything about official support of course...But I did a FULL BACKUP and RESTORE last night for the first time of my TABLET with TI 6559 (SELECTING ENTIRE PC)...(Previously when I could get TI 6027 to boot to a recovery USB Media it could not see my eMMC drive. Last night it saw the eMMC drive (Said MMC in TI)...
I did a FULL BACKUP and the RESTORE it...And it's working 100 percent....But of course I can't guarantee your experience will be the same..
- Log in to post comments

eMMC flash drives are now officially supported with Acronis default bootable Linux recovery which is 32 and 64-bit and legacy/UEFI capable. So far we have an Asus T200 (64-bit), a Winbook801 (32-bit) and a Vulcan (32-bit) confirmed to be working. As long as you can get your media to boot form USB, it will work. Getting the media to work (using a good USB drive, paritioned correctly, option in the bios) would be the only limiting factor at this point.
- Log in to post comments

Mustang wrote:I've asked Acronis how or if they are deciding to build a 32 bit or 64 bit WinPE. As of now, I haven't received an answer so I don't know if it will work for you or not. In any case, it is worth a try.
I'm curious how it determines which version to build. I tried to get True Image 2016 build 6559 to create the 32bit WinPE rescue media by using a 32 bit UEFI Windows 10 virtual machine, but it still created the 64 bit version.
I created what appears to be fullly functional 32 bit 2016 WinPE with the 32 bit MustangPEBuilder 2 ADK and the True Image 2014 plugin. I merged the contents of the files and files32 folders and pointed the TIHome2014.ini to the resulting folder. Then I made the appropriate substitutions to the instructions in the following post.
http://forum.acronis.com/forum/71918?page=2#comment-293829
Finally I performed a test backup and recovery and everything completed without any errors.
Attachment | Size |
---|---|
350796-128152.png | 110.73 KB |
350796-128155.png | 102.66 KB |
- Log in to post comments

I have a fully functional TI 2016 plugin for MustangPE. It will work with both the 32 bit and 64 bit versions of MustangPE. It can also be built on 32 and 64 bit Windows system. I assume the 32 bit version will boot on 32 bit only tablets. Sadly, I don't have access to one for testing.
I plan to release the plugin on my website in a day or two.
- Log in to post comments

I uploaded a TI 2016 MustangPE plugin. It can be downloaded at http://www.mechrest.com/plugins/MustangPEBuilder/Downloads/Files/TI2016.zip
- Log in to post comments

Thanks to all for posting your experience with recovering tablets, which encouraged me to try a recovery of a bitlockered HP Stream 7 tablet. It worked flawlessly: I backed it up from within Windows, booted from an ATI2016 USB stick and recovered the entire eMMC drive. The device restarted without any errors and is running perfectly. As expected, the recovered device is no longer bitlockered and I'm having some difficulty getting it to complete the task but that's not ATI's problem. Possibly I just need to jump through all of Microsoft's "log on with a Microsoft account" hoops and be a bit more patient while it does its thing.
From my point of view this is a big improvement in the usefulness ot ATI 2016. One slight disappointment, though: is there a reason why ATI 2016 can't add the recovery manager to a bitlockered drive? Macrium Reflect is able to do it...
Thanks to the Acronis guys for this improvement in the product.
- Log in to post comments

Hello Howard,
Glad to know that now you would be able to restore your system successfully in case of emergency by using Acronis rescue media.
Activating Acronis Startup Recovery Manager would mean modifying MBR on BIOS and NVRAM variables on UEFI. According to this Microsoft article: https://technet.microsoft.com/en-us/itpro/windows/keep-secure/bitlocker-frequently-asked-questions (Last Updated: 4/6/2016), such changes can lead to boot problems. That is why we do not activate Acronis Startup Recovery Manager on Bitlocker-encrypted disks. I have copied and pasted two questions from the above mentioned article below:
What system changes would cause the integrity check on my operating system drive to fail?
The following types of system changes can cause an integrity check failure and prevent the TPM from releasing the BitLocker key to decrypt the protected operating system drive:
-
Moving the BitLocker-protected drive into a new computer.
-
Installing a new motherboard with a new TPM.
-
Turning off, disabling, or clearing the TPM.
-
Changing any boot configuration settings.
-
Changing the BIOS, UEFI firmware, master boot record, boot sector, boot manager, option ROM, or other early boot components or boot configuration data.
Can other tools that manage or modify the master boot record work with BitLocker?
We do not recommend modifying the master boot record on computers whose operating system drives are BitLocker-protected for a number of security, reliability, and product support reasons. Changes to the master boot record (MBR) could change the security environment and prevent the computer from starting normally, as well as complicate any efforts to recover from a corrupted MBR. Changes made to the MBR by anything other than Windows might force the computer into recovery mode or prevent it from booting entirely.
Regards,
Slava
- Log in to post comments

Thanks very much for the explanation, Slava, much appreciated. I can see now why it's advisable to leave it well alone!
Regards, Howard
- Log in to post comments