olk.exe - Entry Point Not Found (TryCreatePackageDependency) on Windows Server 2022 after New Outlook update build 1.2026.403.100

Atief Jokhoe 65 Reputation points

Hello there,

We are experiencing a critical issue with the New Outlook for Windows (AppX/MSIX package) on Windows Server 2022 (RDS environment).

After an automatic update around April 13โ€“16, 2026, launching olk.exe outputs the following error:
***The procedure entry point TryCreatePackageDependency could not be located in the dynamic link library C:\ProgramFiles\WindowsApps\Microsoft.OutlookForWindows_1.2026.403.100_x64__8wekyb3d8bbwe\Microsoft.Windows.Workloads.dll
***olk.exe - Entry Point not found error - Outlook.png

๐Ÿ‘ User's image


***It seems that the executable (olk.exe) from build 1.2026.403.100 attempts to call the function TryCreatePackageDependency from Microsoft.Windows.Workloads.dll. However, the version of this DLL bundled within the same AppX package does not export this function.

Environment:

  • Windows Server 2022
  • New Outlook version: 1.2026.403.100 (affected build)
  • Microsoft Store is not available on this server.
  • Classic Outlook works without any issues

What I have already tried:
***- Resetting the New Outlook app (via Settings --> Apps --> Advanced options --> Reset)

  • Reinstalling the New Outlook app completely
  • Performing an Online Repair of Microsoft 365 / Office
  • Installed latest Windows Cumulative Updates (KB5082142) and .NET updates.

Is this a known problem in the April 2026 release channel for New Outlook, and is there a fix for it?


Moved from: Outlook | Windows | New Outlook for Windows | For business

  1. Christopher Bell 15 Reputation points

    I am seeing exactly the same problem on my personal W10 laptop (please don't say upgrade to W11, it's too old)
    Will you be fixing that in a patch as well? It's running 22H2 19045.7184

  2. HLBui 6,755 Reputation points โ€ข Independent Advisor

    Hi Christopher Bell

    Yes , this issue is being tracked and will be addressed in a servicing patch. The April 2026 build of New Outlook (1.2026.403.100) introduced a packaging bug where olk.exe calls into Microsoft.Windows.Workloads.dll for a function that isnโ€™t exported, which is why youโ€™re seeing the entry point error. Microsoft has already acknowledged the problem and is preparing a corrected build that will restore proper dependency handling.

  3. Michael Matza 5 Reputation points

    when can we anticipate the "fix" - Thanks!

  4. MELERIX 5 Reputation points

    try the following...

    1 - uninstall Outlook
    2 - go to "%LocalAppData%\Microsoft" and delete "Olk" and "OneAuth" folders.
    3 - restart Windows.
    4 - install Outlook again from Microsoft Store.

  5. Pamela T 5 Reputation points

    Hi, I also would like to be updated for when this will be fixed. I also have Windows 10 that can't be updated. Thanks in advance ๐Ÿ™‚ I was seriously worried I got virused.


Sign in to comment

Answer accepted by question author

HLBui 6,755 Reputation points โ€ข Independent Advisor

Good day Atief Jokhoe

The April 2026 build of the New Outlook (1.2026.403.100) introduced a packaging bug where olk.exe tries to call TryCreatePackageDependency from Microsoft.Windows.Workloads.dll, but the DLL shipped in that same package doesnโ€™t actually export that function. That mismatch is whatโ€™s causing the โ€œEntry Point Not Foundโ€ error youโ€™re seeing.

Since youโ€™re on Windows Server 2022 in an RDS environment, the problem is compounded by the fact that the Microsoft Store isnโ€™t available, so the usual selfโ€‘healing update path doesnโ€™t kick in. Resetting, reinstalling, or repairing wonโ€™t help here because the issue is baked into the package itself itโ€™s not a corruption on your side.

The good news is that this is a known problem in the April release channel, and Microsoft is already working on a servicing update to correct the package dependency. In the meantime, the only reliable workaround is to stick with Classic Outlook until the fixed build is published. If you want to avoid user confusion, you might consider uninstalling the New Outlook app entirely until the patched MSIX is available.

A couple of extra checks you can do:

  • Make sure your hosts are fully patched with the latest cumulative updates (which youโ€™ve already done).
  • Keep an eye on the Outlook for Windows (new) release notes page thatโ€™s where the servicing fix will be announced first.
  • If this outage is businessโ€‘critical, you can absolutely escalate to Microsoft Support even with just Windows Server licenses. Theyโ€™ll confirm the bug and can provide guidance on timelines for the fixed build.

So : you canโ€™t fix it locally, and the workaround is to use Classic Outlook until the servicing update lands. I know thatโ€™s not the most satisfying answer, but at least you donโ€™t need to burn more cycles chasing a issue.

