That's funny - I also ran into non updating pipenetworks recently and chalked it up to the project being quite big and Civil3d just being wonky. (I'm in 2025.2.2 though)
But the fact that it's happening to others without a clear cause is something between a nuisance and deeply concering.
This stuff should "just work", otherwise DRef's are sort of pointless.
Updating the acaddoc.lsp is a nice brute-force solution but it might slow down opening times for files with a lot of references.
I also discovered other issues that were not a problem a release ago: for example automatic corridor intervals at elevation targets are suddenly not created although the setting is set to "True". This can potentially lead to very unpleasant situations.
We are in the remarkable situation that we don't get any new features for certain parts of the software yet still fresh and hot bugs are introduced. Autodesk must have discovered vibe-coding...