Windows 10 Build 14257 Issues Reported: Failed Installs, DPI Issues, High CPU Usage & More

We’re a little behind with this one, since Windows 10 Redstone Build 14257 was released a few days ago. Nonetheless, we’re going to scan through the forums and find some of the most frequently encountered issues with this specific build.

Microsoft has officially aknowledged, as it always does, a couple of problems with this specific build, but besides that, we’ve detected more that were reported by Windows 10 users, so here’s a couple that we were able to find.

Windows 10 Build 14257 issues

A few Windows 10 users say the aren’t able to to download build 14257:

I restored my laptop thursday by using official iso. I was on build 14251 and I’m now on rtm 10586. I had some problems to connect my session to my microsoft account, resolved by creating a second session and deleting the first one. But the new insider preview don’t want to show in windows update since thursday.

Another quite minor error, according to another Windows 10 user, is that he can’t attach screenshots to the Windows Feedback app. Furthermore, he says his system is recording many errors in the Event Viewer. Somebody else says that after upgrading to Windows 10 build 14257, he is getting win32kfull.sys crashes:

After upgrading to build 14257, shortly after logging in the system steadily crashes in win32kfull.sys (SYSTEM_SERVICE_EXCEPTION),
After recovering the previous 14251 build via winRE (I had to reboot manually since the “reboot” phase dured ages) all is ok again.

One user say that this new build makes the Rainmeter widget fail to start. Someone else says that he is still at Wndows 10 build 14251 which is downloading but not installing, and the same goes for the newest build:

Hi, just like to know if anybody has solved this problem. I am still on build 10240. build no. 14251 downloaded but won’t install. same as build no 14257. I have downloaded iso of 14251 and burnt to dvd. It starts with small windows screen but then it says problem and restart pc.

What seems to be the most widespread error, however, is the fact that many aren’t able to finalize the installation for Windows 10 build 14257. Here are just some testimonials:

I am Windows Insider and I’ve tried to update my Windows 10 by 7 times and on every attempt it returned to build 11099 at 95%. I already googled several outputs, including alternating registry keys, but nothing resolves. I thought it’d be disk space, but I have about 150 GB free and still the problem persists. Upon system returns to the build 11099, it doesn’t even reports an error code (such as 0x80240031).

I started having problems with build 14251 not finishing installing. I tried multiple things trying to fix it and all failed. I finally used my Windows 10 RTM flash drive and deleted all partitions and did a clean install. By that time, build 14257 was up and I am having the same problem with it.

There are Windows 10 users whose peripheral devices have even been affected, such as in the case of this Windows 10 user, who says his mouse has stopped working:

My mouse and sometimes keyboard stops working frequently, requiring a restart. This started happening for me in this build. I had wireless keyboard/mouse and switched to USB ones, but still having issues.

There are even complaints that OneDrive is deleting files in shared/added folders in build 14257. Here’s what one affected user has been saying:

There is already Insider feedback that OneDrive is not syncing Shared/Added folders, but in fact is is actually deleting the files on the PC. As I keep backups of my backup I can deal with this, but I won’t be using OneDrive again until I know this is fixed.

Moving forward, we’ve seen people complaining about DPI issues, some cannot change the default browser and others even complain that YouTube on Microsoft Edge is now getting the infamous ‘An error occurred. Please try again later’. One Surface Pro 3 owner says build 14257 is making his headphone audio garbled:

Audio is totally garbled (sounds as though there are channels missing and what is there is phasing in and out) while attempting to listen through my headphones (the headphones are fine – tested on several other devices and sound great). This happens regardless of the program running – whether it’s video or music. I don’t recall this being a known issue with Build 14257 but perhaps I missed it?

Users also complain about high CPU and memory usage while some say they have start up issues with the last 2 builds (14251, 14257), getting a blue screen error. Do leave your comment below and let us know what other issues have you been noticing.