MVP Tool - CUSTOM ATI WINPE BUILDER
CURRENT VERSION:
9.9 Advanced (03/23/2017) released - minor bug fixes (cleanup when done) - brings back the ability to pick custom screen resolutions.
README----Basic Vs. Advanced MVP_ATIPEBuilder
ChangeLog - started with 9.5 on 3/16/2017
Due to the larger size of the Advanced version, (about 60Mb), we are unable to post it directly in the forums so everything has been moved to the Acronis MVP Google Drive.
Indeed! Followed the instructions and the USB boots and sees the disk!
I tried V9.9 yesterday. It would not recognize the RAID drive in my Dell XPS 13 (9350). I still had to go into BIOS and change the SATA mode to AHCI before booting from the USB and running ATI. After doing this I was able to successfully recover an image and then, after returning the SATA mode to RAID, was able to boot and run the computer normally.
George,
Have you tried the basic version 5.9? The basic version as far as RAID driver injection goes is the same as the 9.9 version but simpler to use to insure you make the right choice when adding those drivers.
George, regardless of the version, you must select "yes" to inject custom drivers. We provide the IRST (Intel Rapid Storage Technology) drivers in the tool already, but they only get injected when you select yes to add the custom drivers in that section. You need these to address RAID mode for any OEM system that comes with an NVME PCIE hard drive - this will work for all of the Dell systems.
I did select YES to install the custom drivers. I just tried it again. Apparently an error occured and the IRST driver was not installed. The script window closes a few seconds after cleanup and I didn't get all the details on the error before it vanished. Here is the log from running the tool if that helps.
04-10-2017_09.04.27
MVP Tool - Acronis WinPE Rescue Media Builder
v.9.9
*************************************************
------------------
SYSTEM INFORMATION:
------------------
PC NAME: SKIPLT-4
BIOS UUID: 63BEF200-33DE-11E1-A97E-5453EDB6AE9A
---------------
OS INFORMATION:
---------------
NAME: Microsoft Windows 7 Home Premium
VERSION: 6.1.7601
BUILD: 7601
ARCH: 64-bit
DIRECTORY: C:\Windows
LANGUAGE: en-US
OS UUID: 1ff1e13e-6fb1-4f88-ad40-93cf46581c3f
-------------------
ACRONIS INFORMATION:
-------------------
ATIH VERSION: 2016
ATIH BUILD: 19.0.0.6581
UR VERSION: 11.5.0.39006
DD VERSION: NotFound
DD BUILD: NotFound
--------------
VARIABLE PATHS:
--------------
SCRIPT SOURCE: C:\Users\Skip Forster\Downloads\Acronis stuff\MVP_ATIPEBuilder_v99\MVP_ATIPEBuilder_v99
ATIH PATH: C:\Program Files (x86)\Acronis\TrueImageHome\WinPE
UR PATH: C:\Program Files (x86)\Acronis\UniversalRestore\WinPE
DD12 PATH: NotFound
ADK PATH: C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment
----------------
ADK INFORMATION:
----------------
Installed: 10.0.14393
WINRE64: NotFound
WINRE86: NotFound
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
MVP ATIPeBuilder LOG DETAILS:
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
Mon 04/10/2017 9:05:12.58 You chose [2.] "64-bit Media Builder" - USER selected.
Mon 04/10/2017 9:05:18.87 Skipping network share mapping - USER selected.
Mon 04/10/2017 9:05:20.19 Mounting amd64 winpe.wim.
Mon 04/10/2017 9:05:43.19 The default OS language is English - skipping language options.
Mon 04/10/2017 9:05:43.20 True Image Found. Adding It.
Mon 04/10/2017 9:05:50.17 Universal Restore Found. Adding It.
Mon 04/10/2017 9:05:56.13 Disk Director 12 Not Found. Skipping It.
Mon 04/10/2017 9:05:59.22 Adding in extra goodies.
Mon 04/10/2017 9:07:29.36 Adding custom drivers to amd64 winpe.wim file - USER selected.
Mon 04/10/2017 9:07:53.21 Skipping MSiScsi Support Packages - USER selected.
Mon 04/10/2017 9:08:10.83 Skipping Bitlocker Support Packages - USER selected.
Mon 04/10/2017 9:08:19.96 Do not prompt for any key at boot - USER selected.
Mon 04/10/2017 9:08:27.66 Skipping WinPE screen resolution - USER selected.
Mon 04/10/2017 9:08:29.18 Saving changes to amd64 winpe.wim file.
Mon 04/10/2017 9:09:35.14 Creating Acronis_amd64.iso.
Mon 04/10/2017 9:09:45.83 Acronis_amd64.iso is located in "C:\Users\Skip Forster\Downloads\Acronis stuff\MVP_ATIPEBuilder_v99\MVP_ATIPEBuilder_v99\ISO"
Mon 04/10/2017 9:09:50.17 Creating Acronis_amd64.wim.
Mon 04/10/2017 9:10:27.78 Acronis_amd64.wim is located in "C:\Users\Skip Forster\Downloads\Acronis stuff\MVP_ATIPEBuilder_v99\MVP_ATIPEBuilder_v99\ISO\Wim".
Mon 04/10/2017 9:10:38.06 Creating USB flash drive - USER Selected.
Mon 04/10/2017 9:10:52.23 USB flash drive letter is [F:] - USER Selected.
Mon 04/10/2017 9:11:39.15 Skipping CD/DVD burning - USER Selected.
Mon 04/10/2017 9:11:41.18 Cleaning up now.
Mon 04/10/2017 9:11:47.17 FINISHED.
I'm updating the builder to log the adk driver injection for custom drivers and will release soon. Without seeing the error, really can't say. We have it outputting to the screen so users can see them injected and view the progress in case it takes awhile, but I think logging them will be more useful for troubleshooting.
in the meantime, you could run it again and screenshot the error. You can scroll up at any of the menu stops.
I reran the tool and stopped at the first prompt after driver installation to view the messages. The script attempted to install three drivers: iaAHCIC.inf, iaStorAC.inf and oem49.inf. All three failed with the same error:
INFO: DISM has skipped driver signature check because the version of running OS and that of target OS do not match.
Error - an error occured. The driver package could not be installed. For more information, check for log files in the <windir>\inf folder of the target image.
I am running the tool on a Windows 7 (64-bit) box to a create bootable recovery USB to recover a Windows 10 (64-bit) box. I unclear where to look for the log files referenced in the error message.
George,
You will find the log files in the folder where you extracted the MVP Builder files to after you downloaded the .zip file.
I think your problem is likely that you have the wrong ADK installed on your Win 7 machine. You would need the Windows 10 version of the ADK installed to build a media for the Win 10 system.
Well, the log files in that folder are like the one I sent a few posts back -- no error message info, just a list of the steps run.
The ADK info in the log file is as follows:
----------------
ADK INFORMATION:
----------------
Installed: 10.0.14393
WINRE64: NotFound
WINRE86: NotFound
Can you tell anything from that? If not, I will try downloading the Win 10 ADK and rerunning the tool.
There should be no issue using Win10 ADK on Win7 - I do this myself. However, you can't inject Win7 drivers into Win10 ADK (usually) if providing your own drivers. And, if the winpe.wim is different than the one that originally came with the installed ADK, it won't work either (especially if attempting to replace winpe.wim with winre.wim and just renaming it, but the versions are actually different).
Did you replace the winpe.wim in your ADK with something other than the original? DISM knows the actual version of the winpe.wim that's associated with the installed ADK. It won't let you use installed ADK with a different version of winpe.wim that is not a version match... well, you can use it, but it won't let you inject drivers or add DISM packages because of the mismatch.
In some cases, ADK does not upgrade over itself very well either, so it could be leftovers from an earlier version of ADK if you didn't intentionally swap the original winpe.wim file.
If you are wanting to use winre.wim and attempting to substitute them for winpe.wim, don't do that. Instead, put those winre.wim files in the winre folders of the MVP tool and leave them named as the original winre.wim. The MVPtool, will use DISM to detect the version there. If it matches the installed ADK version and is a match for the current OS, then it can be used. If it doesn't match the OS or the installed ADK, it won't let you use them.
Otherwise, I would suggest reinstalling the ADK. Remove the currently installed ADK from control panel, check to make sure C:\Program Files (x86)\Windows Kits is completely gone, reboot, and re-install the ADK again to make sure it is in a good state. That will ensure that the winpe.wim is the correct version for the installed ADK on the system.
FYI, when you download the ADK from Microsoft, there are 2 options - install on this computer or download to use on another computer. I always select the option to download to use on another computer as that keeps the file available so you don't have to download it again. You can then run that on the local computer to install and hold onto it for posterity if you need to reinstall or use it on another machine again.
New Release - 10.9 Advanced!!!
ChangeLog - check out the 10.9 Advanced improvements!!!
CURRENT VERSION:
10.9 Advanced (04/11/2017)
5.9 Basic (11/26/2016)
README----Basic Vs. Advanced MVP_ATIPEBuilder
Due to the larger size of the Advanced version, (about 60Mb), we are unable to post it directly in the forums so everything has been moved to the Acronis MVP Google Drive.
https://kb.acronis.com/content/59335?build=8041&distributor=86&edition=…
What is wrong with this link?
1. Turn Acronis Active Protection off I don't see thia.
2. I can't find Killer Network stuff
thanks
David, I suspect that you just need to go to https://kb.acronis.com/content/59335 but that the KB document may need to be updated to reflect the changes made to these community tools recently - suggest you go directly to the MVP Google Drive instead which hosts these tools and has all the latest versions.
Acronis Active Protection is a feature of the Premium ATIH 2017 New Generation version (subscription only) and is the anti-ransomware functionality.
Ditto to Steve. I can post Mvp tool updates to Google drive any time. Takes longer to get Acronis approval to test the changes and link them to the KB article. I'll bring this up though and see if they can check out the change I uploaded last night and update the download there too.
Killer Ethernet drivers are located in custom drivers folder and will be added at build if you choose to inject custom drivers. There is no killer app for WinPE though. The drivers just help ensure your NIC can be used in the rescue media. If you have a Killer NIC in the PC, you could also select the option to inject system drivers if you have a compatible OD and compatible ADK installed for the build. Win7 is not supported for system driver injection so you'd have to use the custom driver injection.
New Release...
11.0 Advanced (04/18/2017)
ChangeLog - check out the 11.0 Advanced improvements!!! Wi-Fi is working with ADK/WinRE 1607 and 1703 now.
README----Basic Vs. Advanced MVP_ATIPEBuilder
Due to the larger size of the Advanced version, (about 60Mb), we are unable to post it directly in the forums so everything has been moved to the Acronis MVP Google Drive.
is there anything that needs to be tested regarding 11.0?
Only if you want to try using WinRE.wim to build recovery media with wireless support now - especially if you want to try with 1607 or 1703 ADK and WinRE. Other than that, 10.9 and 11.0 are pretty much the same everywhere else.
The other items you noted before with 10.9 still exist...
-format is quick format for creating USB so may not always work unless the drive has been fully formatted before
-the last note about file not at the very end will still be there for the forseeable future too. It's a last "clean" attempt, in case the builder was terminated early on another run and may have left something behind. If there are no leftovers and/or cleanup has already happened like it's supposed to at this point, it will throw that message because the EXE wants to cleanup as well and we don't have control over that last line that checks itself before closing out.
Does there have to be wireless support on the PC running the Build program? The builder said "The Wireless AutoConfig Service (wlansvc) is not running." (which is true on this PC) and then said I didn't have any wireless profiles in the builder's profiles file. That is not true (unless I put them in the wrong place). The error message complaining about missing profiles is not logged and I didn't copy it before closing the command window.
I may have misunderstood 2 steps in the directions:
3. Go to C:\Temp and find the *.xml file exported in step 1.
Place this xml file in the \Other\x86 or x64\WiFi\Profiles folder.
4. Go to the \Other\x86 or x64\WiFi folder open wifi.cmd in notepad.
Replace YOURPROFILE.xml with the name of the profile you put in the Profiles
folder in step 2 in the following line:
cmd /k netsh wlan add profile filename="X:\Program Files\WiFi\Profiles\YOURPROFILE.xml"
I understand the the "C:\Temp" is generic. I'm less certain about the reference "\Other\x86 or x64\WiFi folder". I assumed that was the \WiFi folder in directory containing MVP_ATIPEBuilder.exe - in my case, "D:\Acronis Utilities\ATI_PE_Builder\Advanced\MVP_ATIPEBuilder_v110". Is that not the case?
Only if you want to try using WinRE.wim to build recovery media with wireless support now - especially if you want to try with 1607 or 1703 ADK and WinRE. Other than that, 10.9 and 11.0 are pretty much the same everywhere else.
The other items you noted before with 10.9 still exist...
-format is quick format for creating USB so may not always work unless the drive has been fully formatted before
-the last note about file not at the very end will still be there for the forseeable future too. It's a last "clean" attempt, in case the builder was terminated early on another run and may have left something behind. If there are no leftovers and/or cleanup has already happened like it's supposed to at this point, it will throw that message because the EXE wants to cleanup as well and we don't have control over that last line that checks itself before closing out.
I haven't consulted the changelog, so ok the file not found message is by design. Perhaps you can add an echo to point out that the following error message is by design.
I still don't get the issue with the USB stick. :(
From my point of view the download of the zip file is a bit bothersome. when you click on the file in google drive it will open the zip instead of downloading it, while it will download it when using the download button on the upper left. I fear there is less we can do about that but it might be irritating for users that are new to the tool and or google drive usage.
We might use Onedrive perhaps to make it a bit easier as there you could post direct download links and won't get the warning about virus protection etc.
As you use Win10 you always have some free Onedrive space.
Karl,
The zip file can be downloaded directly by right clicking it. This opens a menu with a download choice.
A couple comments.
As I commented yesterday, I'm running the Builder on a PC does not need, and normally does not have wireless support. I was able to get past the Wireless AutoConfig Service (wlansvc) problem by plugging in a USB wireless adapter. I don't know if it the Builder needed them, but I imported the wireless profiles that I had put in the Builder's WiFi directory. (I included two profiles.) At the prompt I gate the SSID name that I hope the recovery program will activate by default. I still find the comment " Place this xml file in the \Other\x86 or x64\WiFi\Profiles folder." confusing, but the Builder apparently found everything it needed where I put it.
In the part of the process concerning automatic mapping of network drives it is unclear whether mapping of a public share is supported. I will find out soon.
My first attempt at building bootable USB flash memory failed. The Builder's attempt at formatting the device failed. It reported an error as (I think) a large negative number. (The error was not logged so I cannot corfirm this.) Displaying it in hexadecimal would probably be more meaningful. The Builder then went on to asking about burning a CD/DVD. I reformatted the device using RMPrepUSB, restarted the build, and it succeeded. It would be nice if build process allowed a retry of the USB formatting. Then a new or reformatted device could be tried without restarting the process.
Now I will go try the recovery USB.
Karl,
The zip file can be downloaded directly by right clicking it. This opens a menu with a download choice.
Thanks Mustang, quite uncommon to see webbased context menus in a browser.
Please excuse bonehead questions but I'm really out of my depth technically here.
I tried my recovery system I just built with the ethernet cable unplugged and a USB wireless adapter plugged in. (This was the same adapted that was plugged in when I built the recovery system.) The wireless support did not work. The WinPE (or WinRE - whatever it is) system said no network interface was detected.
I've checked and found the driver folder for the device in the ATI_PE_Builder\Advanced\MVP_ATIPEBuilder_v110\Drivers_Extracted\x64\DDBackup_UUID_2DC79F20-D7DA-11DD-8D12-AC220B74A1D2\Net directory. Do I copy it from the Drivers_Extracted into the Drivers_Custom directory in order to get the driver included?
For drivers of wireless adapters (internal and USB) is there a convenient utility to extract the drivers? I have Double Driver and its Backup function seems to do that, but I'm not sure if that's what you need in the Drivers_Custom folder.
Patrick, were you prompted with the options to add wifi during build? You must be using Windows 10, must have supplied your own winre manually and must have the same version of ADK installed to match the winre.
Microsoft really doesn't wireless in winpe because they don't want it too functional. You'll only get the wireless options during the build if all of the other caveats were met.
if you did, then drivers would be supplied when you pick the option to install system drivers. Check to make solute the log shows no error for wireless drivers though.
theres more info in the history text file. Although it will work for many, I'd still consider wireless integration a bonus and may not work for everyone if the wireless dongle or card requires custom software to work correctly as well.
Patrick,
Seeing the message there is no wireless interface means the driver for the wireless adapter didn't work. First, check the log file to see if there is an error message for the wireless driver. If there is no error in the log and the driver was installed successfully, there could be a problem with the digital signature of the driver sys file. Look in the inf file for the driver to drtermine the name of the service for the driver. Boot the recovery media and open a command window. Enter the following line:
net start ServiceName
where ServiceName is the name you got from the driver inf file. The system will tell you if the service is running or if there is an error. If the service isn't running, there will be no wireless interface on the system.
EDIT:
Also check that a service called vwifibus is running in the recovery media:
net start vwifibus
If is is not, you should copy two files for that service to the driver folder and rebuild the media:
C:\Windows\System32\drivers\vwifibus.sys
C:\Windows\INF\netvwifibus.inf
Patrick, were you prompted with the options to add wifi during build?
Yes, I was.
You must be using Windows 10,
That's all I have.
must have supplied your own winre manually and must have the same version of ADK installed to match the winre.
The ATIPEBuilder log shows
----------------
ADK INFORMATION:
----------------
Installed: 10.0.14393
WINRE64: 10.0.14393
WINRE86: NotFound
I assume that means they match.
Microsoft really doesn't wireless in winpe because they don't want it too functional. You'll only get the wireless options during the build if all of the other caveats were met.
if you did, then drivers would be supplied when you pick the option to install system drivers. Check to make solute the log shows no error for wireless drivers though.
theres more info in the history text file. Although it will work for many, I'd still consider wireless integration a bonus and may not work for everyone if the wireless dongle or card requires custom software to work correctly as well.
The wireless drivers - both the one for the currect system extracted during the build process and on for another system - were included in the build according to the build log. However, fairly early in the build process the message
"There is no wireless interface on the system."
was loggged. That is technically true - it is a USB interface - but it was active and connected during the build. It was not being used since I had my Ethernet connection active, but the interface was present and active. I'll try the build again using just the WiFi adapter.
Patrick,
Seeing the message there is no wireless interface means the driver for the wireless adapter didn't work. First, check the log file to see if there is an error message for the wireless driver. If there is no error in the log and the driver was installed successfully, there could be a problem with the digital signature of the driver sys file. Look in the inf file for the driver to drtermine the name of the service for the driver. Boot the recovery media and open a command window. Enter the following line:
net start ServiceName
where ServiceName is the name you got from the driver inf file. The system will tell you if the service is running or if there is an error. If the service isn't running, there will be no wireless interface on the system.
I'm afraid I flunk. I find lots of things in the driver .inf file but I cannot find any running service that matches them.
EDIT:
Also check that a service called vwifibus is running in the recovery media:
net start vwifibus
If is is not, you should copy two files for that service to the driver folder and rebuild the media:
C:\Windows\System32\drivers\vwifibus.sys
C:\Windows\INF\netvwifibus.inf
I probably won' get to thhis until tomorrow.
Patrick,
I was assuming you were getting the no interface error when you booted the recovery media. It looks like you get that error during the build. You need to have WiFi completely working in Windows before you build. There needs to be a wireless interface in Windows. You then need to connect to your network through the wireless interface and that will create a wireless profile on the system that has the SSID and password of your network. The script will attempt to export the wireless profile to the WiFi\Profiles folder. You then need to edit the WiFi.cmd manually to specify the profile name that was exported during the build.
All this assumes the driver for the wireless adapter has also been added successfully.
I'm sorry, but getting WiFi working is very complicated. When you do get it working, it will only work when you boot the media on the computer you used to build the media. It won't be universal for all computers. You can export profiles from other computers manually and add them to the WiFi\Profiles folder. But, they need to be exported in a very specific way from each computer you want to use. Then you can manually add the profile for the specific computer you boot on after the boot is completed. Then you need to run a connect request. That way you can get it to work for more than one computer. There is a steep leaning curve here.
I should have said initially that I consider myself a guinea pig in this. I would like, but don't absolutely need, this wireless support. Unfortunately I'm a pretty ignorant guinea pig - consider me an "average user". Feel free to tell me to give up and stop wasting your time whenever you want.
Patrick,
I was assuming you were getting the no interface error when you booted the recovery media. It looks like you get that error during the build. You need to have WiFi completely working in Windows before you build. There needs to be a wireless interface in Windows. You then need to connect to your network through the wireless interface and that will create a wireless profile on the system that has the SSID and password of your network.
Actually, I already have two wireless profiles on this PC - the same 2 I use on 2 other computers. However, a "Netsh WLAN show profiles" shows "There is no wireless interface on the system." when I do not have my USB wireless adapter plugged in. When plugged in the command shows both profiles. That makes me think I did not have the adapter plugged in when running the builder. My bad! I will try again (in a few hours).
The script will attempt to export the wireless profile to the WiFi\Profiles folder. You then need to edit the WiFi.cmd manually to specify the profile name that was exported during the build.
I have manually put the profiles in the profiles folder. Should I remove them before running the builder again?
All this assumes the driver for the wireless adapter has also been added successfully.
I think they have been.
I'm sorry, but getting WiFi working is very complicated. When you do get it working, it will only work when you boot the media on the computer you used to build the media. It won't be universal for all computers. You can export profiles from other computers manually and add them to the WiFi\Profiles folder. But, they need to be exported in a very specific way from each computer you want to use. Then you can manually add the profile for the specific computer you boot on after the boot is completed. Then you need to run a connect request. That way you can get it to work for more than one computer. There is a steep leaning curve here.
Could explain that "... in a very special way"? I know only "netsh wlan export profile key=clear folder=____". I have two profiles - one for 2.4GHz, one for 5GHz. My 3 computers use these, but 2 use the 5GHz and one (when it uses any at all) uses the 2.4GHz. That means the command would be different but the profiles would be the same. (The drivers are all different.)
In spite of your comment "It won't be universal for all computers", I'm hoping to create a single build that will work on all 3 of my computers.
Patrick,
You're not wasting my time. It looks like you're very close to having this working.
You should build again with the USB WiFi adapter plugged in. Before you do that, delete the x64 folder from the Double Driver Backup folder to be sure the wifi driver is picked up from the system.
It looks like you exported the profiles correctly. key=clear is the important thing.
You should be able to put all your profiles in the WiFi\Profiles folder before you build and be able to make it work on the three different computers. When the media boots it will add the profile that is specified in the file \WiFi\WiFi.cmd. You need to manually edit that file to enter the profile name to use. During boot of the media the profile is added and the you will see a connection request. If you see the connection was successful, you are all set. If it was not successful, you can open a command window and add the correct profile for the computer you booted on. The issue a connect request. That should work.
Here's the commnad:
netsh wlan add profile filename="X:\Program Files\Wifi\Profiles\YOUR_SSID_PROFILE.xml"
netsh wlan connect name=YOUR_SSID
Heya guys,
there are new RST drivers (inf or setup, just as needed) out
https://www.computerbase.de/downloads/treiber/mainboards/intel-rapid-st…
also new Intel NIC drivers (very widespread on mainboards)
https://www.computerbase.de/downloads/treiber/intel-ethernet-connection…
and here a good compilation of Intel onboard drivers you could extract for the PE environment.
https://www.computerbase.de/downloads/treiber/grafikkarten/intel-grafik…
don't mind it is a german site but the drivers are of course multilanguage.
Hi Karl,
Thanks for the heads up! I will update the IRST drivers in the next release using the ones directly from Intel - they look to be the same though: https://downloadcenter.intel.com/download/26730/Intel-Rapid-Storage-Technology-Intel-RST-?product=55005
In an effort to keep the builds as small for download as possible, we've limited additional drivers to those that the majority of systems would require for WinPE functionality. However, I have grabbed the updated links that point to the new IRST, added both of your links, added Lenovo, Samsung and Surface devices as well ( HP and Dell already exist) - users are more than welcome to grab them for their individual builds as they see fit. In most instances though, the Windows 10ADK seems to support the majority of hard drives and NICS just fine so any specific drivers wouldn't be needed for basic WinPE functionality (in most cases).
We only included IRST specifically for the RAID support since NVME is shipping in RAID mode and I also through in Killer Etherne since it's pretty common for a lot of custom boards and WinPE does not cover those (I have a Killer Ethernet adapter myself).
Although it would be nice to include all of the very lateset Intel NIC drivers, the package from the link you provided is 320Mb by itself (almost 6x the size of the entire MVP pe builder) and would significantly increase the build size - the chipset drivers are specific to the CPU version and are a couple-hundred MB each as well, so it's just too much to add directly. So far though, I haven't found an Intel NIC or CPU that the Windows 10 ADK is unable to support directly out of the box in WinPE, so I think we're covering the majority of home users with references for others to go and get their own specific drivers if they really want to.
I'm still having trouble getting the wireless support to work. When the WinPE recovery medium initialized I get 2 (and sometimes 3) copies of the message "There is no wireless interface on the system." If I manually issue "start net netr28ux" I get (excluding typos) the message "Windows cannot verify the digital signature of this file. A recent harware or software change might have installed a file the is signed incorrectly or damaged, or that might have be malicious software from an unknown source."
Looking in the DISM log from the build process I see:
2017-04-23 15:11:40, Info DISM DISM Driver Manager: PID=4400 TID=9848 Signature status of driver D:\Acronis Utilities\ATI_PE_Builder\Advanced\MVP_ATIPEBuilder_v110\Drivers_Extracted\x64\DDBackup_UUID_2DC79F20-D7DA-11DD-8D12-AC220B74A1D2\Net\802.11n USB Wireless LAN Card\netr28ux.inf is: UNSIGNED - CDriverPackage::InitSignatureStatus
2017-04-23 15:11:40, Error DISM DISM Driver Manager: PID=4400 TID=9848 Failed to find the file in driver store. - CDriverPackage::GetPublishedInfName(hr:0x80070490)
2017-04-23 15:11:40, Warning DISM DISM Driver Manager: PID=4400 TID=9848 Could not get boot critical status for the driver class {4D36E972-E325-11CE-BFC1-08002BE10318} from driver store. Assuming that this is not boot critical. - CDriverPackage::InitBootCriticalFlag(hr:0x80070490)
2017-04-23 15:11:40, Info DISM DISM Driver Manager: PID=4400 TID=9848 Signature status of driver D:\Acronis Utilities\ATI_PE_Builder\Advanced\MVP_ATIPEBuilder_v110\Drivers_Extracted\x64\DDBackup_UUID_2DC79F20-D7DA-11DD-8D12-AC220B74A1D2\Net\Realtek 8812AU Wireless LAN 802.11ac USB NIC\netrtwlanu.inf is: UNSIGNED - CDriverPackage::InitSignatureStatus
2017-04-23 15:11:40, Warning DISM DISM Driver Manager: PID=4400 TID=9848 Could not get boot critical status for the driver class {4D36E972-E325-11CE-BFC1-08002BE10318} from driver store. Assuming that this is not boot critical. - CDriverPackage::InitBootCriticalFlag(hr:0x80070490)
I may not have copied enough of the messages. They seem to be for the extracted driver for the wireless adapted on this PC and the custom driver for the wireless adapter I extracted from another PC.
If I have found the problem, is there some way I can tell either the build process or the WinPE system to use an unsigned driver? (I'm way out of my depth here. I don't even know what I just asked.)
Patrick,
Mustang has been working in the Windows forums and has come up with a resolution for the certificate errors and wireless driver signing in ADK 1607/1703. I'm going to post 11.1 in shortly for you to grab and test.
We are using the forced unsigned driver injection in DISM at build so that part itself is not an issue. DDouble driver may be having issues extracting the full wireless driver on it's own though. Let's see if 11.1 helps at all in your situation or not though.
New Release
11.1 Advanced (04/23/2017)
5.9 Basic (11/26/2016)
README----Basic Vs. Advanced MVP_ATIPEBuilder
ChangeLog - check out the 11.1 Advanced improvements!!! Wi-Fi is working with ADK/WinRE 1607 and 1703 as of 11.0 - additional Wi-Fi improvements added in 11.1
Due to the larger size of the Advanced version, (about 60Mb), we are unable to post it directly in the forums so everything has been moved to the Acronis MVP Google Drive.
Patrick,
Sorry to hear you are having a problem with an unsigned driver for your wireless adapter. I have no solution for that problem. I actually have the same problem with one of my wireless adapters. For me, the driver works in a 64 bit Windows system, but not in ADK's 1607 or 1703. Microsoft has really done a terrible job with these last two ADK's.
The latest release of the MVP Tool has WiFi support working with the 1607 and 1703 ADK's. However, this release won't solve a driver signature problem. Your only solution would be to go back to the manufacturer for an updated driver with a proper signature.
Patrick,
There is one solution that should work. You can use the original Windows 10 ADK (10240). That ADK doesn't like Acronis driver signatures. It throws a BSOD for an Acronis driver during boot. When you see the BSOD you just hit the F8 key to bring up a menu and then hit the F7 key to override digital signature enforcement. This should make the wireless driver work.
Dell XPS 15 9550 1TB NVMe PCIe SSD : 32GB MEM : GTX 960M : i7-6700HQ
Windows 10 Pro 1607 x64
Downloaded MVP Basic ( MVP_ATIPEBuilder_v59 ).
Created MVP PE and selected option #2 to inject IRST drivers.
Bootable media created successfuly.
Booted off of Bootable Media and Acronis splash screen came up.
Selected Backup Disk
My NVME wasn't seen, only USB.
I attached dism.logs ( after cutting & pasting items from today only and removing name )
I didn't see any log files in any of the folders where I downloaded and extracted: ATI_PE_BUILDER-20170424T021433Z-001
Please advise...
MVP ATI PE Builder
v.5.9
Nov 26, 2016
Acronis MVP's:
-----------------------------
Creators: Bobbo_3C0X1
Mustang
-----------------------------
Collaborators: Steve Smith
Enchantech
-----------------------------
***************************************************************
*************************** ***************************
************************** WARNING **************************
*************************** ***************************
***************************************************************
**** ****
**** Although this has been thoroughly tested, ****
**** use at your own will. This script is provided ****
**** "AS IS" with no warranty or support. ****
**** ****
**** Please post in the Acronis forums, if you have ****
**** questions, comments, or concerns before ****
**** (or after) using this home-grown, custom tool. ****
**** ****
***************************************************************
*************************** ***************************
************************** WARNING **************************
*************************** ***************************
***************************************************************
*****************************************************
** Administrative privilege confirmed. **
*****************************************************
::=============================================================::
:: Please select one of the following options. ::
::=============================================================::
:: ::
:: [1.] Build Customized 32-bit Acronis WinPE Rescue Media ::
:: [2.] Build Customized 64-bit Acronis WinPE Rescue Media ::
:: [3.] Exit ::
:: ::
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
2
----------------------------------------
[Backing up original ADK amd64 winpe.wim.]
----------------------------------------
::=============================================================::
:: Would you like to inject custom drivers into your WinPE. ::
::=============================================================::
:: ::
:: [1.] Yes ::
:: [2.] No ::
:: ::
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
1
*****************************************************
** Please ensure that you have added custom 64-bit **
** drivers to the "Drivers\x64" folder in the **
** PEBuilder application before proceeding. **
** **
** IRST drivers are already available. **
** It is recommended to include other custom **
** RAID controller and/or NIC drivers. **
*****************************************************
Press any key to continue . . .
=================================================================
---------------------------------------
[Mounting amd64 temporary boot.wim file.]
---------------------------------------
Deployment Image Servicing and Management tool
Version: 10.0.14393.0
Mounting image
[==========================100.0%==========================]
The operation completed successfully.
=================================================================
-------------------------------------------------------
[Adding custom drivers to amd64 temporary boot.wim file.]
-------------------------------------------------------
Deployment Image Servicing and Management tool
Version: 10.0.14393.0
Error: 2
An initialization error occurred.
For more information, review the log file.
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
=================================================================
------------------------------------------------
[Saving changes to amd64 temporary boot.wim file.]
------------------------------------------------
Deployment Image Servicing and Management tool
Version: 10.0.14393.0
Image File : C:\Users\NAME_REMOVED\Downloads\Acronis\MVP\ATI_PE_BUILDER-20170424T021433Z-001\ATI_PE_BUILDER\Basic\MVP_ATIPEBuilder_v59\MVP_ATIPEBuilder_v59\PE\media\sources\boot.wim
Image Index : 1
Saving image
[==========================100.0%==========================]
Unmounting image
[==========================100.0%==========================]
The operation completed successfully.
=================================================================
-----------------------------------------
[Swapping original ADK amd64 winpe.wim and]
[modified ADK amd64 winpe.wim.]
-----------------------------
*****************************************************
***************** PLEASE WAIT *****************
*****************************************************
*** ***
*** Launching Acronis True Image Media builder. ***
*** Use Acronis to build 64-bit PE media now. ***
*** ***
*** When complete, close the Acronis media ***
*** builder so the script can complete cleanup ***
*** and set things back to normal. ***
*** ***
*****************************************************
***************** PLEASE WAIT *****************
*****************************************************
Deleted
Deleted : Duplicate
Please grab the 11.1 advanced winPE builder which has it's own logging enabled and will show what drivers are failing to load in the custom drivers. All i see in your dism log is an initialization error which really doesn't identify what the problem is - you have an older version of ADK installed, I'd suggest removing it and using the most current Windows 10 ADK instead. There seem to be other errors showing possible issues with either your ADK installation or with a driver you are trying to include. I copied and highlighted a couple, but no smoking gun. They are all errors specifically to DISM though and not the tool.
An initialization error occurred.
2017-04-23 18:53:51, Error DISM DISM Driver Manager: PID=8876 TID=1056 Error, file not found 'oem59.inf'. - CDriverManager::OpenPackageByFile(hr:0x80070002)
2017-04-23 19:28:19, Warning DISM DISM Provider Store: PID=96 TID=14528 There is a possible 32-bit versus 64-bit cross architecture issue with the provider (or one of its dependencies). - CDISMProviderStore::Internal_LoadProvider(hr:0x800700c1)
2017-04-23 19:28:39, Warning DISM DISM OS Provider: PID=12912 TID=14996 Unable to set the DLL search path to the servicing stack folder. C:\Users\NAME_REMOVED\Downloads\Acronis\MVP\ATI_PE_BUILDER-20170424T021433Z-001\ATI_PE_BUILDER\Basic\MVP_ATIPEBuilder_v59\MVP_ATIPEBuilder_v59\PE\mount\Windows may not point to a valid Windows folder. - CDISMOSServiceManager::Final_OnConnect
2017-04-23 19:28:40, Error DISM DISM OS Provider: PID=12912 TID=14996 Failed trying to determine the OS Version. HRESULT=0x80070002 - CDISMOSServiceManager::get_OSVersion
Downloaded and created bootable with Advance and can see the NVMe PCIE now..
Can't perform backup now, I'll do it later... Just wanted to let you know that it can be seen.
Does the program ever modify or change registry?
In future, please add feature to log every single file that is copied, modified or restored n the logs...
Thanks for quick response and suggestion...
Downloaded and created bootable with Advance and can see the NVMe PCIE now..
Can't perform backup now, I'll do it later... Just wanted to let you know that it can be seen.
Does the program ever modify or change registry?
In future, please add feature to log every single file that is copied, modified or restored n the logs...
Thanks for quick response and suggestion...
I now have a recovery medium with wireless support that works on 3 computers with 3 different adapters. (I somehow missed the SSID prompt so have to manually do the NETSH WLAN Add and NETSH WLAN Connect but that's a nit. ) So now on to the next problem.
I'm having trouble mapping network drives. I skipped network share mapping in the build because I didn't want the WinPE startup to wait for 60 seconds in the network activation. (The mapping is going to fail until after I go through the manual wifi configuring so why wait?) Does bypassing the automatic mapping in the build exclude SMB support? Or am I running into some other problem? Both NET USE and the built-in network management utility. My notes are a bit cryptic, but one of those techniques - probably the NET USE - resulted in the message "The specified server cannot perform the requested operation". I've tried both public and private shares and have not been able to get either to work. I can ping the NAS and the network utility can see it (and a couple others I'm ignoring for now).
Just completed full backup of my Dell XPS 15 9550 : 1TB NVMe PCIE SSD.
Backup took less time than it did with earlier ATI 2014 or 2013 software. Don't know if they've made any improvements on backup alogorithms or compression methods, but it took 1hr less than it did in past which is good.
Thanks Bobbo and everyone else who participated to make the MVP Builder Media
The UI ( User Interface ) looks awesome and the added features are great. I didn't add or try wireless and network shares, but I might do that later.
Thanks again....
I've only done full backups ( disk images ) and disk image restores with Acronis.
I'm curious what types of backups are others using the bootable media for.
Do the Acronis Incremental Backups work?
a. are they reliable 100%
b. are they " really " faster, which they should be since they're only backing up new items
c. or are the incremental backups slower because they have to go through complete file system to determine which files to backup?
Patrick,
Congratulations on getting the WiFi to connect. Did you end up using the 10240 ADK to get past the driver signing issue?
I found that mapping network drives over the WiFi interface didn't work until I waited the 60 seconds AFTER the WiFi connect command. How long did you wait?
Also, did you try using IP addresses instead of computer names in the net use command?