Skip to content

[BUG] cppcryptfs-np: Broken autoupdate URLs for 32-bit executables; need to add ARM64 support #657

Closed

Description

@bailey27

Prerequisites

  • I have written a descriptive issue title.
  • I have searched all issues/PRs to ensure it has not already been reported or fixed.
  • I have verified that I am using the latest version of Scoop and corresponding bucket.

Package Name

cppcryptfs-np

Expected/Current Behaviour

The cppcryptfs-np manifest has outdated download URLs for the 32-bit executables in its autoupdate section.

The current releases use:

  • cppcryptfs_32.exe
  • cppcryptfsctl_32.exe

The manifest still references cppcryptfs32.exe and cppcryptfsctl32.exe, which no longer exist. This appears to prevent automated version updates from completing successfully.

Additionally, cppcryptfs now provides native ARM64 executables:

  • cppcryptfs_arm64.exe
  • cppcryptfsctl_arm64.exe

The manifest should be updated to:

  • Correct the 32-bit download URLs.
  • Add ARM64 architecture support.
  • Update the current version to 1.4.5.1.
  • Update the corresponding autoupdate URLs.

I've tested the proposed changes locally using Scoop's checkver.ps1 with -ForceUpdate. It successfully detected version 1.4.5.1 and retrieved SHA-256 hashes for all six executables.

Steps to Reproduce

1. Add the Nonportable bucket if it is not already installed:

   
   scoop bucket add nonportable
   

2. Copy the published manifest into a temporary directory:

   
   mkdir C:\Downloads\scoop-test
   scoop cat cppcryptfs-np > C:\Downloads\scoop-test\cppcryptfs-np.json
   

3. Run Scoop's version checker:

   
   .\bin\checkver.ps1 -App cppcryptfs-np -Dir C:\Downloads\scoop-test -ForceUpdate -ThrowError
   

   Output:

   
   cppcryptfs-np: 1.4.5.1 (scoop version is 1.4.4.10) autoupdate available
   Forcing autoupdate!
   Autoupdating cppcryptfs-np
   Could not find hash in https://api.github.com/repos/bailey27/cppcryptfs/releases
   Downloading cppcryptfs32.exe to compute hashes!
   The request was aborted: The connection was closed unexpectedly.
   URL https://github.com/bailey27/cppcryptfs/releases/download/v1.4.5.1/cppcryptfs32.exe#/cppcryptfs.exe is not valid
   Could not update cppcryptfs-np, hash for cppcryptfs32.exe failed!
   

**Expected behavior:** Scoop successfully updates the manifest to version 1.4.5.1.

**Actual behavior:** Autoupdate fails because the 32-bit executable has been renamed from `cppcryptfs32.exe` to `cppcryptfs_32.exe`.

Possible Solution

I've tested the proposed changes locally using Scoop's checkver.ps1 with -ForceUpdate. It successfully detected version 1.4.5.1 and retrieved SHA-256 hashes for all six executables.

Scoop and Buckets Version

Current Scoop version:
v0.6.0 - Released at 2026-09-30

'main' bucket:
7dada45b45 oh-my-pi: Update to version 18.14.2

'extras' bucket:
84c26f9668 x-anylabeling: Update to version 4.3.0

'versions' bucket:
7fd7723509 swift-nightly: Update to version 20261031.3

'nonportable' bucket:
80460d72 teamviewer-np@15.83.3: Fix hash (Closes #655)

Scoop Config

PS C:\Users\Bailey> Get-Content ~\.config\scoop\config.json | ConvertFrom-Json

last_update                       scoop_repo                              scoop_branch
-----------                       ----------                              ------------
2026-10-31T19:54:04.7959579-04:00 https://github.com/ScoopInstaller/Scoop master

PowerShell Version

PS C:\Users\Bailey> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      5.1.26100.9711
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.26100.9711
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

Additional Softwares

No response

Activity

  1. bailey27 commented on Nov 2, 2026

    @bailey27
    ContributorAuthor

    The contributing guide said I should make an issue before making a PR.

    Can I make a PR for this?

  2. z-Fng commented on Nov 15, 2026

    @z-Fng
    Contributor

    Can I make a PR for this?

    Feel free to open a pull request for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions