New package: PassMark.VolatilityWorkbench version 3.0.1014

[Dragon1573]

Checklist for Pull Requests

• Have you signed the Contributor License Agreement?
• Resolve [Package Request]: PassmarkSoftware.VolatilityWorkbench #319666

Manifests

• Have you checked that there aren't other open pull requests for the same manifest update/change?
• This PR only modifies one (1) manifest
• Have you validated your manifest locally with winget validate --manifest <path>?
• Have you tested your manifest locally with winget install --manifest <path>?
• Does your manifest conform to the 1.10 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

Manual validation

Warning

VolatilityWorkbench.exe failed to launch in my Windows Sandbox instance.

---

Microsoft Reviewers: Open in CodeFlow

[wingetbot]

Validation Pipeline Run WinGetSvc-Validation-116-320347-20251207-1

[Dragon1573]

This may happen for URLs pointing to domains that do not align with the publisher domain or package domain.

osforensics.com is hosted by PassMark™ Software.

[stephengillie]

Manual Validation ended with:

Volatility 3 Framework 2.26.2

(Automated response - build 1178.)

[stephengillie]

Hi @Dragon1573

Since the application returns 2.26.2 as a version number, while 3.0.1014 seems to be written to the Registry, should a DisplayVersion be used?

[stephengillie]

@wingetbot waivers Add Validation-Domain

[wingetbot]

Validation Pipeline Run WinGetSvc-Validation-122-320347-20251212-1

[Dragon1573]

Since the application returns 2.26.2 as a version number, while 3.0.1014 seems to be written to the Registry, should a DisplayVersion be used?

@stephengillie, I think it shouldn't.

The current version of Volatility Workbench is v3.0.1014

This build is based on Volatility 3 Framework v2.26.2. The source code for Volatility 3 Framework was downloaded from github on October 8, 2025 and compiled using Pyinstaller

Originally posted in "Download" section in homepage

[wingetbot]

Publish pipeline succeeded for this Pull Request. Once you refresh your index, this change should be present.