Dualscan™ ShareOFFICIAL OS SHARE SUITE GitHub

MACOS · WINDOWS · CHROME

Your USB image.
Every path, intact.

Move your Dualscan OS project between USB-C, Git and your own AWS S3 bucket. Keep the original image protected. Carry the manifest in one .dualscan file.

Get Share Suite Explore the workflow

Verified file bytes and nested paths.
No drive formatting. No repository ZIP wrapper.

DUALSCAN OS / SHARE SUITE1.3.2
Dualscan OS branded USB-C drive
Select a source. Review the destination. Verify every file.
One projectGit or AWS S3 sources
Three platformsmacOS · Windows · Chrome
Original firstProtected SSS image + added snapshots

STEP BY STEP INSTRUCTIONS

Instruction
manual.

Create a .dualscan file, make an original USB, back up your verified derivative to Git or AWS, and restore it to a new drive. Follow the exact button labels, screenshots and troubleshooting steps.

Read the instruction manual Create a .dualscan file ↓

INSIDE SHARE SUITE

Your project.
A clear path forward.

Pin the source, choose your USB folder, and review each transfer before writing. The same workspace brings discovery, Git and AWS projects together.

Dualscan Share app showing repository transfer, USB backup discovery, Save USB to Git, and .dualscan Git and AWS S3 workspace tabs, with source and destination checks before transfer.
Dualscan™ Share Suite · The transfer workspace. Open the image to see it at full size.

THE WORKFLOW / 01

A project you can
move and verify.

Share works with the actual files. It streams binary content, preserves nested paths, resolves Git LFS payloads and checks file identities before reporting completion.

01

Connect and inspect

Choose a USB folder or pin a public GitHub commit. Find nested Smart Switch snapshots without hardcoding a drive, device ID or backup timestamp.

Standalone APKs are identified by their Android package and detected build. Encrypted Smart Switch presence is reported independently, with its internal version unverified.

02

Back up to your destination

Save a selected USB dataset to your own GitHub, GitLab.com or Bitbucket Cloud repository, or publish a verified Dualscan dataset in a new random folder in your AWS S3 bucket.

Review the destination first. AWS dataset files are public after anonymous verification; protect personal additions with SSS encryption before upload. Existing files and snapshots are not replaced.

03

Restore and read back

Import a filename.dualscan project, connect its Git or AWS source, and select the destination USB folder. Source identities and path collisions are checked before writing.

A verified package wrapper is removed so SmartSwitchBackup2, OEM installers and the original files are placed directly in the USB root. Size, hash and destination read-back checks gate verified completion.

THE ORIGINAL STAYS ORIGINAL / 02

Add your snapshots.
Keep the foundation.

A Dualscan SSS derivative must preserve every original file and app from its pinned official reference. The suite checks the complete original file identities before accepting a derivative.

The official SSS image is listed first in the project. User-added snapshots remain separate beneath SmartSwitchBackup2, with both required snapshot markers checked. Changing or removing an original file blocks the derivative workflow.

Read the Dualscan OS license
PROJECT STRUCTUREILLUSTRATIVE
PACKAGE_ROOT /
├── SmartSwitchBackup2 /
│   ├── official-device /
│   │   └── original-snapshot / ORIGINAL · PROTECTED
│   └── your-device /
│       ├── your-snapshot-01 /
│       └── your-snapshot-02 /
├── OEM installers /
└── other original project files

Original-first is a logical project order. macOS and Windows control their own folder sorting. Home/tray configuration bytes are preserved; icon positions are not decoded or independently certified.

THE PORTABLE PROJECT / 03

One .dualscan file.
Pick up where you need it.

A versioned project file carries the pinned source, file paths, sizes, integrity identities and original-image protection reference. Its Typelocker source locator travels with it.

The project format is data only. It contains source metadata rather than the backup’s binary payloads, and exports exclude account credentials. Binary Typelocker app protection prevents plain-text manifest viewing. Add a passphrase for confidential metadata: the shared app key is recoverable from the app. The source must remain reachable for restore.

Git commit + treeAWS snapshot prefixOEM identitiesOriginal image first

CHOOSE YOUR WORKSPACE / 04

Get the official
Share Suite.

Version 1.3.2 · Use the build for your computer. Desktop and Chrome share the transfer, discovery and project-file workflows.

macOS · Apple silicon

Portable app ZIP · M-series Macs

ARM64 / ZIPDownload

macOS · Intel

Portable app ZIP · Intel-based Macs

X64 / ZIPDownload

Windows

Portable executable · 64-bit

X64 / EXEDownload

Chrome extension

Manifest V3 plugin ZIP · manual developer installation

CHROME / ZIPDownload

Release trust. macOS builds use ad-hoc signatures and do not have Developer ID signing or Apple notarization. The Windows executable is unsigned. Verify download checksums ↗ · Installation instructions ↘

Chrome installation guide ↗

Install the desktop app

First compare your download’s SHA-256 with SHA256SUMS.txt. A match checks download integrity; it does not establish publisher identity or malware safety.

macOS · ad-hoc signed, not notarized
  1. Download the ZIP for your Mac: Apple silicon (ARM64) or Intel (x64), then verify its SHA-256.
  2. Unzip it and move Dualscan™ Share Suite into Applications. Try opening the app.
  3. If macOS cannot verify the developer or notarization, proceed only if you trust this exact download. Open System Settings → Privacy & Security → Open Anyway, then confirm Open and authenticate if requested. This creates an exception for this app.
  4. If macOS reports malware, damage, or a policy block, stop and contact support or your administrator.

See Apple’s app-opening guidance.

Check the Mac download’s SHA-256
shasum -a 256 ~/Downloads/Dualscan-Share-1.3.2-mac-arm64.zip

For Intel, use Dualscan-Share-1.3.2-mac-x64.zip instead. Compare the entire digest with the matching filename in SHA256SUMS.txt.

Windows · unsigned portable EXE
  1. Download the Windows x64 EXE and verify its SHA-256. Open it as your normal user; no installer is required.
  2. If SmartScreen identifies an unrecognized app, choose More info → Run anyway only after verifying this download and deciding you trust it.
  3. If that option is unavailable, or Smart App Control or an organization policy blocks the app, stop and contact support or your administrator. Keep those protections enabled.

See Microsoft’s SmartScreen guidance and direct-distribution guidance.

Check the Windows download’s SHA-256
Get-FileHash "$env:USERPROFILE\Downloads\Dualscan-Share-1.3.2-win-x64.exe" -Algorithm SHA256

Run this in PowerShell. Compare the entire digest with the matching filename in SHA256SUMS.txt.

BEFORE YOU BEGIN

Your storage.
Your destination.

  • Use a USB 3 capable drive and port for better throughput. Thousands of small files and full verification add work beyond a sequential speed rating.
  • Confirm the selected folder is the intended USB root and has enough free space. The browser cannot certify the connector, drive identity or free capacity.
  • AWS uploads require scoped credentials and a public-read policy for the reviewed random dataset folder. Downloads of public projects need no AWS keys. Chrome needs the regional host grant and bucket CORS. AWS storage and request charges apply.
  • Tokens and AWS credentials stay in session memory. Project files and evidence reports exclude them. There is no publisher-operated transfer relay.
  • A verified file transfer does not establish a successful Samsung Smart Switch restore. Device and backup compatibility still apply.