wsappbak /backup /target <path> [/package <fullPackageName>] [/noprogress] [/v]
| Switch | Description |
|-----------------|-----------------------------------------------------------------------------|
| /backup | Perform a backup (required). |
| /target | Output directory for backup files. |
| /package | (Optional) Specific package family name. Omit to back up all user apps. |
| /noprogress | Suppress progress display. |
| /v | Verbose logging. |
The wsappbak file is generated during the creation of Windows bootable media. When you use the Media Creation Tool from Microsoft to download and install Windows 10 or Windows 11 onto a USB drive, the tool prepares partitions, formats the drive, and copies setup files.
During this process, some temporary or backup metadata related to Windows Store applications (modern UWP apps) may be stored in a file named wsappbak. It is not executable; it is generally a metadata container or a lightweight database file that the installer references when provisioning apps during the Windows installation.
If you use Rufus with advanced settings (e.g., creating a Windows To Go drive or enabling Windows Store app preloading), Rufus may also create a wsappbak file.
wsappbak stands for Windows Store App Backup.
It is a legitimate folder created by Windows (usually found in C:\Program Files\WindowsApps) that stores backup data for pre-installed applications, specifically the Microsoft Store and its associated apps. wsappbak
Prerequisites:
Step 1 – Locate the wsappbak File
Search your entire internal storage. Common locations:
Step 2 – Copy the File
Copy the .wsappbak file to:
Internal Storage/WhatsApp/Databases/
Step 3 – Rename the File
Rename it to exactly:
msgstore.db.crypt12
Note: If you already have a msgstore.db.crypt12 present, rename the old one to msgstore.db.crypt12.old first. wsappbak stands for Windows Store App Backup
Step 4 – Set Correct Permissions (Root users or troubleshooting)
Using a terminal or advanced file manager, set permissions to 600 (owner read/write) or equivalent: rw-------.
Step 5 – Reinstall or Open WhatsApp
Uninstall WhatsApp completely, then reinstall it from the Play Store. When prompted to restore from Google Drive, skip that option. Instead, WhatsApp should automatically detect the local msgstore.db.crypt12 file and offer to restore it.
Warning: If the
wsappbakfile is corrupted or uses an older encryption method (crypt7, crypt8, crypt10), WhatsApp will fail to restore it and may create a new empty database.
Advanced users can use an open-source script like whatsapp-decrypt.py (found on GitHub). This requires:
Without the key, the wsappbak file is unbreakable due to AES-256-GCM encryption. resulting in a wsappbak file.
Some advanced users who customize Windows images (using NTLite or MSMG Toolkit) rely on the wsappbak file to restore preloaded Store apps. If you are not modifying Windows images, you have no need for it.
When you run a “cleanup” or “duplicate finder” app, the tool scans for large .crypt12 files. Some of these apps (particularly older versions) do not recognize the .crypt12 extension. To prevent accidental deletion, they rename the file to a neutral extension—like .wsappbak—and move it to a folder such as ./backups/temp/ or ./WhatsApp/Backups/Manual/.
Similarly, some automatic cloud backup apps (like Dropsync or FolderSync) may rename files during transfer if a naming conflict occurs on the destination server, resulting in a wsappbak file.
Key takeaway: A
wsappbakfile is almost always a valid WhatsApp database file in disguise.