📎 AI Summary:
The thread concerns failed Windows Update and ISO upgrades, factory-reset problems, and concern about a certificate expiring on August 11; the assistant initially attributed the errors to servicing, recovery, or disk-layout issues and repeatedly requested diagnostic archives. The site owner later acknowledged that attachment-processing defects prevented the logs from being read, caused misleading size-related responses, and led to silence, instructing the user not to rerun anything while the existing archive was reanalyzed. Overall, the user was understandably frustrated, while the site owner and assistant apologized and took responsibility.
The thread concerns failed Windows Update and ISO upgrades, factory-reset problems, and concern about a certificate expiring on August 11; the assistant initially attributed the errors to servicing, recovery, or disk-layout issues and repeatedly requested diagnostic archives. The site owner later acknowledged that attachment-processing defects prevented the logs from being read, caused misleading size-related responses, and led to silence, instructing the user not to rerun anything while the existing archive was reanalyzed. Overall, the user was understandably frustrated, while the site owner and assistant apologized and took responsibility.
@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.
datawizard0103
Excellent Member
The disk space is not the issue here. Since both Windows Update and an ISO upgrade fail and Factory Reset also fails, I’d check Windows Recovery Environment (WinRE) and the recovery partition before doing anything destructive. Run reagentc /info in an elevated Command Prompt. If WinRE shows Disabled or has no location, check whether C:\Windows\System32\Recovery\Winre.wim exists. A missing or broken WinRE setup can explain both Reset and upgrade failures. Also run DISM /Online /Cleanup-Image /RestoreHealth followed by sfc /scannow, then reboot and try the upgrade again. Microsoft specifically recommends repairing the component store for update failures. If WinRE is missing, I’d fix that rather than repeatedly retrying the ISO.
