
Microsoft 365 atWork; Senior Digital Advisor at Predica Group
The following article summarizes a recent YouTube video by Szymon Bochniak (365 atWork) that addresses a pressing issue affecting some Windows 11 users. In the video, the author explains how the January 13, 2026 security update KB5074109 can cause Classic Outlook profiles using PST files and POP accounts to hang, freeze, or become inaccessible. Consequently, the presenter walks viewers through practical recovery steps to regain access to email, calendar items, and contacts while Microsoft investigates a permanent fix. The straightforward tone aims to help administrators and end users decide how to act fast without taking unnecessary risks.
Bochniak demonstrates each step on a live system and emphasizes safety measures such as backing up files before attempting repairs. He highlights common patterns that lead to corruption, especially when PST files live in synced folders like OneDrive, and he tests both built-in utilities and configuration changes. Therefore, the video serves as a compact troubleshooting guide for people experiencing sudden Outlook failures after the update. It also frames the tradeoffs between quick workarounds and long-term safety.
According to the video, the problem appears when the Windows update alters how Outlook interacts with local profile data, causing abrupt termination or failure to restart. As a result, users report lost sent items, freezing on exit, and error messages that point to corrupted PST structures. The presenter shows that symptoms are more likely with older Classic Outlook setups that use POP accounts and large local store files. Thus, the issue is a software regression rather than a hardware failure, and it affects file handling and profile stability.
Moreover, Bochniak notes that storing PST files in cloud-synced folders amplifies the problem because background synchronization can interfere with file locks and writes. Consequently, even pausing a sync client may not fully avoid the conflict, and users should treat synced storage cautiously. The speaker also points out that Microsoft published an advisory and is investigating, but at the time of the recording no universal patch had been rolled out. Therefore, understanding the root cause helps teams prioritize mitigations that balance speed with data protection.
First, the video recommends creating a full copy of any affected PST files before attempting repairs, and then running the built-in Inbox Repair Tool (ScanPST) to correct logical corruption. Bochniak demonstrates how to close Outlook, run ScanPST, and verify repaired files, which restores access in many cases without data loss. Next, he shows how to build a fresh Outlook profile to isolate configuration problems and import repaired data into the new environment to prevent repeated crashes. These steps often resolve issues for users with moderate corruption while keeping changes reversible.
If the standard tools fail, the presenter outlines other options such as repairing the Office installation and, as a temporary measure, uninstalling the problematic update to restore prior behavior. However, he stresses that removing a security update introduces risk and should be a short-term move only for critical business continuity. As a final step, moving PST files out of synced folders to a local, unsynced directory reduces the chance of future conflicts and is an effective preventive measure. Thus, the video balances quick recovery techniques with safer, longer-term adjustments.
Bochniak openly discusses the tradeoffs that administrators must weigh before applying fixes. For instance, uninstalling KB5074109 can restore functionality immediately, but it also removes a security patch designed to protect systems, so organizations must accept short-term vulnerability in exchange for operational recovery. Similarly, using third-party PST repair utilities may recover more data in stubborn cases, yet these tools can carry cost and introduce trust or compatibility questions compared with Microsoft’s native ScanPST.
Another important tradeoff involves relocating PST files: moving them out of cloud-synced folders reduces corruption risk, but it also removes the convenience of automatic cloud backups and cross-device access. Consequently, teams must weigh local reliability against backup and access policies and consider alternative approaches such as migrating POP accounts to exchange-like setups or archiving mail into smaller, segmented stores. Therefore, every remedy requires a careful evaluation of operational needs, security posture, and data protection practices.
The video concludes with practical recommendations for both end users and IT teams to reduce downtime and data loss potential. Bochniak advises creating standard operating procedures: back up PST files regularly, test recovery steps in a controlled environment, and educate users about storing data in appropriate locations. Furthermore, IT teams should monitor vendor advisories and prepare rollback plans that balance security and availability, as well as consider modernizing accounts away from legacy POP setups when feasible.
Finally, the presenter encourages documenting each recovery attempt and escalating persistent cases to Microsoft support, since complex corruption may require deeper intervention. Meanwhile, keeping systems updated with the latest vendor fixes remains critical once a reliable patch becomes available. In short, the video provides a pragmatic, step-by-step path to recovery while highlighting the strategic choices and risks that decision makers must manage.
Outlook PST repair KB5074109, Fix Outlook PST Windows 11 update, Repair broken PST after KB5074109, ScanPST Windows 11 fix, Outlook data file corrupted KB5074109, Restore PST after Windows 11 update, Outlook PST recovery tools Windows 11, Resolve Outlook corruption KB5074109