Image 1 — Privacy tech company Proton AG breaks its own password manager Proton Pass with transition to MSIX build—and now advises turning off VPN to fix it
Image 2 — Privacy tech company Proton AG breaks its own password manager Proton Pass with transition to MSIX build—and now advises turning off VPN to fix it
Image 3 — Privacy tech company Proton AG breaks its own password manager Proton Pass with transition to MSIX build—and now advises turning off VPN to fix it
Image 4 — Privacy tech company Proton AG breaks its own password manager Proton Pass with transition to MSIX build—and now advises turning off VPN to fix it

Privacy tech company Proton AG breaks its own password manager Proton Pass with transition to MSIX build—and now advises turning off VPN to fix it

Update 1: I've now confirmed Proton's own VPN (Windows client) is the culprit, even when the browser doing the authenticating is excluded under split tunneling rules. I've notified Proton. No response as of this update. The VPN only needs to be disabled during the authentication/handoff. You can enable it after that and still get into Proton Pass. I'll update further if I discover any other anomalies.

-----

Proton has recently begun transitioning its password manager Proton Pass for Windows to a new MSIX build from the previous .exe installer. Once you install the new build, open it, and try to sign into it, you're auto-redirected to your default browser. That's where you authenticate into your Proton account. Once you do, you get a browser popup that you must manually click to redirect back to the Windows Proton Pass app. But even though you successfully authenticated via browser, the Proton Pass app itself refuses to process the handoff, throwing an "Invalid selector" error and locking you out.

I reported this defect to Proton Support. They suggested I try downgrading my privacy by turning off my VPN.

I then posted a terms-compliant reply to another redditor's comment about the same issue. I did this on Proton's sub r/ProtonMail. My reply was instantly shadow-banned.

This is increasingly Proton's blueprint: user finds bug, user reports bug, Proton says downgrade security as a workaround, user posts on Reddit, Proton shadow-bans user.

u/RemarkableOil451 — 11 days ago

⚠️Numerous Systemic Post-Upgrade UI Bugs + Tech Support's Weeks-Long Broken Ticketing System

UPDATE (July 21): After 20 days (just 1 day after this post went live), a "Senior Support" agent emailed me directly via email, not using their ticketing system. She completely validated my post.

The agent provided supposed screenshots of their internal dashboard purporting to show they had "replied" to me on July 3, July 6, and July 15. But their ticketing system's outbound routing is completely dead; it never sent a single one of those emails to my inbox.

To facilitate a software rollback, this Senior Support agent didn't give me a direct link to Reolink's own servers but rather a link to the Internet Archive's Wayback Machine. Does that sound professional to you? (Thank you to the community members here who actually had the direct Reolink download links).

They again asked for my PC logs and system specs to diagnose their own known hard-coded UI scaling defect.

I resent the screen recording I'd already sent them, and I denied their request for intrusive and irrelevant personal information. I also refused the Wayback Machine rollback link and demanded they forward the video evidence to Engineering for a patch.

Here's the senior agent's full email, along with their attached screenshots. Note that the agent never explains why their ticketing system has generated numerous additional tickets, and why they haven't responded to any of those either (not just the original ticket referenced below):

https://preview.redd.it/0ug68cjdtpeh1.png?width=1359&format=png&auto=webp&s=8edfbbb1275e9ff4da5a506613018115c0a11bcc

https://preview.redd.it/wculmjenupeh1.png?width=2864&format=png&auto=webp&s=3cf9692b60c7bc16b98da0d42ad8d4a487bfd85f

https://preview.redd.it/d23q6fgpupeh1.png?width=2680&format=png&auto=webp&s=38aecdef8cb5d48f3e01614a69fb7952592a7adc

https://preview.redd.it/l8wfczyrupeh1.png?width=2067&format=png&auto=webp&s=f00e4530f4167196b4ca595af5bd55d76e44353e

https://preview.redd.it/o77vbxwtupeh1.png?width=2763&format=png&auto=webp&s=5fbc01f90cf16cbaea6ee19152abfcc362c9d4c1

_____ORIGINAL POST_____

I'm posting this to warn the community about numerous systemic UI bugs in the latest Windows client v8.21.4 update, and to hopefully get the attention of Reolink staff, because their standard email support has been a complete void for weeks.

👉 The Software Bugs (v8.21.4) (triggered immediately on upgrading)

1️⃣ UI Scaling Failure #1: On Windows 11 at 125% DPI, the application's viewing window forces a scale that exceeds physical display boundaries. Manual edge-resizing and native window controls (maximize/restore) are completely unresponsive. Screenshot below:

