mirror of
https://github.com/clechasseur/pathcopycopy.git
synced 2026-04-26 04:36:00 +03:00
[GH-ISSUE #50] Last build doesn't install unless SmartScreen is turned off #51
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#51
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 @aybe on GitHub (Nov 20, 2018).
Original GitHub issue: https://github.com/clechasseur/pathcopycopy/issues/50
Originally assigned to: @clechasseur on GitHub.
This was bugging me for quite some time, previous build was working fine.
Currently on
Microsoft Windows [Version 10.0.17134.345]nothing happens when you click the EXE and you end up with this:After fiddling a bit, turning SmartScreen off allows it to run:
You get the old-school warning:
But now it starts:
Not sure if it's related to the wave of buggy patches from Microsoft, e.g. such as I do get my default apps being reset at every boot.
And while Defender reports I'm using Bitdefender Endpoint Security, this setting definitely predates it.
Anyway, that's the fix I found working and wanted to share it with you !
@clechasseur commented on GitHub (Nov 21, 2018):
I basically have this version of Windows too and my SmartScreen option is active, yet I don't experience this. Anyone else had this issue? I'll leave this open.
@thendarion commented on GitHub (Dec 28, 2018):
my AV quarantined the 16.0 installer for no apparent reason on 26th November, and another installer around the same time. so this might not be an issue with the installer but with some random virus definitions in the cloud. :)
@clechasseur commented on GitHub (Apr 30, 2019):
Not sure this was really related to Path Copy Copy - more likely to a bug in Windows itself. I'll close this since no one else seems to be affected.