Hello Windows Insiders!
We’ve received reports of users hitting error code 80096004 when attempting to install a build via Windows Update. We kicked off our investigation process and have information to share.
Who:
Windows Insiders attempting to download/install any current development branch build up-to and including 17046 in either the Fast or Slow ring via Windows Update.
ISO-based installs are not affected.
What:
During the initial download and verification process, the install will fail with error code 80096004.
Additionally, any attempted downloads of language packs or additional Windows features (FODs) will also encounter an install failure for the affected builds.
When:
This is a recent issue, appearing within the past week (since approximately December 1st).
Why/Root Cause:
Investigation of the issue has led us to the root cause of the issue which is a bug in the way we sign the files (.cabs) for builds that are delivered via UUP.
Mitigation/Bypass:
There are no steps that can be taken on individual PCs to bypass this issue. See below for additional details. Also, no steps are required by Windows Insiders to receive and install the next preview build that will be released via Flighting. Simply wait for another build to be released to the ring you’ve selected. In the interim, we’ve paused build availability to prevent user machines from needlessly downloading and failing the build install.
What happened? A bug has been discovered in the way we sign the files for builds delivered via flighting that which impacts all Insider Preview builds from 17000 through 17046.
As such, any attempted installs of builds in this range will fail with the error code noted above.
There are no long-term issues created by this scenario. The bug has been fixed and newer preview builds being tested internally are not affected.
As noted, we’ve paused the availability of builds in the Fast and Slow rings. For any user who already has a build installed, there is no concern. You many continue using the build as expected. Pausing the Flights was done simply to conserve user bandwidth and prevent confusion from any additional installs of the affected builds which would have all resulted in a failure and error code. If you attempt to install a build from the Fast or Slow ring at this time, your machine will simply show that it is up-to-date.
If there are any additional questions, please post below so we may review. And worth reiterating, there’s no action required on your part. Simply wait for the next build to be released to the ring of your choice and your machine should update as expected.
Thank you to all Windows Insiders who filed feedback and reported this issue!
- Jason