The new version of Windows 10 Technical Preview released today, brings along some great new features and many changes compared to the previous editions. However, as with any major release, there are a number of bugs and issues, and you should be aware of these before taking the plunge.
According to Microsoft these are the problems you should expect to have with this latest build:
Some people might hit an issue where the username and password boxes do not appear or don’t accept input when logging in, which will prevent them from logging in. Possible workarounds include clicking the “Switch User” button, using Ctrl+Alt+Del, or pressing the power button on your PC to sleep/resume and try again.
It is possible to manually lock your PC during the initial out-of-box experience. If you do this, you will have to hard reboot your PC and restart the OOBE experience. (So don’t lock your PC during OOBE 🙂
There are several accessibility issues in this build, which may make it difficult to use with Narrator or 3rd party screen readers. Additionally there is an issue where using a Lens after enabling Magnifier may cause the screen to be unusable.
You might notice a chess knight icon on your Lock screen to the right of the screen. This was added by the Lock screen team so they could tell via screenshots if someone was using the new Lock screen or the old one, and will eventually be removed in a future build.
Font sizes on the Lock screen on devices with high DPI can be really large.
We currently have the Tablet Mode notification turned off by default to address some of the issues we’ve been seeing. The notifications can be turned back on via Settings.
The touch keyboard doesn’t show up on login screen which prevents you from unlocking your PC when Narrator is on.
Some people might see frequent prompts to restart to install updates, even though no updates need a restart. This prompt can be ignored safely.
As you can see, this list is quite lengthy which means that you should not install this build as your daily driver. After looking at all the issues, now you know why this build is hitting the Fast ring first.
Microsoft has previously released patches for builds of Windows 10 and while we do not know if they intend to do the same here, as they are upping the release cadence of Windows 10, when a build is pushed to the Slow ring, it will be more stable than the Fast ring.