Recover Surface 3
I have tried to recover Surface 3 with ATI 2016, Build 6027. This is only possible with WinPE. Creating WinPE on an USB-Stick at the USB 3.0 port from the tools menue was no Problem. I copied than the previous made backup image from the micro SD-card of the Surface to the USB-stick because the micro SD-card drive will not be seen on WinPE.
First in UEFI (press loudness + and power on) secure boot has to be disabled. Upon re-start drive / usb-stick has to be choosen. Keybord and touchpad of the surface works so navigation is no problem. This means no USB-hub is need for an additional port for an USB mouse. The USB-stick alone is sufficiant.
The TI windows appiers and you see at PC the drive C as destination of the recover. The micro SD-card drive can not be seen but the image was copied to the USB-stick before. I did not make the recovery but up to this point it works.
After that secure boot has to enabled again at UEFI.

- Accedi per poter commentare

@S22 thanks. I added with DISM (Deployment Image Servicing and Management) from the Windows Kits Depoyment tools (Windows ADK 10) the latest system drivers of Surface 3, Novemer 2015, to the WinPE.
Now I see the SD card drive with content including the TI image I created before and I can select the image for recovery.
The Drive C: is shown in the overview but without content! I must correct me in my posting above: Without the added drivers I did not see the content. But this has not changed even I added all system drivers. I do not know if this is important in case of for recovery.
- Accedi per poter commentare

I will try in some minutes if i have access to "my" Surface 3....
Stay tuned...
- Accedi per poter commentare

Hi
i started my Surface with the ATI USB Stik and i did see all the subfolders in C but only if i did go to the "Datei and Verzeichnis" option.....
Strange....
S22
- Accedi per poter commentare

The only driver I did not add is "Surface Integration Driver".
- Accedi per poter commentare

After many tries and variations I am not able to revover my Surface 3: I cannot see the Drive C: After booting with USB-stick and WinPE even so the latest system drivers 11/2015 have been added. Only the SD-card drive can be read.
System Drivers are:
GPIO - General-Purpose I/O (GPIO) Driver
DPTF - Dynamic Platform and Thermal Framework (Intel® DPTF)
I2C - Intel Serial IO I2C Host Controller (touch and pen device)
MBI - Intel® Mailbox Interface Device (Intel® MBI) Driver
PMIC - Intel Power management integrated circuits device Driver
SPI - Serial Peripheal Interface IO controller Driver
TXEI - Intel Trusted Execution Engine Interface (TXEI) Driver
UART - Universal Asynchronous Transceiver Transmitter (UART) Driver
Surface Integration Driver.
I guess that only GPIO, I2C, SPI, UART, and Surface Integration Driver (?) are needed.
The mass device at C: is 128 GB eMMC Flash, 128 GB.
The Acronis media plugin seems to be not compatible to run the drivers for the eMMC Flash. That means Arconis True Image is worthless for Surface 3.
- Accedi per poter commentare

Hi Wglobal
i try to describe how i created my working medium:
1. I used ATIPE Media builder to create a WinPE64 USB Stik
2. I started DismGui as Admin
3. under "mount control" I choosed the *.wim file on the usb stik as source. and a temp file somewhere on my pc as "mount location" -> press Mount Wim afterwards.
4. after wim file is sucessfully mounted you can see all files of the wim in your temp folder.
There i careated a subfolder "driver" in which i copied all the Surface 3 drivers.
Afterwards in dism gui under "Driver Management" i chossed the driver folder in my temp folder. i checked the "forced unsigned" box and added all driver.
after all drivers have been added (thought there have been around 40 drivers) did go to "mount Control" and dismounted my image (i did get a question if all changes shoudl be applied, of course i answered with yes).
after wards all drivers are added directly in your wim on the rescue usb stik file and should be available during boot from USB stik. I dont know if all this is really necessary but id did work perfect for me....
S22
- Accedi per poter commentare

@S22: Thanks for the hint of this nice DISMGui. I did it manuelly with the DISM command line as administrator:
In C: there are the folders \Temp, \mount\, and \Drivers with all necessary drivers.
dism /Mount-Wim /WimFile:C:\Temp\boot.wim /Index:1 /MountDir:C:\mount
dism /Add-Driver /Image:C:\mount /Driver:C:\Drivers\ /Recurse /ForceUnsigned
dism /Get-Drivers /Image:C:\mount
dism /Unmount-Wim /MountDir:C:\mount /Commit
In the second DISM line above /Recurse enables search of .inf files in sub folders of Drivers\. This is much comfortable. DISM runs without error and the new boot.wim is in \Temp which I then copied to the WinPE USB-stick in the source folder. Then I booted the Surface from the WinPE with secure boot set to disabled before.
I think the result is the same but it does not work for me ... Drive C: is not visable ... Strange ...
- Accedi per poter commentare

I will give it a last try with the complete driver paket using the DISMGui.
- Accedi per poter commentare


I have made a fresh WinPE and followed the procedure with DISMGui to add all the latest drivers to it. No success, the WinPE USB-stick is below this PC on drive C: (!) and there are 4 local Drives, 2 of them are empty with content zero. I assume one of it is the old C:. The SD-card drive can be read.
- Accedi per poter commentare

I must correct me: I could not drill in the local drives to see the content because they where encrypted.
Now just for fun I dared a full recover from WinPE on my USB stick with secure boot disabled (and bitlock too but data are still encrypted) and it was successful with one exception. At the last process to recover the mysterious 128 MB MSR partition (Microsoft Reserved Partition) between UEFI and Windows an exception happened writing the sector 0 (boot sector MBR). I ignored this and after recover the Surface 3 started in secure boot disabled. All was fine and I started it again with secure boot enabled.
But now the system behaved different regarding bitlock. The system control item "system and security" changed to "system" without the possibility to administrate bitlock (activate / deactivate, bitlock of files to go, export of the bitlock key). Even so after booting with secure boot disabled the window to enter the bitlock key and the extended start up menue disappeared. Starting with bootable USB stick was still possible.
Encryption and TP (trusted platform) is gone.
- Accedi per poter commentare