Skip to content

exFAT Image Builder v3.6.4 — Faster PFS Builds & Honest Progress

Latest
Latest

Choose a tag to compare

View all tags
@kerrdec97 kerrdec97 released this 12 Jun 01:03
· 2 commits to main since this release
v3.6.4
45d2e4c

🚀 PS5 exFAT Builder v3.6.4

A major stability, reliability, and audit-focused release.

This update includes a large number of fixes, investigations, performance improvements, and workflow enhancements discovered during the ongoing audit process, alongside the upgrade to MkPFS 0.0.8.

⚠️ Important: Many of the fixes included in this release are based on audit findings and targeted bug reports. While they have been tested, several are still receiving wider community validation. If you encounter a problem that was supposed to be fixed, or if an issue still exists on your system, please report it with a full Output Log so it can be investigated further.

⚡ MkPFS 0.0.8 Upgrade

✅ Updated from MkPFS 0.0.7 → 0.0.8
✅ Faster streaming pack operations
✅ Faster verification
✅ Improved stability and reliability
✅ Better compatibility with modern workflows
✅ Improved image packing performance

🛠 Build & Conversion Improvements

✅ Improved final output handling across drives
✅ Safer move/copy verification logic
✅ Better protection against missing output files
✅ Improved cleanup and recovery paths
✅ Additional safeguards against incomplete builds
✅ Better handling of cross-drive operations

🚚 Cross-Drive Output Hardening

  • Final output placement is now fully verified.
  • Cross-drive moves automatically fall back to verified copy operations.
  • Builds can no longer report success while the final file is missing.
  • Partial files are preserved safely if a move fails.

⚡ Temp Folder Improvements

  • Dump → .ffpfsc builds now correctly honour the configured temp folder.
  • Heavy intermediate image creation can now run on fast SSD/NVMe storage while final output remains on slower HDDs.
  • Clear staging diagnostics added.
  • Better handling of temp/output drive combinations.

💾 exFAT Creation Improvements

✅ Added free-space preflight checks before image creation
✅ Improved OSFMount failure diagnostics
✅ Clearer low-space error messages
✅ Better reporting when image creation fails
✅ Improved troubleshooting information

📦 Extraction Improvements

✅ Faster extraction performance on SSD/NVMe systems
✅ Improved extraction reliability
✅ Better extraction diagnostics
✅ Multithreaded Robocopy extraction improvements

📈 PFS Extraction Progress

  • Added progress reporting for .ffpfs and .ffpfsc extraction.
  • Community validation is ongoing to improve accuracy across different PFS image types and workloads.

🖼 Library & Cover Art Improvements

✅ Added .ffpfs support to Library scanning
✅ Improved cover-art lookup logic
✅ Fixed incorrect cover-art selection in extraction workflows
✅ Better handling of image metadata

🔧 Stability Improvements

✅ Unicode path handling improvements
✅ Better handling of unusual filenames and folder names
✅ Improved error recovery
✅ Multiple audit findings addressed
✅ Additional logging and diagnostics throughout the application
✅ Improved final output verification and cleanup

🧪 Community Testing Requested

The following areas are still receiving wider testing and feedback:

📂 PFS Extraction

Please report:

  • .ffpfs extraction behaviour
  • .ffpfsc extraction behaviour
  • Progress display accuracy
  • ETA accuracy
  • Speed reporting accuracy

🌍 Unicode Paths

Please report issues involving:

  • Accented characters (é, ó, ü, etc.)
  • Non-English filenames
  • Japanese, Chinese or Korean paths
  • Special characters in source/output/temp folders

💾 exFAT Creation

Please report:

  • OSFMount errors
  • Low disk space failures
  • Image creation failures
  • Unusual output-drive behaviour

⚡ Temp Folder Behaviour

Please report:

  • Dump → .ffpfsc builds
  • SSD temp + HDD output workflows
  • Different temp/output drive combinations
  • Unexpected staging behaviour

⚠️ If a fix mentioned in these release notes does not work correctly on your system, please report it. Real-world testing is a huge part of the audit process, and reports help identify edge cases that may not appear during development.

📝 Reporting Issues

When reporting problems, please include:

✅ Application version
✅ Windows version
✅ Operation being performed
✅ Source path
✅ Output path
✅ Temp folder path
✅ Full Output Log

The more information provided, the faster issues can be reproduced and fixed.

🙏 Massive thanks to everyone who has tested builds, submitted logs, reported bugs, suggested features, and helped track down difficult issues throughout the audit process.

Your reports directly contributed to many of the fixes included in v3.6.4.

Assets 4
Loading