diff --git a/src/crypto/index.ts b/src/crypto/index.ts
index 4b5b5a5b6..cad5800ac 100644
--- a/src/crypto/index.ts
+++ b/src/crypto/index.ts
@@ -974,10 +974,9 @@ export class Crypto extends EventEmitter {
                 const backupKey = await this.getSessionBackupPrivateKey() || await getKeyBackupPassphrase();
                 if (!backupKey) {
                     // This will require user intervention to recover from since we don't have the key
-                    // backup key anywhere. It's possible that this is a legacy setup where the SSSS
-                    // master key is the same as the key backup key, but we can't assume that it is:
-                    // we'd have to at least check it against the backup. Alternatively, the user could
-                    // just set up a new key backup and the key for the new backup will be stored.
+                    // backup key anywhere. The user should probably just set up a new key backup and
+                    // the key for the new backup will be stored. If we hit this scenario in the wild
+                    // with any frequency, we should do more than just log an error.
                     logger.error("Key backup is enabled but couldn't get key backup key!");
                     return;
                 }