JPGRepair Changelog

What's new in JPGRepair 2.8.101

May 27, 2020
  • Added MCU clone tool
  • To repair a JPEG you typically need to remove corrupt data which affects alignment of all data following corruption. To re-align you then insert stuff bytes (zeros) which leave a grey horizontal line. In this video I show how I use MCUs directly above the grey line to replace the stuff bytes.
  • File selection dialog ‘show all files added’.
  • Brings JpegDigger to version 2.6.121
  • Adds ability to load disk images. Only RAW images supported.
  • Adds ability to create a RAW disk image. Testing is limited to memory cards and USB flash drives I have at my disposal. I have tried to make it as robust as possible, also when dealing with unstable memory cards and flash drives.
  • Manual defrag requires less clicks: add option to auto render, so resulting image is loaded as soon as you select or deselect clusters.
  • May feel slower as I was too optimistic in previous build with discarding blocks of data, resulting in the tool missing potentially recoverable data.

New in JPGRepair 2.8.88 (Apr 14, 2020)

  • I removed and changed code that might upset virus scanners because that’s becoming a bit of a plague.
  • Various virus scanners have been flagging my tools as trojan lately, I must stress these are false positives. JPEG-Repair nor JpegDigger do what they’re intended for, repair and recover digital images. They do not leave traces on your system, don’t call home or anything of the sorts.
  • These detections are ‘heuristic’ Some AV vendors refer to it as ‘AI’ that supposedly learns how malware behaves and what it looks like. So the scanner does not actually and factually find a virus, but think the program might contain some harmful code. Sometimes this is based on for example readable strings in the compiled program. So for example there is code in the program that deals with handling the registration key. Certain variable names may resemble code in ransomware software as both deal with hashing and encryption. And indeed, something simple changing names of such variables to something more neutral, lowers detection rates.
  • It is kind of ridiculous that I have to put so much time and work into this because they get it wrong.
  • If your AV software complains about JPEG-Repair or JpegDigger, please submit them to the AV software vendor for analysis.
  • Brings JpegDigger to version 2.6.48. I have been bug hunting to try to pin point some perky bugs that show up lately; hang while scanning, hang while copying and error 13 messages.