Why do old apps keep working on new servers?
Operating systems maintain decades-old code because critical municipal and enterprise applications written 20 years ago still depend on it to run. This leaves platforms unable to remove legacy cruft, even when the original creators have retired or died and nobody fully understands how the system works.
What people tried
Every workaround mentioned in the threads below. We haven’t tested any of them — and nobody here is claiming they worked.
Found another way around this?
Share your steps and trade-offs so fellow engineers don't have to reinvent the wheel. No account required.
- 1Continuing to support decades-old legacy code and applicationsDid this help you?
- 2Writing translation layers or emulators like Rosetta or x86_64 emulatorsDid this help you?
- 3Splitting operating systems into separate channels or versionsDid this help you?
In their words
Unedited, grouped by where they were said, most upvoted first within each place, each linked to the thread it came from.
“I work in municipal government and we’ve got applications written 20 years ago that all the people who understand what it does or why have retired or died. It still runs under server 2025 just as it did under server 2000 when it was developed.”source ↗
“Microsoft can't remove the legacy cruft as an application might still be using it.”source ↗
Where this came up
People with this problem also raised
- 10How to migrate scary legacy software nobody wants to touch
- 4How to reactivate QuickBooks desktop after computer died
- 9How to handle undocumented legacy database changes
- 15Why is keeping up with software updates so exhausting?
- 6How to handle enterprise hardware hitting end-of-life on a tight budget
- 14How to test if a software integration actually works