Getting error 0x80070002 when installing 25967 update even after trying every major fix!

I am currently running the Insider Preview Canary 25951 Prerelease build on my Dell G15 5510, and have been trying and consistently failing to upgrade to the 25967 Canary release for the past 2 days through Windows Update. I can't install Canary 25967 build despite trying multiple fixes such as running Windows Update troubleshooter, system file checker and DISM commands, ensuring system date & time are correct, deleting SoftwareDistribution folder to redownload the update from scratch! I even ran CHKDSK and Windows Memory Diagnostic when all else failed, but to no avail! Could someone PLEASE help me? This laptop is the only computer I own, and I initially joined the Dev channel only to get Windows 11 as soon as it was released through the Insider Preview. Microsoft then forcibly converted the Dev channel to the Canary channel, and now I'm stuck with an update that refuses to install and keeps reverting mid-installation with the message "Undoing changes made to your computer", and then giving the 0x80070002 error code after reboot.

Hi and welcome to the forum.
Sorry you are having issues with the update to 25967.
I am not sure what you mean by 'major fix' but have you tried downloading the ISO?
It takes a bit longer but at least you have an image to work with.

Welcome to the forum. First let me say I'm not an insider any more so others can probably advise you better than I can. I decided right quick it was just too much trouble to be an insider on one's main machine.
I believe your issue has something to do with you using an expiring build. The Insiders here will correct me if I am incorrect.

On the Insider site MS states "To move off the Insider Preview build expiring on your device, you can either get preview builds in the Dev Channel, reinstall Windows using a Windows Insider ISO to move to the Beta channel, or start fresh with a clean installation of Windows
reference Using ISOs - Windows Insider Program


Here's a discussion on MS forum

OAT said:

Hi and welcome to the forum.
Sorry you are having issues with the update to 25967.
I am not sure what you mean by 'major fix' but have you tried downloading the ISO?
It takes a bit longer but at least you have an image to work with.

UUP (Unified Update Platform) Generation Project (v2.4.18) [by @rgadguard & whatever127]

This project helps you just download UUP files or download and create an ISO image in one click.

uup.rg-adguard.net

Click to expand...

Thank you SO much! I actually didn't know about this website! I only looked at Microsoft's own website, and the latest 25967 build wasn't available there! I will try installing the new build through this method! Thanks again!

glasskuter said:

Welcome to the forum. First let me say I'm not an insider any more so others can probably advise you better than I can. I decided right quick it was just too much trouble to be an insider on one's main machine.
I believe your issue has something to do with you using an expiring build. The Insiders here will correct me if I am incorrect.

On the Insider site MS states "To move off the Insider Preview build expiring on your device, you can either get preview builds in the Dev Channel, reinstall Windows using a Windows Insider ISO to move to the Beta channel, or start fresh with a clean installation of Windows
reference Using ISOs - Windows Insider Program


Here's a discussion on MS forum

I cant leave canary channel in windows insider

first, i join windows insider and then i accidentaly click canary build but at first i didnt notice it. Then i just keep update my windows until now and have..

techcommunity.microsoft.com

Click to expand...

Thank you so much for replying! You are absolutely correct that it is certainly unadvisable and quite a hassle to have an experimental build running on one's primary computer! But the fact is, I have pretty much come to terms with this situation, and more importantly, I just can't risk losing all my data reverting to a more stable build of Windows, at least not for now, as I'm still hopeful that Microsoft would eventually fix this issue, and more importantly, my current build is nowhere near its date of expiry. But still, thank you so much for showing me this route! I will probably have to revert to a stable release if Microsoft refuses to fix this issue, which I certainly hope won't be the case!