An HFS+ drive does not need to be reformatted for Windows before file recovery. If the physical storage can be read, use a tool that understands HFS+ and export files to another device. First confirm that the volume is actually HFS+: APFS, encrypted storage and a failed enclosure are separate conditions.
Identify the original Mac volume
Record the format from the original Mac or reliable disk records if available. Mac OS Extended refers to HFS+ variants; Apple documents the distinction between HFS+ and APFS. A disk that once belonged to a Mac is not necessarily HFS+.
Include whether it was journaled or case-sensitive. Apple’s HFS Plus technical note describes these structures and variants. These details help identify the source; they do not prove that a particular damaged volume will recover.
If encryption was used, locate the legitimate credentials and resolve the access requirements before treating the disk as ordinary plaintext HFS+. Do not infer encryption support from a general HFS+ file-system label.
Connect without preparing the disk
Use a compatible connection and the correct power supply. Check the model and physical capacity in Windows. Cancel initialization and formatting prompts. Windows being unable to browse the file system is not permission to replace it with NTFS or exFAT.
If the original Mac can still read the files reliably, ordinary copying or a known-good backup may be simpler. Prioritize that route for existing files. If the drive makes abnormal sounds or produces persistent read errors, stop repeated access and assess preservation before scanning.
Prepare separate output storage that Windows can write and that has enough space for the files you need. Keep the recovery application off the source. A disk image, where appropriate and safely obtained, should also reside elsewhere.
Scan the readable HFS+ source
XRecovery supports quick-scan recovery of HFS+ storage from Windows. Select the identified device or relevant volume and inspect the resulting folders and files. This is a Windows recovery workflow; it does not require or imply a native macOS edition of the program.
Search for distinctive project or folder names and check dates and sizes. Preview supported common formats where useful, then export a small set to the destination. If the source is a case-sensitive variant, watch for names that differ only by letter case when saving to a destination that does not distinguish them. Keep conflicting files in separate folders rather than accepting an overwrite prompt.
Results depend on the volume’s condition and the readable metadata and file content that remain. If the expected content is not found, recheck the original format and access conditions before repeatedly scanning with unsuitable assumptions.
Validate ordinary files and Mac workflows differently
Open exported photos and documents to inspect their full content. Compare to known-good copies where available. A Mac application project may rely on several companion files, package contents or metadata that a simple document preview does not validate. Keep the recovered folder structure and test that workflow on an appropriate Mac before declaring the project restored.
If only generated names survive, retain a mapping as you identify files on the destination. Do not rename or reorganize the source during recovery. After preserving the useful output, decide separately whether the original disk should be repaired, erased or replaced. Recovering files on Windows does not itself restore normal Mac mounting or establish complete Mac backup compatibility.