Public beta release notes
Nodrive 0.50.6
. A consistent four-step drive-creation path, provider setup from each provider card and a security fix for authorisations held in memory.
Changes since 0.50.5. This release concentrates on one path only: creating a drive. The wizard now has four steps for everyone, and Google Drive, OneDrive or Dropbox is connected where users expect it — from the provider card, rather than by pressing “Continue”.
It also includes an invisible security fix: when Nodrive was locked, a provider authorisation granted moments earlier could remain in memory. It now disappears together with the key to your data.
Existing data is unchanged: the drives you already have remain exactly as they were.
Section 01
🆕 New drive: the same four steps for everyone
Previously, the flow had three or four steps depending on the drive type selected two screens earlier: when there was no provider to choose, the Storage step disappeared. A flow that changes length forces users to reinterpret their position every time, and “3 of 3” for one drive is not the same place as “3 of 4” for another.
There are now four steps for every drive: Drive type · Storage · Settings · Confirmation.
For This PC and Nodrive Cloud, the Storage step asks for nothing — it shows where the encrypted data will be stored (the storage folder or the account) and how much space is available there. Previously that figure was unavailable until after the drive was created. If the storage device does not report it, Nodrive says so rather than inventing a zero.
Section 02
🔌 Connect a provider from its own card
Previously Google Drive, OneDrive and Dropbox were selected from a list and authorisation started only after pressing Continue. WebDAV and S3 were the only providers with their own setup screen.
All five now have one: select a provider and its card contains a Connect button (or Set up when credentials are required), together with an explanation of what happens — the browser opens, and access can be revoked at any time from the provider account. After connection, the provider list returns with a Connected badge and the account name, and Continue becomes available.
Three behaviours have also been corrected:
- Back from a provider card returns to the provider list, not to the drive-type choice. Changing provider should not mean changing drive type.
- Connected does not mean selected. Connect Drive and then OneDrive: both remain connected, while a check mark shows which one this drive will use. Previously the second connection disabled the first.
- What you already supplied stays available for the working session. A second drive on the same provider can be created without reopening the browser or re-entering an S3 key. Reopening a provider card during the session preserves the values already entered.
Section 03
🔒 Locking now removes provider authorisation too
🔓 Lock removes the key that opens your data from memory. It did not remove a freshly granted Dropbox, Google Drive or OneDrive consent token — which provides access to your storage at that provider. It now disappears with everything else, and any WebDAV or S3 credentials entered during the session are cleared too.
Drives already created continue to open as before: their permission is stored inside the drive’s encrypted catalogue, not in that temporary memory.
Section 04
✏️ Names used across the interface
The UI/UX wording table has been applied everywhere, not only in the wizard:
- “Your cloud” → “Your storage” (including drive cards and drive migration);
- “This computer” → “This PC”;
- the step is called “Choose storage”, and final confirmation is “Create drive”.
Section 05
⚙️ Drive settings (step 3)
- The title describes the step, not the drive type: “Set up your drive”. Previously it repeated the choice made two screens earlier.
- Access mode uses two side-by-side cards with their own icons — Available offline / Online only — and neither is preselected. Keeping an encrypted local copy is a privacy-relevant choice and should not be made by inertia.
- Continue becomes available only when the step is complete (valid name and access mode selected). If another drive already uses the name, the reason appears below the name field while typing.
Section 06
ℹ️ About Nodrive: all links are present
Website · Release notes · Support · Open-source licences · Terms · Privacy — each opens the page in the language selected in the app, rather than the Windows language.
This closes two known limits from 0.50.5: What’s new in this version no longer points to a missing per-version page, and Terms and Privacy can now be opened from the app.
Section 07
💻 System requirements
- 64-bit Windows 10 version 1709 or later, or Windows 11. Windows 7 and 8.1 are unsupported: the app uses WebView2, the Microsoft Edge engine, which is no longer supported on those systems. Current Windows 10 and Windows 11 installations normally include WebView2 already.
- Windows on ARM is unsupported because no build is currently produced for that architecture.
- WinFsp must be installed. It is the component that presents the drive as a Windows volume (D:, E:…). It is not bundled with Nodrive; the app detects when it is missing and provides the official download link. This is the only step that requires administrator rights; Nodrive itself installs only for the current user.
- Windows Server 2019/2022: not tested.
- Two-step verification requires Windows Hello (fingerprint, face or PIN), a FIDO2 security key, or a Bluetooth phone. It remains optional. ⚠️ A security key is not an ordinary USB memory stick: it is a dedicated device, does not appear as a drive, and needs a PIN before Windows can offer it.
⚠️ The installer is not yet signed. Windows will display a SmartScreen warning with “Unknown publisher”. Choose More info → Run anyway to continue. Code signing is planned.
Section 08
📌 Known limits
- Open-source licences are currently available only on the website. Licence text should also accompany the application and be readable offline; this is in progress.
- Terms and Privacy open in the browser, but are not yet readable offline or bound to the exact version accepted. During the beta, the conditions shown in About Nodrive and in the account panel’s Privacy tab remain applicable.
- The drive letter is not selected during creation; it is selected when mounting, from the letters available at that moment.
- A recovery key copied with Copy remains in the Windows clipboard and, when clipboard history is enabled, in
Win+V. Prefer Save as file… or overwrite the clipboard immediately afterwards. - Provider authorisations can expire quickly while Nodrive’s provider apps remain in test mode.
- The 0.50.1 limitations remain for provider-to-provider moves (closed drive and three full passes) and for transfers between accounts and computers, which use export and reimport.
Section 09
🧪 What is most useful to test
- Create a drive on your storage: connect a provider, go Back from its card, inspect another, and confirm that the first remains connected.
- Create a second drive on the same provider immediately afterwards: the browser should not reopen.
- 🔓 Lock, unlock, then create another drive: the browser must reopen here; this checks the security fix in this version.
- Create a drive on This PC: the Storage step should show the folder and free space, and Settings should not ask for an access mode that has no meaning for a local drive.
- Switch to English and repeat the wizard.
