We've been seeing the same problem since yesterday 12/7 We can work around it by installing an older build from a previous version or a current version prior to 12/ 7, then upgrading it to the latest. (See mtzatzos comment above) Posted issue FB11861318