Feedback Hub and Settings Insider error CAA5004B

Have you gone to Settings, Account, and verified your account?

Have you set your Diagnostics to full?

I am having the same issue.

What do you mean by reset the computer completely.

I added local accounts after installing the update so Recovery will not let me uninstall the update.

Basically factory resetting the Device was the only way to renable it.  Was your machine initially added to azure AD?  I tried to troubleshoot it and it appears as though it cannot logon as windows hello requires a Pin but cannot be set - I blogged about it here https://www.onthewinside.com/blog/navigating-windows-insider-18317-issues

I initially setup my machine on AzureAD so I didn't even have a local account. I also renamed my computer after joining AzureAD.

I tried "Go back to the previous version of Windows 10", but Windows would not allow it because I had added the local account after installing the update. I may try the reset instead, maybe I will have better luck with that.

Thanks

I'm having this problem, too (also on AzureAD). It is affecting Windows Hello PIN, in addition to the Feedback Hub. PIN configuration in the Settings app says, "something went wrong". Also, after the first login, my password will no longer work.

I've been able to restore to a previous version to work around the issue, but each re-update causes the same problems.

FWIW: I'm on 18323

I have exactly the same experience, basically got locked out of my Surface Book as I only use Azure AD logon, so rebuild and back to 18323 and I can logon with my password, Hello keeps saying it has to have a pin, but that is how I set it up. And to add to this, my Office 365 account cannot be added to Outlook as it fails with CAA5004B, and mail keeps prompting me to fix my account with the same result of CAA5004B.

I have reverted to using outlook.office.com for email and am hoping this is a build issue and the next update fixes it. Thankfully everything is stored in a few onedrives.

Also my Windows Hello and PIN worked fine for a day or so after the rebuild, but now both don't work, so make sure you have a second account to logon or be prepared for yet another rebuild.