InDesign Undo history clears itself without user action

Desde hace unas semanas solo me permite hacer 2 veces Ctrl + Z no guarda el historial de lo que voy haciendo y es muy frustrante, esto entorpece en gran manera el trabajo. 

Agradeceria si me pueden ayudar a solucionar este error, estoy utilizando la version 21.0.2

Bug Confirmation: Undo History Auto-Purge During Idle State

Hello,

I can confirm experiencing the identical issue described in this thread.

System Configuration:

• OS: Windows 11 25H2
• InDesign versions tested: 21.x and 20.0 (issue persists across both)
• Hardware: Adequate RAM allocation, >100GB free disk space

Issue Behavior: Undo stack grows normally during active editing (reaches 15-20 steps), then automatically purges after 30-90 seconds of idle time, reducing to ~8 steps (sometimes 4). This is not a static limit but an idle-triggered memory management behavior.

Troubleshooting Performed (no resolution):

1. Preferences reset (Ctrl+Alt+Shift on launch)
2. Complete InDesign uninstall/reinstall
3. Tested on InDesign 20.0 (downgrade from 21.x)
4. Verified adequate disk space (>100GB free)
5. Tested on new documents + local files (non-cloud storage)
6. Disabled InDesign Recovery folder (%LocalAppData%\Adobe\InDesign\...\InDesign Recovery)
7. Attempted Windows update rollback

Key Observations:

• Issue onset correlates with recent timeframe (was not present months ago)
• Reproducible on blank documents
• Pattern: active editing → stack grows → idle period → automatic purge
• Not a static memory limit but idle-state triggered behavior
• Stack purge occurs at application level, not UI refresh issue (confirmed via Ctrl+Z limit)

Technical Hypothesis: Given the correlation with the December 9, 2025 Windows update (KB for 23H2/24H2/25H2) and idle-triggered behavior, this appears to be a conflict between InDesign's undo stack memory management and Windows' modified Virtual Memory Manager or memory compression policies in recent builds.

Available for providing diagnostic logs, memory dumps, or additional testing if needed.

Be careful!!! If you make critical changes that need to be undone, you may not be able to undo causing major headaches. I can only undo two steps. Also, when only selecting one character, portions of the screen/text box turn all white. I have to type blind, zoom in and out, deselect, roll the mouse wheel to get the text to reappear. IT has installed all updates, drivers, everything. Problem is still happening. I was working on a major project for a year and half and InDesign decides to short-circuit on my during the last week of the project. It took FOREVER to complete simple tasks like changing a semicolon to a comma. Please fix this ASAP!!!

Hello everyone,
Maybe the bug has been fixed? My history pane is full of commands, and the smile is back on my face!

So, I also have 16 GB of ram... and have the problem. I asked a collegue freelancer (who doesn't have this bug) to check and he has 32 GB ram.

I have this problem too. laptop with Windows 11. completely new installation. with a full disk cleanup. Windows protection is disabled. even without an internet connection, the problem appeared immediately. InDesign version 20.3.1. I'm crying!!!

Or, put another way:

Is there anyone here who works with 16 GB RAM (or less) and DOESN'T have these problems?

Is there a Windows user in this thread with MORE than 16 GB RAM computer power where the described problems occur?

I've noticed from users who have posted their computer specs that they are running 16GB of RAM 

Is this the case for everyone with this bug? 

My work laptop has 16GB and has this issue whereas my own desktop has 64 and does not.

Everyone writing posts just to grouse about this: Please go to the bug on UserVoice (https://adobe.ly/4jaiQSs), add a vote to the tally, and click the "Critical" button. That's the appropriate way to let Adobe know how many people are impacted by it and need it fixed. And once you've done that, UserVoice will notify you when there is a status change. I'm pretty sure the developers are already trying hard to figure out what's causing it (it's clearly a complex problem), but more votes can't hurt. Complaining here with no new info doesn't help anyone - it just fills all our email inboxes with notifications of more angry posts and wastes everyone's time reading them. (And don't just grouse in the UserVoice comment section either - if you don't have concrete info to add that might help the developers diagnose the problem, just wait.)