![]() However before I did the installs, the recovery media builder did not function properly. Clearly the ATI boot builder uses the new environment to build boot media that work. I think ATI media builder has a flaw in its program code.īob, thanks for you explanation of the ADK, WinRe, and WinPe and why the different look and size difference. It was only after it did a quick format and left it as exFAT, that the media builder on the Win 10 laptop asked to reformat it. When I inserted that USB into my Windows 7 machine, it also recognized and display it but it asked if I wanted it formatted. ![]() I suspect that the USB was 64GB of exFAT but unallocated. It proceeed for about 3 mins and then reported that it could not write to the USB but gave no reason or option. Media builder complied a 700 MB file size and began to execute the build. When ATI Boot Media ran, it also saw the USB and displayed it as a potential media to write to. Hi Bob, When I plugged the new USB stick into the Win10 Laptop, Windows recognized it and displayed it in the My Computer window. Overall, 100MB is not going to make the rescue media much faster (or slower) and doesn't take up a bunch of space. As each package is added, the size of your resulting media will grow. In order to add things like bitlocker support, you have to manually add those packages too. This can be ideal in some situations where you don't want to have competing drivers causing issues at startup (remember it's basically a Windows OS). WinPE, is a stripped down version of WinRE that is more "generic" since it doesn't have the preinstalled system drivers. The reason WinRE is larger than WinPE is that it includes other packages by default, not found natively in ADK - some of which include the local system drivers (the system where the winre was taken from), wireless support services and bitlocker support. ADK is the manual method to create WinPE and WinRE can be built if you have a good recovery environment partition already. You must create it on a fully licensed version of Windows OS. Windows PE and RE are not allowed to be distributed "built" per the Microsoft terms of service. It does the job in a pinch, but falls short in driver support on many new systems that have requirements for RAID (IRST for PCIE NVME drives often come set in RAID by default from the computer manufacturers like HP and Dell). iso of the Linux rescue media in your account downloads. Linux is a free distro that can be distributed and that is why you'll see a pre-staged. the default from Acronis is a Linux distribution which is a small build based off of busybox. not available to Windows, not available to programs that run in Windows.Īs for the rescue media variances. If the drive is not initialized and not available to Windows, Acronis will not be able to use it as a target for rescue media creation since it is a program that runs on top of Windows. It's not uncommon that a new drive will not be initialized at all, and should be standard practice to initialize it with Windows disk management and format it as desired. Each new drive (external USB, flash USB, internal, etc.) can be formatted differently by manufacturers. The new USB disk not being formatted or initialized should have been detected by your original system (assuming Windows 10) as well as Windows 7. There is some compound info/problems here. I inserted the USB into my Windows 7 PC and it said the USB was not formatted so I let it format exFAT and only then when I inserted it into the Windows 10 Laptop did the boot builder recognize it as a functional USB and presented a dialog box requesting to reformat it (FAT32 I presume).Īll I have to say is that I am sorry Norton Ghost pulled out of the Backup market. Also I inserted a brand new 64GB Sandisk USB and the boot builder said it was unable to wirte to it. There is definitely some problems with the Acronis S/W and that is disappointing. It had the same graphics and loaded the same as the WinPE version and the file was 100MB larger, but it was also fully stable and the Win command line ran in the background as well. I went back to the Boot Builder and created another USB using the Simple method (WinRE). It had a whole different look with MS Tiles showing as it started up, and behind the ATI graphics was a windows command line X:\windows \ system32> winpeinit. I then booted off the USB stick and it worked fine. The builder in Advanced Mode then proceeded to calculate and places the files on the USB stick. Before the Advanced mode would proceed, it directed me to MS and had me download and execute ADK setup and ADKWINPE setup (which took about an hour). I ran the boot media builder and selected Advanced.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |