Windows 10 build 15035

Windows 10 build 15035 is a build of Windows 10 Creators Update. It was leaked to BetaArchive on 2019-11-24. This build is currently notable to be the only leaked Windows 10 client build available for ARM (ARMv7) processors. It is possible to run this build under QEMU as well as on various other devices that originally shipped with Windows RT or Windows 10 Mobile.

Applications
This build omits certain apps not available for ARM (ARMv7) processors. The only included apps are:


 * Alarms & Clock - Version: 2017.203.236.0
 * Calculator - Version: 2017.131.1904.0
 * Messaging - Version: 3.2.2001.0
 * Microsoft Edge - Version: 40.15035.0.0
 * Feedback Hub - Version: 1.1611.3471.0
 * People - Version: 2017.203.2255.0
 * Settings - Version: 6.2.0.0
 * Tips - Version: 4.5.6.0
 * View 3D Preview - Version: 1.1701.30049.0
 * Voice Recorder - Version: 2017.130.1208.0
 * Xbox - Version: 2017.113.1250.0

Although the included apps are limited there are numerous Microsoft and third party apps still available in addition to updates for the ones listed above which will work on this build without modification and result in a more complete feel to installation.

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 devices, if installed Windows Update will work to provide any available updates for Office 2013 RT.

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 a missing registry entry, this can be resolved by applying the registry entry below:
 * Using Event Viewer or Task Scheduler causes a BSOD error (PANIC_STACK_SWITCH), this only occurs after either one is opened and you attempt to view an entry other than the one selected by default or otherwise interacting with the UI on those windows. One report indicates this is caused by NTFS.sys crashing.
 * On some devices the Screen Brightness setting does not persist after a reboot and Automatic Brightness might not function correctly.
 * On some devices Night Mode may not always function correctly.
 * The legacy Windows Defender UI (MSASCui.exe) is not functional and will terminate with a critical error (0x800b0101).
 * The background color for windows is gray instead of white.

Compatibility

 * 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 (IRQL_NOT_LESS_OR_EQUAL) 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.
 * Use bootarm from Windows RT 8.1 build 9600, the bootarm included with this build would disable the Secure Boot unlock and prevent this build from running.

Miscellaneous

 * Neither Microsoft Print To PDF or Microsoft XPS Document Writer is available after installation due to the respective certificates being outside of the validity period. As any device this build is installed on will be in Test Mode both of these drivers can be manually installed from  and overriding the Driver Signature Enforcement Check when prompted.