Skip to main content

Creating WINPE (x86) with 2016-6581 -Winpe(ati6581) banner reports Ver 2016-6571

Thread needs solution

1. Running Win 7 x86 with ati 2016-6571, no problems creating WinPE Rescue disk

2. Updated to ati 2016-6581, ATI d/l'd & installed ADK (WIN10) automatically.

3. Rebooted, ATI main app reports 2016-6581

4. Ran Rescue Builder Tool, to Create WinPW Media (tried both direct to CD burn, also to ISO file, then used Nero to burn) - no difference

5. Upon Rescue boot, ati does boot, but checking the "about box" in WinPe made with 2016-6581, reports it's "2016-6571" not 6581

No yet sure if it's simply a forgotten source file mistake by Acronis or the created WinPE is the wrong version.

Bob

0 Users found this helpful

Further info...

prior winpe 2016-6571 iso is  446,627,840 bytes reported by windows

"2016-6581" iso(which reports as ...6571?)  winpe iso reports:  489,095,168 bytes

bob

Sounds like a forgotten change.  This occured with the first relase of 2017 as well for some where it reported as Acronis Small Business instead of True Image Home.  Ultimately, not much changes with the PE anyway, it really depends on the version of the Windows ADK installed that makes the most difference as newer ADK has better out of the box driver support for things like newer PCIE NVME drives and newer Intel NICS.  If you have a Win 7 OS or newer, you can remove older ADK and install the latest Windows 10 ADK (I'm still using the 1511 version though) and Acronis 2017 can build WinPE with it. 

Hello Bob,

We tried to replicate the same behavior on our side and it didn't. Created WinPE media displayed build 6581 as expected on the Help - About window.

You can submit a support ticket if you need any further assistance on the matter.

Regards,

Slava

I have tested this once again with the same problem.  Tried both USB & CD Rescue media.  I did contact support as you requested.  I should mention that I originally had ATI 2016-6571 installed, working fine and sucessfully created the WinPE media.  Then when I next started ATI 2016, it informed me that a new version was available and I allowed it to install 6581 OVER the existing 6571.  After this, Running the main TRue Image, reports on-screen that it is ver 2016-6581...but after newly creating a new WinPE it reports 6571 not 6581.

Can it be that some 2016-6581 installation files were "built" with the wrong Bld number in the source code?  That would possibly explain why your test is ok ...maybe a different installed version??

 

bob

Look in C:\Program Files (x86)\Acronis\TrueImageHome\WinPE. You will see a file called WinPE.zip. Look inside and you will see TrueImage.exe. You will see the version number is 6571. When you installed over the top, the WinPE.zip file was not replaced.

You can fix this by uninstalling TI 2016 and reinstalling TI 2016 build 6581.

Paul

Thanks..I did as you suggested and you are correct..of course!  Do you think a NORMAL uninstall will do it, or do you suggest including a Acronis CLEANUP run as well?

Last question, and I want to do this right, I don't want to "lose" my currently registered (on this PC) serial number.  As I currently have about 3 UNUSED (not yet installed and nor registered) ATI2016 serials (some are Family pack where 1 s/n = 3 installs) I want to be certain that the S/N on THIS PC carries forward!

In the past, I had the experience that during a re-fresh install, Acronis grabbed yet another serial from my account!  This became a nightmare and in the end it was never fixed!  Thus I want to be extra-careful.

A thought:

Checking the C:\Program Files (x86)\Acronis\TrueImageHome\WinPE  folder and the TrueImage.exe you refered to, I see a number of files that show the same "windows date", being 5/10/2016...Hmm.  Wonder if I do a clean install on another PC...maybe just grab the mentioned exe (or folder contents) and manually copy them..or am I looking for more trouble?  Guess I could check the MD5 checksums to be certain.

bob

I suggested an uninstall and reinstall just to make sure there were no other files left behind by the over the top installation. I'm sure the cleanup tool would not be needed.

My experience with Acronis products and the serial number activation has been very good. In fact much better than many other companies. They say the serial number can be used on just one computer. I have found this to be enforced in a very fair manner. I have been able to uninstall and reinstall many times on the same computer as long as the computer name in Windows has not changed. You shouldn't run into any problems until Acronis sees more than three computer name activated. And even then, there is a procedure to move a license from an old to a new computer.

It you want to just fix this problem and take your chances on the rest of the files, you could just delete the WinPE.zip file and run a "Repair" installation of build 6581. If something goes wrong, you can alway uninstall and reinstall.

Thanks to all....your ideas proved to be just right.  If a user has ATI2016-6571 (or likely earlier as well) and when ATO WinApp (or self knowledge) causes the user to accpt Acronis in-program advice and allow the WinApp to update to 2016-6581, the main win-app is updated, but the existing contents of: (as suggested by Mustang etc)

QUOTE:

Look in C:\Program Files (x86)\Acronis\TrueImageHome\WinPE. You will see a file called WinPE.zip. Look inside and you will see TrueImage.exe. You will see the version number is 6571. When you installed over the top, the WinPE.zip file was not replaced.

You can fix this by uninstalling TI 2016 and reinstalling TI 2016 build 6581.

UNQUOTE

Indeed this works...  My conclusion is a Still-Existing Bug in the 2016-6581 (perhaps v2017xxx too?) that skip-over the aforementioned file, which results (I think) not only in athe WinPE (x86 & x64) WinPEs reporting ver 6571, blut also using therefore likely skipping any WinPE Build 6581 updates.

Hope the Acronis will release a fixed 2016 installer if a Overlay/Repair Install is performed...Have not checked if this but exists on v2017-xxxx.

 

Bob

FAILURE TO ACTIVATE???

Hi Guys,

Hope you can give some feedback.  The suggested Uninstall of 6571 & then reinstall of 6581 worked fine on my 2 x w7-x86 pcs.

Today I needed to do the same (2016-6571---> 2016-6581) on my Dell Laptop running latest W10 x64.  It had an activated 6571 for a few months, no issues.  So I did the same routine, with a CLEAN install of 2016-06581.  No issues.  Rebooted, and when starting ATI, I get a message " RED !, The activation failed.  Please try again later.  Days remaining: 30"  No other errors, except after 10+ minutes W10 would pop up "Failed to connect to activation server".  Ok, so tried "Offline Activation option", generated Installation Code", took to second PC, went to acronis.com/activation, entered installation code from first PC, even put in PC-Name.  Clicked Green Generate Activation code"...NOTHING HAPPENS!  At bottom of browser (FF) window I see some activity connecting to other sites, but NO ACTIVATION CODE (nor error ) appears on offline webpage.  Did Support chat, sent screen shots as requested along with installation Code File.  No response...Got case#, tried chat again...now no response from Chat...just "waiting to connect".  Absolutely no issues on my end, allowed popups, put firewall down etc.  I wonder if Acronis Activation system down?  I can connect everywhere, even to Acronis and D//L update files etc?  I'm trying to be patient, but after 12 years and thousands of $'s of SW bought...well my patience is wearing kinda thin.

So Hope I can get some ideas from you guys

Bob

Bob, sorry to hear about this activation issue with your Dell laptop, the most likely explanation would seem to be an issue with the Acronis activation server, but don't see why that would affect your ability to have a chat session with their support agents?

Unfortunately we have no access to any of the Acronis backend servers / systems as we are just users too, so I can only recommend to keep knocking on their door about this issue.

If you don't get any joy through the support chat route, then send a PM to Gaidar, General Manager Acronis True Image and see if he can get this issue moved on and resolved as quickly as possible.

Thanks Steve,

I , and others really do appreciate the input of the MVP members such as yourself.  I have to say that the responsiveness of the Acronis support chat guys has improved, but i find that the seemingly existing language and culture barriers still stand in the way of much meaningful assistance...

i hopd u really just how much the Acronis customer base relies on the support provided in these support forums....YOU GUYS TRULY ARE THE HEART & SOUL OF ACRONIS USER SUPPORT.  I will give the normsl channel another day and see what happens before i make a "higher level" contact.

condidering the odd , outside of ATI app" cannot connect to server errors, its odd to me that Acronis support staff are not aware of what i think will be Acronis backend services...

on all my other pcs, starting the ATI  program, DOES show all as activated and the state of Cloud access...even on the Dell, which shows not activated, it PROPERLY  reports only 4 days of renaining Cloud Access...but i suppose the Activation servers are separate....

thx again, i'll keep u posted, even if just to report the results which other users might find helpful

bob

 

 

Bob, I can confirm that there does seem to be an issue with the Live Chat service this evening as I have just tried submitting my own support ticket for a problem I can reproduce for another user in the 2017 forum - I had the live chat window open but was never connected after waiting for some time.

I have submitted my ticket by email instead and got an immediate response with my case number by email.

Thanks for the feedback...I received an email from support this morning, confirming a problem with their activation server....all is running well now.

bob

Bob, glad to hear you were able to finish the activation and the server issue was solved.