quantenemitter

Results 10 comments of quantenemitter

0x8a15000f : Data required by the source is missing

In my case, I could resolve the issue as follows: 1. Log-in with local administrator 2. powershell -> winget source update

0x8a15000f : Data required by the source is missing

For clarification In my case, just running PowerShell with a "normal" user, but selecting "as Administrator" did _not_ help. I literally meant: Start the windows-session as local Administrator. My last...

OneDrive falsely reports Ransomware while using new vault format in 1.5.0+

> other than informing about such false positives Yes, that's what this report is about: to take into _consideration_, if the user should be informed about this. > Is this...

OneDrive falsely reports Ransomware while using new vault format in 1.5.0+

I've tested it: No warning after upgrading an already-uploaded vault. BUT a warning on another occasion shortly after changing some (>2) files in a vault (new format).

OneDrive falsely reports Ransomware while using new vault format in 1.5.0+

The files OneDrive reported ended with .c9r

OneDrive falsely reports Ransomware while using new vault format in 1.5.0+

This issue didn't reappear for quite a while now. Close?

OneDrive falsely reports Ransomware while using new vault format in 1.5.0+

Just to.keep things straight: I'm not that person at GitHub. And thank you for the feature request at OneDrive.

OneDrive falsely reports Ransomware while using new vault format in 1.5.0+

Version 1.5.6, status: Got another ransomware-message after filling a new vault with ~15 MB of files. → their KI has not updated yet.

OneDrive falsely reports Ransomware while using new vault format in 1.5.0+

This still happens w/ the latest version of cryptomator after creating many excrypted files at onedrive. (=keep-alive for this issue)

OneDrive falsely reports Ransomware while using new vault format in 1.5.0+

While syncing cryptomator files with OneDrive Build 23.189.0910.0001, an icon of a safe shows up, so OneDrive seems to recognize the extension. There's hope the upstream bug has been fixed.