+4Hi,
We run Apps 10 UPD25.
Most users have Windows 11 Pro 24H2 installed. This works fine.
Now some users upgraded their workstations to Windows 11 Pro 25H1. After this the interaction between IEE client and Windows file explorer makes the IEE client crash.
Event viewer shows that the crash is casued by: msvcp140.dll.
It seems as Windows 11 25H1 has made some changes causing this problem.
Does anyone experience same problems and eventually have a solution?
+3We are starting to have the same issue pop up. It’s happened on 25H1 as well as 23H2. Same error in the event viewer.
We’re seeing the same behaviour in Apps 10 Update 22 and 25. Any attempt to import or export files through IFS—whether via document attachments or any feature that opens File Explorer—causes the IFS client to crash on the user’s workstation.
Drag‑and‑drop still works because it bypasses File Explorer entirely.
At the moment we’re waiting to see whether an upcoming Windows update resolves the issue. In the meantime we’re relying on machines that haven’t received the problematic update to handle the affected tasks.
One person in the community mentioned that deleting the 2.0 folder fixed it for them, but testing that on our side didn’t resolve the issue sadly.
If we manage to resolve the issue on our end I’ll message anyone that is still having the issues.
+3Deleting the 2.0 folder did not work for us either. We also tried a new user that had never logged into the computer before which created a new directory path and 2.0 folder but it still freezes. It’s a combination of the msvcp140.dll and something with windows. I did open a separate ticket with IFS as this problem could become widespread within our organization. I will also post if we hear of any solution.
We’re seeing the same behaviour in Apps 10 Update 22 and 25. Any attempt to import or export files through IFS—whether via document attachments or any feature that opens File Explorer—causes the IFS client to crash on the user’s workstation.
Drag‑and‑drop still works because it bypasses File Explorer entirely.
At the moment we’re waiting to see whether an upcoming Windows update resolves the issue. In the meantime we’re relying on machines that haven’t received the problematic update to handle the affected tasks.
One person in the community mentioned that deleting the 2.0 folder fixed it for them, but testing that on our side didn’t resolve the issue sadly.
If we manage to resolve the issue on our end I’ll message anyone that is still having the issues.
We’ve now figured out a temporary fix for this. I’ve included an explanation on my post here -
Import & Export Issues within IFS
Hopefully IFS can resolve this in the near future
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
