Hi Kelly Fu,
Sorry to hear that you're experiencing updates issue with the new Insider build. And you're correct, based on what other Insider users are reporting, your situation does not appear to be a unique case. I just want to clarify a few things so you can better decide what's the correct path forward:
- The flight certificate expiration will only affect the ability to continue receiving Insider Preview builds. It does not deactivate Windows or invalidate your license. Devices that miss that will only stop receiving new Insider flights until it's updated.
- The
CrossDeviceResume.exeerror is likely a secondary symptom. Since you mentioned using tools that modify permissions on system folders, I would avoid making any further manual ACL/ownership changes. - Windows Insider ISO does not necessarily mean a clean install. In-place upgrade can keep your files and apps:
- If the ISO build matches your Insider channel and is newer than your current build, you can typically launch
setup.exedirectly and perform an in-place upgrade, choosing Keep personal files and apps. - However, this is a suggestion based on standard system corrupt behavior. If the issue you're facing is relating to the build itself, it's not guaranteed that reinstalling Windows may help.
- If the ISO build matches your Insider channel and is newer than your current build, you can typically launch
So before considering the In-Place upgrade, it's reasonable to wait and see if there's any official updates from Microsoft on this. In addition, some users recently recommended focusing on Insider enrollment components when persistent 0x80070005 errors occur. You can try them out in the meantime to see if anything improves:
- Open
services.msc> verify Windows Insider Service (wisvc) exists and is running. - Sign out of the Microsoft account > switch to a local account > restart PC and sign back in.
- Review Event Viewer logs under Microsoft > Windows > WindowsUpdateClient and User Device Registration
Overall, given that numerous users are reporting the same behavior and you've already run the standard repair procedures (started seeing other errors too), I would not continue applying random repair steps in case things get worse. Instead, back up your important files and wait to see whether Microsoft releases a follow-up build or acknowledges the issue publicly.
If you think the answer is helpful to you, please mark this as accepted. If you have extra questions about this answer, feel free to click "Add Comment" and ask!
Note: Follow the steps in our documentation if you want to enable and receive the related email notifications for this thread.