Windows version
InDesign encounters Error 2 while saving files or crashes during the save process after the January 13, 2026, Microsoft Windows updates.
After installing the January 13, 2026, Microsoft Windows updates, Adobe InDesign encounters Error 2 during file save operations or crashes when working with files stored in cloud-synced locations such as OneDrive, Dropbox, Google Drive, etc.
Affected Windows Versions
- Windows 10 - January 13, 2026—KB5073724 (OS Builds 19045.6809 and 19044.6809)
- Windows 11 - January 13, 2026—KB5074109 (OS Builds 26200.7623 and 26100.7623)
Based on our investigation, it appears to be related to recent Windows operating system changes, specifically how cloud-backed files are handled after the update. There have been no recent changes in InDesign that would cause this behavior.
Microsoft has acknowledged the issue (Windows 10 and Windows 11), and we’re working closely with them to resolve it as quickly as possible. In the meantime, here are a few workarounds that may help reduce the impact.
Microsoft released an out-of-band (OOB) Windows update on Saturday, January 24, 2026, to address the reported issue. This update was announced in the Windows Message Center and Microsoft Learn. Documentation was updated in the Windows release health dashboard, M365 admin center (authenticated users), and Windows update release notes.
This OOB update is available through Windows Update for Windows 11 devices running the updates released this month. To install it, open Settings > Windows Update, and select Download and Install.
This update will appear in Windows Update only if you have installed one of the January updates that caused this issue. Some devices may install the update automatically (e.g., Hotpatch capable (KB5078167), devices with Get Windows updates as soon as they're available turned on).
For supported versions of Windows Server and Windows 10, the OOB update is available from the Microsoft Update Catalog. Refer to the KB articles below for detailed information and installation steps.
|
|
KB article link |
|---|---|
|
Windows 11, versions 25H2 and 24H2 |
|
|
Windows 11 Enterprise versions 25H2 and 24H2 |
Hotpatch KB5078167 |
|
Windows 11, version 23H2 |
|
|
Windows 10 ESU (22H2) and Windows 10 Enterprise LTSC 2021 |
|
|
Windows Server 2025 |
|
|
Windows Server 2025 Datacenter: Azure Edition |
Hotpatch KB5078239 |
|
Windows Server, version 23H2 |
|
|
Windows Server 2022 |
|
|
Windows Server 2022 Datacenter: Azure Edition |
Hotpatch KB5078238 |
|
Windows Server 2019 and Windows 10 Enterprise LTSC 2019 |
IT administrators
IT administrators using Microsoft Intune or Windows Autopatch should follow the guidance below for installing the OOB update via Windows Update.
- Expedite Windows quality updates in Microsoft Intune
- Deploy an expedited quality update using Windows Autopatch
IT administrators using WSUS distribute updates released to the Microsoft Catalog at enterprise scale using the insights from:
The latest Windows update should be available to all users. If you’re unable to see the update or experience any issues during installation, please don’t hesitate to contact Microsoft.
You can open a support case with Microsoft for help installing the Windows update or to get clarification on any Windows-related behavior after the out-of-band (OOB) fix has been deployed.
If you are unable to install the Windows update, please use the workaround listed below as a temporary measure until the update is successfully installed.
Workaround 1
Uninstall the Microsoft updates released on January 13, 2026.
-
Select Settings > Windows Update > Update history > Uninstall updates on your Windows system.
-
Select the recent update KB5073724 (Windows 10) or KB5074109 (Windows 11) in the Control Panel list.
-
Select Uninstall.
-
Restart your system.
-
Open the Group Policy Management Console (GPMC).
-
Navigate to Computer Configuration > Administrative Templates > System > Group Policy.
-
Select the policy Configure rollback of problematic updates.
-
Specify KB5073724 (Windows 10) or KB5074109 (Windows 11) update to be rolled back.
-
Apply and enforce the policy across the affected machines.
Workaround 3
Save the document to the local drive and then copy it to the cloud-synced locations, such as OneDrive, Dropbox, Google Drive, etc.