mirror of
https://github.com/clechasseur/pathcopycopy.git
synced 2026-04-25 12:15:58 +03:00
[GH-ISSUE #105] Pathcopycopy release 18.0 will not allow me to accept license terms and install #103
Labels
No labels
bug
duplicate
enhancement
enhancement
enhancement
fixed
help wanted
help wanted
invalid
pull-request
question
waiting for input
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/pathcopycopy#103
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @pabristow on GitHub (Jan 28, 2020).
Original GitHub issue: https://github.com/clechasseur/pathcopycopy/issues/105
Originally assigned to: @clechasseur on GitHub.
Describe the bug
Pathcopycopy release 18.0 will not allow me to accept license terms and install.
Windows 10, having version 17.1 installed OK.
Cancel button does not cancel, but closing window via X
To Reproduce
Steps to reproduce the behavior:
Go to location of pathcopycopy18.0.exe
Click on pathcopycopy18.0.exe
Try to accept the license terms, but cannot get the button to light.
Click on cancel - nothing happens.
5 Click on X, exists setup with a message to confirm.
Expected behavior
install
Software (please complete the following information):
Additional context
Add any other context about the problem here.
version 17.1 installed OK.
@clechasseur commented on GitHub (Jan 29, 2020):
Strange. Did you get to choose between All Users and Current User installation modes before getting to the license page?
If the answer is no, can you try to uninstall your current version and then try to install 18.0? (You won't lose your settings if you uninstall.)
@pabristow commented on GitHub (Jan 29, 2020):
Strange indeed, but the good news is that pathcopycopy 18.0 installed as expected after a cold start this morning.
I've checked my version and that it works OK too.
(The install failure may be connected with an strange Outlook behaviour unable to read any downloaded messages, also 'fixed' by a cold start).
So I blame Windows 10 for this. Sorry for noise. (And thanks again for an excellent applet - should be standard Windows!)