Edge-Drop on the Microsoft Store: What to Expect

The Microsoft Store is the most discoverable distribution channel for Windows desktop apps. Edge-Drop is listed there as an MSIX package, alongside the canonical GitHub NSIS installer. The two channels have different update models, different permissions, and occasionally different feature parity. This guide covers what to expect from the Store listing, how Store builds differ from GitHub builds, what permissions the Store package requests, and how to pick a channel. For the source-build alternative see how to build from source for the curious; for the donation model see Ko-fi and UPI support: what donations fund.

What the Store listing offers

The Microsoft Store listing for Edge-Drop provides:

• A one-click install via the Store app, no separate installer download.
• Automatic updates via the Store's update infrastructure.
• A standard uninstall path via Settings → Apps.
• A listing page with screenshots, description, and version history.
• Store ratings and reviews.

For end users who are not comfortable running installers from GitHub, the Store is the friendlier path. The install is sandboxed; the package cannot write outside its install directory; the uninstall is clean. For users on Windows 10 S mode or Windows 11 SE, where only Store apps are allowed, the Store is the only path.

What Store builds cannot do

Store builds cannot auto-update via the app. The Store owns the update lifecycle. This means:

• A new Edge-Drop version released on GitHub today will not appear in the Store until it passes Store certification, which typically takes hours to days but can stretch to weeks for ambiguous cases.
• The Store checks for updates on its own cadence; the user can also trigger a manual check via Microsoft Store → Library → Get updates.
• Edge-Drop's in-app "Check for updates" button does not work on Store builds; it links to the Store app instead.

This is not an Edge-Drop decision; it is Microsoft Store policy. Every Store-listed desktop app faces the same constraint. The trade-off is documented in how Edge-Drop updates on GitHub builds and the broader GitHub installer vs Microsoft Store: which build comparison.

What permissions the Store package requests

Store apps run in an AppContainer sandbox with declared capabilities. Edge-Drop's Store package typically requests:

• Clipboard access — required for the core feature.
• File system access (limited) — for the user data folder under %APPDATA%\Edge-Drop and for reading file paths from the clipboard (HDROP).
• Network access (limited) — for fetching link card titles and favicons (if enabled in Behaviour). See how to open links from Edge-Drop in your browser.
• Run at startup — for the launch-at-login behaviour. See how to launch Edge-Drop at login.
• Notifications — for the "restart to update" prompts (on GitHub builds) and other in-app notifications.

The package does not request:

• Broad file system access outside %APPDATA%\Edge-Drop.
• Camera, microphone, or location.
• Contacts, calendar, or account info.
• Background execution unrelated to clipboard polling.

The declared capabilities are visible in the Store listing under "Permissions" before installation. Users can verify before installing.

For the broader topic of auditing app permissions, see how to audit whether a clipboard app talks to the network.

How Store builds differ from GitHub builds

The two channels cannot be installed side-by-side. Switching channels requires uninstalling one and installing the other. See how to uninstall Edge-Drop cleanly for the uninstall workflow.

Feature parity

Most Edge-Drop features are identical across channels. The exceptions:

• Auto-update — GitHub only. Store builds use the Store.
• Launch at login — both channels support it, but the mechanism differs. Store builds use the Store's startup API; GitHub builds use the registry Run key. See how to launch Edge-Drop at login.
• In-app "Check for updates" — GitHub only. Store builds show a link to the Store app.
• Permissions UI — Store builds show the Store's permission prompt at install time; GitHub builds show no prompt (standard desktop install).
• Certification-induced differences — occasionally, a feature may be removed or modified in the Store build to pass Store certification. These are documented in the changelog when they happen.

For the vast majority of users, the difference is invisible. The channel choice is about update cadence and trust model, not feature set.

How to install from the Store

1. Open the Microsoft Store app on Windows.
2. Search for "Edge-Drop".
3. Click the listing.
4. Click "Get" or "Install".
5. The Store downloads and installs the package.
6. Edge-Drop appears in the Start menu.

The install does not require administrator elevation; Store apps install per-user by default.

To verify the install:

1. Open Settings → Apps → Installed apps.
2. Find Edge-Drop. The version shown should match the Store listing.
3. Open Edge-Drop from the Start menu.
4. The tray icon appears; the shelf is ready.

For the broader install workflow, see how to install Edge-Drop on Windows 10 and 11.

