Microsoft has been in the smartphone market for nearly two years with its dual-screen Android phone, the Surface Duo. The device was not a huge sales success, but it did attract a loyal customer base. In September 2022, Microsoft released the Surface Duo 2. Both devices offer the openness of Android with unique features from Microsoft. However, the latest software update for the Surface Duo and Surface Duo 2 is causing some major problems. Here are the details…

Microsoft Surface Duo Users Report Random Reboots After Installing May 2023 Update

If you’re developing a smartphone with two screens and aiming to create some advantages that dual-screen offers, your task is quite challenging. Even Microsoft, a company valued at $141.6 billion and employing 221,000 people worldwide, is struggling to achieve this. We all remember the software issues that were present at the launch of the Surface Duo and Surface Duo 2. Although this situation was not well-received by some users, we all acknowledged the problems that Android phones had when they first launched. Especially after the bug festival that Google Pixel models presented to their users and us.

However, bugs coming with updates long after their release, are simply unacceptable. Unfortunately, this is precisely what Surface Duo and Duo 2 users are experiencing. A recent May 2023 security update has introduced new and serious issues. Users from all over the world have reported that their devices are randomly rebooting after installing the update. The subsequent reboot screen apparently also asks users whether they’d like to try booting up again or factory resetting their device. Even though these issues are driving users insane, they won’t last long.

Microsoft, aware of the problem users are facing, made a statement about the issue to a competitor as respectable as Gizmochina, saying: “Microsoft is aware and is looking into it. For additional information please refer to our Microsoft’s Q&A community page: Surface Duo 2 – permanent reboots after Update May 30 2023 – Microsoft Community.” Unfortunately, the statement did not provide information on when the problem would be resolved.

RELATED:

(via)