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-22T13:30:01+00:00

    Hello.

    We are on Citrix but this affects RDS. Issue is not really with Office but more with the Windows server 2019/2022.

    We've had this issue for the past 4 months and Microsoft has been working on it but with no success.

    We've gotten the errors 1001, 48v35 which the only real way to fix is by re-creating the profile.

    The 58tm1 can be easily fixed and takes 10 seconds, sign out of all office applications and sign back in.

    After troubleshooting the issue is in the core of the Server 2019/2022 but Microsoft hasn't found the cause as to why this is happening and the fact it's random.

    Eric

    0 comments
  2. Anonymous
    2025-01-10T11:55:36+00:00

    if you have this register value set to something other than 1, try changing it to 1 :

    REG_PATH: HKLM\SOFTWARE\Policies\Microsoft\Windows\WwanSvc\CellularDataAccess

    REG_KEY: LetAppsAccessCellularData

    https://kb.omnissa.com/s/article/97111?lang=en_US&queryTerm=97111

    0 comments
  3. Anonymous
    2025-01-10T11:23:34+00:00

    The same issue started manifesting at our clients company. Random users, random app clients: Teams, Outlook, Word, Excel.

    Is there any news about it? Hotfix? Is MS aware of it?

    There is no AVD/VDI so no FSLogix in this environment at all:

    0 comments
  4. Anonymous
    2024-12-18T03:28:04+00:00

    It did not work at all.

    0 comments
  5. Anonymous
    2024-12-17T07:59:23+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),

    Thank you so much for sharing.That makes sence.

    0 comments