InvalidOperationException: Collection was modified; enumeration operation may not execute
A list/dictionary was changed while a foreach loop was iterating it.
Seen on:
.NET
Meaning
Removing items inside foreach, or another thread modifying the collection during enumeration, invalidates the enumerator.
Common causes
- Add/Remove inside foreach over the same collection
- Concurrent modification from another thread/event
- LINQ query re-enumerating a changing source
⚡ Quick fix
- Iterate over a copy (ToList())
- Use RemoveAll / a reverse for loop
- Use concurrent collections or locks for multi-threaded access
Detailed fix by platform
C#
- csharp
items.RemoveAll(i => i.Expired); // or foreach (var i in items.ToList()) if (i.Expired) items.Remove(i);
How to diagnose
- Loop — Modifying the same collection?
- Threads — Concurrent writers?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in .NET
- NullReferenceException System.NullReferenceException: Object reference not set to an instance of an object
- FileNotFoundException assembly Could not load file or assembly 'X, Version=…' or one of its dependencies
- InvalidOperationException InvalidOperationException: Unable to resolve service for type 'X' while attempting to activate 'Y'
Other ways to find it
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
Was this page helpful?
Report a correction or suggest an improvement
Last updated 7 Oct 2026