Daga
08-01-2011, 06:34 PM
Hey, I've got a Windows 7 (64-bit) laptop with the Targus/DisplayLink ACP51US (Item #52). The DVI connection works great most of the time but randomly locks video output.
In the Windows Application logs after every lock-up is an Event ID 1530 (as a "Warning"):
Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards.
DETAIL -
1 user registry handles leaked from \Registry\User\S-1-5-21-547952399-1897659035-470046771-1000_Classes:
Process 4520 (\Device\HarddiskVolume2\Program Files\DisplayLink Core Software\DisplayLinkUI.exe) has opened key \REGISTRY\USER\S-1-5-21-547952399-1897659035-470046771-1000_CLASSES
Microsoft's help refers to this page:
http://technet.microsoft.com/en-us/library/hh203956(WS.10).aspx
For now I have updated to the latest release of the DisplayLink software (5.6.31870 as of today), but it was not that large of a revision upgrade and I have not been able to find a reference to this issue yet.
I'll post back if I am still having issues, but it would be nice to hear if I missed the documentation for this fix somewhere. If not for me, for the next guy. :-)
Thanks!
In the Windows Application logs after every lock-up is an Event ID 1530 (as a "Warning"):
Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards.
DETAIL -
1 user registry handles leaked from \Registry\User\S-1-5-21-547952399-1897659035-470046771-1000_Classes:
Process 4520 (\Device\HarddiskVolume2\Program Files\DisplayLink Core Software\DisplayLinkUI.exe) has opened key \REGISTRY\USER\S-1-5-21-547952399-1897659035-470046771-1000_CLASSES
Microsoft's help refers to this page:
http://technet.microsoft.com/en-us/library/hh203956(WS.10).aspx
For now I have updated to the latest release of the DisplayLink software (5.6.31870 as of today), but it was not that large of a revision upgrade and I have not been able to find a reference to this issue yet.
I'll post back if I am still having issues, but it would be nice to hear if I missed the documentation for this fix somewhere. If not for me, for the next guy. :-)
Thanks!