Outlook broke after Office 365 update to 16.0.19328.20158 – cannot open emails Windows Server 2016
Hello everyone, posting to report that after the latest automatic update to Microsoft Office 365 version 16.0.19328.20158, we are experiencing a critical issue on multiple company machines running Windows Server 2016: The Outlook desktop application launches normally, but when trying to open any email, the following error appears: “There was a problem opening this item... The text formatting command is not available... Reinstall Microsoft Outlook.” Launching Outlook in safe mode (Outlook /safe) does not help. Creating the FORMS2 folder (suggested workaround) does not fix it. Attempting a downgrade via OfficeC2RClient.exe fails with error 30183-27 (400). Quick/online repair from Control Panel also has no effect. In our environment, this issue appeared simultaneously on many workstations and servers, right after the Office update today. Temporary solution: We are instructing users to access their mail via Outlook Web App (OWA), which is not affected by this bug. We would like to know: If others have experienced this bug with this build, including on Windows Server 2016 If any working workaround exists, or an official fix timeframe from Microsoft Thanks to anyone who can share their experience or updates!Enable Moderation and Administrative Oversight for Outlook Newsletter
I’m requesting the ability to become the full administrator of Outlook newsletters not just in my organization, but across Microsoft 365. I want to manage templates, delivery settings, analytics, and permissions. My goal is to have broader control over how newsletters are created, customized, and distributed. I’m passionate about communication and want to help shape how newsletters work in Outlook. Please consider adding a role or feature that allows users like me to take ownership and lead newsletter strategy across organizations. I’ve seen cases where people used newsletters to share inappropriate content, including profanity and offensive language. Without proper moderation tools, this can damage professional communication and create serious issues. I want to help prevent misuse by having the ability to moderate, approve, or restrict newsletter content before it’s sent. I also want to contribute to improving the overall design and performance of the newsletter experience, making it more intuitive, professional, and reliable. Giving users like me full control over Outlook newsletters would improve communication quality, prevent abuse, and empower responsible leadership across organizations. If exclusive admin control isn’t granted, at minimum there should be a designated Admin role because without clear ownership, misuse and poor communication will continue unchecked. I’m ready to take on that responsibility and help shape the future of Outlook newsletters.
Microsoft Graph rich subscription creation fails for GCC clients.
I’m trying to create a Microsoft Graph subscription to watch Outlook events with encrypted resource data. My request body looks like this: { "changeType":"updated,deleted", "notificationUrl":"https://my-inbound.url", "lifecycleNotificationUrl":"https://my-inbound.url", "resource":"users/<redacted>/events?$select=id,subject,start,end,attendees,isCancelled,isOrganizer,iCalUId,uid,bodyPreview,uid,organizer,onlineMeeting,onlineMeetingUrl,changeKey,sensitivity,lastModifiedDateTime,originalEndTimeZone,createdDateTime,allowNewTimeProposals,hasAttachments,singleValueExtendedProperties", "expirationDateTime":"2025-08-15T12:02:19.124967+00:00", "includeResourceData":true, "clientState":"<redacted>", "encryptionCertificate":"<redacted>", "encryptionCertificateId":"<redacted>" } When I POST to: https://graph.microsoft.us/v1.0/subscriptions I get the following error: { "error": { "code": "ExtensionError", "message": "Operation: Create; Exception: [Status Code: BadRequest; Reason: were unable to deserialize ]", "innerError": { "date": "2025-08-13T12:18:05", "request-id": "cde172db-4cc2-4cd2-9e1c-63f46f36d0e3", "client-request-id": "cde172db-4cc2-4cd2-9e1c-63f46f36d0e3" } } } This request payload works for all our clients except those on Microsoft GCC High. Is there a different setup required when configuring clients in GCC High?
