Ver 16 install

[MSpagni]

Uninstalled the latest install and cleaned a bit of the mess.
When I reinstalled the latest version the installer said: "the licence is ok".
Terminated the install: "unregistered".
The password file was left where it was and not moved to the new position.

[psguru]

What did you mean by "Terminated the install"? Was the password copied when you completed an install? When? Also, what's in the log?

[MSpagni]

What did you mean by "Terminated the install"?

Bad wording. "Completed the install..."

Was the password copied when you completed an install? When?

No. And the password was copied when I manually copied it.

Also, what's in the log?

Sorry, I didn't ask for a log in that case.

[psguru]

You can find setup log files in your %temp% folder, the look like Setup Log [timestamp] [number].txt. If you find the latest, please attach here.

[MSpagni]

You can find setup log files in your %temp% folder, the look like Setup Log [timestamp] [number].txt.

Do you mean that the setup log would be created even without "/log" command line option?
The only log file I have is the one attached here, but it comes from the installation in which everything went ok.

[psguru]

Do you mean that the setup log would be created even without "/log" command line option?

Yes. The log will be created in the %temp% folder.

The only log file I have is the one attached here, but it comes from the installation in which everything went ok.

The log you attached shows that you installed into C:\Program Files\ExamDiff Pro, where password.bin file already existed. The scenario I'm curious about is when EDP 16 is first installed while previous installation(s) existed and had a password file.

[MSpagni]

The scenario I'm curious about is when EDP 16 is first installed while previous installation(s) existed and had a password file.

Yes, I know.

Do you mean that the setup log would be created even without "/log" command line option?

Yes. The log will be created in the %temp% folder.

Are you sure? I have no log files in %temp%.

[psguru]

Yes, we are using this option in setup:

https://jrsoftware.org/ishelp/index.php ... tuplogging

f set to yes, Setup will always create a log file. Equivalent to passing /LOG on the command line.

And then

/LOG
Causes Setup to create a log file in the user's TEMP directory detailing file installation and [Run] actions taken during the installation process. This can be a helpful debugging aid. For example, if you suspect a file isn't being replaced when you believe it should be (or vice versa), the log file will tell you if the file was really skipped, and why.

The log file is created with a unique name based on the current date. (It will not overwrite or append to existing files.)

The information contained in the log file is technical in nature and therefore not intended to be understandable by end users. Nor is it designed to be machine-parsable; the format of the file is subject to change without notice.

Perhaps your log files are located in a different folder.

[MSpagni]

I made a search in the whole disk.

[MSpagni]

(...and NOT using the windows search service but a program who really scans the directories.)

[psguru]

I don't know what to tell you: the flag is set, and it works for me. In any case, there's always the explicit /LOG option.

[MSpagni]

Next time we'll see.

[MSpagni]

Here it comes (automatically generated).

[psguru]

Thanks. I see the following:

2025-02-25 20:51:47.695 [EDP]: Copying "C:\Program Files\ExamDiff Pro\password.bin" to "C:\Program Files\ExamDiff Pro 16.0\password.bin"

Was it copied?

[MSpagni]

Sorry, I didn't look.
What a stupid!