We can say that build 14251 is the most troublesome Windows 10 Preview build released in the recent time, because there’s a huge amount of complaints on Microsoft forums. So, in case you still didn’t upgrade your Windows 10 Preview to the latest version, we’re going to inform you about the possible issues, so you can know what to expect.

Windows 10 Preview Build 14251 Reported Issues

First reported problem we spotted on Microsoft forums is the problem with BSOD when installing the latest build. One user reported that when he/she tries to install the build, computer restarts, and the BSOD appears. “When I update to build 14251, it went through the first stage “copying files” well, then after reboot it went to BSoD, with info “INACCESSIBLE_BOOT_DEVICE”.” A Microsoft Support Engineer reach to the user with the possible solution, but there was no answer, so we can’t confirm if the solution is working. However, if you want to try the suggested solution, you can check it out at Microsoft forums, but once again, nobody confirmed that it works. Next thing users reported on Microsoft forums is the error 0x80240031 when trying to install the update. So as you can see, some users can’t even install the latest Windows 10 Preview build. “I am trying to upgrade from Insider Preview build 11102 to 14251 and I get the error message Windows 10 Insider Preview 14251 – Error 0x80240031” “Ran update 3 times cant update to next build keeps going back to previous build” Support engineers suggested some basic, cliché solutions for this error, but you can guess, these are not helpful. We don’t have an exact solution for the problem, but you can try some of our solutions for Windows 10 Update errors, and maybe you’ll get lucky. These users are not alone, as some other users reported other update errors, like the error 0x80070001. “Pl.solve the error for updating and  installing latest build  Windows 10 Insider Preview 14251 – Error 0x80070001 and retry. Again  I retried , but no result was resolved.” Again, no fixes have been provided by Microsoft. Another issue that bothered some users is the error with Services. User who reported this issue is apparently from South Korea, so we’re not sure about the error which causes this issue, but some users from other parts of the world also confirmed the problem. “services.msc Script Error in Windows 10 Build 14251 64bit Home Edition.  What should I do?” SPONSORED “Nothing happens when you click yes or no, but clicking on the X closes the window, without loading the gpedit or services content.” This is quite a serious issue, because Services script is an important part of the system, and Microsoft should quickly provide a solution, but its support engineers remain silent on Microsoft community forum. Besides abovementioned BSODs, some users are also unable to boot their systems normally after the update. A lot of users have reported that their system now boots in the Recovery Mode, and the only possible known solution is to re-install the system. “When upgrading from 1099 to 14251 the update begins installing then reboots into recovery mode with no option to simply upgrade like it has previous builds. I simply have too much stuff installed to reset my system and if that’s the only recourse I’ll just drop out of the Insider program and go back to Threshold 2.” One fellow Insider recommended a solution, but it wasn’t helpful. No actions from Microsoft, again. Users are even having problems with third party apps and games after they installed Build 14251. So, one user complained on Forums that he’s not able to use Git anymore, because of the constant crashes.[nextpage title=”Go to Page 2″] “I have updated my Surface Pro 3 and my desktop PC to 14251, and now Git keeps crashing. Anyone has any idea? I have already tried to reinstall Git.” And another user reported that he’s unable to play older games from Windows 7 since he installed the latest update. “I’ve been installing Windows 7 games for Windows 10 with every new build but 11099 and 14251 prevent them from running. What can be done to allow them to run as they have done with every previous preview build? The versions in the “Store” are horrible.” You can guess what Microsoft engineers said about these issues. You’re right, nothing! The latest Windows 10 Preview build apparently removed Windows Remote Server Administration for Windows 10. Microsoft didn’t say anything about this before, but some users assume that it won’t be supported in Windows 10 until the Redstone build is released. Again, these are just speculations, as we have no official word from Microsoft. “Previous builds have removed the Windows Remote Server Administration Tools, however, Build 14251 removes RSAT and does not allow it to be reinstalled, erroring with “Installer encountered an error: 0x80240043” “Just incase you have a win10 box at work you use with RSAT (like me), you’ve been warned. Hopefully we’ll see a bugfix for this issue in the next build.”

Name * Email * Commenting as . Not you? Save information for future comments
Comment

Δ