Windows 10 build 15035

Windows 10 build 15035 is a build of Windows 10 Creators Update uploaded to BetaArchive on 24 November 2019. It is notable for being the only available Windows 10 client build available for ARM32 processors. It is possible to run this build under QEMU as well as on various ARM (ARMv7/v8) phones and tablets that originally shipped with Windows 10 Mobile or Windows RT if the appropriate drivers are available and Secure Boot can be disabled. Although the build is not suitable for daily use, it has attracted some interest from the remaining users of ARM (ARMv7) devices as an unofficial replacement for Windows 10 Mobile or as an upgrade from Windows RT with scripts created to assist with the installation for both phones and tablets.

Installation
Installation guide on QEMU: 1. Download and install QEMU 4.2 for Windows. 32-bit version. 64-bit version.

2. Download and install GTK2-Runtime 2.14.4-2008-10-22.

3. Download Linaro UEFI 15.10 32-bit and copy this file to the QEMU installation folder.

4. Download HxD Hex Editor.

5. Download ARM32 build of viostor driver.

6. Patch trustzone, for this open  in the HxD Hex Editor and replace the following hex string:   with:.

7. Add viostor driver to the WIM image. Extract  archive, then run Command Prompt as administrator and then run the following commands:

dism /mount-image /imagefile: /mountdir: /index:1 dism /image: /add-driver /driver: dism /unmount-image /mountdir: /commit

8. Create needed VHD files by using the  utility. For this, run the following commands. (Note that these files will be created in a directory on your C drive called "15035", and they will be mounted under the drive letters P and W).

create vdisk file="C:\15035\hdd.vhd" maximum=40000 type=expandable select vdisk file="C:\15035\hdd.vhd" attach vdisk convert gpt create partition efi size=100 format quick fs=fat32 assign letter=p create partition primary format quick assign letter=w exit

9. Apply the WIM image, and then create boot files:

dism /apply-image /imagefile: /index:1 /applydir:W:\ bcdboot W:\Windows /s P: /f UEFI

After that, eject P or W. Once ejected, P remains and disappears after a reboot.

10. Run QEMU by going to your QEMU installation folder, saving the following text to a batch file, and then running it to start the emulator:

11. If you want to change screen resolution press F2 to enter EFI settings, enter  and then. Change the resolution to the desired one then commit the changes and exit. Choose  in the QEMU menu and then reset the emulator.

12. Select. Enter a drive letter (such as ) in the shell and run the following command:

efi\boot\bootarm.efi

(The above commands allow you to start the OOBE).

During the first launch, error  is possible. You must disable driver signature enforcement. To do this, press the F8 key and then press the 4 key.

13. Set testsigning on.

To do this press Shift + F10, then the command line will appear. Enter the following command:

bcdedit -set testsigning on

After the completion of the OOBE, you can boot into the system.

14. If OOBE fails.

If OOBE fails, then you must follow the steps below to bypass it and log in:

a. On the first screen of OOBE, press Shift + F10, a command prompt will appear.

b. Enter the  command, then you will open the Registry Editor.

c. Go to the following path:.

d. Change the value of the  parameter from   to.

e. Change the value of the  parameter from 1 to 0.

f. Change the value of the  parameter from 4 to 1.

g. Close Registry Editor and at the command prompt type the following command:  to reboot.

h. Now, if you did everything right, when you boot, you should automatically have a command line. You need to manually create an administrator account and delete the defaultuser0 account. To do this, run the following commands:

net user Administrator /active:yes net user defaultuser0 /delete

i. After that, launch the Task Manager. To do this, in the command line, enter the  command. Then end the  process.

Applications
This build omits certain apps that were either not available for ARM (ARMv7) processors at the time or were simply excluded from the build for other reasons. Although the included apps are limited there are numerous additional apps still available as well as updates for the preinstalled apps that are compatible with this build.

