Well look for errors starting from the end of the logs. Sometimes they are quite selfexplanatory, sometimes they aren't, but you have to start somewhere.
Well, I was able to get a log from setuperr.log. These are from immediately after attempting the upgrade: [ReAgentc.exe] IOCTL_STORAGE_QUERY_PROPERTY failed: 0x32 [ReAgentc.exe] BcdOpenObject(WinRE) failed: 0xc0000034 [ReAgentc.exe] BcdOpenObject(WinRE) failed: 0xc0000034 [ReAgentc.exe] winreConvertDirNameToOffset failed: 0x3 [ReAgentc.exe] failed to install winre: : 0x3 [ReAgentc.exe] BcdOpenObject(WinRE) failed: 0xc0000034 [ReAgentc.exe] IOCTL_STORAGE_QUERY_PROPERTY failed: 0x32 [ReAgentc.exe] WinReUnInstall failed: : 0x2 [ReAgentc.exe] IOCTL_STORAGE_QUERY_PROPERTY failed: 0x32 [ReAgentc.exe] BcdOpenObject(WinRE) failed: 0xc0000034 [ReAgentc.exe] BcdOpenStore failed for \Device\HarddiskVolume4\EFI\Microsoft\Recovery\BCD: 0xc000000f [ReAgentc.exe] Failed to open recovery BCD store: 0x2 [ReAgentc.exe] IOCTL_STORAGE_QUERY_PROPERTY failed: 0x32 EDIT: I randomly found someone in a similar predicament. I had to delete the Provisioning folder and a key in the registry, then the upgrade proceeded successfully. Now I just have a sticky update that won't progress, kb5034015
Glad my suggestion helped. For KB5034015, frankly (aside the academical curiosity) I wouldn't waste time trying to fix it. Updates on preview builds that are going to be in place upgraded each month or so are pointless, perhaps it's likely that update is shown by mistake...
It's possible, but the update is stuck. It will download and never install. Searching for new updates only brings up KB5034015. So I'm sort of stuck in a loop now. I can't even hide the update through any of the usual methods.
I understand but what the practical problem is supposed to be? There isn't any meaningful update for beta OSes, so obviously you don't see anything other than the bogus update, nor you will see any in the future, except some useless defender updates. So just ignore it, if a popup annoys you, just stop the WU service, clanup the softwaredistribution folder, and use winaerotweaker to disable WU altogether.
LCU updates are broken on Canary for a year after cleanup (and with resetbase) the "fix" is to build ISO without cleanup and perform in-place upgrade, don't forget to disable scheduled cleanup after the upgrade
Well that's a better answer than 'there is no fix'. I have no clue how to do that, I don't suppose there's a tut anywhere?
get MSFT ISO, use W10UI to integrate full updates set: defender-dism-x64_24.01.2024.cab windows10.0-kb5034016-x64_General_1010.1.0.cab windows10.0-kb5034017-x64_DU.SafeOS_1010.1.0.cab windows11.0-kb5034015-x64_LCU_1010.1.0.msu windows11.0-kb5034478-x64-ndp481_CU_9220.4.cab you can get these updates on UUP dump for example in W10UI settings enable LCUwinre, UpdtBootFiles (and Net35 if you wish) options | never enable cleanup for Canary builds after that perform in-place upgrade from that ISO yep, we were supposed to get new build two weeks ago and MSFT can't fix some bug, maybe it's about very old LCU re-installation issue