I just stumbled upon this project. Can one join a domain and make use of Direct Access on the duo phone with this?

Every time I use the pen to write a note for a few minutes, the touch control will be broken, both the pen and hand could not touch. Log off and log on can fix the touch control. But if I don't have a mouse with me, I can do nothing to fix that. The only thing I could do is shutdown.
Sometimes other conditions may also cause the issue, but in these conditions, leave it there for a while the touch will back to work.Only when use the pen and cause this issue, leave it for a while could not make it back to work.

After installing the X: and Y: drive, I flashed the Drivers and rebooted using fastboot boot boot.img.

I landed up on Recovery screen displaying the digital signature of the file couldn't be verified. File\...\qxppx8180.inf_arm64_... ***.sys
Error: 0x....428.

Is there a way to bypass the digital signature?

after I updated Android, the duo 1 hangs on uefi during initial boot screen. I tried both uefi and same problem.

any hints or help please and please lol

Have done the install a few times successfully, but most recently, I'm getting this new screen and not booting into windows, its got a qr code that has a url beneath it of "aka.ms/devicerecovery". What could I potentially doing wrong?

Did a clean install of Windows 11 IoT Enterprise LTSC for the Microsoft Surface Duo 1 as followed by the Surface Duo 1 guide, all the latest available drivers installed for it. The getting ready screen phase where it installs all of the devices has passed, but when it rebooted into the second phase, I’ve got greeted with an unexpected BSOD that says SOC_SUBSYSTEM_FAILURE related to the qcbattmngr8150.sys file.

attached image to this issue for proof.