https://preview.redd.it/88jnscz30keh1.jpg?width=1925&format=pjpg&auto=webp&s=ac7030257480f3775e980aa78b0d647005aebcf4

2️⃣ UI Scaling Failure #2: Even when DPI is set to 100% (recommended), sizing, resizing, minimizing, and maximizing the application's viewing window cuts off the entire bottom portion of the window, including all UI control elements. It takes several re-sizings/maximizings/minimizings for the application window to appear normal. Screenshot below:

https://preview.redd.it/rtb92zcz1keh1.jpg?width=1280&format=pjpg&auto=webp&s=a5e98e92901100f57e1d16d1fee843eccd48abf1

3️⃣ Live View Perimeter Protection Flipping: In Live View, both the "Line Crossing" and "Zone Intrusion" visual overlay markings flip ≈45° on the y axis. For example, if your camera is mounted on the front of your property facing the street, and someone crosses into your property, the visual overlay markings get drawn not along the front and sides of your property but from your property outward into the street and up into the sky. Because this only happens in Live View, I haven't yet captured a screenshot of the behavior, but it happens consistently.

4️⃣ Window Drift: Even when system scaling is dropped to 100%, a maximized client window slowly "drifts" out of position on its own without any user input. Because this happens slowly over time, it's impractical to show before and after screenshots. This behavior is also intermittent.

5️⃣ Auto Live View: The client no longer respects the "Auto Live View" toggle. The application's viewing window launches in Live View even when the "Auto Live View" toggle is off. Toggling it on and off repeatedly doesn't change the malfunction.

👉 The Support Failure

I observed all the above bugs as soon as I upgraded, so I immediately opened Ticket 1795340 on July 2. Support replied with a canned script asking for my camera UID, hardware version, and PC model—which are completely irrelevant to a local Windows GUI rendering defect. They also asked for a screen recording, which I provided right away via email. That was almost three weeks ago, and I've heard absolutely nothing back. Worse, when I followed up repeatedly on the same ticket thread, their ticketing system kept (and keeps) generating brand new tickets (2944006, 2967607, 2970319, etc.).

Regardless, each of those new tickets includes the following promise:

https://preview.redd.it/toe1yksy4keh1.png?width=1230&format=png&auto=webp&s=801a553730989743060ef346bb40b71a558b2cf2

Despite this promise to reply within days, Reolink hasn't replied whatsoever even though it's been three weeks.

It's implausible that Reolink doesn't know not only about all these bugs but also about its broken ticketing system. Yet they've done nothing to correct either. This is inexplicable and unacceptable.

If any Reolink staff monitor this sub, I need you to troubleshoot your ticketing system and the numerous issues I've reported. To that end, escalate this matter to management and Engineering.

reddit.com
u/RemarkableOil451 — 3 months ago
▲ 63 r/ProtonPublic+3 crossposts

“Privacy by Deception”: The Cost of Protecting Proton’s (Proton AG) Privacy Image

[Note: This isn’t about an isolated tech support issue. It’s about what one of the most “privacy-centric” companies on the planet—including its most-senior personnel—did when I exposed an architectural defect in one of their privacy apps that corrupted downloads of encrypted user data. The company’s official position was this, until I fought them for weeks to change it, and even then, they dodged any meaningful accountability: the affected user base should downgrade their entire privacy and security posture in order to “workaround” the app’s architectural defect.]

—

I’m an active Proton Unlimited subscriber and enjoy contributing my time and energy by reporting new bugs and when possible, helping to craft fixes for those bugs. A few months ago, I diagnosed and reported a data-corrupting defect in the Proton Drive Android app. The bug wasn’t massive, but it was substantive. From almost the moment I reported it, Proton fixated not on patching the defect but on managing me, the person who found it and who insisted it be treated the appropriate priority for an architectural defect.

What followed was a singular, nearly 50-day campaign of bad-faith damage control by Proton involving multiple Support agents, a supervisor, three “accountability” teams, and a public-facing reddit account, culminating in my outright administrative censorship. Although it took weeks of persistence (more on that below), I persuaded Proton to patch the defect begrudgingly. What I learned in the process is ugly: Proton’s “Privacy by Default” image is just a mask for what lies beneath: “Privacy by Deception.”

Here’s the timeline of how Proton weaponized its privacy image and corporate standing to manipulate a substantive defect and suppress the person who exposed it for telling the truth about the nature of that defect.

• Phase 1: The Misclassification (Filip G.)

