Skip to main content
Question

FME Workbench 2025.2 Really Slow, Possible .NET Framework Update Issues?

  • July 23, 2026
  • 1 reply
  • 49 views
t.rogers
Participant
Forum|alt.badge.img

Hello,

Last night a forced .NET framework update disrupted a huge AutoCAD based translation.

Now today, even after an uninstall and reinstall of FME, the workbenches i build are painfully slow and i ultimately cancel any processing because initiating translations just takes so much longer than it did yesterday.

When i try and place an AutoCAD reader onto my Canvas, i get a message of ‘Trying to find a DYNAMIC plugin for reader named ‘ACAD’’. Ultimately the reader loads, but it is significantly slower than it was yesterday.

The readers and transformers i place on the canvas are also extremely slow and when i try and run the workbench, the ‘Trying to find a DYNAMIC plugin for reader named ‘ACAD’ appears for a considerable amount of time again before eventually doing what i’ve asked.

 

Has anyone experienced this issue before and know the root cause?

 

Thank you in advance!

      1 reply

      evieatsafe
      Safer
      • evieatsafeSafer
      • Safer
      • August 4, 2026

      Hi ​@t.rogers! Sorry to hear about the disruption in your translation and the following slowdown you are experiencing afterwards.
      The message you are seeing, Trying to find a DYNAMIC plugin for reader named 'ACAD', is FME searching for the AutoCAD library it needs in order to talk to when the reader initializes. Normally this resolves almost instantly. The big slowdown right after the update points to something in that resolution path getting disrupted, rather than a problem with your workspace or the AutoCAD reader itself.

      A few things worth looking into:

      • Check whether an antivirus is actively scanning the newly updated .NET Framework files or your FME installation folder in real time. Excluding the FME install directory can make a noticeable difference.
      • Confirm the .NET Framework version. A forced update can sometimes change the default runtime without fully removing the previous version.

      Since a full reinstall of FME did not resolve it, this does look environment-specific rather than something wrong with your workspace. If none of the above helps, it would be worth submitting a support ticket at https://support.safe.com/s/submit-case so we can dig into your FME log files and confirm what is happening. When you do, please include your exact FME Workbench build number, anything specific to your environment, and a translation log showing how long initialization is now taking.

      Let us know how it goes!

      Happy to help - Evie

      Community Stats

      32,835
      Posts
      124,499
      Replies
      41,399
      Members
      Terms & ConditionsAccessibility statement
      A product of
      Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.