MVP Tool - CUSTOM ATI WINPE BUILDER
CURRENT VERSION:
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.
Basic now includes automated DRIVER injection for custom 32-bit OR 64-bit WinPE builds.
Advanced - just as easy to use to build your WinPE rescue media as the basic! It does everything that Basic does and also includes Bitlocker support, ISCSI support, a web browser, file explorer, an explorer shell, 7zip association, PDF associations, tools, logging, customizations and more !!!! As of version 9.6, the build process has been completely re-vampped and no longer requires the Acronis media builder. It is also possible to use WinRE to incorporate Wi-Fi support now. And, it will automatically include Universal Restore and/or Disk Director 12 if they are found on the local machine.
WHAT IS THIS ?
MVP ATIPEBuilder is a .bat 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 7, 8, 8.1 or 10, as longs as there is a compatible version of Acronis True Image Home (2017/2016) installed on it already, and a pre-existing installation of the Windows ADK (5.x, 6.x or 10.x).
This tool does NOT work with legacy versions of Acronis True Image Home (2015 and earlier) and there are no MVP plans to provide support for them, due to varations 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 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, that has a current version of Acronis 2016 or newer, 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. As of version 5.7, this tool supports automatic driver injection in both the 32-bit and 64-bit media creation process.
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.
README----Basic Vs. Advanced MVP_ATIPEBuilder
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 the current 32-bit/64-bit Linux Acronis Bootable Rescue Media and/or the defautl 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) The current and default version of the Acronis Bootable Resuce Media is based on Linux and usually does 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.
02) The current Acronis Bootable Rescue Media Builder only creates 64-bit WinPE. This will not boot on a 32-bit only UEFI system.
03) Driver injection is now built into the tool and additional drivers can seemlessly be added "on-the-fly". By default, we 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 (Acronis currently only builds 64-bit WinPE rescue media in the default media builder). We have added a section for CUSTOM / AUTOMATIC driver injection too! As of Advanced build 9.5 and newer, the entire process is handled with Microsoft DISM commands from the WinPE ADK packages so that we can includue the ability to add custom drivers, copy drivers from the local system into the bild, include Bitlocker support, ISCSI support and native OS language support. Furthermore, instead of limiting the WinPE media to just True Image Home, it will search the system for Universal Restore and Disk Director 12 and include them if they are already installed.
CAVEATS / CONSIDERATIONS / RECOMMENDATIONS
01) This is not an official Acronis tool, but they like it a lot. 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). 1) All current advnaced versions are now an EXE that forces admin access before launching. 2) The older version use a shortcut to require admin privileges by default. 3) The older version scripts will prompt for UAC access if it is not launched with the shortcut and detects it has been run with a regular user account. 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. This is because it includes A43 file explorer, 7zip and is a .bat script downloaded from the Internet without a digital signature. 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.
04) If you have not already installed the Windows ADK to create your 32-bit or 64-bit WinPE Acronis Bootable Rescue Media, please do so before running the tool, as it needs to check for existing file paths to function correctly. If the file paths don't exist, the script will terminate automatically and you will not be able to continue with the custom WinPE rescue media creation.
05) As of 9.5 advanced and newer, the tool is strictly self-sufficeint and no longer needs the Acronis media builder. However, it goes through the same process of checking for licenses to ensure proper activation in the WinPE. Additionally, it will look for other installed Acronis products (Universal Restore and/or Disk Director 12) and include those too.
If your customized WinPE Acronis Bootable Rescue Media boots successfully, but still does not detect your hard drive, you will need to re-run the tool and make sure to have the drivers ready to include them in the automated driver injection process.
Alternatively, you can still use the DISMGUI tool and instructions in this thread to inject drivers manually, after you've created WinPE Acronis Bootable Rescue Media.
CURRENT VERSION:
6.8 - Released !!!! (11/23/2016)
Due to larger size, (about 50Mb), we are unable to post it directly in the forums so it is available from the Acronis MVP Google Drive.
Now includes automated DRIVER injection for custom 32-bit OR 64-bit WinPE builds, a web browser, file explorer and more !!!!
New Release!!!
CURRENT VERSION:
7.0 Advanced (11/26/2016)
5.9 Basic (11/26/2016)
README----Basic Vs. Advanced MVP_ATIPEBuilder
Due to larger size, (about 50Mb), we are unable to post it directly in the forums so it is available from the Acronis MVP Google Drive.
Both versions include automated DRIVER injection for custom 32-bit OR 64-bit WinPE builds.
Advanced version also includes , a web browser, file explorer and more !!!!
New Release!!!
CURRENT VERSION:
7.2 Advanced 12/7/2016
Does everything that Basic does and also includes Bitlocker support, ISCSI support, a web browser, file explorer, shell, 7zip association, PDF associations, tools, customizations and more.
README----Basic Vs. Advanced MVP_ATIPEBuilder
Due to the larger size of the Advanced version, (about 50Mb), we are unable to post it directly in the forums so everything has been moved to the Acronis MVP Google Drive
7.3 advanced released - 12/12/2016
Better launchbar icons (fixed a bug where the True Image icon was "generic" when built with 2016 versions, updated explorer++ icon), cleaner script for source variables, brought back irfanview in addition to the default pdf viewer (Sumatra) per request.
How do I add Chrome Portable to the available apps?
I'm not really familiar with WinPE setup. I gather the actual OS
is in sources/boot.wim but not how to add additional software?
Ideally I'd like the launcher bar to reflect the added available
chrome portable too.
The nice thing about "portable" apps is that they're just that - portable. Put them on your thumb drive with the portable apps .exe and navigate to the EXE on the root of the USB to to launch portable apps.
However, I have not had much luck Chrome Portable in WinPE either (other than with winpese which is a lot more than winpe). You get lucky with some portable apps, but not all work in winpe. Try copying them to your usb drive and launching them from the explorer++ or A43 file explorer to see if they work - Chrome doesn't (at least not for me.).
If it does, and/or you want to customize your winpe more, you can mount the boot.wim with DISMGUI. YOu can then copy files/folders as you see fit into it and commit the changes to the boot.wim. Shortcuts aren't as easy since you need to make them point to X:\ProgramFiles (PE mounts as X).
The launchbar we are using is a portabler app itself. It will not allow you to just put apps there without modifying a config file. However, it will find shortcuts in the program files directory and can be launched from the startbutton.
9.6 Advanced is released - entirely new build process - give it a whirl and let us know what you think - now that the retooling is complete, we hope to be able to provide additional updates as needed on a more regular basis.
CURRENT VERSION:
9.6 Advanced (03/16/2017)
5.9 Basic (11/26/2016)
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
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.
Hi,
I am trying to rescue some files from a Surface Book, using this nice MVP tool, but I can't see the internal drive. The reason I am using this tool is of a crashing Surface Book in Win10 64 bit after a Windows Update. At the time I bought this laptop (last year in April), I was not using Acronis, so I don't have any recent backups too. I created a 64 bit usb stick and tried to add as much as drivers I could find for the internal drive (a MvE?) which I downloaded at the support site of Microsoft Surface Book, but that was not succesfull. Anyone who can direct me to the correct set of drivers to inject into the WinPe stick?
Best regards,
Ton.
Ton, welcome to these user forums.
With your Surface Book you should be able to just create the Advanced version of the MVP Tool and just include the default supplied drivers as these should be sufficient for your NVMe internal drive which is most likely to be running in RAID mode. When you have worked your way through the script panels and the Acronis Rescue Media Builder tool is launched, make sure that you select to build the second option for the Windows PE Rescue Media and not take the default top option which builds the Linux Rescue Media.
Quick note. The latest advanced Mvp builder does not launch the default Acronis media builder now, so we don't have to worry about users accidentally still picking the default Linux media. It will only build WinPE.
The key to getting the surface book nvme drive to be seen is to select YES when it asks about adding custom drivers. We have provided the Intel rapid storage technology (IRST) drivers needed for the nvme drives in SATA mode RAID configuration (this is the new default for most OEMs using NVME PCIE hard drives now) in the custom driver folder to be injected. You must say yes to add the custom drivers in that s cation though. That should be all you need.
Hi Steve,
I appreciate your quick response! i already did use the correct build of this tool, and now again with your recommendation regarding the injection off the standard provided irst drivers. I know get 3 errors, all saying that the version of the running os differs from the target os, and so no drivers will be copied. Here is what I did in the proces of making the winpe usb stick;
option 2. winpe 64 bit
option 2 no network
option 1 yes irst for raid
errors! as stated
option 2 no iscsi
option 2 no bitlocker
option 2 no prompt
a default resolution
option 2 do not create usb, since the errors that is no use.
My operating system is Windows 7 Professional 64 bit.
Any suggestions on solving this?
Hi Bobo,
I posted this answer to Steve:
Hi Steve,
I appreciate your quick response! i already did use the correct build of this tool, and now again with your recommendation regarding the injection off the standard provided irst drivers. I know get 3 errors, all saying that the version of the running os differs from the target os, and so no drivers will be copied. Here is what I did in the proces of making the winpe usb stick;
option 2. winpe 64 bit
option 2 no network
option 1 yes irst for raid
errors! as stated
option 2 no iscsi
option 2 no bitlocker
option 2 no prompt
a default resolution
option 2 do not create usb, since the errors that is no use.
My operating system is Windows 7 Professional 64 bit.
Any suggestions on solving this?
regards, Ton.
Ton,
1. What version of the Windows ADK have you installed? You can see this by looking at Programs and Features in Windows.
2. Did you see the option to include drivers from your Windows system? This option would have come after the mapping a network drive option and before the add custom drivers for IRST and RAID option.
Hi Mustang,
Thank you for joining my issue.
1. I have version 10.1.10586.0 of WADK.
2. no, I can't remember seeing that option.
Best,
Ton.
Ton,
Would you please attach the last log file in the Logs folder from the Tool so I can see what is says.
Hi Mustang,
here is the log.
Win 7 drivers from the system won't fit in the win 10 adk so local system drivers option is disabled in this situation.
However custom drivers should still be an option.
I think based on this, I'd like to change the custom drivers to go to the log instead of on screen so we can see which ones failed if those are as well.
well need a screenshot of the errors for injection for now.
Hi Bobbo_3C0x1,
In the meanwhile I created a fresh W10 pc and installed WADK, Acronis with all tools and off course the MVP tool.
I started a new build for a winpe-usb stick and now I am getting different screens, and I do see the drivers injected nicely.
I will attach that log here as well. i tried top boot from this new stick, but now I am not able to boot from it. Is it possible that the uefi of a Surface book can't deal with 64-bits bootdevices? In the Boot Configuration I select the usb as only device to boot from. other options are Windows Boot Manager, Internal Storage and PXE Network..Can you enlighten me with this?
best,
Ton.
Hi,
just created a 32-bit usb, but again no succes with booting from that too..It looks like the uefi is very buggy in its options..
I did manage a boot from a usb stick, created with mvp-tool, but with that version i wasn't able to see the internal drive...
I am pretty sure I used a 64-bit version that time...
Anybody with experience in booting into a Surface Book?
Best,
Ton.
Hi,
just created a 32-bit usb, but again no succes with booting from that too..It looks like the uefi is very buggy in its options..
I did manage a boot from a usb stick, created with mvp-tool, but with that version i wasn't able to see the internal drive...
I am pretty sure I used a 64-bit version that time...
Anybody with experience in booting into a Surface Book?
Best,
Ton.
- It will have to be 64bit. Your bios requires 64bit (Surfacebook/surface Pro do not have a 32-bit bios - only 64-bit).
- Make sure you are uefi booting the recovery media if you have enabled CSM\legacy mode in the bios. This is critical that it's UEFI booted since you are using a PCIE NVME hard drive with a UEFI OS install on the Surface Book. https://www.microsoft.com/surface/en-us/support/warranty-service-and-recovery/how-to-use-the-bios-uefi-with-surface-book-and-surface-pro-4#bootWin10
- I don't have a surface book but did test it on a surface pro4 without issue.
- Make sure you're using the 64bit media builder and the latest advanced build.
- Make sure you use the custom driver injection option.
- Make sure you only have the default custom drivers we provide in the WinPE custom driver folder under 64bit.
- Make sure you've disabled secure boot in the bios of the surface book - just in case: https://www.onmsft.com/news/how-to-disable-secure-boot-on-surface-pro-devices and also this one: https://technet.microsoft.com/en-us/itpro/surface/manage-surface-uefi-settings
On the Security page you can also change the configuration of Secure Boot on your Surface device. Secure Boot technology prevents unauthorized boot code from booting on your Surface device, which protects against bootkit and rootkit-type malware infections. You can disable Secure Boot to allow your Surface device to boot third-party operating systems or bootable media. You can also configure Secure Boot to work with third-party certificates, as shown in Figure 3. Read more about Secure Boot in the TechNet Library.
Configure your Surface to start from a USB device
Once your USB drive is set up as a bootable drive with an appropriate operating system on it, you’ll need to set up your Surface to boot from this drive. This requires you to make changes in the UEFI. Here’s how to configure the boot order on Surface so the USB drive is the first option.
For info on using the UEFI on your Surface, see How do I use the BIOS/UEFI?
To make changes in the UEFI:
| Step 1: | Shut down your Surface. |
| Step 2: | Once Surface has turned off, press and hold the volume-up button. |
| Step 3: | With the volume-up button held down, press and release the power button. |
| Step 4: | Continue holding the volume-up button until the Surface or Windows logo no longer appears on the screen.
You should now see the Surface UEFI. Do one of the following:
|
| Step 5: | Select Configure Alternate System Boot Order. |
| Step 6: | Do one of the following:
|
| Step 7: | Select Exit Setup. |
| Step 8: | Select Yes to save the configuration and restart Surface. |
| Step 9: | Select Secure Boot Control. |
| Step 10: | Select Disable. This will allow Surface to search for an alternate device to boot from aside from your SSD.
Note This may affect the look of your Surface splash screen.
|
| Step 11: | Select Exit Setup. |
| Step 12: | Select Yes to save the configuration and restart Surface. |
| Step 13: | Select Boot configuration. |
| Step 14: | Select USB Storage and drag it to the top of the list. |
| Step 15: | Select Exit and then select Restart Now. |
Start Surface from a USB drive
Once you’ve followed the steps above to set up a USB drive as a bootable drive and configure the UEFI appropriately, you’re ready to start your Surface from your USB drive.
Notes
- Before starting your Surface from a USB drive, make sure you don’t have any other USB devices connected to your Surface, including USB mice, keyboards or other storage drives. Surface will try to boot from other USB devices after you change the UEFI configuration.
- If you don’t want to start your Surface from your USB drive, make sure the drive is not inserted in the USB port on your Surface when you start it.
Surface Studio, Surface Book, Surface Pro 4, Surface 3, or Surface Pro 3 with a configured boot order in UEFI
| Step 1: | Shut down your Surface. |
| Step 2: | Insert the bootable USB drive into the USB port on your Surface. |
| Step 3: | Press the power button to turn it on. |
| Step 4: | Follow the on-screen instructions to boot from your USB drive. |
Surface Studio, Surface Book, Surface Pro 4, or Surface Pro 3 without a configured boot order in UEFI
| Step 1: | Shut down your Surface. |
| Step 2: | Insert the bootable USB drive into the USB port on your Surface. |
| Step 3: | Press and hold the volume-down button on Surface. |
| Step 4: | While holding down the volume-down button, press and release the power button. |
| Step 5: | Follow the on-screen instructions to boot from your USB drive. |
- Make sure that you do a shutdown/p to force a full shutdown or it may be going into hibernation (fastboot) instead of shutting down. This will lock your hard drive if it is going into hibernation.
- Use adk 1607 instead of your current adk to build the WinPE. Ideally, you want the adk and the OS versions to match (although not necessary as long as you provide the correct drivers for the ADK being used - IRST drivers work for all versions of Windows 7, 8, 8.1 and 10. We are providing the latest from Intel HERE (Version: 15.2.0.1020 (Latest) Date: 10/20/2016).
Hi Bobbo_3C0X1,
OK. I managed to create a working usb stick and managed to boot the Book from it!
But again, I only see my usb-stick in True Image/Backup/My Disks...
I want to try another 2 things before I open the window and trow the Book out :-)
1. I downloaded the drivers and firmware from https://www.microsoft.com/en-us/download/confirmation.aspx?id=49497
(a zipfile, 845 mb) I see that there are drivers in the system section, SurfaceNVMExpressController. Is it an idea to inject these into a new winpe-stick to see if they are the working ones?
2. Since you succesfully created a bootstick, is it possible to post an iso or something, so I can create a stick from that one to test it on my Book?
I can arrange a share on my Stack-ip for your convenience where you can put it in, if neccessary..
Best,
Ton.
Hi,
just tested with a stick with the NVMe drivers mentioned in my previous post, no success...
Anyone suggestions?
Regards,
Ton.
P.S. the window is open...(nice weather in Amsterdam)
Ton,
Adding the driver you mention in reeply # 24 should solve the problem. Are you sure the driver was in the correct format to be added to WinPE? When you build with the MVP tool, you will see output on the screen as the custom drivers are added. Do you see a message that the SurfaceNVMExpressController driver was added successfully?
Please see my guide https://forum.acronis.com/forum/100770 for adding drivers. It tells you how to get the drivers from your system. Basically, you need to get the INF file for the driver and look at it to see what files it needs.
I'd also like to know how the SATA mode is set in the BIOS of the Surface Book. Is it set to AHCI or RAID? If it is set to RAID, you may have success by setting it to AHCI and doing the restore. Then set it back to RAID before trying to boot the restored disk. This assumes there is only one NVMe drive in the computer and there is no actual RAID array.
Hi Mustang,
unfortunally the link to your guide does not seem to work. As far as I remember using the MVP tool I saw in the output on the screen that the drivers were included succesfully. Since I am home now I can't review the log-files, I will do that coming Monday.
The options in the BIOS of the Surface Book are very poor. There are 5 pages, 3 of them contain options, but nowhere I can see advanced options like setting the Sata mode.
Please find attached the file listing of the folders Drivers and Firmware inside the SurfaceBook drivers-zip. The folder in System\SurfaceNVMExpressController contains 2 files, which I used to make the usb stick: surfacenvmexpresscontroller.cat and surfacenvmexpresscontroller.inf Perhaps you can tell if there are other folders to explore in this zip?
Have a nice weekend.
Ton.
Ton,
I fixed the link in reply #26.
The important thing is you have the inf file for the correct driver to add. There are other files you need. Use notepad.exe to open the inf file. Look at a section called [SourceDisksFiles]. You will see a list of the needed files. You can pick them up from the Windows system of the Surface Book. Sys files are found at C:\Windows\System32\Drivers and dll files are found at C:\Windows\System32. Put them in the same folder as the inf file in the Drivers_Custom folder of the MVP tool and build again. This should make WinPE see your NVMe drive in the Surface Book.
Hi Mustang,
Thank you for fixing the link. I will look into the .inf as well. The problem with adding drivers from the system32 folder on the Surface Book is that I can't reach them, since the laptop freezes after 30 secs when booting into Windows. It crashes after a miute or 2 with a blue screen..(see my original post #10)
Is there any other way to get those drivers?
Best,
Ton.
Hi Mustang,
I looked in the SurfaceNVMExpressController.inf to see which inf files are needed. (see attached .txt file) I found that it needed stornvme.inf, so I copied that file from my W10 pro 64 bit pc from the windows\system32\DriverStore\FilesRepository. There were 2 versions of them with different dates so I tried them both to insert into the usb stick (see results-window-screendump in mvp-tool.jpg) Both versions did not show the internal disk....Apparentely I am overlooking something? While creating the bootstick, I also ran into a remark in the mvp-toolbuilder, please see the attached mvp-tool2.jpg It says "\MVP was unexpected at this time"and I was wondering if this is an error?
Regards,
Ton.
Hi Ton,
Interesting driver. You need to take the entire folder for stornvme.inf from the FileRepository. It contains stornvme.sys which is needed.
Thanks for reporting the error in mvp-tool2.jpg. I'll look into it. There seems to be a problem with a statement needing quotes to deal with spaces in the path name. You can get around this for now by running from a folder with no spaces in the name. Don't put the MVP folder in C:\Program Files (x86). Move it to the C: drive root so it looks like this:
C:\MVP_ATIPEBuilder_v99
That should eliminate the error.
EDIT:
I don't see any problem in the script. The error may be caused by a permissions problem in the C:\Program Files (x86) folder. Moving the MVP folder to C: should work.
EDIT 2:
The problem is the script sets the source folder when it runs. This is the folder from which the script is being run. It is not being set properly when run from C:\Program Files (x86). I can't see how to fix it right now. It has nothing to do with missing quotes. Just don't run it from there.
Hi Mustang,
I did copy the entire content of that folder to the custom driver folder...(there is only the .sys and the .inf file in it) I also tried a nvraid inf, since that file is using the stornvme.sys too, but with no succes. i am running out of options I am afraid...
Ton.
Did you rebuild after moving the folder out of C:\Porgram Files (x86)?
Yup. And there were no messages which seem odd...
Looks like you're running low on options.
What do you mean by there were no messages? Did you get a new ISO file?
Is it possible to install Windows on that computer? Have you tried booting a Windows installation DVD to see if it can see the hard drive?
Is it possible to remove the hard drive from that computer?
I'm sure there is a way to deal with this somewhere.
Mustang,
I meant there were no errors in the dialogue while creating the usb flash drive...
A Surface Book has no dvd built in... I tried with a bootable usb with the universary version on it, but when I use that one, it keeps returning to the bios pages...I don't think an external dvd-drive on usb will be an option to boot from...I can't open this device whitout breaking the garantee-rules, besides that I think there will be a m2 card or similair in it..
Mustang,
when I boot from the MVP stick and then insert the W10 stick, I can run the setup.exe from it, using the built-in explorer on the mvp-stick...I am not sure if that will be the solution, since I want to rescue some files from the Surface Book and not a new installation...
I'm running out of ideas to save files from that hard drive short of getting it out of the computer and mounting the m2 card on a PCIe adapter card and putting it in a desktop computer to copy off the files or do a restore to it.
Ton,
One last thought. You may need to inject a RAID driver in addition to the drivers you've already injected. The IRST driver we have included in the MVP tool may not work for that controller.
I'm going to head to a BestBuy or Costco later this week and plug in an MVPWinPE built stick into a SurfaceBook system and try to boot it and see if it sees the drive or not.
No issues on Surface Pro 4 and really don't see the hardware being that different here, but would like to see this issue for myself if it exists. Could it be a hardware error at all - what made Windows stop working - maybe a physical issue? Not sure - I'll feel better when I can see the behavior on a SurfaceBook myself, or debunk it that it is working. One way or another, we shall see later this week.
As for the issue with the tool not runnin gwhen it is put in C:\program files (x86), I'm not 100% sure either. I tested and when I did this, I definitely had to set the permissions on the MVP PE folder to give trusted installer and all users full access to the root of the folder. Otherwise, I was getting denied access when trying to modify and edit certain files in the directory - something the tool needs to do in a few places to get system information and set variables. I got denied access, manually modifying a few files and trying to save them directly to the oriignal location. I would be forced to save them somewhere other than the original location so I would save them to the desktop... then, when I copied them back to the folder again where the MVP tool was placed in program files (x86), UAC requires me to specifically say yes or no - I think this is one major issue.
I got the initial script to run after making a couple of changes. It was literally just a couple lines of code, but a hundred different methods before it didn't bomb out after the "scanning the system" section. I got it to run all the way to the request to do driver injection. I pressed yes to inject, it detected my previous drivers and then as it tried to chug on, it bombed out. There's a lot going on this section and I'm not sure it's worth troubleshooting to get it to work in this specific instance - it runs fine from the root of any drive, or the user desktop or just about anywhere else that is not a system folder.
My real guess is that the brackets in (x86) are the cause. Brackets are used in bat scripts to enclose groups of code. Those brackets may be causing some issues in the name based on how the executable is calling on the source path which includes "program files (x86)" when you move the folder there.
I'll play with it a bit, but am not too worried about this as it's meant to be a portable tool and not tied to the program file (x86) location and the easy fix is to move it anywhere other than there (desktop, root of a drive, etc).
User with SurfaceBook - working fine in Acronis forum post: https://forum.acronis.com/forum/101718
Sounds like he didn't even have to use custom drivers... not sure how that is if the thing is using RAID in the bios and PCIE NVME though., but perhaps the key is from the next post mentioned below which states you must have an external USB keyboard attached.
I've cloned the surface book several times using a boot usb of ****. You just need to connect an external keyboard, disable secureboot ( with machine off, press power then immediately hold the volume up button until you reach UEFI) within these settings you can also change the boot order to boot from usb and then ***** will boot.
Hi Bobbo_3C0X1,
I am very interested in the results of the test with the Surface Book at Bestbuy or Cosco, but again if it is possible to hand over a copy of the working Surface Pro stick, it would be great. I am not looking for an option to clone my Surface Book, since it is crashing all the time. I can't prepare the Book to create rescue media with Acronis anyway.
Regards,
Ton.
Hi Mustang,
yes, it occured to me I might need a raid driver, but then the question is, which raid-driver is used in the Surface Book? I scrolled through the latest drivers-update-zip but I can't see anything wat looks like a raid driver..
Ton.
Ton,
Can you give me a link to the Surface Book drivers? Maybe I can see the RAID driver.
Mustang,
sure, it was already in my post#24, but here it is https://www.microsoft.com/en-us/download/confirmation.aspx?id=49497
Ton.
Mustang,
sure, it was already in my post#24, but here it is https://www.microsoft.com/en-us/download/confirmation.aspx?id=49497
Ton.
Ton,
Nothing jumps out at me either. I think I would try supplying the entire System folder to see if that helps. Just keep the extra driver we found for the NVMe controller in addition to the System folder.
Mustang,
the problem is that I cannot create the stick from the Surface Book, it is freezing after 30 secs....I even can't copy the System32 folder to an usb device, it stops at 5% and then the Surface Book shows a blue screen with Critical_Proces_Died....
Ton,
Sorry for the confusion. I ment the System folder from the downlaod link you gave me. That's the folder that has the subfolder for the NVMe controller.
Mustang,
ok, so the mvp-tool will look in the subfolders and add all the drivers?