Windows 10 Build 15035 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:Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System]"EnableLUA"=dword:00000000
- Cameras will not work even with the appropriate app and drivers installed due a missing registry entry, this can be resolved by applying the registry entry below:Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Media Foundation\Platform]"EnableFrameServerMode"=dword:00000000
- Using Microsoft Management Console (MMC) snap-ins can cause a BSOD error (PANIC_STACK_SWITCH). 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.
- The Screen Brightness setting does not persist after a reboot and Automatic Brightness does not always function correctly.
- Night Mode does not function correctly.
- The background colour for windows is gray instead of white.
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 (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.
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 (MSASCui.exe) is not functional and will terminate with a critical error (0x800b0101).
- The Diagnostics Troubleshooting Wizard is not functional and will terminate with a critical error (0x800b0101).
- 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
\Windows\System32\spool\toolsand overriding the Driver Signature Enforcement Check when prompted.
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.