For Windows 10 and 11
Browse your Quest's shared folders, copy files in either direction, and install apps you have as APK files—all from one Windows app. An APK is an Android app installer file, the format used for Quest apps you build or receive outside the Meta store.
Version 0.4.0 is the first QuestIonAble File Manager release and includes the signed Rusty Kiosk 0.6.4 bundle. Free and open source under the MIT License; the guided setup is the recommended download.
The first connection uses USB. After the headset has authorized this PC, the same app can also help you move to Wi-Fi.
Open the guided setup. Review the app name and publisher before approving the Windows administrator prompt.
Download the current Windows package from Android Developers. It supplies ADB, the developer connection File Manager uses. You do not need to type ADB commands yourself.
Follow Meta's device setup guide. File Manager cannot enable the account-level setting for you.
Use a USB data cable, put on the headset, and approve the debugging prompt. In File Manager select Refresh, then choose the ready [USB] headset at the top.
Why Windows asks for trust: this public preview uses a project certificate rather than a commercial code-signing identity. The guided setup explains the certificate before adding it. If your Windows policy blocks that route, use one of the alternative downloads below.
Select a ready headset first. Every action is then scoped to that device.
Open Files. Browse the shared storage shown by the app, select a file or open a folder, then use Pull to copy from Quest to Windows or Push to copy from Windows to the open Quest folder.
The starting location is the Quest's shared storage, not private app data.
Open APKs, choose an APK on your PC, review the install options, and select Install on selected headset. Wait for the result before disconnecting.
Installing an APK does not copy saves, purchases, downloaded assets, or store entitlement.
Confirm the headset at the top, enter or browse a permitted Quest path, then select Pull or Push. The status bar at the bottom reports the result.
These are available when you need them, but they are not part of the first connection.
Install a complete base-and-split APK set together, or export a sideloaded app when Android reports it as one APK file.
Move an already-authorized headset to Wi-Fi ADB and run one bounded install across several selected Wi-Fi headsets.
Read headset and controller battery levels, keep a connected headset awake, or set and later clear fixed CPU and GPU levels.
Rusty Kiosk is a separate headset app that gives you a searchable launcher, portable tags, and normal or softly guarded launch.
Open the Rusty Kiosk tab to install and provision it over the authorized USB connection. After setup, that tab can manage its catalogue, tags, launch actions, and optional direct link.
Nothing in Rusty Kiosk is required for ordinary file browsing, APK installation, Wi-Fi ADB, or device status. Those File Manager functions continue to work when Kiosk is not installed.
The upper half of the tab holds the one-time USB setup and the optional direct link. Read Transparent status before sending another change.
Search and filter the headset catalogue, launch the selected installed app, or import and export its tag file. Missing apps remain labelled and cannot be launched.
The screenshots above are deterministic app renders with sample device and app data; they contain no headset identifiers or device captures.
For a manual signed install, download the certificate, then the App Installer file or MSIX. If package installation is restricted, use the portable ZIP.
Start with an authorized USB connection. Open Wi-Fi ADB, choose Enable and connect, review the confirmation, then select the new [Wi-Fi] entry. Wi-Fi ADB may stop after a reboot, network change, or authorization change.
Connect at least two ready Wi-Fi headsets, check the intended targets in APKs, choose one APK or one bundle folder, and set a sensible parallel limit. File Manager keeps a separate result for each headset.
Export works only when Android reports one APK file. Apps made from a base APK plus split APKs are refused so an incomplete backup is never presented as usable.
Confirm Developer Mode, try a data-capable cable and another USB port, and look inside the headset for the debugging approval. Also check whether File Manager reports that ADB is missing.
Install Android SDK Platform Tools, then reopen the app. Advanced users can also add its folder to PATH or set QUESTIONABLE_FILE_MANAGER_ADB to the full path of adb.exe.
The app may target a different CPU or Android version, require another package, or expect assets that were not included. The APK file alone is not always the complete app.
No. It shows only the paths Android permits through the authorized developer connection. Private app data remains protected.
For checksums, known issues, and bug reports, visit GitHub Releases or open an issue.
