starred/pathcopycopy

Fork 0

mirror of https://github.com/clechasseur/pathcopycopy.git synced 2026-04-25 12:15:58 +03:00

[GH-ISSUE #95] Disable "Check for updates automatically" doesn't work #94

New issue

Closed

opened 2026-02-25 21:32:38 +03:00 by kerem · 8 comments

kerem commented

2026-02-25 21:32:38 +03:00

Owner

Originally created by @AlexIn-Tech on GitHub (Oct 16, 2019).
Original GitHub issue: https://github.com/clechasseur/pathcopycopy/issues/95

Originally assigned to: @clechasseur on GitHub.

Dear Clechasseur,

I'm using your soft and it's really great. The only issue I get is with the auto check for update.
I disabled this option but Path Copy Copy is still showing me there is a new update available.

Best regards ,
Amar0g

Originally created by @AlexIn-Tech on GitHub (Oct 16, 2019). Original GitHub issue: https://github.com/clechasseur/pathcopycopy/issues/95 Originally assigned to: @clechasseur on GitHub. Dear Clechasseur, I'm using your soft and it's really great. The only issue I get is with the auto check for update. I disabled this option but Path Copy Copy is still showing me there is a new update available. ![image](https://user-images.githubusercontent.com/18593496/66890631-0c0a5b80-efe7-11e9-8249-e411b99cfade.png) Best regards , Amar0g

kerem

2026-02-25 21:32:38 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-25 21:32:38 +03:00

Author

Owner

@clechasseur commented on GitHub (Oct 16, 2019):

What version are you currently using?

Using regedit, can you navigate to the following key:

HKEY_CURRENT_USER\Software\clechasseur\PathCopyCopy

and validate that there is a value named DisableSoftwareUpdate with value 1?

@clechasseur commented on GitHub (Oct 16, 2019): What version are you currently using? Using `regedit`, can you navigate to the following key: `HKEY_CURRENT_USER\Software\clechasseur\PathCopyCopy` and validate that there is a value named `DisableSoftwareUpdate` with value `1`?

kerem commented

2026-02-25 21:32:38 +03:00

Author

Owner

@AlexIn-Tech commented on GitHub (Oct 16, 2019):

17.0.1

This registery key doesn't exist.

As a workaround I can create it.

Edit : I just ticked and unticked the check box and the reg key appeared. So , by default, the auto-update was disable (in the UI) but there was no reg key to apply this settings.

@AlexIn-Tech commented on GitHub (Oct 16, 2019): 17.0.1 This registery key doesn't exist. ![image](https://user-images.githubusercontent.com/18593496/66925827-4eef2200-f02d-11e9-93fc-5da7831a63cf.png) As a workaround I can create it. Edit : I just ticked and unticked the check box and the reg key appeared. So , by default, the auto-update was disable (in the UI) but there was no reg key to apply this settings.

kerem commented

2026-02-25 21:32:38 +03:00

Author

Owner

@clechasseur commented on GitHub (Oct 16, 2019):

Can you check if it exists in the following keys instead (if they exist):

HKEY_LOCAL_MACHINE\Software\clechasseur\PathCopyCopy
HKEY_LOCAL_MACHINE\Software\Wow6432Node\clechasseur\PathCopyCopy

@clechasseur commented on GitHub (Oct 16, 2019): Can you check if it exists in the following keys instead (if they exist): `HKEY_LOCAL_MACHINE\Software\clechasseur\PathCopyCopy` `HKEY_LOCAL_MACHINE\Software\Wow6432Node\clechasseur\PathCopyCopy`

kerem commented

2026-02-25 21:32:38 +03:00

Author

Owner

@AlexIn-Tech commented on GitHub (Oct 16, 2019):

I can confirm, it exists in HKLM \Software\clechasseur\PathCopyCopy

but not in Wow6432Node

@AlexIn-Tech commented on GitHub (Oct 16, 2019): I can confirm, it exists in `HKLM \Software\clechasseur\PathCopyCopy` but not in Wow6432Node

kerem commented

2026-02-25 21:32:38 +03:00

Author

Owner

@clechasseur commented on GitHub (Oct 16, 2019):

Did you initially install Path Copy Copy using the .msi installer that once existed, by any chance? Other perhaps via Chocolatey? I'm not sure how it ended up there.

What version of Windows are you using? 32-bit or 64-bit?
Are you using an alternate Windows Explorer?

In the meantime, try creating the value in HKCU and see if it stops offering you the update.

@clechasseur commented on GitHub (Oct 16, 2019): Did you initially install Path Copy Copy using the .msi installer that once existed, by any chance? Other perhaps via Chocolatey? I'm not sure how it ended up there. What version of Windows are you using? 32-bit or 64-bit? Are you using an alternate Windows Explorer? In the meantime, try creating the value in HKCU and see if it stops offering you the update.

kerem commented

2026-02-25 21:32:38 +03:00

Author

Owner

@AlexIn-Tech commented on GitHub (Oct 21, 2019):

Hi ,
Sorry for the delay.

So currently I'm installing the software with this command : "PathCopyCopy17.0.1.exe" /VERYSILENT /SUPRESSMSGBOXES /NORESTART

I'll edit the registry.

Best regards,

Edit : In my folder I have a settings.reg file in the same folder than the installer. Do you have an option that 'll check if a settings.reg file is available in the same folder than the installer and apply the settings in the registry ? If yes, I guess the issue is linked to this file. But I cannot remember where it came from. Or, maybe, this file is just a backup I made.

@AlexIn-Tech commented on GitHub (Oct 21, 2019): Hi , Sorry for the delay. So currently I'm installing the software with this command : "PathCopyCopy17.0.1.exe" /VERYSILENT /SUPRESSMSGBOXES /NORESTART I'll edit the registry. Best regards, Edit : In my folder I have a settings.reg file in the same folder than the installer. Do you have an option that 'll check if a settings.reg file is available in the same folder than the installer and apply the settings in the registry ? If yes, I guess the issue is linked to this file. But I cannot remember where it came from. Or, maybe, this file is just a backup I made.

kerem commented

2026-02-25 21:32:38 +03:00

Author

Owner

@clechasseur commented on GitHub (Oct 21, 2019):

So currently I'm installing the software with this command : "PathCopyCopy17.0.1.exe" /VERYSILENT /SUPRESSMSGBOXES /NORESTART

Hmm, that still doesn't explain how the setting got in HKLM. Weird.

Edit : In my folder I have a settings.reg file in the same folder than the installer. Do you have an option that 'll check if a settings.reg file is available in the same folder than the installer and apply the settings in the registry ? If yes, I guess the issue is linked to this file. But I cannot remember where it came from. Or, maybe, this file is just a backup I made.

No, the installer does not check for such a .reg file.

Let me know if creating the value in HKCU fixes the issue or not. I'll leave this open, as it still doesn't explain why update checks are performed when the updates are disabled globally.

@clechasseur commented on GitHub (Oct 21, 2019): > So currently I'm installing the software with this command : "PathCopyCopy17.0.1.exe" /VERYSILENT /SUPRESSMSGBOXES /NORESTART Hmm, that still doesn't explain how the setting got in HKLM. Weird. > Edit : In my folder I have a settings.reg file in the same folder than the installer. Do you have an option that 'll check if a settings.reg file is available in the same folder than the installer and apply the settings in the registry ? If yes, I guess the issue is linked to this file. But I cannot remember where it came from. Or, maybe, this file is just a backup I made. No, the installer does not check for such a .reg file. Let me know if creating the value in HKCU fixes the issue or not. I'll leave this open, as it still doesn't explain why update checks are performed when the updates are disabled globally.

kerem commented

2026-02-25 21:32:38 +03:00

Author

Owner

@clechasseur commented on GitHub (Jan 4, 2020):

I've tested this locally and if updates are disabled, the update dialog does not appear. However, I thought of some possible scenarios which would cause this, but it involves using shells with different bitness.

Since I did not hear back about this, I'll close this until we can get a reproducible scenario.

@clechasseur commented on GitHub (Jan 4, 2020): I've tested this locally and if updates are disabled, the update dialog does not appear. However, I thought of some possible scenarios which would cause this, but it involves using shells with different bitness. Since I did not hear back about this, I'll close this until we can get a reproducible scenario.