#Windows10 #Windows10Mobile – How to Fix a Device Bricked by Windows 10 : Microsoft accidentally published Windows 10 build 16212 earlier today and, as we’ve already reported, it appears that this release bricks smartphones by pushing them into an infinite reboot loop.
While there are no major bugs on PCs, Microsoft says that everyone receiving this build shouldn’t use it, as it wasn’t supposed to be released for public users.
In the case of PCs that got it, Microsoft says that users can wait until a new build is released and then update through Windows Update or simply roll back to the previous build from Settings > Update & security > Recovery. This process needs to be started in the next 10 days as per the rollback policy and works only if you do not use Disk Cleanup to remove previous Windows installation.
No new builds coming this week
What’s important to know is that, should you decide to wait until a new build is released, Microsoft has no plans to roll out a new build this week after today’s fiasco.
Also, in the case of PCs offered build 16212 even if they weren’t enrolled in the Windows Insider program, Dona Sarkar explains that a small number of systems indeed received this build, but they couldn’t install it. The build only showed up in Windows Update, but nobody in the production ring was allowed to install.
For Windows 10 users who received the build on mobile devices, Microsoft says it won’t install on the device, but if you already did that, the smartphone is stuck in a reboot loop. This means that recovering it with the WDRT and resetting the phone is the only option, which means you’re going to lose all your files.
Smartphones that received the build and didn’t install it need to reset as well, but a backup in this case is available from Settings > Update & security > Backup.