A medical practice contacted us because MMD Auto Reports Downloader, also referred to as VisualFeed in their setup, kept displaying an invalid JSON error. Reports were still downloading, but the same files returned on each sync. Emma Mitchell traced the failure to the step that tells the supplier’s service a report has been downloaded. A supplier-provided application update restored that step and stopped the repeated downloads in testing.
Short answer: if reports download but the application fails while updating their status, confirm the fault with your supplier and obtain the supported downloader update. Installing version 1.1.13 fixed our October 2026 case. That is the version we tested, not a claim that it is the latest release.
Resolved by Emma Mitchell, Senior Engineer. Written up by Elliot Munro, CISO.
The MMD file-status error
The title of the error referred to updating a VF report ID. Other windows referred to VT or ACT records. The body read:
‘<‘ is an invalid start of a value. Path: $ | LineNumber: 0 | BytePositionInLine: 0.

In this case, signing in and downloading reports succeeded. The error followed the downloads, when the program tried to update their status. The next automatic sync then downloaded the same reports again.
Why the same reports kept downloading
The downloader expected a JSON response from the service that marks a report as downloaded. Emma reproduced the failure and found that this request returned HTML instead. The program could not read that response, so the service did not record the reports as completed.
That explains why files could arrive successfully while errors continued to appear. Repeated downloads were a consequence of the failed status update. The error was initially investigated as a sign-in problem, but the later reproduction showed that the failure occurred after sign-in and download.
The wording alone does not prove the same cause in every installation. Establish which action triggers it before resetting credentials or changing network settings.
Check where the downloader actually runs
- Identify the computer or server running the MMD program. In our case, staff used Remote Desktop, so the application ran on the server rather than on the workstation in front of them.
- Record the downloader version and the shortcut each affected user opens. We found different versions launched through shared and per-user shortcuts.
- Check whether sign-in succeeds, whether new reports arrive, and whether the same reports download again on the next sync.
- Capture the full error for the supplier. Remove patient information, report identifiers and account details from screenshots and logs shared outside approved support channels.
Install the supplier’s supported update
In our case, BOC Ophthalmic Instruments supplied version 1.1.13 after the fault was escalated. Contact your existing supplier or Micro Medical Devices for the currently supported installer and instructions. Their contact page is a support route, not a public release note for this fix.
- Agree on an installation time and ask affected staff to close the downloader, including sessions on a shared server.
- Have your IT team install the supplier-approved update on the computer that actually runs the program.
- Check that shared Desktop and Start menu shortcuts open the updated version. Review per-user shortcuts and startup entries so they do not launch an older copy.
- Close any old downloader processes still running in other sessions. Ask staff to reopen the updated application and confirm the correct account and destination folder.
We removed obsolete shortcuts rather than assuming a system-wide uninstall had removed every per-user copy. Follow your supplier’s instructions before removing application files or saved configuration.
Verify the next sync, not just the first download
Emma tested two report downloads after the update. Both completed without the error, and the next automatic sync did not download them again. That second check confirmed the completion-status step was working.
- Use a supplier-approved test or controlled download and confirm it completes without a status-update error.
- Wait for the next automatic sync and confirm the same completed reports are not downloaded again.
- Confirm that the practice’s normal destination folder is configured correctly and that staff can find new reports.
Do not delete original clinical reports or reset download history simply to clear the repeated-download symptom. If the error remains, send the supplier the version, timing and failing step so they can investigate the response from their service.
Other medical software troubleshooting
- Bp Premier displays This Site Uses XSLT
- Bp Premier encounters an error emailing a patient file
- GCIT software support
If a report downloader keeps failing or repeating work, get in touch with our team.