FILE COPY ISSUES

[SKIBUM17]

I am using windows 10 64 bit with the latest builds installed.

And I just purchased XYplorer.

When I do file copies the following message pops up: "Could not close the previous instance of this script. Keep waiting?"

It shows up when I select the next tab to continue the copy process to a different drive.

Does anyone know how to eliminate this message from popping up?

I have never seen it before so I am assuming it has something to do with my XYplorer.

thanks

[admin]

This message is not from XYplorer. Do you have a screenshot of the message box?

[bdeshi]

"Could not close the previous instance of this script. Keep waiting?"

I suspect that's from contextmenu64.exe. Or some other autohotkey script. So do you have any such scripts running? [edited]

[SKIBUM17]

hello,

thank you for your response.

I have attached a jpg of the message.

It doesn't mean anything to me. I don't know what a "script" is.

First time I remember seeing this message.

[SKIBUM17]

This message is not from XYplorer. Do you have a screenshot of the message box?

Hi

I submitted a screenshot per your request.

thank you

[SKIBUM17]

"Could not close the previous instance of this script. Keep waiting?"

I suspect that's from contextmenu64.exe. Or some other autohotkey script. So do you have any such scripts running? [edited]

I don't have any scripts running as far as I know; I don't even know what a script is.

[admin]

Thanks for the shot. Try this: Close XYplorer. Open Task Manager and look for a process called "contextmenu64.exe". Kill it. Then start XYplorer again.

[SKIBUM17]

Thanks for the shot. Try this: Close XYplorer. Open Task Manager and look for a process called "contextmenu64.exe". Kill it. Then start XYplorer again.

Hi
checked and I don't have a process called "contextmenu64.exe" listed.

[admin]

Hm. Out of ideas for now.

[SKIBUM17]

Hm. Out of ideas for now.

ok thanks. odd thing is it doesn't always show up when I do file copies. And it just started showing up when I installed XYplorer. I read the "usage tips" webpage and made some changes according to the tips. Wonder if tweeking Windows Defender has something to do with it?

[HectorTod]

I don't see how Windows Defender would mess around with this, but who knows. Did you actually try to play around with any of the settings?

[SKIBUM17]

I don't see how Windows Defender would mess around with this, but who knows. Did you actually try to play around with any of the settings?

no I haven't; but I will try undoing the changes I made after reading the usage tips. I will let you know. thanks

[SKIBUM17]

Hm. Out of ideas for now.

I noticed that there is an "exe" file in the XYplorer installation folder called "ContextMenu64". I added it to the exclusions list in both Windows Defender and Malwarebytes, still got the same message but at least this time I saw it in the Task Manager window. I killed it and re-ran XYplorer but I got the message again.
I also tried running ContextMenu64 as an administrator but that didn't work either.

Is there a 64 bit version of XYplorer? The one I have is the 32bit version and I am running 64bit windows 10 Pro, could this be the problem?

[SKIBUM17]

I don't see how Windows Defender would mess around with this, but who knows. Did you actually try to play around with any of the settings?

no I haven't; but I will try undoing the changes I made after reading the usage tips. I will let you know. thanks

I noticed that there is an "exe" file in the XYplorer installation folder called "ContextMenu64". I tried tweeking my system but nothing I could do would stop the message from popping up.

[jupe]

This is more of a workaround than a solution, but the following option will stop that exe file from running (and I assume the message that is showing):

Configuration | Other | Shell Integration | 64-bit Windows | Show the 64-bit context menu

it may require a restart of XY.