How to update a Store build

Store builds update via the Store:

1. Open the Microsoft Store app.
2. Go to Library (bottom-left in Windows 11).
3. Click "Get updates."
4. The Store checks all installed apps and updates any with a newer version available.
5. Edge-Drop updates in place; user data is preserved.

The Store also auto-checks for updates on its own cadence. Manual checks are useful when you know a new version shipped on GitHub and want to see if it has reached the Store yet.

For the auto-update companion, see how Edge-Drop updates on GitHub builds.

How to switch from Store to GitHub

To switch from the Store build to the GitHub build:

1. Quit Edge-Drop (tray icon → Quit).
2. Uninstall via Settings → Apps → Installed apps → Edge-Drop → Uninstall.
3. Download the latest NSIS installer from https://github.com/Deepender25/Edge-Drop/releases.
4. Run the installer.
5. Edge-Drop starts as a GitHub build; auto-update takes over from then on.

User data under %APPDATA%\Edge-Drop is generally preserved across the switch. See where Edge-Drop stores data on disk for the layout and how to uninstall Edge-Drop cleanly for the full clean-uninstall workflow.

How to switch from GitHub to Store

1. Quit Edge-Drop.
2. Uninstall via Settings → Apps.
3. Open the Microsoft Store.
4. Search for "Edge-Drop".
5. Install.

User data is generally preserved.

When to pick which channel

The decision tree:

• Want updates as soon as they ship? GitHub build.
• Want Store-managed updates, no manual intervention? Store build.
• On Windows 10 S mode or Windows 11 SE? Store build (the only option).
• Corporate environment with Store-only policy? Store build.
• Want to inspect the installer or run from a known commit? GitHub build (or source — see how to build from source for the curious).
• Want side-by-side testing? Neither channel supports side-by-side; use a virtual machine.

For most users, the Store is the simpler path. For users who want the latest version or who want to verify the binary against a GitHub release, the GitHub build is the right choice. For a deeper comparison, see GitHub installer vs Microsoft Store: which build.

What Edge-Drop does not claim

• Store builds are not "more secure" than GitHub builds. The sandbox is a structural difference, not a security claim. Both channels ship the same code (modulo certification-induced differences).
• Store builds are not "faster" or "slower" than GitHub builds. Performance is the same.
• Store builds do not have access to features the GitHub build lacks. The two are at feature parity (with the exceptions noted above).
• The Store listing's rating is not a quality claim. Store ratings reflect user feedback, which is subjective and may include reviews from older versions.
• The Store does not guarantee a specific update cadence. The certification pipeline can introduce variable delays.

For the broader topic of Store vs direct distribution, see Microsoft Store clipboard apps vs GitHub releases and store ratings vs actual clipboard quality.

Summary

Edge-Drop is in the Microsoft Store as an MSIX package. Store builds offer one-click install, Store-managed updates, a sandboxed permissions model, and clean uninstall. They cannot auto-update via the app; the Store owns the update lifecycle. Store builds may lag the GitHub release by hours to weeks due to certification. Most features are at parity with GitHub builds; the differences are auto-update, launch-at-login mechanism, and the in-app "Check for updates" button. To switch channels, uninstall one and install the other; user data is preserved. For most end users the Store is the simpler path; for users who want same-day updates or binary verification, the GitHub build is the right choice.

Related reading

• Ko-fi and UPI Support: What Donations Fund
• How to Install Edge-Drop on Windows 10 and 11
• What Local-First Software Means for Clipboard Apps
• How to Enable Clipboard History in Windows 11

Sources

• Microsoft Learn — Microsoft Store overview — official documentation for the Microsoft Store distribution channel
• Microsoft Learn — MSIX package identity — documents the MSIX packaging format used for Store builds
• Microsoft Learn — App capability declarations — documents the permission model that Store builds use
• Microsoft Learn — Microsoft Store policy — documents the policy that prohibits in-app updaters in Store-listed apps
• Microsoft Support — Install apps from the Microsoft Store — official instructions for installing Store apps including Edge-Drop

Copy. Stack. Drop.

Transform your clipboard into an interactive edge shelf. Stack, pin, and drag assets into any app with zero friction.

Download for Windows Get from Microsoft Store

How to Install Guide · First 10 Minutes Guide · Drag & Drop Guide · Edge-Drop vs Win+V · Support