Updates
Although it is possible to install more recent versions of the Microsoft Store, it will only be able to install updates for apps that are manually installed or apps that have already been purchased and are available on the users account, the purchase and installation of new apps directly from recent versions of the store on this build will not work. The lists below detail the preinstalled versions and the latest known versions of various Microsoft apps that will work with this build as of November 2020. 

Additional software

 * Internet Explorer 11 is not installed or included in the Windows image as a Feature on Demand package by default however it is available as a separate optional package on the installation media in  which can be installed by running the command below:


 * This build supports all versions of Office 2013 RT which were previously included with Windows RT, if installed on this build Windows Update will work to provide any available updates for Office 2013 RT.
 * Most software that was recompiled for jailbroken Windows RT devices will run on this build.

Bugs
This build contains a few notable bugs:


 * The User Account Control user interface is broken, leading to issues starting programs requiring administrative privileges. Disabling UAC using the registry is mandatory to run these programs, this can be achieved by applying the registry entry below:


 * Cameras will not work even with the appropriate app and drivers installed on Surface RT devices due to a missing registry entry, this can be resolved by applying the registry entry below:


 * Using Microsoft Management Console (MMC) snap-ins can cause a BSOD error . This issue occurs most commonly with Event Viewer and Task Scheduler while occurring somewhat less frequently with Disk Management however it may manifest at random with any MMC snap-in.
 * On some devices the Screen Brightness setting does not persist after a reboot and Automatic Brightness does not always function correctly.
 * On some devices Night Mode may not always function correctly.
 * The background color for windows is gray instead of white.

Driver compatibility
This build is for the most part compatible with drivers originally intended for Windows RT aside from the following exceptions:


 * This build technically does not support NVIDIA Tegra processors, like the ones found in the Surface RT and Surface RT 2. The sdbus driver, responsible for providing an interface layer with the eMMC dropped support for the NVIDIA storage controller during Windows 10 development. You can however replace the driver with the one from Windows RT 8.1 build 9600.16384 to make the build boot on Surface tablets. On the Surface RT 2 (may also apply to Surface RT), using a version of sdbus newer than 9600.16384 will conflict with the nvpep driver causing a BSOD error ) on boot. Later versions of the Surface RT 2 USB recovery media in particular may contain version 9600.16497 of sdbus driver which will trigger the error.
 * This build does not support legacy touch drivers built for Windows 8 RTM. Loading these drivers will cause the OS to register touch inputs in the top left corner of the screen.
 * This build does not support the Nokia Lumia 2520 Qualcomm Power Engine Plugin driver. Loading a newer driver for the Snapdragon 800 is mandatory.

Expired digital signatures
Numerous issues are caused when attempting to use this build beyond its expiry date due to various digital signatures being outside of the validity period, this is normal and is by design once the build reaches its expiry date or when installed after it. Examples of some of the issues caused by installing or running this build with current date set are listed below.


 * The legacy Windows Defender UI is not functional and will terminate with a critical error.
 * The Diagnostics Troubleshooting Wizard is not functional and will terminate with a critical error.
 * Neither Microsoft Print To PDF or Microsoft XPS Document Writer will be available after installation. Should these be required both drivers can be manually installed from  and overriding the Driver Signature Enforcement Check when prompted.

Restrictions
Although it is not an edition of Windows RT, this build has inherited some of the restrictions present in Windows RT. When certain Windows RT restrictions were established they were applied not by SKU but were instead applied to a specific architecture, in this case ARM (ARMv7). Issues known to be caused by this are:


 * User defined start-up programs are not available.
 * Incoming Remote Desktop connections are not available.

Modified variants
Following the publicly share of this build to BetaArchive, two pre-prepared images have been distributed for Surface devices in both Simplified Chinese and English languages.


 * An image released in January 2020 has had its Edition modified to Windows RT 10 and Version increased to 1703 whilst retaining the original build number.
 * A highly modified image based on this build was released in May 2020 which has had its build number modified to 17763, while this image does contain components from later builds likely obtained from Windows PE it is in fact still build 15035.