As the title suggests, auto rotation is not working for me on my Duo 1, although the option to lock the rotation appears, and the device seems to recognise when you rotate it, as the start menu hides when you rotate the device. Also if I manually enable the SurfaceDisplayConfiguratorService_46b83 service (which doesn't start automatically when logging in), everything seems the same, except that now I can't disable or enable rotation lock from the control center. Video of the issue (sorry for the quality, I have to compress it to fit the 10mb limit):

I used the latest drivers and UEFI (2305.25), Windows 11 Insider Beta 22624.1690, used epsilon_vb definition file.

I am able to select and boot windows, but after a long wait on a blue screen of "please wait" there is a login screen with Other User. I cannot log in, and a USB keyboard also does not work to attempt to boot into safe mode. Has anyone else had this problem?

new issue with sleep (not observed on 2303.84 or how was it called)
device turns off after some time closed (usually 2+ hours)
device: GEN
UEFI: 2305.45 in dualboot setup
Driver set: 2305.45
Android base: 2022.827.21
Windows: 23451

How to reproduce: boot device into Windows, close the lid. wait for {some} time. open the lid. device is turned off anf can be turned on by pressing the power button. Boot process will start.

minidump applied
Uploading 051823-44515-01.zip…

Now i did everything right and i installed the vNext (Zinc Semester) but now if i fastboot boot uefi.img windows load thanf the circle stop doing anything and it boot bacl into bootloader.

Driver are installed correctly with the drivers (12 hrs. ago)

Last Issue from my side Please help

Device was put to sleep overnight, after waking it up the next day, the autorotation functionality was missing - the Action Center button is greyed out, and the option to toggle it is missing from Settings.

After initial investigation, the Surface Display Configurator service has been stopped, based on the date of logs, during the wake-up process.
For reference the functionality is restored after manually restarting the service.

Crash logs:
APPCRA~1.ZIP

Would it be possible to build an image like that or must the EFI file be completely recompiled? Thank you!

After following the Surface Duo WOA guide exactly for the Surface Duo 1, Windows 11 Build 25951 seems to boot up fine until it goes to the "Getting ready" phase where it stays there for a few mins then suddenly an error message pops up saying "Windows Setup couldn't configure Windows to run on this computer's hardware.".

OS Build used: Windows 11 Enterprise build 25951 (Canary Channel) ARM64

Looking into the setup error logs, it says the following:

2023-09-09 00:45:01, Error                 CONX   ApphelpDebug: ERROR,ApphelpChpeModSettingsFromQueryResult,892,SdbQueryResults was null or not the correct size.

2023-09-09 00:49:24, Error                 SYSPRP Sysprep_Specialize_Bcd: There was an error setting firmware variable support reg key. Status=[0xC000003B]
2023-09-09 00:49:24, Error                 SYSPRP ActionPlatform::LaunchModule: Failure occurred while executing 'Sysprep_Online_Specialize_Bcd' from C:\Windows\System32\spbcd.dll; dwRet = 0xa1
2023-09-09 00:49:24, Error                 SYSPRP SysprepSession::ExecuteAction: Failed during sysprepModule operation; dwRet = 0xa1
2023-09-09 00:49:24, Error                 SYSPRP SysprepSession::ExecuteInternal: Error in executing action for Microsoft-Windows-Sysprep-SpBcd; dwRet = 0xa1
2023-09-09 00:49:24, Error                 SYSPRP SysprepSession::Execute: Error in executing actions from C:\Windows\System32\Sysprep\ActionFiles\Specialize.xml; dwRet = 0xa1
2023-09-09 00:49:24, Error                 SYSPRP RunPlatformActions:Failed while executing Sysprep session actions; dwRet = 0xa1
2023-09-09 00:49:24, Error      [0x0f0435] SYSPRP Callback_Specialize: An error occurred while either deciding if we need to specialize or while specializing; dwRet = 0xa1[gle=0x00000002]

I have also attached the original files (setupact.log and setuperr.log) to this issue, not too exactly sure if this is a Windows Insider build issue. I've tried searching online for the error code and came up with no results.

setupact.log
setuperr.log

I am testing with a 256GB device, and I noticed a few things:

1. I get a tar chown 1000:1000 Operation not permitted warning with several files when I untar the DuoBoot tar file.
2. If I continue with the guide, the UEFI Shell boots up no problem. The left screen displays the information and the right screen reads touch inputs for the left screen.
3. If I add the --no-same-owner to the tar command, all the files extract properly, but the left screen is a static mess of colors and the right screen does not respond to touch (from what I can gather)

I attached my console log to show the chown warning
console.txt

The right side of both the two screens could not touch.This zone is about 2mm wide.And the calibrate program could not run at all.
It looks like that the touch feedback position of the whole touch screen is offset by 2mm to the left

Followed the instruction and failed to copy sensors files, 7zip can not open /mnt/vendor/persist/sensors/ folder, can you update the "InstallWindows-SurfaceDuo1.md" to tell how to copy those files in TWRP or Android method instead?

If I was to use this project on a Surface Duo 2 could I not have android installed and just dedicate it all to windows.

My Duo shows this artifacts when updating to a new build, and kind of refreshes when pressing the power button, although the device updated normally:

For reference, it should show this screen:

Using 2305.💯 UEFI and 2305.90 Drivers, with epsilon.txt definition file. I was updating from build 23471 to 23475.

My Surface Duo 2 changed the screen on the left and the screen flashed when I turned it on and I couldn't enter the system. I learned that the hardware encrypted the code that will recognize the screen at startup. Is there any way to fix this problem by modifying the startup file? If so, what should I do? Did anyone tell me?

Hello everyone,
I installed Windows 11, I followed all the steps, I managed to boot on Windows, but I can't go any further because I can't install the drivers, the last step: DriverUpdater.exe -d "\definitions\Desktop\ARM64\Internal\epsilon.txt" -r "" -p Cmd doesn't give me an error but it also doesn't install the drivers on X:

Can you help me what mistake am I making?

I remain at your disposal for any other questions

Hugo

Downloading the zip just contains a file called
uefi.img

figured I'd just edit this instead of creating something else. Is there a fix for this or is it a bug?

after enter "fastboot boot surfaceduo1-uefi.img" , can see windows boot menu,

but after choose win11 to boot, surface duo auto power off after a while and failed to boot into win11.

It is a fresh new install of win11 with no change to other settings other then power plan and text scale settings

Hello, I would like to know the model of the touch IC for the surface duo

Follow the update instruction to use latest driverupdater and driver set(Version 2212.12 (B)), reboot with latest uefi, the first and second reboot occurs a green screen crash, and after the third reboot, everything works, but wifi is missing, also if drag the brightness bar, the two screen's brightness change is different visually. Power charging is not work at first, and after a 4th reboot, power charging is worked, but still, finally wifi is still missing.

the new touch style taskbar looks good, but not get used to it yet.

Nice job, but seems need further works, I'll do more test when I got spare time.

when i want to boot to windows the comand
fastboot boot surfaceduo1-uefi.img
is not working!

i need to put the uefi.img file in the adb direcory AND change the code to
fastboot boot uefi.img
then it worked

would be great if this would stand in the skript as well

ufile.io let me pay for a subscribe to download

I went through the whole walkthrough, with no notable issues, but when I run uefi.img this is as far as I get. Widows never launches, it just hangs on a static screen.

How can i Setup Windows, if a USB Mouse is not working?
I‘m in the menu, where i can select the Language/Country?

Please help :/

after following the steps and installing all the drivers the windows stuck in it's first boot up and the circling dot keep circling noting is happing!

This issue was reported to happen with ZN_RELEASE and also NI_* Windows 11 builds and began with version 2305.25.

Hello,

I followed the tutorial and got everything installed and the bootloader options updated, testsigning on, etc. The bootloader is showing Windows 10 instead of Windows 11 for some reason, and when I select it it goes to BSOD. I'm not sure if it matters but it's a Surface Duo 1 (256 GB) and has Android 11 installed, I just factory reset it before attempting this. I did the 400 MB for the fat32 partition because it was didn't work with 300 MB.

10.0.22000.318.co_release_svc_prod1.211102-1556_arm64fre_86abe5724c69

Any ideas?

"Navigate with the volume up/down buttons to Mass Storage Mode or Windows, and press the Power Button to confirm.
If you did everything right, Windows will now boot! Enjoy!"

Following this step Duo loads to a screen that says "UEFI Mass Storage - Connected" and I can access my duo as a mass storage device on the host machine, but Windows does not boot.

Hello all, thanks for the great work.

The precision is off when using the surface Pen, and when trying to calibrate the pen, nothing come up on the screen in windows..

Is there a way to manually fix the pen or touch precision?

Using Duo one with Dual Boot

A way to completely undo everything and start from a clean slate as in from the factory.
I did a factory ota install but the partitions that were made are still there.

Edit: Nevermind, found it in the guides.