Between May 22 and 26 (2026), I notified Proton that when the Proton Drive app’s auto-lock feature was set to “Immediately” (a mandatory setting for those whose Proton Drive syncs with not just their phone but also their numerous other devices, including their tablets and PCs), the act of initiating a download would trigger the app’s (not Android’s) lock screen, interrupt the OS intent, and result in a corrupted 0-byte download of the target file onto the device. This was a glaring architectural defect, not the intended behavior, and I have no doubt Filip G. understood its seriousness.

Given that I’d already diagnosed the bug, it was easy enough to prioritize it properly and slate it for an immediate patch. But on May 26, just four days after my initial report, Proton began establishing their bad-faith strategy. First, Support Agent Filip G. misclassified the data-corrupting failure of lifecycle management as a mere “suggestion,” which means it wouldn’t be fixed in the foreseeable future. I pushed back via additional emails, and when that proved fruitless, I asked for a supervisor.

• Phase 2: The Stonewalling (Marija S.)

Support Agent Marija S. took over on June 1. First, she wasn’t even a supervisor. Second, all she did was parrot back to me my own diagnosis and her colleague’s (Filip G.’s) misclassification. I reiterated the clear and reproducible data-corrupting nature of the defect and again asked for a supervisor.

• Phase 3: The Gaslighting (Damjan)

On June 2, Supervisor Damjan finally stepped in. He immediately built a straw-man argument (saying “background” downloading wasn’t possible, which had nothing to do with the behavior I reported), and he likewise parroted back to me the problem I myself had discovered. Because Damjan was the third person (a supervisor, no less) to churn me through the same dead-end hand-waving, there was no longer any doubt: Instead of owning up to and fixing the architectural defect in their privacy-oriented software, they were trying to manage and gaslight the person who exposed it and wanted it addressed properly.

But Damjan was just getting started. The next thing he did was to advise me to weaken my multi-device security as a “workaround” to their engineering failure. When I called him out on June 4, he conceded his negligence: “I completely understand and apologize for offering such a workaround in the first place.” Despite this, he continued pretending the bug wasn’t a defect but a “suggestion” and requested “improvement.”

I demanded he put me in touch with his own superiors. He claimed he forwarded my “latest” email to them. I demanded he send his superiors the entire ticket thread, not just my latest message. He changed his tune and claimed he’d already sent the whole thing. I repeated my demand for his supervisors so I could file a complaint against him. He pretended he couldn’t do that, and then he prematurely and unilaterally closed the ticket while still insisting the defect was just a requested improvement: “Due to the fact that we cannot provide an estimated time of arrival for this improvement, we would not be able to keep this ticket request open, and will need to close it.” Soon after, he followed through and buried the ticket. I pushed back, but he became unresponsive altogether.

• Phase 4: The Containment, Cover-Up, and Censorship

I bypassed Damjan and escalated the full ticket thread via email to Proton’s security@, abuse@, and legal@ teams. Their response: 🦗🦗🦗 Not even an acknowledgement, not even when I followed up.

Having exhausted the organizational chain of command, I went public, posting the documented timeline with appropriate evidence to r/ProtonMail under the title “Proton Support Loses the Plot: Misclassifying defects, pushing bad security advice, gatekeeping formal complaints, closing unresolved tickets, and oversight teams that are M.I.A.” But my original post was immediately “filtered.” I asked (exceedingly politely) that my post be approved for publication, but I heard nothing back. My post remained (and remains) shadow-banned.

The next day, Proton used its official reddit account to respond, but only with more self-serving gaslighting and fabricated claims. I pushed back using their own quoted words proving their response was full of lies. But Proton shadow-banned my reply as well. That means the only thing that is and was ever visible is my title and Proton’s response. They didn’t just get the last word; they got the only word. And if that still wasn’t enough, they even hid my reddit post from search indexing. See for yourselves: https://www.reddit.com/r/ProtonMail/comments/1uqolpe/proton_support_loses_the_plot_misclassifying/ (if they kill this link entirely, I’ve archived it here: https://ghostarchive.org/archive/BOcZh).

Proton creates a façade of “Privacy by Default” to hide its true nature: “Privacy by Deception.” It protects its image by willfully misclassifying defects as “suggestions” and “improvements,” negligently suggesting users compromise their own security in service of Proton’s almighty image, burying unresolved tickets and refusing to re-open them, obstructing users from holding Proton technically and organizationally accountable, and then censoring you users when they go public with the truth.

Now I’m left to wonder if Proton will target this post as well, even though it’s not on their subreddit. We’ll see.

reddit.com
u/Ok_Combination_1548 — 3 months ago