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

Question

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

Atief Jokhoe 65

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

Christopher Bell 15 Reputation points

2026-04-17T10:56:30.9666667+00:00

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
HLBui 5,380 Reputation points Independent Advisor

2026-04-17T11:07:42.86+00:00

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.
Michael Matza 5 Reputation points

2026-04-17T21:46:55.41+00:00

when can we anticipate the "fix" - Thanks!
MELERIX 5 Reputation points

2026-04-18T00:43:41.1166667+00:00

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.
Pamela T 5 Reputation points

2026-04-18T13:51:32.62+00:00

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.
Hornblower409 8,200 Reputation points

2026-04-18T22:03:29.73+00:00

@MELERIX said

try the following [New Outlook for Windows "Clean Sweep"]

You might want to edit you comment to include that following your instructions will completely reset New Outlook for Windows and the user will have to re-add all of their accounts and re-do all of their settings.

Thank you for your suggestion. But this seems to only fix the problem for a very small number of people. Given that you can "OK" your way thru the error messages and there is no loss of functionality in Outlook because of this bug, a "Clean Sweep" seems to me like trying to use a sledgehammer to kill a mosquito. And usually missing the mosquito.
Hornblower409 8,200 Reputation points

2026-04-18T22:17:26.3633333+00:00

@Pamela T said

I also would like to be updated for when this will be fixed.

As far as I know there is no official Microsoft Service Health bulletin on this issue for us to track. All you can do is check this Question for comments and answers from the Microsoft staff and advisors.
David Timson 0 Reputation points

2026-04-20T00:54:15.71+00:00

When will this be fixed, I have ended up spending money for I.T specialist to fix and it came back, after reinstall of outlook due to your mistake.
Roger Brockway 0 Reputation points

2026-04-20T21:14:54.68+00:00

So, when we click the slider to turn off "New Outlook" to try to return the old Outlook, we get the error:

Cannot start Microsoft Outlook. Cannot open the Outlook window. The set of folders cannot be opened. An unexpected error has occurred.

and the program doesn't run. Linux to the rescue!
Hornblower409 8,200 Reputation points

2026-04-21T00:20:25.0766667+00:00

@Roger Brockway said

click the slider to turn off "New Outlook"

Try running Classic Outlook directly, not by using the New Outlook for Windows toggle. (They can run side-by-side)

Look for OUTLOOK.EXE in C:\Program Files\Microsoft Office\root\Office16\ or C:\Program Files (x86)\Microsoft Office\root\Office16\

Cannot start Microsoft Outlook. Cannot open the Outlook window

Common problem. Just means that the Classic Outlook config and profile have not been setup correctly. Can almost always be fixed.

https://support.microsoft.com/en-us/office/i-can-t-start-microsoft-outlook-or-receive-the-error-cannot-start-microsoft-outlook-cannot-open-the-outlook-window-d1f69da6-b333-4650-97bf-4d77bd7abb85

If that doesn't get you running Classic, 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.

Answer accepted by question author

4 additional answers

Your answer

Christopher Bell 15 Reputation points

2026-04-17T10:56:30.9666667+00:00

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
HLBui 5,380 Reputation points Independent Advisor

2026-04-17T11:07:42.86+00:00

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.
Michael Matza 5 Reputation points

2026-04-17T21:46:55.41+00:00

when can we anticipate the "fix" - Thanks!
MELERIX 5 Reputation points

2026-04-18T00:43:41.1166667+00:00

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.
Pamela T 5 Reputation points

2026-04-18T13:51:32.62+00:00

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.
Hornblower409 8,200 Reputation points

2026-04-18T22:03:29.73+00:00

@MELERIX said

try the following [New Outlook for Windows "Clean Sweep"]

You might want to edit you comment to include that following your instructions will completely reset New Outlook for Windows and the user will have to re-add all of their accounts and re-do all of their settings.

Thank you for your suggestion. But this seems to only fix the problem for a very small number of people. Given that you can "OK" your way thru the error messages and there is no loss of functionality in Outlook because of this bug, a "Clean Sweep" seems to me like trying to use a sledgehammer to kill a mosquito. And usually missing the mosquito.
Hornblower409 8,200 Reputation points

2026-04-18T22:17:26.3633333+00:00

@Pamela T said

I also would like to be updated for when this will be fixed.

