My issue is your lack of common sense and ever decline products.

Lejeune, P 0 Reputation points
2026-02-27T18:36:38.3833333+00:00

Aside from the fact that Microsoft appears to be working diligently to reduce the rather mediocre quality of its products, you also need assistance in understanding language. When I am writing an email, it changes with every character I type. Then when I go to send it I am told it cannot send because it has been altered. Whoever reads this needs to understand that the very act of composing a document entails altering it. Every NEW character is, by definition new. So you can imagine my irritation that some bright little techie person has decided not to send something because it has been written using more than one word. I am sure this will be totally ignored but if you could focus on leaving well alone instead of tinkering with it so you can earn your probably excessive paychecks it would be wonderful. Why the Child requirment, is it so the child like programmers can understand?

Outlook | Web | Outlook.com | Email
0 comments

1 answer

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-02-27T18:36:57.8033333+00:00

    The behavior described while composing and sending email is not fully detailed in the available documentation, but there are a few known Outlook-related issues and settings that can cause confusing behavior when typing or sending messages.

    For issues where Outlook changes language, characters, or text unexpectedly while composing:

    1. Classic Outlook replacing characters with question marks (extended or accented characters, symbols like ®, £, etc.):
      • This is a known issue in Outlook for Microsoft 365 Version 2601 (Build 19628.20150+).
      • Workarounds include:
        • Use Outlook on the web or New Outlook instead of classic Outlook.
        • In classic Outlook: go to File > Options > Advanced > International Options and:
          • Uncheck Automatically select encoding for outgoing messages (Workaround #2), and/or
          • Set Preferred encoding for outgoing messages to Unicode (UTF-8) (Workaround #3).
        • If necessary, revert Outlook to the prior version 2512 (Build 19530.20184) using the documented Click-to-Run command, and temporarily disable automatic updates until the fix is released.
    2. Strange or mixed characters in message bodies or meeting requests:
      • This can be caused by the Windows “Beta: Use Unicode for UTF-8 worldwide language support” setting.
      • To work around it on Windows:
        1. Open Settings.
        2. Go to Time & Language > Language.
        3. Under Related settings, select Administrative language settings.
        4. In Language for non-Unicode programs, select Change system locale.
        5. Clear Beta: Use Unicode for UTF-8 worldwide language support.
        6. Restart the computer.
    3. New Outlook / Outlook.com auto-features that interfere with typing (for example, auto-capitalization or Editor behavior):
      • In Outlook.com or new Outlook on the web, auto-capitalization and other Editor behaviors can be turned off while composing a message:
        1. Start composing a new message or reply.
        2. On the message toolbar, expand the toolbar (small down-arrow if it is collapsed).
        3. Select Message on the toolbar.
        4. Select Editor on the far right.
        5. Open Editor Settings.
        6. Turn off Enable Auto Capitalization and any other Editor options that are changing text in unwanted ways.
    4. New Outlook Editor language switching unexpectedly:
      • There was a known issue where Microsoft Editor proofing/spellcheck languages in new Outlook for Windows could change unexpectedly (default language switching, languages disappearing, or order changing). This has been fixed service-side as of December 2024.
      • If language switching was part of the problem, ensure the Editor language settings are now correct using the guidance in Check spelling before sending a message.

    If the product reports that a message “cannot be sent because it has been altered,” this typically indicates Outlook or a related component believes the message content or encoding changed in a way that conflicts with its current settings or a known bug. Applying the encoding workarounds above, disabling problematic auto-features (such as auto-capitalization/Editor behaviors), or using Outlook on the web or New Outlook instead of classic Outlook are the supported mitigations in the current documentation.

    For persistent or unclear send failures, use the official support channels for Outlook.com or Outlook to provide details (including version, platform, and exact error text) so that the product team can investigate and address the underlying issue.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.