If this guidance proves helpful, feel free to click โ€œAccept Answerโ€ so we know weโ€™re heading in the right direction and let me know if you need any assistance. Thank you!

  1. Charles Pool 5 Reputation points

    Where can we go to get an official update on the status of this issue?

  2. HLBui 6,755 Reputation points โ€ข Independent Advisor

    Hi Charles Pool

    Microsoft Q&A (Learn platform): Engineers and product team members often confirm issues here.

    Microsoft 365 Admin Center (if you have admin rights): Service health dashboard and message center posts will show if thereโ€™s a tenant-wide advisory.

    Release Notes for Microsoft 365 Apps: Outlook updates are documented here, including when a fix is rolled out.

    Microsoft Support โ€“ Known Issues in Outlook: There are separate pages for classic Outlook and new Outlook for Windows. These pages are updated regularly with current bugs, workarounds, and fixes.

  3. Atief Jokhoe 65 Reputation points

    Hi Microsoft team / HLBui,

    Can we please get an update on the servicing update for the olk.exe - TryCreatePackageDependency packaging bug?

    Has a corrected build (e.g. after 1.2026.4xx.xxx) been released to the stable channel yet?
    I checked the release notes for Outlook for Windows (new) but could not find any newer versions that state that this issue is fixed.


Sign in to comment

4 additional answers

  1. Beeg Deek 5 Reputation points

    It's broken fix this sh-

    0 comments No comments

    Sign in to comment
  2. Petteri Moilanen 0 Reputation points

    Used to be trash but now it's even more trash. They also removed the mark as read icon from the top of the e-mails... Making everything just more harder to use. I hope someday Linux will take over all this trash.

    0 comments No comments

    Sign in to comment
  3. Emkay1001 20 Reputation points

    Version 1.2026.420.300 released in Microsoft Store seems to have fixed the issue for me.

    1. ์ต๋ช… 5 Reputation points

      https://learn.microsoft.com/en-us/officeupdates/release-notes-outlook-new ์—…๋ฐ์ดํŠธ๊ฐ€ ๋˜์—ˆ๋‹ค๊ณ  ๋‚˜์˜ค๋‚˜ ํ•ด๋‹น ์˜ค๋ฅ˜์— ๋Œ€ํ•œ ๊ฒŒ ๋งž์•„? ์™œ ms๋Š” ์ธ์ •์„ ์•ˆํ• ๊นŒ...


    Sign in to comment
  4. ์ต๋ช… 5 Reputation points

    windows10 22h2 19045.6456/1.2026.407.100์—์„œ๋„ ๋ฐœ์ƒ์ค‘์ž…๋‹ˆ๋‹ค.

    ์ด์ œ ์œˆ๋„์šฐ10๋Š” ์•„์˜ˆ ์ง€์›์„ ์•ˆํ•˜๋Š”๊ฑธ๊นŒ์š”.... ํ•ด๊ฒฐ๋ฐฉ๋ฒ• ์ข€ ์•Œ๋ ค์ฃผ์„ธ์š”!

    1. Issac Jay 0 Reputation points

      Just waitting until the servicing update lands

    2. Hornblower409 9,750 Reputation points

      @์ต๋ช… said

      It is also occurring on windows10 22h2 19045.6456/1.2026.407.100 Does Windows 10 not support it at all anymore...?

      1 -- If you are asking about the TryCreatePackageDependency error, then it is a New Outlook For Windows App error. It has nothing to do with your Windows Version.

      2 -- For most users you can just [OK] thru the three or four error pop-ups and New Outlook for Windows will open and everything will run as it normally does. The TryCreatePackageDependency error does not seem to break anything.

    3. Christopher Bell 15 Reputation points

      I am on Windows 10 22H2. Just click "OK" 2 or 3 times on the warning messages at startup and (at least for me) everything works fine. It's irritating, but not a problem.

    4. ์ต๋ช… 5 Reputation points

      olk.exe --safe ์•ˆ์ „๋ชจ๋“œ ์‹คํ–‰์‹œ ์ •์ƒ์ ์œผ๋กœ ์‹คํ–‰๋˜๊ธดํ•˜์ง€๋งŒ. ์‚ฌ์šฉ์ž๋Š” ๋ถˆ๋งŒ์ž…๋‹ˆ๋‹ค. ms์—”์ง€๋‹ˆ์–ด๋Š” ์œˆ๋„์šฐ10์„ 11๋กœ ์—…๊ทธ๋ ˆ์ด๋“œ ํ•˜๋ผ๊ณ  ํ•ฉ๋‹ˆ๋‹ค.

    5. Hornblower409 9,750 Reputation points

      @์ต๋ช… said

      Although olk.exe runs normally when executed in Safe Mode, users are dissatisfied. Microsoft engineers recommend upgrading from Windows 10 to Windows 11

      I think you are in the wrong thread. This conversation is about the New Outlook for Windows App and a TryCreatePackageDependency error.

      New Outlook for Windows does not have a "Safe Mode". That is only for Classic Outlook.

      There have been no recommendations from anyone, Microsoft or normal users, that upgrading to Windows 11 has any effect on the error.

      You need to start a new thread using the "Ask a question" button at the top of this page to create a new Question and include the details for your specific problem instead of commenting on this thread.


    Sign in to comment
Sign in to answer

Your answer