Share via

Outlook error message "Somehting went wrong. [48v35]"

Anonymous
2024-09-30T08:38:29+00:00

Hi

I have a user encountering this outlook error msg intermittently "Something went wrong. [48v35]" when he open an email from "New" MS Outlook.

To date I notice by logout & login his M365 credential from his "New" MS Outlook only temporary solved the issue.

Is there a perm fix and appreciate advise. Thank you.

Outlook | Windows | New Outlook for Windows | For home

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

36 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2025-01-14T18:42:10+00:00

    Step 1: Close all Office applications.
    Step 2: Navigate to C:\Users\AppData\Local\Microsoft by pressing the win+r buttons.
    Step 3: Check if the OneAuth and IdentityCache folders are present.
    Step 4: If they are present, delete them.
    Step 5: Restart your computer.
    Step 6: Rerun a test to see the result.

    9 people found this answer helpful.
    0 comments
  2. Anonymous
    2024-11-06T11:57:52+00:00

    Sharing my progress.

    KB5043935 has a known issue:

    https://support.microsoft.com/en-us/topic/september-10-2024-kb5043064-os-builds-19044-4894-and-19045-4894-cd14b547-a3f0-4b8f-b037-4ae3ce83a781

    After installing this update, or subsequent updates, you might experience an extended black screen that stays between 10 to 30 mins when you login toAzure Virtual Desktop(AVD). Additional symptoms you might experience include:

    • Failures related tosingle sign-on(SSO) experience on Office applications such as Outlook and Teams, which could prevent you from connecting to backend services or synchronizing data.
    • Office apps display losing network connectivity even though other applications, such as Edge, retain intranet and internet access.

    This issue is caused by a deadlock in the interactions between the Azure Active Directory (AAD) broker and the underlying AppX deployment service(AppxSvc) and Background tasks infrastructure service. You are more likely to experience this issue if you are usingFSLogixuser profile containers on multi-session environments. FSLogix is a Microsoft tool that helps manage and speed up user profiles on computers, especially in virtual environments like remote desktops.

    5 people found this answer helpful.
    0 comments
  3. Anonymous
    2025-01-23T10:51:22+00:00

    Same issue here after upgrading RDS Windows 2012 to Server 2022. All users randomly having this problem, every few days - just a nightmare.

    3 people found this answer helpful.
    0 comments
  4. Anonymous
    2024-10-03T06:27:57+00:00

    Also getting a 48v35 error in excel. Seems to be Office related in general. Re-adding the Microsoft account fixes it only temporarily.

    Running Microsoft 365 Apps for Enterprise in shared activation mode on a Windows Server 2019 Datacenter system. This is deployed into a RDS environment.

    Tried checking above folders, they do not exist.

    We are having the same issue. So far only one user in the AVD farm seems to be affected. Every week she's getting the 48v35 error and we remove the Microsoft account by removing the AADBrokerPlugin folder and signing in again.

    We use FSLogix (latest version: FSLogix 2210 hotfix 4 (2.9.8884.27471) with the RoamIdentity set to 1.

    I have other customers running exactly the same setup and FSLogix versions, but so far everone else seems to be running without problems.

    3 people found this answer helpful.
    0 comments
  5. Anonymous
    2024-11-08T10:13:12+00:00

    Yes, I can confirm removing that patch AND the later ones after, fix the issue.

    The patch cannot be removed with wusa /uninstall /KB:xxxxx

    What we did is rebuild a golden image with latest Win 10 22h2 from Azure marketplace (it does not have the patch),

    2 people found this answer helpful.
    0 comments