unable to see the network after creation of universal WinPE recovery media
Hello
I just bought Acronis 2016 build 6027 software and have no problem creating a backup from my Windows 10 X64 computer to my NAS through the network.
But when booting from USB, with my newly created WinPE Acronis Universal Recovery Media (or via the F11 boot key), my network is not found.
I think it's coming from the unknown (from Acronis and current Windows kit ) I219V lan chip. Thus no recovery is possible and my software is useless for restoring entire system disk which was the main goal of my purchase.
Any help from the Support would be greatly appreciated
Best regards from France
Thanks Mark
You'r absolutely right. Problem is to find a working WinPE driver for the Intel I219-V Lan chip.
The described procedure with the standart Win driver failed.
And not even the shadow of a I219-V WinPE driver one on the INTEL website.
Pezzed:
The Acronis WinPE is 64-bit and you're using Win 10 64-bit on your PC, so can you find the .inf file that your ASUS motherboard is using either from ASUS or on your PC in C:\Windows\INF? The driver that works in Win10 64-bit should also work in WinPE 64-bit. See the "Tips" in the article I referenced in reply #1 here: https://forum.acronis.com/forum/100770
Hello Mark
I did exactly as indicated in link https://forum.acronis.com/forum/100770
I identified the seven (.dll, .inf, .cat, .din, .sys) I219-V driver files for Windows 10 and integrated them in the .wim file.
The procedure went out perfectly with not even a warning.
The kit indicated me at step 3 that the drivers where correctly included.
I completed the procedure, copied the .wim file and booted on my new USB key.
One more time : NO NETWORK.
No network available when browsing the system.
I concluded that the Windows 10 LAN drivers are not the drivers requested by WINPE.
I am absolutely sure the ACRONIS software developers have a solution or an answer to this problem but I do not understand why they keep silent.
Pezzed:
Acronis doesn't always respond to forum posts so if you want to get in contact with them you should use the link "How to get Support" at the top left of this page.
Hello,
I have the same problem as Pezzed. I've tried the same steps including the corresponding Intel LAN-Drivers into the boot.wim file.
All to no avail. Is there a solution to the problem yet?
Regards,
Michael
Go to the command prompt in WinPE and use the net use command to map the network share to a drive letter.
net use y: \\ComputerName\ShareName /user:UserName password
This command maps the share to the y: drive.
Hello Mustang,
thanks for your answer. But that solution would require an existing network configuration. And as the network interface driver is missing (or not properly recognized, whatever the reason) there is no way to run net use.
Michael
How do you know the network adapter is not recognized? In WinPE True Image does not show any information under Network even when the network adapter is working. I would expect that WinPE from the Windows 10 ADK would have built in drivers to support the Intel I219-V adapter. Did you try the net use command?
I sure did. And I would expect network support for I219-V as well with True Image 2016 (without me adding any further drivers manually).
How I know that the network adapter is not recognized? Try ipconfig, a standard commandline tool to view and manipulate the network configuration.
Michael
What version of Windows are you running and which version of the ADK do you have installed? You can check the exact ADK version from control panel, installed applications. Our WinPE did not pick up some of the NICS on the newer Dells with 6th gen itnel chipsets and latest ethernet adapters as well. I always keep a generic USB to ethernet adapter on hand for instances like this, just in case. Any generic USB 3.0 gigabit adapter should work fine with Linux or WinPE - I kind of like this one for the added USB ports as well since some laptops need extra mice/keyboard, networking, external hard drive and bootable USB, but that's just my preference.
Intel drivers for this exact adapter are available at: http://ark.intel.com/products/82186/Intel-Ethernet-Connection-I219-V#@downloads
I downloaded the 20_7_CD.zip as a test. It has a bunch of drivers for Windows, BSD and Linux so it's overkill, but you can extract out just the Windows ones and load them all into your PE so you have them all next time.
Hello Bobbo_3C0X1 and thanks for your response! First of all, here's what I used to make the custom WinPE:
- OS: Windows 10 Education N 64bit
- ADK version: 10.0.1586.0 (info taken from Windows Assessment Console)
- PRO1000 Win10(32bit) Intel LAN Drivers: e1s6532.inf, e1s6532.sys
I followed each and every step from Mustang's guide (https://forum.acronis.com/forum/100770) to get the network drivers into boot.wim.
The LAN drivers match exactly the OS and ADK and the ones from Intel I downloaded from your link aren't newer than the ones that came with the ASUS driver CD. The path structure to the designated driver which I followed was:
.\PRO1000\Win32\NDIS65\WinPE
This and the corresponding readme.txt tell me I'm in the right place. Unfortunately it does not work out. So I think I'll opt to the external USB NIC solution you suggested. It might come in really handy for the future.
Michael
I see your mistake. You have used a 32 bit driver. The WinPE is 64 bit and needs the 64 bit driver. You can't pull the drivers from a 32 bit operating system. I would download and unzip 20_7_CD.zip and add PRO1000\Winx64\NDIS65\e1d65x64.inf.
Not really. I did a copype x86 right from the start. So I should be in 32-bit WinPE, right?
Michael
No. TI 2016 is only available in a 64 bit version so you must use a 64 bit WinPE.
- I am having the same problem. Using the 64 bit driver listed above but still unable to see network.
Just to make sure for Pezzed (OP), Michlin and Jerry...
1) You're all running Windows 10 v1511 and using the Windows 10.1 ADK?
2) If so, when you originally create the WinPE for Acronis, you're using a USB flash drive and not an .iso, correct (the .WIM needs to be accessible and modifiable)?
3) When running the Windows 10 ADK "Deployment and Imaging Tools Environment", you're using elevated credentials (right click and "run as admin".
4) From there, you're mounting the "boot.wim" file from your Acronis USB drive to some folder on your PC? ****NOTE that you don't need to extract WinPE_amd64... replace the path from the example below with your Acronis boot.wim that is on your Acronis USB media. Your mount directory can be anywhere on your system as well - but the folder has to exist first so if you take the default in the example, create that folder path first and make sure that everyone has access to it. The Windows examples assume you're working with a generic winPE, but you're not going to copy and use the .WIM from WinPE_amd64 as you already have the .wim on your Acronis bootable media.
https://technet.microsoft.com/en-us/library/hh824972.aspx
Example:
Dism /Mount-Image /ImageFile:"C:\WinPE_amd64\media\sources\boot.wim" /index:1 /MountDir:"C:\WinPE_amd64\mount"
5) Once your folder has been mounted, you are injecting the drivers into it and not a generic ADK .wim from the Windows examples.
https://technet.microsoft.com/en-us/library/hh825070.aspx
Example:
Dism /Image:C:\test\offline /Add-Driver /Driver:C:\drivers\mydriver.inf /ForceUnsigned /Rescurse
****NOTE replace the paths above with your Acronis boot.wim mounted folder path from step 4. Repace mydriver.inf with the actual driver you want to inject. I recommend using /forceunsigned and /recurse always - this will help install drivers that may not have proper signatures and will allow you to install several drivers within folders at the same time if there are multiple that need to be added. If you are doing a single, specific driver and pointed to the .inf file, /recurse is not needed.
6) Once drivers are injected, commit the changes back to the .WIM and you're good to go. Again, change the paths in the example to your mounted folder from step 4.
Example:
Dism /Unmount-Image /MountDir:C:\test\offline /Commit
If you're doing this to this to the letter, have the correct 64-bit driver and it's not working, you may need to consider adding the chipset driver into your boot.wim as well. If that doesn't do it, I'd say your drivers are too new for Windows ADK and this is Windows issue that wiill hopefully be resolved with later Windows ADK updates.
There've been some great and pretty technical replies here! Having just successfully made it through this rite of passage, I know how overwhelming this whole WinPE thing can be. So, while it's still fresh in my mind...
I've written a detailed, step-by-step guide to doing this (for optical media, but flash drive users can adapt the protocol). It's posted here, reply #5.
z
Hello zzwerzy
Thanks for your investigations.
But would you please confirm that you used the Intel I219-V Lan chip driver to create the boot.wim file and could see your network.
I know your procedure works fine with a lot of driver but in fact not with this NIC.
I was working with a different NIC: the Marvell Yukon 88E8075.
Go back to my walk-through and try the steps listed under "Supplement" to determine if the driver(s) you have will work (drvload ?????.inf). Iow, generate a WinPE disc directly in Acronis Rescue Media Builder, boot to that disc, and then try your drivers using the drvload command in the WinPE command prompt window. You can place those drivers on a flash drive or store them on your c: drive. Both should be visible in the command line environment.
When you load the correct driver (and perform the other commands), ipconfig will return IP addresses, mask, gateway, etc. Once this happens, you know you've got the right files and can proceed to generate your custom media.
Remember, only 64-bit drivers will work. Many different drivers will be available. Your best bet is to get them direct from the builder (Dell, etc) or, if it's a homebuilt or small vendor built machine, from the motherboard manufacturer (Gigabyte, MSI, etc).
Luck!
z
I was working with a different NIC: the Marvell Yukon 88E8075.
Go back to my walk-through and try the steps listed under "Supplement" to determine if the driver(s) you have will work (drvload ?????.inf). Iow, generate a WinPE disc directly in Acronis Rescue Media Builder, boot to that disc, and then try your drivers using the drvload command in the WinPE command prompt window. You can place those drivers on a flash drive or store them on your c: drive. Both should be visible in the command line environment.
When you load the correct driver (and perform the other commands), ipconfig will return IP addresses, mask, gateway, etc. Once this happens, you know you've got the right files and can proceed to generate your custom media.
Remember, only 64-bit drivers will work. Many different drivers will be available. Your best bet is to get them direct from the builder (Dell, etc) or, if it's a homebuilt or small vendor built machine, from the motherboard manufacturer (Gigabyte, MSI, etc).
Luck!
z
Pezzed,
Maybe I can help you sort this out a little more...
Tell me the manufacturer and model of your system, or if it's a home or small builder created machine, the make and model of your motherboard.
With the right info I might locate the correct driver for you.
Loves a mystery,
z
The procedure in the link is very confusing. I elected to buy a USB 3.0 to Ethernet adapter instead. It works fine with the recovery disk. No extra drivers needed. Thanks for all the help and input.
i have the excat issue with the Intel I219LMV Gigabit Ethernet driver :-( - very frustrating !!
Mark, see my reply in your post: http://forum.acronis.com/forum/122938