Windows 10 build 17112 breaks Mixed Reality and Microsoft Store [FIX]

by Madalina Dinita
Madalina Dinita
Madalina Dinita
Windows & Software Expert
Madalina has been a Windows fan ever since she got her hands on her first Windows XP computer. She is interested in all things technology, especially emerging technologies... read more
Affiliate Disclosure

Microsoft rolled out a new Windows 10 built to Fast Ring Insiders. Yes, if you had any plans for the weekend, you should change your schedule a bit in order to add a few hours for testing the new build.

Unlike the previous builds, Windows 10 build 17112 doesn’t bring any new features focusing instead of improving the overall system stability.

However, many Insiders already wish they had skipped this build release due to the issues that they encountered.

This article will show you what you can expect in terms of bugs after installing build 17112. If you already installed it, then this post will make you feel a bit better knowing that you’re not the only one experiencing these problems.

Windows 10 build 17112 issues

  1. Windows Mixed Reality won’t work
  2. The Microsoft Store disappears [FIX]
  3. Green screen of Death
  4. USB mouse won’t work
  5. Processes are ‘suspended’ in Task Manager

1. Windows Mixed Reality won’t work

If you use Windows Mixed Reality on a daily basis, it’s best to simply skip this build. Windows Mixed Reality runs at about 8-10fps on this build version. Moreover, there are frequent crashes at startup which will prevent you from actually launching WMR.

You can pause the build update by going to Settings > Update & Security >Windows Insider Program>  select ‘Stop Insider Preview builds’ > click on ‘Pause updates for a bit’.

Geoff, an engineer working on the WMR team at Microsoft offered more explanations about this problem on Reddit:

Although this update fixes several issues, it also causes severe performance issues in Windows Mixed Reality, including SteamVR. If you joined the Insider program […]we recommend you pause updates for a time and stay on 17110. […] This issue will be fixed in the next build we publish.

2. The Microsoft Store disappears [FIX]

fix microsoft store powershell

Insiders who installed build 17112 can’t use the Microsoft Store due to various issues that include pinned tiles missing on Start/Taskbar, apps won’t show in “All Apps” list / Start, the Store is missing from Settings > Apps & Features, and more.

Fortunately, there is a quick workaround available that should help most users fix this problem. Here are the steps to follow:

  1. Restart your computer
  2. Launch Powershell with Admin permissions
  3. Enter the following command:
    • Get-AppXPackage *WindowsStore* -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)AppXManifest.xml”}
  4. Restart your machine again and check if the Microsoft Store is available.

Keep in mind that you should not try to reset the Microsoft Store app. This action will remove all visible traces of the app from your PC and you won’t be able to reinstall it.

3. Green screen of Death

If you decided to install build 17112 on your Windows 10 computer, you should limit OneDrive use. If you open a file that is available online-only from OneDrive, you may experience GSOD errors.

Fortunately, you can avoid this error by right-clicking on the respective files and selecting “Always keep on this device.”

If the issue persists, use this troubleshooting guide to fix it.

4. USB mouse won’t work

Some users reported that USB mouse devices fail to work on build 17112. The devices are unresponsive and the cursor won’t move at all.

have some mouse usb isue.. like some stoping work ( i move with mouse but not move) mouse is mx master logitech

Use the troubleshooting  guides below to fix mouse issues on Windows 10:

5. Processes are ‘suspended’ in Task Manager

task manager process suspended

If all the Task Manager processes appear suspended, you’re not the only one.

So, I guess this is how Task Manager is going to look now? Everything is “suspended” at first glance, even things that can’t be, like Win32 apps, and it’s left to the user to intuit that if the word “Suspended” is preceded by a “0” then it’s NOT actually suspended, whereas if it’s preceded by a 1, 2, or 3 it is, and that that number signifies…uh…maybe a level of suspension?

Well, these are the most frequent build 17112 issues reported by Insiders.

Have you installed build 17112 on your computer? Tell us more about your Insider experience in the comments below.


This article covers:Topics: