I have tested this scenario and everything worked as expected for me. I have download and tested the same setup ("Citrix ShareFile Drive Mapper"). In order for me to further investigate this, could you please give me some more details about your environment such as:

1. is the setup that you are trying to repackage located in a shared location?

2. what OS does your VM hold? is it Windows 10 or another version? Also, could you please tell me what version is the Windows are you using (on the VM)? To do so, simply open the run window (WIN + R) and type "winver" then please give me the version + the OS Build number.

I have further tested this but unfortunately I was still not able to replicate the behavior.

Maybe the language of the OS has something to do with this (my VM had the English language). Please give me some more time to further investigate this and I will come back to you with what I have concluded.

That was most probably a bot that somehow passed our anti-bot system. I have deleted it and I apologize for the inconvenience.

In what regards the issue you are encountering, this is still under investigation on our side. The main problem of this consists of the fact that we can not reproduce the behavior, which makes it really hard for us to track down the problem.

If you could help me further investigate this by trying the following, it would be great. Previously, you have said that the EXE is located on a shared location (a shared folder from a network location). Does this issue reproduces when, during the Wizard, you pick the EXE from normal location (e.g. a folder from your Desktop)? Could you please test this out and let me know the results?

It is strange, indeed. You are not the only on that encountered this issue but unfortunately we were never able to replicate this on our side to see where the problem resides.

Here is a screenshot of the logs after I have done the repackaging operation on my machine:

tempsnip.png (50.7 KiB) Viewed 437 times

The error you are encountering here is a system error, which can be translated to: "The network path was not found".

You can either check this by looking it up on the internet or, if you have Visual Studio installed, you can open it --> from the toolbar, press "Tools" --> "Error Lookup" --> enter 53.

There are few things that I was thinking of lately:

1. is your computer part of a domain? If yes, I was thinking that maybe there are some policies which do not allow you to connect to the network location.

2. I have not asked you this before since I was pretty sure this was not the case, but I will give it a try now. Have you tried to manually connect to the network drive. For instance, you can open a CMD prompt and run the following line:

net view \\yourNetworkLocation

If the returned error code is 53, this might indicate that the problem does not reside in Advanced Installer, but in the computer's configuration instead.

3. do you have the "File and Printer sharing" option enabled? To check this, you can open Control Panel --> "Network and Sharing Center" --> "Change advanced sharing settings" --> "Turn on file and printer sharing"

When this option is on, files that you have shared from your computer can be accessed by other people from the network.

Hopefully some of the above information will be useful for you. I will further try to investigate this and see what I can find.

It works now! But i don't know what exactly was the solution for this, because i changed so much settings and i can't remember wich change was the right one. Maybe Trend Micro was the problem. But you can see this case as done and thank you very much for your help!