Error when drag-and-drop zero length files from guest to host

[yumashka]

Version: 5.2.20, 5.2.18 Host: Windows 7 SP1 Guest: Windows 7 SP1 RU/EN, Windows XP SP3 RU Guest additions: installed according to VirtualBox version

Error occurs when dragging zero length file from guest to host:

Drag and drop operation from guest to host failed.
Current drop operation still in progress.
Result Code: E_FAIL (0x80004005)
Component: GuestDnDSourceWrap
Interface: IGuestDnDSource {dedfb5d9-4c1b-edf7-fdf3-c1be6827dc28}
Callee: IDnDSource {d23a9ca3-42da-c94b-8aec-21968e08355d}

Same error occurs when dragging folder with zero-length file from guest to host.

After that error any other drag-and-drop operation even with non-enpty files fails with error:

Drag and drop operation from guest to host failed.
Another drop operation already is in progress.
Result Code: E_INVALIDARG (0x80070057)
Component: GuestDnDSourceWrap
Interface: IGuestDnDSource {dedfb5d9-4c1b-edf7-fdf3-c1be6827dc28}
Callee: IDnDSource {d23a9ca3-42da-c94b-8aec-21968e08355d}

Steps to reproduce: 1) Install guest Windows 7 or Windows XP (any language in to the VB) 2) Install VB Additions 3) Turn on drag-and-drop from guest to host (or bidirectional) 4) Drag and drop any non-zero-length file to check that it works 5) Create any new empty file (for ex. new notepad document) 6) Drag it from guest to host 7) Get error

It is possible to "reset" the satuation by trying to drag any file from host to guest. May be not immediately, may be couple of times. I did not find exact scenario. Sometimes attempts to drag files from host to guest after error leads to guest interface partially hang. In that case shutdown procedure asks to forcibly close VBoxTrayDnDWnd.

Additional: errors appear in host log files, not in guest.

[yumashka]

VBox.log on host with Windows XP guest

[yumashka]

VBoxTray.log from WinXP guest

[yumashka]

VBox.log on host with Win7 guest

[yumashka]

Is it possible to change "Component:" to "DnD" ?

[socratis]

This is a duplicate of #17443, which was supposedly fixed in 5.2.20.

If you're still seeing this with 5.2.20, then I believe that this ticket should be closed as [Duplicate] (in any event) and ticket #17443 re-opened.

[yumashka]

I've reopened #17443. How to close this?

[socratis]

*They* will close it... ;)