Salta al contenuto principale

Problems with Bootable Media

Thread needs solution

Acronis True Image Home 2016 v 6027 originally installed on WIn 8.1

Major problems with Acronis Bootable Media (see below) so I created a WinPE (8.1). This boots properly.

It doesnt offer any network option in recovery/ browse but if I type in the adress of my NAS i.e

\\10.0.0.8\

it accesses the NAS and I can browse and select and recover - I tried a test recovery - no problems.

I have now updated windows to Windows 10 so I created a WinPE for windows 10 and repeated as above. In this case typing in the adress doesnt work.

I tried IPCONFIG in the command window and the ethernet card is configured - but no luck - so ...

Should I keep the WinPE (8.1) boot to recover Win10 backups?

Whats wrong with WinPE (10) - perhaps I missed part of the build - I only included Deployment and WinPE.

NOW - what about Acronis Bootable Media instead - it just doesnt work. The same problems occur on both my laptop and desktop. Both are mede by HP and both have the latest BIOS updates.

There are 4 boot scenarios for Acronis Bootable Media

1. Legacy Bios - 32 bit: This works but has no UK keyboard support - despite the information on Acronis Website and in the User Guide it just does not support either the inbuilt UK keyboard on my laptop or the wireless USB UK keyboard on my desk top. Also despite the paperwork saying a UK build is available the support team say there is ONLY a US build.

2. Legacy Bios - 64 bit: See photo 7 attached. When booting under legacy BIOS settings and choosing 64 bit this crash occurs.

3. UEFI BIOS - 64 bit: See Photo 3. This screen shows a crash. It did not wait for user input to select 1/2/c. There was no option presented to select 32 bit.

4 UEFI BIOS 32 bit - this does not appear to be available - see (3) above.

Recovering from these crashes has involved BIOS recovery and hard disk file repair.

So - effectively - there is NO fully functional standalone boot available for windows 10

0 Users found this helpful

Hello Alan,

You certainly do have issues here.  I would recommend that you do keep your Win 8.1 WinPE boot media as it appears to work and should be good to use for recovery of a system disk backup image if necessary.

Since your issues invlove that of recovery, support is not limited to the 30 day period relegated to the other functions of the product.  Therefore Support is available to you through the support channel.  I recommend that you take advantage of that.

In my opinion for your issues with boot scenario 1, the product not having UK keyboard support I think would be due to the language variant used to create the WinPE media.  The application should direct you to the correct variant and it sounds like that did not occur.  Support needs to know this.

For scenario 2, This condition might be attributable to your machine bios settings for boot options.  Support can direct you as to what would be required for your machine.

For scenario 3, I suspect this might be a result of having Secure Boot enabled in your machine bios.  This should not be the case however as I can confirm that the WinPE media does in fact work on a machine with Secure Boot enabled.  Support needs to investigate that.

For scenario 4, UEFI BIOS 32 bit not apearing as an option would indicate that your configuration does not support it as the current configuration of the bios stands.   That option is therefore unavailable.

I encourage you to contact support as clearly these issues need to be addresed at that level.

The 4 issues related to Acronis Bootable Media was logged as a support issue on Jan 2nd - so far with little enthusiasm from Acronis's end.

The failure of wINpe (10) is new to me today, but others with other applications also seem to be having problems getting WinPE(10) to access network shares.

The language isssue is NOT with WinPE which works with IUK keyboard layout - it is with Acronis Boot Media 32 bit. It is an Acronis issue.

 

I can make the WinPE (10) bootable media access network share by manually entering the following command into the script windows

 

wpeutil initializenetwork

net use Z: \\10.0.0.8\public /user:username password

 

Now I just need to work out how to add these two commands to the startup script

 

Allan

The only way I have discovered to get access to a network with this version of winPE is by entering the following commands into the Windows Command Prompt window.

wpeutil initializenetwork

net use z: \\10.0.0.8\public /user:username password

This creates a shared drive entry in the browse list from which I have successfully recovered data.

Note that when creating the share the credentials were supplied in the command. There is something not quite right here which I have not yet figured out

Accessing a share on a Win 10 computer:

The command:

net use z: \\10.0.0.10\folder

Without credentials in the command line - WinPE prompts for credentials and these are required on my computer as the folder has restricted access.

Accessing a share on my NAS Drive (Seagate  Personal Cloud):

net use z: \\10.0.0.8\folder

does not prompt for credentials - they should not be needed as the folder has no restrictions - and fails, the share is not created System Error 58 is generated. I believe the SEagate drive uses Samba (this could be wrong) could this be connected to this fail?

net use z: \\10.0.0.8\folder /user:x y 

works, but note that "user: x y' are nonsense credentials.

I found instructions for addig commands ti the WinpE 'startcmd.cmd' file at https://technet.microsoft.com/en-gb/library/hh824972.aspx

I have added the following 3 lines of code to my startnet.cmd

wpeutil initializenetwork

ping -n 15 127.0.0.1

net use z: \\10.0.0.8\public /user:username password

The ping command is used to create a delay to allow the network to come up, without it the net use command fails. I have used a 15s delay, but have not tried a shorter delay. the address 127.0.0.1 is the generic addres for the machine that this command is run on.

 

Allan

 

Acronis starts from a file called startnet.cmd at Windows\System32 in the WinPE build.  You can add your script lines to that file before the line that starts TI 2016.

Your issue with non access to your NAS drive running SAMBA is a known problem in Windows 10 build 10586 any version and is related to the Browse functions of server level computers on your subnet.  This issue is being addressed by Microsoft but the fix will not be available until the next service release of Win 10 due in March.