oliverjia, A mate has a Surface Book (or maybe a Pro). He uses IFL and TBWinRE. The IFL he uses is 64-bit.
I have to say that is a terrible response. I thought that you may have actually been able to give me the answer.
ifw works fine as well. what i have seen with surface 3, pro and others is they are very fickle is which usb sticks and which pe environment they use at times. not all the time but there are those cases. have you checked the drive as was suggested?
correct i always have to when using ifl. if you are using any NON uefi bootable usb you have to disable secure boot
I have UEFI and MBR systems and I don't have to disable Secure Boot in the UEFI systems when I use IFL. IFL and TBWinRE support Secure Boot. But as you say, to boot IFD or BIBM you have to disable Secure Boot. My son acquired a Dell XPS 13" a few weeks ago. To use IFL or TBWinRE we have to change the UEFI BIOS setting from RAID to AHCI otherwise the drives aren't seen. This would apply to all WinPEs. In addition, we have to use the 64-bit version of IFL as the standard version doesn't load. But no problems with Secure Boot.
sorry what i meant was if you are using ifl and are NOT using a uefi boot stick you have to disable secure boot on the SURFACE specifically. lol its like 5am here been working all night on a big project and getting tired.
I checked the TeraByte forum. All recent versions of IFL support UEFI Secure Boot with the exception of the Microsoft Surface computers. As you say, Secure Boot has to be disabled. I haven't tried this myself.
What do you want to know exactly in order for an answer to be deemed helpful? You look for a working solution and I pointed one to you, isn't that helpful? you want to know WHY it will work? Find it out yourself. ~ Removed Off Topic Personal Comments ~ You do your own research to find out.
If memory serves me right, one of my friends told me the only disk imaging tool that worked on his surface tablet is the Enterprise solution from Acronis: Acronis backup v11.7 boot disk. The consumer version of ATI home did not work.
I have used Aomei Backupper free to backup my Surface 3 Pro. However, I have not had to use or attempt a restore. Now, I'm nervous that it won't work.... P.S. I only had a 32 GB flashdrive and Macrium's compression would not fit the image on my flashdrive; yet, Aomei did work. Otherwise, I would have used Macrium.
I had a bad experience with also. I don't know about you guys but even though I have Macrium set to boot with windows, ifigure the only time I would need to use that option is when I can still boot up my PC. currently I just use my usb stick to restore an image. I do have to going into BIOS before hand and select the USB stick. I used Ghost back in the day. Macrium is one of the easiest imaging software I know of. Tarnak I do not use the verify option and never had any issues yet.
About verify, I never use it. I learned back in the Shadowprotect testing days verify didn't always mean you could restore. I found a better test if you need do it is simply mount the image, find a video file and see if it plays with video and audio. If it does I've never had a restore failure
Alex, I gather the Surface Pro/Book computers have issues with booting some UFDs. Can you boot your Aomei Backupper UFD and browse to your backup images? You might have to disable Secure Boot temporarily. Please let us know the Secure Boot setting. Out of interest, does the Macrium UFD boot?
you should be fine. if you have issues simply boot to the bios and turn off secure boot then boot to aomei do your restore. when done turn it back on. you should be okay. the surface tabs are just very finicky about booting usb media.
I'll leave you alone. Too strange for me to understand you. I am sorry I bothered to ask. I'll move on.
So I don't think I'll be getting Surface Book anytime soon. This is a heads up. Hassle-free imaging is non-negotiable.
I discovered what I did wrong. I was trying to restore the backup created on December 5th. What I didn't understand at the time, was I should have initiated a restore using the incrementals made since that backup. So, this time I used the last incremental created on February 7th, i.e. using the most current in a chain of incrementals made subsequent to December 5th. So, late this evening I finally achieved a successful restore. P.S. This time I didn't use the 'verify option'.
