Drag and drop error when copying folder from WinXP guest to Win10 host (#17447)

[simon31337]

[Related ticket: #17447: Drag and drop error when copying folder from WinXP guest to Win10 host]
Bug was first observed with VirtualBox 5.2.2 and now 5.2.4. This did not happen on VirtualBox 5.1.x releases.

Host OS: Windows 10, version 1709, build 16299.192
Guest OS: Windows XP SP3 (with latest POSReady 2009 updates applied)

Log files are attached. Look for "DnD: Error opening/creating guest file ..."

How to reproduce the bug (on Windows XP guest):

• start Internet Explorer 8 and visit http://catalog.update.microsoft.com/v7/site/Home.aspx
• type "KB4056941" in the search box (or choose a different KB number)
• click "Add" button on the right of entry "2018-01 Security Update for Windows XP Embedded SP3 for x86-based Systems (KB4056941)"
• click "view basket" above these "Add" buttons
• click the appearing "Download" button right below "view basket"
• in the "Download Options" window, click "Browse..." and select "Desktop", click "Continue"
• close IE8 browser when the message "Download Completed" appears
• if you drag&drop that folder "2018-01 Security Update for Windows XP Embedded SP3 for x86-based Systems (KB4056941)" to a Windows 10 host...

...you should get:

Drag and drop error from host (VERR_PATH_NOT_FOUND).

Fehlercode:VBOX_E_IPRT_ERROR (0x80BB0005)
Komponente:GuestWrap
Interface:IGuest {13a11514-402e-022e-6180-c3944de3f9c8}

This bug might be related to how Internet Explorer 8 handles the destination folder when downloading from Microsoft Update Catalog. Bug does not occur when using Firefox ESR 52.5.3

IE 8 version used: Refer to "Cumulative Security Update for Internet Explorer 8 for WES09 and POSReady 2009 (KB4052978)": German (this update is installed), English (for reference only).

[socratis]

This bug might be related to how Internet Explorer 8 handles the destination folder when downloading from Microsoft Update Catalog. Bug does not occur when using Firefox ESR 52.5.3

Why would you say something that bad about IE8?

No, joking aside, if you can DnD something that you downloaded using method A, but not with method B, then I would say that something is wrong with method B. Also, do you have any "local" files that you can replicate this with? Not with the convoluted method that you gave, but something... simpler perhaps?


PS: I fixed your URLs, and KUDOS for including the ticket # on your thread title!!!

[simon31337]

Reduced test case:

• Create new empty folder with name "2018-01 Security Update for Windows XP Embedded SP3 for x86-based Systems (KB4056941)" on Windows XP guest.
• In this folder, create new text file with content "123", save this file.
• Rename text file to "X86-de-windowsxp-kb4056941-x86-embedded-deu_c634c79dffa84d150ad48e7c58a484a7de6e774a.exe"

When copying the folder to a Windows 10 host, the bug occurs:

Drag and drop error from host (VERR_PATH_NOT_FOUND).

Fehlercode:VBOX_E_IPRT_ERROR (0x80BB0005)
Komponente:GuestWrap
Interface:IGuest {13a11514-402e-022e-6180-c3944de3f9c8}

The bug does NOT occur if you do the exact same steps, but remove "X86-de-" from the pseudo-exe filename. Could this be a PATH_MAX issue?

Please note, if you create an empty text file with no content, the behavior is undefined!
This 0-size-text-file bug has already been reported in ticket #17443

In this case, you may receive:
1) No error message, but folder is not created on the host.

2) Current drop operation still in progress.
Fehlercode:E_FAIL (0x80004005)
Komponente:GuestDnDSourceWrap
Interface:IGuestDnDSource {dedfb5d9-4c1b-edf7-fdf3-c1be6827dc28}
Callee:IDnDSource {d23a9ca3-42da-c94b-8aec-21968e08355d}

3) Another drop operation already is in progress.
Fehlercode:E_INVALIDARG (0x80070057)
Komponente:GuestDnDSourceWrap
Interface:IGuestDnDSource {dedfb5d9-4c1b-edf7-fdf3-c1be6827dc28}
Callee:IDnDSource {d23a9ca3-42da-c94b-8aec-21968e08355d}

4) Maybe more errors...

[socratis]

Nicer, that's much better
I saw that you updated the ticket as well. I'm sure that the developers will see that. I was able to replicate your issue on an OSX 10.11.6 with 5.2.5 (r120042), and I removed the " (KB4056941)" part and it worked... So I guess you're on to something.