Windows 10 build 15061 is here, as the second Preview build Microsoft released this week. With this build, Microsoft pushed a few more bug fixes and system improvements, that the development team missed with build 15060.
However, even though the build has been around for less than 24 hours, users have still managed to report some of the issues it causes. So, in this article, we’re going to talk about issues caused by Windows 10 build 15061, so you can know what to expect from it, in case you haven’t installed it yet.
Windows 10 build 15061 reported problems
Some users are unable to install the new build, due to the error
0x80091007. Here’s what one of them says on the forums:
Trying to upgrade from 15058 to 15061 fails with the same error code 0x800b109, similar to the upgrade to 15046. In the case of 15046, I ultimately had to reinstall the Preview version from DVD. I checked with the latestwu.diagcab. Initially, a problem was detected and repaired. The second time it is indicated that the problem solver is not able to repair the problem.
Unfortunately, no one had a proper solution for this problem, so we can’t say for sure what the workaround is. However, if you’ve encountered the same problem, try running the WUReset script. However, this is not a confirmed solution.
There’s another installation issue that’s preventing users from installing the latest build. This time, it’s the error
0x800b0109, which points out that some update files are not correctly signed. Here’s what one Insider says about the problem:
Trying to upgrade from 15058 to 15061 fails with the same error code 0x800b109, similar to the upgrade to 15046.
It’s the same situation as with the previous error, as no one managed to provide a viable solution for this problem. So, alternative solutions are, for now, the only hope.
That’s about it. As you can see, installation issues are the main problem of Windows 10 build 15061. That’s not surprising since this build is a tiny release, that brings just a few changes to the system. It usually takes a ‘bigger’ build to cause more major problems.
Unfortunately, no one had a proper solution for this problem, so we can’t say for sure what the workaround is. However, if you’ve encountered the same problem, try running
the WUReset script. However, this is not a confirmed solution.
source:windowsreport
