Answer accepted by question author
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
Where can we go to get an official update on the status of this issue?
-
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.
-
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
