Jump to content

BugZapper

Members
  • Content Count

    3
  • Joined

  • Last visited

About BugZapper

  • Rank
    New Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I got word back that the fix in the latest version does, in fact solve the problem. Thanks again for this great product and support!
  2. Thank you very much! The update did come down, and the batch-file test case was fixed, so I'm pretty sure ScanSnap will work too. Unfortunately, installing Malwarebytes uninstalled the anti-ransomware beta on the PC with ScanSnap before we had a chance to test the fix.
  3. Hi, Problem: “Convert to Searchable PDF” in SnanSnap Organizer for Fujitsu scanners fails with error 5 when beta 0.9.18.807-1.1.29 is enabled. Temporarily disable protection, and the problem goes away. Exclusions don’t seem to help. OS: Windows 10 1709, 64-bit. Confirmed on a second PC. Investigation: I used ProcMon to identify the source of the error as SetRenameFileInformation() failing with ACCESS DENIED (Windows error 5). Then I identified the application causing this by a process of elimination. I found that the ScanSnap organizer runs OCR and adds the info to a copy of the original PDF. Then, if successful, it replaces the original with the updated copy. However something MalwareBytes Anti-Ransomware is doing seems to be breaking the SetRenameFileInformation() internal Windows API for .PDF files, and several other file types such as .jpg, and .txt, but not for .docx, .htm, or random extensions such as .xxx. When protection is enabled, this API returns ACCESS DENIED for files with certain extensions. But when disabled, the API succeeds as expected. Fortunately I found that this problem can be reproed using the following simple batch file so you don’t need a Fujitsu scanner to work on this: @echo off echo Test > f1.pdf echo Test > f2.pdf echo ---------------- echo Moving PDFs will fail (access denied) if Anti-Ransomware protection is enabled, and succeed if disabled echo on move f1.pdf f2.pdf @echo off echo. echo ---------------- echo But many other file types are not affected anda move always succeeds echo Test > f1.xxx echo Test > f2.xxx echo on move f1.xxx f2.xxx Note that when the above move fails, the del command will delete the destination file. So I know this isn't a problem with permissions or a file being locked in memory. I suspect this problem may break other software as well. Thanks. This is the first problem I’ve had since the very early beta. I really like your program. Others nag me with false positives, but this seems much smarter.
×

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.