📎 AI Summary:
The thread concerns Windows Update and ISO upgrade failures (0x80070005 and 0x80070057-0x20003), failed recovery/reset attempts, and concern about a certificate expiring on August 11, with the assistant initially recommending servicing repairs, cache resets, and a Dynamic Update-disabled ISO upgrade. After several unsuccessful log uploads, the site owner acknowledged that attachment-processing bugs—not the user’s files—prevented diagnosis, apologized for the unnecessary steps, and said the existing archive would be analyzed after fixes were deployed. The overall sentiment shifted from user frustration and urgency to an apology and reassurance, but the specific technical fix had not yet been provided.
The thread concerns Windows Update and ISO upgrade failures (0x80070005 and 0x80070057-0x20003), failed recovery/reset attempts, and concern about a certificate expiring on August 11, with the assistant initially recommending servicing repairs, cache resets, and a Dynamic Update-disabled ISO upgrade. After several unsuccessful log uploads, the site owner acknowledged that attachment-processing bugs—not the user’s files—prevented diagnosis, apologized for the unnecessary steps, and said the existing archive would be analyzed after fixes were deployed. The overall sentiment shifted from user frustration and urgency to an apology and reassurance, but the specific technical fix had not yet been provided.
@loopt, thanks for reporting this. Build 29671 has not resolved the upgrade failure on your machine, so simply telling you to wait for a newer build would not be enough.
I also need to correct our earlier certainty: we treated the suspected regression as established too quickly. Your message matches ProfPieHunter’s ISO error, but matching error codes alone do not establish the same underlying cause. SetupDiag and the surrounding Setup log entries are needed to distinguish them.
Please start with these read-only checks, without retrying the installation:
I also need to correct our earlier certainty: we treated the suspected regression as established too quickly. Your message matches ProfPieHunter’s ISO error, but matching error codes alone do not establish the same underlying cause. SetupDiag and the surrounding Setup log entries are needed to distinguish them.
Please start with these read-only checks, without retrying the installation:
- Run
winverand tell us your currently installed build. Are you also upgrading from 29617? - Tell us whether the 29671 attempt used Windows Update or an ISO. If ISO, where did you obtain it?
- In File Explorer, enter
%windir%\Logs\SetupDiagand attachSetupDiagResults.xml, if present. Windows Setup normally writes its automatic diagnostic report there. Please check that its date corresponds to the 29671 attempt. (learn.microsoft.com)
Last edited:
@loopt, your report identifies a specific package-processing failure, rather than confirming the earlier
What remains uncertain: whether the missing package content originated in the UUP-created media, Setup’s update downloads, or another servicing issue. This report alone cannot distinguish those possibilities.
0x80070005 issue.What is confirmed
DISM reported:Setup failed during Safe OS, while adding
Windows.Workload.ExecutionProvider.OpenVino.amd64 from C:\$WINDOWS.~BT\DUImageSandbox, with 0x80070057–0x20003.What remains uncertain: whether the missing package content originated in the UUP-created media, Setup’s update downloads, or another servicing issue. This report alone cannot distinguish those possibilities.
Minimum next checks
- Tell us whether you selected “Not right now” for downloading updates during Setup, or allowed Setup to download them.
- Share
setupact.logandsetuperr.logfromC:\$WINDOWS.~BT\Sources\Panther, corresponding to the September 19, 12:52 failure. Review them for personal information before uploading.
