MVP Tool - CUSTOM ATI WINPE BUILDER
CURRENT VERSION:
18.6 Advanced (01/22/2019)
How To Tutorial: MVP Tool - CUSTOM ATI WINPE BUILDER
README----Basic Vs. Advanced MVP_ATIPEBuilder
Changelog - Version 18.6 is fully compatible with all versions of Acronis 2019. It is backward compatible with Acronis 2018, 2017 and the most current version of 2016. It is also fully compatible with all publicly released versions of Windows Operating System 10, 8.1, 8 and 7. It also supports the incorporation of multiple Acronis products into the same WinPE media (True Image, Universal Restore, Disk Director, Acronis Revive, Snap Deploy and Backup)!
Due to the larger size of the Advanced version, (about 140Mb), we are unable to post it directly in the forums so everything has been moved to the Acronis MVP Google Drive.
Basic is no longer supported and considered deprecated since the release of Acronis True Image Home 2018. Please use the advanced mode; trust us, you’ll like it and it's every bit as easy to use.
Advanced - just as easy to use to build your WinPE rescue media as the old Basic version! It does everything that Basic did, but also includes options for Bitlocker support, ISCSI support, a web browser, file explorer, explorer shell, 7zip association, PDF association, custom tools, screen resizing and more! As of 18.2 (and newer), additional Acronis products can be added to the same WinPE rescue media if they are already installed on the system where the media is being created (True Image, Universal Restore, Disk Director, Acronis Revive, Snap Deploy and Backup).
WHAT IS THIS?
MVP ATIPEBuilder is essentially a batch script tool designed by MVP's: Bobbo_3C0X1 and Mustang, with collaboration from Steve Smith and Enchantech and testing by other MVP's.
This tool can be run on any 32-bit or 64-bit system that is using Windows Operating System 7, 8, 8.1 or 10, as longs as there are compatible versions of Acronis products already installed on it.
This tool does NOT work with legacy versions of Acronis True Image Home (Early versions of 2016 and earlier) and there are no MVP plans to provide support for them, due to variations in the Acronis provided WinPE content. Additionally, newer Acronis products are designed to have better compatibility with newer hardware technologies and current Operating Systems and we believe that using more current versions of Acronis products is beneficial for users looking to migrate to these newer technologies.
Anyone with a Windows 7, or newer, Windows OS and has a current version of a supported Acronis product, may use this tool to build CUSTOM 32-bit or 64-bit Acronis Bootable Rescue Media. This will be especially useful for those of you that have 32-bit only UEFI systems or the OEM manufacturer has set the SATA mode to RAID in the BIOS and it cannot be changed. This tool also supports automatic driver injection in both the 32-bit and 64-bit media creation process, with support already embedded for the latest PCIE NVME hard drives and Intel Rapid Storage Technology (IRST).
Whether using this tool to build 32-bit or 64-bit customized WinPE Acronis Bootable Rescue Media, the resulting media can also be booted in legacy mode for ANY system (32-bit or 64-bit), where the bios supports legacy/CSM booting and/or UEFI mode for ANY system where the bios supports UEFI booting.
WHY DO WE NEED IT?
If you have a 32-bit only UEFI tablet or laptop that came with an eMMC flash hard drive, or any system that came with a PCIE NVME hard drive, you may have found that 32-bit/64-bit Linux Acronis Bootable Rescue Media and/or the default 64-bit WinPE Acronis Bootable Rescue Media won't detect your hard drive. This is because the manufacturer has set the bios SATA mode to RAID and/or:
01) Prior to the release of Acronis True Image Home 2018, the default version of the Acronis Bootable Rescue Media was based on Linux and typically did not have RAID controller drivers such as Intel Rapid Storage Technology (IRST), which are needed to detect newer hard drives when the SATA mode in the bios has been set to RAID by the manufacturer. Although Acronis True Image Home 2018 (and newer) has options to build rescue media with WinPE or WinRE, and also includes driver injection now, it still has some limitations compared to this tool.
02) Driver injection is now built into the MVP tool and additional drivers can seamlessly be added "on-the-fly". By default, we already provide the latest Intel Rapid Storage Technology (IRST) drivers (if you choose to run the driver injection option) so that anyone using the latest NVME PCIE hard drives can create media that will support it out of the box - even if the manufacturer has set the SATA mode to RAID in the bios. (Note: if your system has a custom RAID controller such as LSI or Rocket-RAID, you may still need to add those drivers into the driver folder before running the tool).
HOW DOES IT WORK?
What we've done with this tool is simply emulated the Acronis default media builder process, but enhanced it. We take full advantage of the provided 32-bit and 64-bit WinPE tools that Acronis provides. We have added a section for CUSTOM / AUTOMATIC driver injection too! The entire process is handled with Microsoft DISM commands from the WinPE ADK packages so that we can include the ability to add custom drivers, copy drivers from the local system into the build, include Bitlocker support, ISCSI support and native OS language support. Furthermore, instead of limiting the WinPE media to just True Image, it will search the system for all installed Acronis products such as True Image, Universal Restore, Acronis Revive, Snap Deploy, Backup, and include them in the recovery media.
CAVEATS / CONSIDERATIONS / RECOMMENDATIONS
01) This is not an official Acronis tool, but they like it a lot and have been supporting development. It has even been integrated into the application for easy access. However, we recommend checking the MVP Google Drive to ensure you are getting the latest version. We've tested it thoroughly and feel that it is not only useful, but safe to use. If you do have issues, please be sure to post here in the forums for assistance.
02) The tool should always be run with Administrative Privileges to ensure that the script has the proper access for making changes where necessary. We've taken precautions to ensure that the script is always run with admin access (even if you forget). All current advanced versions are now an EXE that forces admin access before launching. However, please still try to always right-click and "run as administrator" whenever possible - just to be sure though.
03) On some machines, the tool may flag as an untrusted file under Windows Smart Screen or may even flag as malware. Working with Acronis, we are now releasing "signed" versions of the tool to alleviate this issue (18.4 and newer), but different antivirus programs may behave differently. This tool is not malicious and contains no malware. You can safely run it without fear, but please do so only if you are comfortable doing so.
I just uploaded a modified version with a slightly fixed folder structure (as I noticed the names didn't match exactly).
Unfortunately, different .zip programs behave differently so we've opted to keep a folder within the .zip to ensure that all of the embedded contents don't extract as individual files/folders on someone's computer. That can end up being "messy" if extracting to a folder with other content already in it (like the root of C: drive" and may confuse some people too.
If you use 7zip and right-click on the .zip file, navigate to the 7Zip menu item in Windows Explorer and then select "extract files", you'll end up with the double folder structure that you're experiencing. The same behavior occurs when using the Windows 10 default tool if you right-click the .zip file and then select the "extract all" option.
To end up with a single folder structure, instead...
If you use 7zip, right-click and select "open archive" and it will open to the main folder automatically and then you can just copy and paste the folder out of it and it will only have the one folder name structure. The same behavior will occur when you use the Windows 10 default tool and right-click and select "open", which will then allow you to just copy and paste the folder with the single folder structure too.
Alternatively, feel free to cut the contents out of the second folder and move them up a level and then delete the empty folder. The name of the folder wont' matter since the script is coded to run in whatever the "current folder" is that the application is launched from. As long as everything is in one folder, regardless of the name, it should operate just fine.
Cheers!
Hello,
I'm not sure if this is where I should post this, but after I entered my USB Flash drive letter (E:) so that I can create a bootable USB Flash Drive, the utility failed and was unable to FORMAT my flash drive (64GB KINGSTON). How can I create a bootable flash drive with the WinPE that I just created?
Thank you.
Ron
Hi Ron,
Make sure you are just typing
E:
and nothing else when prompted (assuming E: is indeed the correct drive).
Also, It is typically recommended that you use a 32Gb or smaller (down to 2Gb) flash drive. Some systems cannot boot a flash drive that is larger.
You could try the 64Gb drive again as a test, but I'd recommend doing a full format in Windows first (not just a quick one) to ensure it is completely wiped with no hidden partitions (Windows can only see one on USB flash drives but there could be others from a previous tool like Rufus or some other WinPE builder). To do this, just locate the drive in Windows file explorer, right click and "format". Then unselect the quick option and go have a beer and watch a show as the full format may take awhile.
It may be easier to grab a smaller thumb drive if you have one available to be on the safe side though. Please see this Acronis KB article: https://kb.acronis.com/content/58108
We've added a how-to video tutorial to the stickies now - for those wanting to know how it works or what it does, please check it out.
This tool is so nice! Thanks alot for making it...
Im using a version om summer 2018. Is there any reason for me to make a new USB boot stick with the newest MVP tool?
Best regards
Peter, if the version you have is working, it should be fine.
Mustang made some of the code better for creating A WinRE version and the ability to add in Acronis Revive and a few other under the hood things during the build process, but the final product should be pretty similar to what you already have now.
Check out the change log though. Personally, I always build a new version when Acronis releases an update to True image and then use the latest MVP build then. But that's more so I can have the latest Acronis application (although sometimes it fixes some bugs but introduces new ones - usually nothing major though).
Just wanted to note that the current version of the tool is working with the 2020 beta without issue.
Disk formatting error during build.
I believe this has been discussed before, but not for a long time, and I don't remember a good solution.
For some previously unused USB flash memory devices, the Builder fails in the Format step. (My error: "ERROR: Failed to format "D:"; DiskPart errorlevel -2147024809")
Using the Windows Format function - even doing a full format - does not fix the problem. Rebuilding the device using RMPrepUSB (and probably other utilities) does fix the problem so I assume there is some partitioning problem involved.
It would be nice if this problem could be detected early in the build process rather than at the very end. Or it would be nice if the Build program could detect the error in the Format step and give a retry option. (Without knowing the internals of the program, I have no idea if this is possible.) If not, maybe a "Read Me" should describe how to determine if a device is usable.
I'm not sure it's possible. The build is just a dism command to take the created boot.wim and burn it disk using the tools available in ADK. Even if we ran the format first, it would probably still fail to write later since the disk command formats the drive and writes the data right after. I'll see if there are any forums with a potential recommendation to consider.
Do you know what the Format function is that gets invoked from within DISM and whether it can be invoked other than from within DISM? It is obviously difference from the standard Windows Format. If we could invoke it prior to running the builder we would know ahead of time that the USB device was unacceptable.
Patrick O'Keefe wrote:Do you know what the Format function is that gets invoked from within DISM and whether it can be invoked other than from within DISM? It is obviously difference from the standard Windows Format. If we could invoke it prior to running the builder we would know ahead of time that the USB device was unacceptable.
example:
Makewinpemedia /ufd C:\winpe_amd64 F:
To my knowledge, the format is built into the command. The only suggestion, might be to use diskpart to format the drive manually first (could be scripted, but would still be an extra step) and then the command would format again and try to build the media.
If the rescue media builder in the MVP tool or the default Acronis media are failing... if you manually format the drive in Windows first, does it still fail in the media builder afterwards?
Bobbo_3C0X1 wrote:If the rescue media builder in the MVP tool or the default Acronis media are failing... if you manually format the drive in Windows first, does it still fail in the media builder afterwards?
I've tried the standard Windows Format - both quick and long versions. The formats run but do not fix the problem. I haven't tried Diskpart; maybe that will work.
OK, yeah, try
Diskpart /clean
on the drive and after that you can initialize it and quick format in Windows disk management or you manually do this with diskpart, but it's more commands. It's a lot easier to just use disk management after running the diskpart /clean command.
MakeWinPEMedia.cmd is a command script written by Microsoft. You will find it in the ADK and can right click on it and select "edit" to read the script. In the past I introduced a modification to help with a similar problem when a used reported a fix. I can't remember exactly what the situation was but I think it had to do with a timing issue. There may be a way to fix the current problem you are experiencing. Do some googling to see if anybody has reported a recent modification to MakeWinPEMedia.cmd to fix the problem.
Also try using the MakeWinPEMedia command straight from a 1903 ADK to see if it works on one of these drives. Maybe Microsoft has modified the latest version of the command. Although I doubt it. The don't seem to be handling things very well these days. Let me know what you find.
Bobbo and Mark, I haven't yet done what you have suggested, but I did compare and unusable drive to one that has been reformatted with RMPrepUSB. (Where "unusable" means unusable for creating a bootable drive. It is still usable for most Windows activity.)
These are both 15GB devices. The unusable one has a 15GB partition at offset 0. This partition cannot be selected in Diskpart.
The usable device has a 14GB partition at offset 1024KB. The partition is selectable.
I know very little about drive formats but I'm pretty sure there is supposed to be a file allocation table, and it looks like the unusable drive doesn't have room for one.
Patrick, did the unusable ones come that way? Or is it the result of rescue media creation? I'm assuming they came that way since they should be usable with the rescue media builders after they've been formatted with a different tool. I'm really surprised that diskpart isn't even able to clear it. But if windows can't, then the dism creation won't either. Good find. This might explain issues for others... And maybe even why some people have to always reboot to clone... If there is something similar going on with other new disks.
This was a set of 10 Enfain "16GB" USB flash memory sticks, never used, ordered through Amazon. Several years ago I got another set - different name but probably made by the same Chinese manufacturer - that had the same problem.
I used Diskpart to look at the devices but haven't yet tried it to fix them. (Every device I fix is one I lose for diagnosis.) I'll give it a try. I don't know if I need to do a "Clean" or if I can get away with just doing a "Create Primary Partition". I'll try without "Clean" first.
============ several minutes pass ==============
I was able to successfully fix the device with Diskpart. I had to do Clean first, but was then able to create the primary partition and activate it. I was then able to use the device as target for the ATI Rescue Media Builder. (That was an easier test than launching the MVP builder.)
Mustang wrote:MakeWinPEMedia.cmd is a command script written by Microsoft. You will find it in the ADK and can right click on it and select "edit" to read the script.
I looked at that and immediately got lost. Is %TMP%\UFDFormatDiskpartScript.txt something created (by the MVP Builder tool, for instance) prior to invoking MakeWinPEMedia? Not knowing the content of the script makes for a lot of guess work. I know that I can get around the problem of the Builder failure by manually invoking Diskpart and doing
- clean
- create partition primary
- select partition 1
- active
so I assume that does not get done by the MVP Builder's use of MakeWinPEMedia. Is that correct or am I way off base?
I looked at MakeWinPEMedia.cmd from the 1903 ADK. I see the line with:
%TMP%\UFDFormatDiskpartScript.txt
That line is creating a blank text file called UFDFormatDiskpartScript.txt in the %TMP% folder and assigning it to the variable DISKPARTSCRIPT. Later in the MakeWinPEMedia.cmd script they add lines to the txt file by means of echo commands to the DISKPARTSCRIPT variable. So Microsoft creates the script as MakeWinPEMedia.cmd is executed.
Now can you answer a question for me? Can you take a new USB drive with this problem and execute MakeWinPEMedia.cmd from the 1903 ADK manually and get it to work? You need to go to the Windows Start Menu/Windows Kits/Deployment and Imaging Tools Environment and run it as Admin. Then enter these lines in the command window:
copype amd64 C:\winpe_amd64
MakeWinPEMedia /UFD C:\winpe_amd64 F:
Where F: is the drive letter of your USB drive.
After you are done remember to delete the folder at C:\winpe_amd64.
If it works, I'll look into making changes in the MVPTool to incorporate the 1903 MakeWinPEMedia.cmd. If it doesn't work, there's nothing I can do for you. I'm NOT going to put the diskpart lines you show above in the MVPTool. IT'S WAY TOO DANGEROUS. IF SOMEONE ENTERS THE WRONG DRIVE LETTER THERE WILL BE HELL TO PAY!
I suspect it will not work because there is something odd about your USB drives. Perhaps something like there is a hidden partition before the partition that gets the drive letter.
Same error as from the MVP Builder:
ERROR: Failed to format "D:"; DiskPart errorlevel -2147024809.
This is after what looks like a bunch of activity to the USB device (based on its LED blinking).
This was the fix we added in the MVP tool. Doesn't sound like it applies here and is likely more related to some custom partitioning on these drives by the manufacturer.
Patrick,
Thanks for testing. There's nothing we can do for those drives. You'll need to continue to fix them manually. Are these USB 2.0 drives or am I missing something on Amazon? I'd buy one to test it if it was USB 3.0, but I would not want any more USB 2.0 drives. They take an eternity to boot.
If you want to send me one, I'll try to figure out why it doesn't work. Have you tried backing up one of the drives as it comes from the factory so you can restore it after you make changes. That way you can use just one drive for multiple tests.
These are USB 2.0. I wanted a bunch of cheap devices to test with so didn't mind 2.0. Next time I'll order a small bunch of USB 3.0 devices. Maybe they are formatted better.
Patrick O'Keefe wrote:Same error as from the MVP Builder:
ERROR: Failed to format "D:"; DiskPart errorlevel -2147024809.This is after what looks like a bunch of activity to the USB device (based on its LED blinking).
I got that when trying to put the MVP Builder on a 250GB Samsung SSD.
Acronis build worked fine on the SSD. MVP Builder went on to a CD.
I did get MVP onto a USB when I went for a simple 32 GB USB3 drive.
Michael Kenward wrote:Patrick O'Keefe wrote:Same error as from the MVP Builder:
ERROR: Failed to format "D:"; DiskPart errorlevel -2147024809.This is after what looks like a bunch of activity to the USB device (based on its LED blinking).
I got that when trying to put the MVP Builder on a 250GB Samsung SSD.
Acronis build worked fine on the SSD. MVP Builder went on to a CD.
I did get MVP onto a USB when I went for a simple 32 GB USB3 drive.
The best we can suggest is to clean all partitions on the usbs first (diskpart or a free third party tool like minitool partition wizard). This appears to be related to something about the existing disk alignment that the ADK (dism commands from the Microsoft makepemedia.cmd) is unable to handle in its own formatting and writing process. I've used the MVP tool and Acronis media builder and survival kit builder on various flash drives from 64-128GB as well as external Hard drives with larger capacities that are connected with USB to SATA adapters. Most of my disks have been diskpart ) cleaned or partitioned with Minitool at some earlier point in time though and I haven't run into an issue were they could not be written too.
I recently read in a forum posting that there is an instructional video about this tool that states that the tool should be ubzipped into the root directory of a drive. I never watched the video so missed the bit about unpacking to the root of a drive. I don't remember how long ago I built this directory structure, but I installed mine far from Root:
D:\Acronis Utilities\ATI_PE_Builder\Advanced\MVP_ATIPEBuilder_v182
where "MVP_ATIPEBuilder_vnnn" has gone through several iterations. I've never had any obvious problems. What is behind this Root suggestion and what problem am I eventually gong to have by ignoring it?
It doesn't have to be root - mostly, just a folder not in the user profile, or in a specific Windows System or program folder or anywhere with unique permissions. Putting it on the root of a drive, is just the easiest way to alleviate having to identify other potential folders where issues could arise.
I think that the reason it also doesn't like the user profile is the script variables (which call on "run from this folder - wherever it is launched) probably don't like the default Microsoft Windows junctions for things like %appdata%, My Documents (MyDocs), etc.
I'm not sure if this is where I should post this, but after I entered my USB Flash drive letter (E:) so that I can create a bootable USB Flash Drive, the utility failed and was unable to FORMAT my flash drive (64GB KINGSTON). How can I create a bootable flash drive with the WinPE that I just created?
64GB is too large to use for bootable media - this is a Microsoft restriction that USB boot drives be 32GB or less in size.
See KB 58108: Acronis products: using USB sticks with more than 32GB capacity
It depends on the OS. Windows 10 1803 and newer support larger USB drives and flash drive partitioning. However, many bios themselves may not support booting on removable storage that is larger than 32GB. Best to start with a smaller drive to test with first.
Hi, this tool is so awesome! Thanks a lot for making it...I probably should make a new USB boot stick with the newest MVP tool for correct working
Hi guys,
I'm trying to restore an Acronis image into my newly purchased Dell laptop XPS 15 (2019) 7590. I am running the latest MVP Acronis WinPE Media Builder (v 18.6) to inject the RAID drivers as the SSD hard drive ain't visible otherwise.
The process with MVP works well until I am prompted to create the USB flash drive. I have an 8GB USB flash drive which I recently formatted and used to create the normal Acronis bootable USB without issues. When I select the drive in the options and type in the pertaining letter drive (D: in this case) the formatting process begins and then I get the following error:
ERROR: Failed to format "D:"; Diskpart errorlevel - 2147024809
Any ideas what to do to correct this and get the USB bootable drive properly created?
Thanks in advance
Joel
Can the current version of be used to build USB Rescue Media for W10 Version 1909?
WIth newest ADK/PE of course.
Yes, it works fine with Win 10 #1909 using either WinRE or the current ADK for the PE files.
Hi,
Latest build of Acronis True Image installed, ADK and using latest MVP. When I build PE Recovery Media from ATI, both 64 and 32 bit ISO images work fine. When I build MVP Recovery Media, the 64 bit ISO works great, however I'm getting the attached error with the 32 bit MVP ISO. Any ideas why?
There is a compatibility problem between True Image and the version of snapman.sys and snapapi.dll on the media. What Acronis products do you have installed on your system?
Please post the log from the 32 bit build. That may tell the story. We may need to use dism.exe to mount the boot.wim file from the 32 bit media to determine exactly what version of the snapman driver is present because the properties dialog doesn't work in WinPE.
Hi,
Thanks for the response. I have all trial versions of Acronis products (listed in the attached logs) as testing MVP Tool (last time I played around with PE was Bart's PE, so you know how long ago that was). Have attached logs from a working 64 bit build and a 32 bit build with the errors. All of this is built and tested in VMWare.
Please don't spend too much time with this as I'm most probably going to use the 64 bit build only. I was just curious why the error as ATI 32 bit PE works fine.
Thanks for the logs. The problem is clear. With the current 32 bit versions True image and Snap Deploy can't work together in the same PE. With older versions they could. This is an Acronis problem we can't fix. They need to redesign the snapman driver.
You can get True Image to work by hiding the Snap Deploy WinPE files while building with the MVP Tool. Navigate to C:\Program Files (x86)\Acronis\SnapDeployConsole\PE and rename WinPE32.zip to XWinPE32.zip. The MVP Tool will tell you that it is adding Snap Deploy, but it won't be able to find the 32 bit files. True Image will work.
You're a star, thanks.
I think the MVP Custom WinPE recovery medium is one of the most useful recovery tools I've run into. Having wireless support is a lifesaver for me. I don't do recoveries over WiFi (except to test the process), but all my configuration documentation is on a NAS. Even when I'm recovering a laptop from a portable drive I often want access to that configuration data. Having wireless access beats dragging Ethernet cables around.
HOWEVER, ...
A peculiarity in the way the WinPE recovery medium handles wireless configuration data makes redefinition a pain. And I just experienced that pain because I needed to add two new SSIDs.
I spent ages trying to get the following WiFi.cmd to work:
netsh wlan add profile filename="Profiles\Okeefeler0000.xml" user=all
netsh wlan add profile filename="Profiles\Okeefeler0001.xml" user=all
netsh wlan add profile filename="Profiles\Okeefeler0002.xml" user=all
netsh wlan add profile filename="Profiles\Okeefeler0003.xml" user=all
ping -n 10 127.0.0.1 > nul
netsh wlan set profileorder name="Okeefeler0000" interface="Wi-Fi" priority=2
netsh wlan set profileorder name="Okeefeler0001" interface="Wi-Fi" priority=3
netsh wlan set profileorder name="Okeefeler0002" interface="Wi-Fi" priority=1
netsh wlan set profileorder name="Okeefeler0003" interface="Wi-Fi" priority=4
It would work fine if the WiFi folder was copied into the Extra folder and manually executed from there, but would not work during the recovery medium's initialization. I would get 4 "file not found" kind of errors. I finally discovered that I had to include the full path names:
"X:\Program Files\WiFi\Profiles\Okeefeler0000.xml"
etc.
Apparently WiFi.cmd file is not executed by the initialization even thought (I think) the builder copies it into the recovery medium. (Maybe the .cmd file is interpreted by the initialization code?) But putting that full path name in the builder's WiFi.cmd means the command cannot be executed to check for syntax, etc - not unless I create a drive X: with a Program Files directory just for testing the WiFi.cmd.
Is there some reason the WiFi.cmd is not actually executed? And even if it is interpreted, is there a reason the absolute path names have to be included in the profile names? After all, the interpreter must know command it is interpreting and the corresponding Profiles directory live in X:\Program Files\WiFi\.
The full path is needed because the WiFi.cmd is executed from X:\Windows\System32. This is the normal way to execute commands at startup because the default path in WinPE is only X:\Windows;X:\Windows\System32.
I really know almost nothing of scripting so this may be a really stupid question, but ...
Could %~dp0% be used instead of X:\Program Files\WiFi\ ?
(I know I could try it, but continually rebuilding and booting a recovery medium to do the testing gets tedious.)
The commands as you've written them should work if you copy the entire Profiles folder to X:\Windows\System32.
Try this by adding these lines to the beginning of your script:
md X:\Windows\System32\Profiles
copy "X:\Program Files\WiFi\Profiles\*.*" X:\Windows\System32\Profiles\*.*
My comments were based on a major misunderstanding. I had assumed that the AddWirelessProfile.cmd in the recovery medium's X:\Program Files\WiFi\ was a copy of the WiFi.cmd that we edit in the builder's WiFi folder. I see that it isn't.
I could do the process you suggest, but it is easier to just copy the builder's WiFi folder into Extra and manually execute WiFi.cmd.
Just out of curiosity, what is done with WiFi.cmd? The information in it obviously makes it into the recovery system somewhere but the command and the profiles obviously get put in separate places.
As I mentioned before, WiFi.cmd is installed in X:\Windows\System32. It is run by Goodies.bat which is also installed in X:\Windows\System32 and run at startup.
If you want to execute WiFi.cmd from a modified copy in the Extra folder, you will need to change the directory in the command window to where the WiFi.cmd you want executed lives otherwise the command window prompt will be on X:\Windows\System32 and you will get that version instead of the version you want.
cd "X:\Program Files\Extra\WiFi"
I found a different way.
In the Builder folder Extra\x64\ I've created folders WiFi and WiFi\Profiles. In the WiFi\Profiles folder I've put my exported profile .xml files (surprise, surprise). In WiFi I've put WiFi.cmd containing:
@echo off
echo.
netsh wlan add profile filename="%~dp0%Profiles\Okeefeler0000.xml" user=all
netsh wlan add profile filename="%~dp0%Profiles\Okeefeler0001.xml" user=all
netsh wlan add profile filename="%~dp0%Profiles\Okeefeler0002.xml" user=all
netsh wlan add profile filename="%~dp0%Profiles\Okeefeler0003.xml" user=all
ping -n 10 127.0.0.1 > nul
netsh wlan set profileorder name="Okeefeler0000" interface="Wi-Fi" priority=4
netsh wlan set profileorder name="Okeefeler0001" interface="Wi-Fi" priority=2
netsh wlan set profileorder name="Okeefeler0002" interface="Wi-Fi" priority=3
netsh wlan set profileorder name="Okeefeler0003" interface="Wi-Fi" priority=1
echo.
pause
echo.
exit
In the builder file WiFi.cmd I've put
@echo off
REM --> Create subfolders \WiFi\ and \WiFi\Profiles\ in the Builder's \Extra\x64\ folder.
REM --> Copy wireless profiles into Extra\x64\WiFi\Profiles
REM --> Put the associated NETSH WLAN commands in \Extra\x64\WiFi\WiFi.cmd"X:\Program Files\Extra\WiFi\WiFi.cmd"
Echo To make changes to WiFi config, edit and run X:\Program Files\Extra\WiFi\WiFi.cmdecho.
pause
echo.
exit
The WiFi.cmd in \Extra\x64\ works whether executed when executed under Windows or executed from X:\Program Files\Extra during Recovery Medium initialization. I'm happy.
I'm glad to hear it is working for you.
In your WiFi readme, you say I need W10 ADK 1511 or earlier to have wifi support. Where can I download version 1511 of ADK? It appears that the MS site's available downloads do NOT go back that far.
We were able to fix the problem with ADK's above 1511. You can use the ADK that matches your version of Windows. If you are using Windows 10 1909, you can use the latest ADK version 1903. WinRE in 1909 is version 1903. This will give you the version match needed to get WiFi support.