Copying files from VMWare Workstation often fail
Forum rules
You might want to read this if you're looking for priority service
Please Include The Following Information
1) Your XYplorer Version (e.g., v28.00.0801)
2) Your Windows Version (e.g., Win 11)
3) Your Screen Scaling Percentage (e.g., 125%).
Use Your Profile Or Signature
We strongly recommend adding your Windows Version and Screen Scaling Percentage to the Location field in your Profile or to your Signature. That way, you only have to type them once, and we won't have to search for that vital information.
How To Attach Images
When attaching an Image, please use the Attachment tab at the bottom of your post and click "Add files".
You might want to read this if you're looking for priority service
1) Your XYplorer Version (e.g., v28.00.0801)
2) Your Windows Version (e.g., Win 11)
3) Your Screen Scaling Percentage (e.g., 125%).
We strongly recommend adding your Windows Version and Screen Scaling Percentage to the Location field in your Profile or to your Signature. That way, you only have to type them once, and we won't have to search for that vital information.
When attaching an Image, please use the Attachment tab at the bottom of your post and click "Add files".
-
Kernik
- Posts: 37
- Joined: 24 Jul 2018 07:05
Copying files from VMWare Workstation often fail
With VMware Workstation Pro on Windows 10 and XYplorer 32-bit v27.20.1509, pasting files/folders from the VM fails with "The system cannot find the file specified."
But I discovered that if I paste the same clipboard contents into Windows Explorer first, I can then immediately paste into XYplorer (without copying the file again) and it works.
The failure also occurs with Custom Copy and background processing disabled, and with fresh XYplorer settings.
But I discovered that if I paste the same clipboard contents into Windows Explorer first, I can then immediately paste into XYplorer (without copying the file again) and it works.
The failure also occurs with Custom Copy and background processing disabled, and with fresh XYplorer settings.
-
admin
- Site Admin
- Posts: 67271
- Joined: 22 May 2004 16:48
- Location: Win8.1, Win10, Win11, all @100%
- Contact:
Re: Copying files from VMWare Workstation often fail
Interesting, but there's nothing I can do about it.
FAQ | XY News RSS | XY X
-
Kernik
- Posts: 37
- Joined: 24 Jul 2018 07:05
Re: Copying files from VMWare Workstation often fail
I've done some additional testing and found something that might help explain it.
1. Copying a file inside the VM and pasting into XYplorer fails with "The system cannot find the file specified."
2. But every successful Explorer paste creates a new hexadecimal staging subdirectory under %TEMP%\vmware-<Windows User Name>\VMwareDnD, containing a copy of the file.
3. When XYplorer subsequently succeeds (right after pasting via Explorer), it does not create another staging directory. It appears to reuse the file staged by Explorer.
For example, XYplorer initially failed trying to copy:
E:\Temp\vmware-UserName\VMwareDnD\f9f314d4\Test.md
Explorer's successful paste then created the file under:
E:\Temp\vmware-UserName\VMwareDnD\a48cb0d6\Test.md
Afterward, XYplorer could paste successfully.
So VMware appears to defer creating the actual temporary file until a receiving application initiates the transfer through the appropriate Windows Shell/OLE mechanism.
Explorer performs whatever additional interaction is required to materialize the file, after which XYplorer can copy it normally.
Could it be that XYplorer is still extracting the CF_HDROP path and attempting a conventional copy, rather than passing the original clipboard IDataObject to the Shell?
Either that or VMware requires an additional interaction that Explorer performs but XYplorer's Shell fallback doesn't trigger.
1. Copying a file inside the VM and pasting into XYplorer fails with "The system cannot find the file specified."
2. But every successful Explorer paste creates a new hexadecimal staging subdirectory under %TEMP%\vmware-<Windows User Name>\VMwareDnD, containing a copy of the file.
3. When XYplorer subsequently succeeds (right after pasting via Explorer), it does not create another staging directory. It appears to reuse the file staged by Explorer.
For example, XYplorer initially failed trying to copy:
E:\Temp\vmware-UserName\VMwareDnD\f9f314d4\Test.md
Explorer's successful paste then created the file under:
E:\Temp\vmware-UserName\VMwareDnD\a48cb0d6\Test.md
Afterward, XYplorer could paste successfully.
So VMware appears to defer creating the actual temporary file until a receiving application initiates the transfer through the appropriate Windows Shell/OLE mechanism.
Explorer performs whatever additional interaction is required to materialize the file, after which XYplorer can copy it normally.
Could it be that XYplorer is still extracting the CF_HDROP path and attempting a conventional copy, rather than passing the original clipboard IDataObject to the Shell?
Either that or VMware requires an additional interaction that Explorer performs but XYplorer's Shell fallback doesn't trigger.
-
admin
- Site Admin
- Posts: 67271
- Joined: 22 May 2004 16:48
- Location: Win8.1, Win10, Win11, all @100%
- Contact:
Re: Copying files from VMWare Workstation often fail
Could be. You get the same issue with drag and drop or other non-clipboard ways of copying?
FAQ | XY News RSS | XY X
-
Kernik
- Posts: 37
- Joined: 24 Jul 2018 07:05
Re: Copying files from VMWare Workstation often fail
I just tested drag and drop.
"Use standard shell drag and drop": Enabled
VM -> HOST
----------
1. Windows Explorer -> XYplorer: FAIL
2. Windows Explorer -> Windows Explorer: SUCCESS
3. XYplorer -> XYplorer: FAIL
4. XYplorer -> Windows Explorer: SUCCESS
HOST -> VM
----------
5. XYplorer -> Windows Explorer: SUCCESS
6. XYplorer -> XYplorer: FAIL
7. Windows Explorer -> Windows Explorer: SUCCESS
8. Windows Explorer -> XYplorer: FAIL
Observations:
------------
- When dragging from the VM into XYplorer on the host, the mouse cursor changes to a prohibited symbol (circle with a slash) when moved over XYplorer.
- All 4 transfers with Windows Explorer as the destination succeed.
- All 4 transfers with XYplorer as the destination fail.
- The source application makes no difference.
- The direction of transfer makes no difference.
The common factor in every failure is XYplorer being the destination.
"Use standard shell drag and drop": Enabled
VM -> HOST
----------
1. Windows Explorer -> XYplorer: FAIL
2. Windows Explorer -> Windows Explorer: SUCCESS
3. XYplorer -> XYplorer: FAIL
4. XYplorer -> Windows Explorer: SUCCESS
HOST -> VM
----------
5. XYplorer -> Windows Explorer: SUCCESS
6. XYplorer -> XYplorer: FAIL
7. Windows Explorer -> Windows Explorer: SUCCESS
8. Windows Explorer -> XYplorer: FAIL
Observations:
------------
- When dragging from the VM into XYplorer on the host, the mouse cursor changes to a prohibited symbol (circle with a slash) when moved over XYplorer.
- All 4 transfers with Windows Explorer as the destination succeed.
- All 4 transfers with XYplorer as the destination fail.
- The source application makes no difference.
- The direction of transfer makes no difference.
The common factor in every failure is XYplorer being the destination.
-
admin
- Site Admin
- Posts: 67271
- Joined: 22 May 2004 16:48
- Location: Win8.1, Win10, Win11, all @100%
- Contact:
Re: Copying files from VMWare Workstation often fail
Thank you! I put it on my list.
FAQ | XY News RSS | XY X
-
Kernik
- Posts: 37
- Joined: 24 Jul 2018 07:05
Re: Copying files from VMWare Workstation often fail
Thanks, Don!
-
admin
- Site Admin
- Posts: 67271
- Joined: 22 May 2004 16:48
- Location: Win8.1, Win10, Win11, all @100%
- Contact:
Re: Copying files from VMWare Workstation often fail
That's all with v27.20.1509? Did you already test the current 64-bit version?
FAQ | XY News RSS | XY X
-
Kernik
- Posts: 37
- Joined: 24 Jul 2018 07:05
Re: Copying files from VMWare Workstation often fail
I also confirmed that the latest 32-bit version (v27.20.1607) also has the VM file transfer problem.
As for the 64-bit version, I haven't been using it because the last time I checked it out, it wasn't as good as the 32-bit version yet.
But after your post, I tried it out to test this issue.
Just an FYI, on first startup, I got this error:
---
Error: 380 (0x0000017C)
Desc: Invalid property value
Dll: 0
Proc: LOUS@90 <90>
Source:
XY ver: XYplorer 28.40.0617 (64-bit) (Virgin)
OS: Windows 10 Enterprise, 64-bit, Version 22H2, Build 19045.7807 (10.0)
Locale: 1033 (en-US)
ANSI: 1252, ACP: 1252 (ANSI - Latin I)
Font: 0, 0, DBCS: No
DPI: 130 (135.4167%), 3840x2160
Date: 2026-11-06 02:09:34
---
But after I registered and restarted it, the error didn't come up any more.
But that aside, I'm happy to report that pasting from the VM into XY x64 worked successfully.
So whatever the issue with VM file transfer is, you've got it working in the 64-bit version.
As for the 64-bit version, I haven't been using it because the last time I checked it out, it wasn't as good as the 32-bit version yet.
But after your post, I tried it out to test this issue.
Just an FYI, on first startup, I got this error:
---
Error: 380 (0x0000017C)
Desc: Invalid property value
Dll: 0
Proc: LOUS@90 <90>
Source:
XY ver: XYplorer 28.40.0617 (64-bit) (Virgin)
OS: Windows 10 Enterprise, 64-bit, Version 22H2, Build 19045.7807 (10.0)
Locale: 1033 (en-US)
ANSI: 1252, ACP: 1252 (ANSI - Latin I)
Font: 0, 0, DBCS: No
DPI: 130 (135.4167%), 3840x2160
Date: 2026-11-06 02:09:34
---
But after I registered and restarted it, the error didn't come up any more.
But that aside, I'm happy to report that pasting from the VM into XY x64 worked successfully.
So whatever the issue with VM file transfer is, you've got it working in the 64-bit version.
-
admin
- Site Admin
- Posts: 67271
- Joined: 22 May 2004 16:48
- Location: Win8.1, Win10, Win11, all @100%
- Contact:
Re: Copying files from VMWare Workstation often fail
Wow, that's great, thanks for testing!
Maybe the problem was simply the bitness.
The LOUS@90 error is fixed in v28.40.0619.
The LOUS@90 error is fixed in v28.40.0619.
FAQ | XY News RSS | XY X
-
Kernik
- Posts: 37
- Joined: 24 Jul 2018 07:05
Re: Copying files from VMWare Workstation often fail
It's not the bitness.
For one thing, you had a prior bug report that was very similar - and for that, neither the 32 or 64 bit version of XY worked until you fixed it.
But in addition, I just tested this issue with the 32-bit version of Double Commander, and pasting from the VM worked just fine. So this is definitely possible with a 32-bit file manager.
I wonder if the OLE/Shell handling of the 32 and 64 bit versions of XY are different, because that could definitely explain it.
For one thing, you had a prior bug report that was very similar - and for that, neither the 32 or 64 bit version of XY worked until you fixed it.
But in addition, I just tested this issue with the 32-bit version of Double Commander, and pasting from the VM worked just fine. So this is definitely possible with a 32-bit file manager.
I wonder if the OLE/Shell handling of the 32 and 64 bit versions of XY are different, because that could definitely explain it.
-
admin
- Site Admin
- Posts: 67271
- Joined: 22 May 2004 16:48
- Location: Win8.1, Win10, Win11, all @100%
- Contact:
Re: Copying files from VMWare Workstation often fail
I'm not aware of any explicit changes to the source code here, but the improvement could also be due to something provided by the language or the compiler (VB compared to tB).
FAQ | XY News RSS | XY X
-
Kernik
- Posts: 37
- Joined: 24 Jul 2018 07:05
Re: Copying files from VMWare Workstation often fail
A couple of additional testing notes:
I previously tested pasting into XY64, and that does work.
But I just tested drag and drop - and that does *not* work when XY64 is the target.
As it turns out the 32-bit Double Commander behaves the same way - pasting into it works, dragging into it does not.
So these may be slightly different problems. I almost never use drag and drop, so the paste behavior is what I'm most interested in.
---
Now, I don't know if this is the problem, but I found something interesting...
Microsoft's documentation identifies two different ways to access clipboard contents.
Traditional Win32 clipboard API: GetClipboardData(CF_HDROP)
This retrieves the data associated with a particular clipboard format, ordinarily a list of filesystem paths.
OLE clipboard API: OleGetClipboard → IDataObject::GetData
This retrieves a COM data object that can communicate with the application supplying the clipboard data.
Critically, Microsoft says that an IDataObject returned by OleGetClipboard can forward requests to the original data provider, potentially involving remote procedure calls.
So if 32-bit XYplorer obtains a CF_HDROP path using the traditional clipboard API, it may end up with a path to a file that VMware hasn't transferred - that exactly matches the testing I did.
If the 64-bit version instead uses the OLE data object and the appropriate Shell transfer operation, that could explain why it successfully triggers staging the same way Windows Explorer does.
Reference:
https://learn.microsoft.com/en-us/windo ... l/dragdrop
Any chance this is the issue?
I previously tested pasting into XY64, and that does work.
But I just tested drag and drop - and that does *not* work when XY64 is the target.
As it turns out the 32-bit Double Commander behaves the same way - pasting into it works, dragging into it does not.
So these may be slightly different problems. I almost never use drag and drop, so the paste behavior is what I'm most interested in.
---
Now, I don't know if this is the problem, but I found something interesting...
Microsoft's documentation identifies two different ways to access clipboard contents.
Traditional Win32 clipboard API: GetClipboardData(CF_HDROP)
This retrieves the data associated with a particular clipboard format, ordinarily a list of filesystem paths.
OLE clipboard API: OleGetClipboard → IDataObject::GetData
This retrieves a COM data object that can communicate with the application supplying the clipboard data.
Critically, Microsoft says that an IDataObject returned by OleGetClipboard can forward requests to the original data provider, potentially involving remote procedure calls.
So if 32-bit XYplorer obtains a CF_HDROP path using the traditional clipboard API, it may end up with a path to a file that VMware hasn't transferred - that exactly matches the testing I did.
If the 64-bit version instead uses the OLE data object and the appropriate Shell transfer operation, that could explain why it successfully triggers staging the same way Windows Explorer does.
Reference:
https://learn.microsoft.com/en-us/windo ... l/dragdrop
Any chance this is the issue?
-
admin
- Site Admin
- Posts: 67271
- Joined: 22 May 2004 16:48
- Location: Win8.1, Win10, Win11, all @100%
- Contact:
Re: Copying files from VMWare Workstation often fail
I currently have no time to dive into this, but as I said before, the old 32-bit VB version and the new 64-bit TB version don't differ in handling paste, at least not from the source code POV.
FAQ | XY News RSS | XY X
-
Kernik
- Posts: 37
- Joined: 24 Jul 2018 07:05
Re: Copying files from VMWare Workstation often fail
Not to worry, I understand.
Maybe this will pose an interesting puzzle if you're experiencing insomnia at some point.
Maybe this will pose an interesting puzzle if you're experiencing insomnia at some point.
XYplorer Beta Club