Forum Discussion

jmsolanes's avatar
jmsolanes
Brass Contributor
May 07, 2022

I cannot update from 22610.1 to 22616., I see I'm out of Insider - error 0x800bfa0e

I had tried Windows Update after was announcing 22616.1 but I hadn't received it. For my surprise, I see that laptop is not join the Windows Insider Program. I again try to join to the program, but I receive an error 0x800bfa0e.

 

I have computer join to corporate domain, last 5 builds were upgrade without problems. I have control of GPOs and EndPoint Manager policies and it hadn't modifies. I only apply MDM join (not Endpoint policies deliver) and Windows Hello policies (for PIN, Face, fingerprint).

I had removed device from MDM, but I have same result.

 

Do anybody same problem? Do you know how to resolve it?

8 Replies

  • HI jmsolanes 

    Please watch this video - it is worth checking the settings:

    https://www.bing.com/videos/search?q=something+went+wrong+we+arent+able+to+talk+to+our+service+right+now&docid=608032313997145195&mid=9A8D1E138088E65A49379A8D1E138088E65A4937&view=detail&FORM=VIRE

    And this is an old post, but these simple steps still work:

    https://answers.microsoft.com/en-us/insider/forum/all/error-0x800bfa07-when-trying-to-fix-insider-builds/60cc88ac-f5e6-48ad-a174-3cd837887e24

    • jmsolanes's avatar
      jmsolanes
      Brass Contributor
      Thank you, I had tried that without changes. Finally, my option has been doing a clean installation without change any policies in my Active Directory, now It works. Why? I don't know, I hadn't format my computer since las June, first insider version of Windows 11.
      • Deleted's avatar
        Deleted

        jmsolanes 

        The problem probably resulted from the combination of the Beta and Dev channel.
        But now Microsoft has already separated it and there will be no such errors 🙂

  • rtkachuk's avatar
    rtkachuk
    Copper Contributor
    I've no advice to assist, but have the exact same issue. Was fine up until this build, and until we added some WHfB policies.

    now, nothing but 0x800bfa0e

Resources