Drag and drop error when copying folder from WinXP guest to Win10 host -> fixed in 5.2.20

[simon31337]

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 on 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): ​http://download.windowsupdate.com/d/msdownload/update/software/secu/2017/11/ie8-windowsxp-kb4052978-x86-embedded-deu_47bd241186dc8e1200e5971c414d4b0035d8b122.exe English (for reference only): ​http://download.windowsupdate.com/d/msdownload/update/software/secu/2017/11/ie8-windowsxp-kb4052978-x86-embedded-enu_655de71433b5df451bbe435cd0912865302139f6.exe

[simon31337]

zip file

[simon31337]

Forum link: ​https://forums.virtualbox.org/viewtopic.php?f=6&t=86207

Reduced test case:

Create new empty folder with filename "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: https://www.virtualbox.org/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]

I was able to replicate your issue on an OSX 10.11.6 with 5.2.5 (rev. 120042), and I removed the "(KB4056941)" part and it worked. So I guess you're on to something.

[pentagonik]

Just reproduced the issue, working on a fix.

[Socratis]

Fixed? As in... you have a test build for verification?

[pentagonik]

Whops, one button press too many :)

I already know the root cause of the problem and having a fix.

[pentagonik]

We found and fixed the issue -- the bugfix will be available in the next upcoming maintenance version. Thanks for the report!