And the internal cache only stores a limited number of updated link targets. If successful the link destination is updated and cached *internally*, but the lnk file itself remains unchanged bitwise and thus is still broken. In fact the links are NOT maintained, but when the service is running, the broken link does no fail immediately but a background search is triggered. There is a Windows service called "Distributed Link Tracking Client" which is supposed to "maintain links between NTFS files within a computer" when running in the background, but actually fails to do so. As soon as you move/rename the target lnks are broken. Or is there a way to prevent broken shortcuts in the first place? I never quite understood how on Earth OS designers could come up with such a broken thing. update lnk to moved target) ?Īs always, if that exists, a TC-centric solution would be preferable (if possible for XP)
Can you recommend a tool for repairing broken lnk files (i.e.
0 kommentar(er)
