Windows 10 build 20236.1000

Windows 10 build 20236.1000 is the seventeenth Insider Preview build of Iron. This build was released to Windows Insiders in the Dev Channel on 14 October 2020. A few hours prior to this build's release, some screenshots of this build were shown by a Microsoft employee on some GitHub threads.

New features and changes

 * You can now change the refresh rate of your displays from the advanced display settings page located under Settings → System → Display.
 * The updated emoji picker and touch keyboard from build 20206 were rolled out to all Insiders on the Dev Channel, but they were only enabled on upgraded installations, clean installations have these features disabled by default.

Bugs

 * New applications will fail to install and instead return with a Windows Installer service error on x86 versions of this build.
 * Attempting to perform a Reset this PC operation using the Keep My Files option will fail with the error “There was a problem resetting your PC. No changes were made”.
 * The update process to this build has a chance of hanging for extended periods of time.
 * Live preview doesn't work for pinned site tabs on some machines, a gray window is seen instead of the intended content.
 * There's a chance of randomly encountering a BSOD with the error code  when using certain virtualization technologies.
 * Selecting an IME candidate or hardware keyboard text prediction candidate may insert the candidate adjacent to the one selected.
 * On some PCs, the taskbar is obscuring the Power button in the Start menu blocking the access to its options. To workaround this issue, use the options from the User menu ( Win + X ).
 * There's a chance of randomly encountering a  BSOD.
 * GPU Compute scenarios, such as using CUDA and DirectML, are not working inside of the Windows Subsystem for Linux.
 * Windows PowerShell does not work on the ARM64 versions of this build. To use the app, open up “Windows PowerShell (x86)” or “Windows PowerShell ISE (x86)”, which is located on the Start menu instead.
 * Installing games downloaded from the Microsoft Store to a secondary drive that has no OS on it will result in the secondary drive becoming inaccessible. To prevent this bug from occurring, the default storage location for new content must be changed prior to installing the game. This can be done by navigating to Settings → Storage → Change where new content is saved.

Installation
"In the guide below, '#' signifies the drive where the mounted ISO is located in setup, while '%' indicates an index in that is listed by the dism /get-wiminfo command, while 'X' is the drive (usually 'C') that the operating system is being installed to, and '?' is the volume that contains the majority of the disk space."
 * Some UUP-converted ISOs of this build have a bug that causes setup to encounter an error when attempting to start setup normally. This includes the copies stored on the BetaArchive FTP server. To bypass it, you must follow the instructions below.
 * Create a VM in VMware as you normally would, but use UEFI instead of BIOS.
 * Start the setup using an ISO of a different build. Proceed normally until you arrive to the drive partition page. Once you're on that page, click on the New button, then click on Apply, then click on OK on the message that appears. After setup creates the partition, insert the affected ISO and then restart the VM.
 * Once you are back on 20236, press Shift + F10 to open up Command Prompt.
 * Type in . When   opens, type in   to list the volumes. Assign a drive letter to the volume whose file system is marked as "RAW". This can be done by typing in   ("?" being the number of the volume that usually contains the majority of disk space), then typing in.
 * After assigning a drive letter, check the drive letter assignment by entering in.
 * Exit.
 * After exiting, format the drive by typing in  , then apply the installation image by using DISM.  It is recommended to check the list of SKUs that you want by typing in.
 * Start the installation by using
 * After DISM finishes copying the files, use  to create the boot records on the drive that it was installed on.
 * Restart the VM after all the aforementioned steps are done, and if done correctly, it will proceed like a normal install.