As far as I know there is no official Microsoft Service Health bulletin on this issue for us to track. All you can do is check this Question for comments and answers from the Microsoft staff and advisors.
David Timson 0 Reputation points

2026-04-20T00:54:15.71+00:00

When will this be fixed, I have ended up spending money for I.T specialist to fix and it came back, after reinstall of outlook due to your mistake.
Roger Brockway 0 Reputation points

2026-04-20T21:14:54.68+00:00

So, when we click the slider to turn off "New Outlook" to try to return the old Outlook, we get the error:

Cannot start Microsoft Outlook. Cannot open the Outlook window. The set of folders cannot be opened. An unexpected error has occurred.

and the program doesn't run. Linux to the rescue!
Hornblower409 8,200 Reputation points

2026-04-21T00:20:25.0766667+00:00

@Roger Brockway said

click the slider to turn off "New Outlook"

Try running Classic Outlook directly, not by using the New Outlook for Windows toggle. (They can run side-by-side)

Look for OUTLOOK.EXE in C:\Program Files\Microsoft Office\root\Office16\ or C:\Program Files (x86)\Microsoft Office\root\Office16\

Cannot start Microsoft Outlook. Cannot open the Outlook window

Common problem. Just means that the Classic Outlook config and profile have not been setup correctly. Can almost always be fixed.

https://support.microsoft.com/en-us/office/i-can-t-start-microsoft-outlook-or-receive-the-error-cannot-start-microsoft-outlook-cannot-open-the-outlook-window-d1f69da6-b333-4650-97bf-4d77bd7abb85

If that doesn't get you running Classic, 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.

Answer 1

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!

Charles Pool 5 Reputation points

2026-04-17T16:10:56.17+00:00

Where can we go to get an official update on the status of this issue?
HLBui 5,380 Reputation points Independent Advisor

2026-04-17T17:40:46.2366667+00:00

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.

Answer 2

Beeg Deek 5

It's broken fix this sh-

0 comments

Answer 3

Petteri Moilanen 0

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

Answer 4

Emkay1001 20

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

익명 5 Reputation points

2026-04-27T06:46:51.6833333+00:00

https://learn.microsoft.com/en-us/officeupdates/release-notes-outlook-new 업데이트가 되었다고 나오나 해당 오류에 대한 게 맞아? 왜 ms는 인정을 안할까...

Answer 5

익명 5

windows10 22h2 19045.6456/1.2026.407.100에서도 발생중입니다.

이제 윈도우10는 아예 지원을 안하는걸까요.... 해결방법 좀 알려주세요!

Issac Jay 0 Reputation points

2026-04-21T02:45:48.3233333+00:00

Just waitting until the servicing update lands
Hornblower409 8,200 Reputation points

2026-04-21T02:48:55.1166667+00:00

@익명 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.
Christopher Bell 15 Reputation points

2026-04-21T07:50:58.6933333+00:00

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.
익명 5 Reputation points

2026-04-21T07:57:25.5133333+00:00

olk.exe --safe 안전모드 실행시 정상적으로 실행되긴하지만. 사용자는 불만입니다. ms엔지니어는 윈도우10을 11로 업그레이드 하라고 합니다.
Hornblower409 8,200 Reputation points

2026-04-21T12:48:09.6633333+00:00

@익명 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.
익명 5 Reputation points

2026-04-21T23:32:56.67+00:00

https://learn.microsoft.com/en-us/microsoft-365-apps/outlook/administration/architecture-changes-new-outlook
Hornblower409 8,200 Reputation points

2026-04-21T23:51:33.8366667+00:00

Hornblower409 said

New Outlook for Windows does not have a "Safe Mode".

@익명 said

https://learn.microsoft.com/en-us/microsoft-365-apps/outlook/administration/architecture-changes-new-outlook Safe mode in new Outlook is a troubleshooting feature that allows users to launch the application with minimal functionality. It provides a temporary, isolated session where users can access essential features like email and calendar while addressing issues or working with Microsoft Support.

I was wrong and you are correct. Thank you for pointing this out. olk.exe --safe does start New Outlook for Windows in Safe Mode and it does bypass the TryCreatePackageDependency error.

But, give the limitations of Safe Mode (excludes PST, S/MIME, offline usage, and web add-ins) and that the user can just [OK] thru the TryCreatePackageDependency errors with no loss of functionality, I still do not think that it is an appropriate technique for most people.

Share via

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

4 additional answers

Your answer