Hi Robin,
The print that previously failed now completes without problem using 5.2.30 USB install and Cura 4.11. I attach a photo of the failed print in case it gives you any input to what might have caused the problem. Below are the steps that led me to the current state:
I was running on Windows 7 Pro, Cura 4.11.0 which had worked with Cura 4.10.0. In my download folder I also found 4.9.1, 4.8.0, 4.4.1, and 3.1.0.
I had just upgraded the FW to 5.2.18 via LAN cable internet. I don't know which version it was on before this. I had no problems prior to this.
On the PC I uninstalled all Cura and removed the obvious folders. Then I installed 4.10.0 and 4.11.0 (on my Win7 Pro).
The UM3E FW was changed via LAN cable internet to whatever test version was also published at the time I reported the problem. From there I upgraded to 5.2.11 via USB. When starting the printer I was prompted to update to 5.2.30 on the screen, which I by mistake started off as a LAN cable internet update. I finally installed 5.2.30 via USB.
This is the configuration that succeeded with the yet only print I have done after the problem.
There is no indication of a hardware or filament feed issue. The printer makes no disturbing sounds that could relate to wear or damage. Where I live we hardly ever have electricity issues and nothing indicates there was one during the failed print.
If we assume that problems with UM3E are not random, and judging by other posts, I would guess that somewhere along the line UM made some change in a particular Cura or FW version that they forgot to include in the dependency check. That would explain why some users are hit and not others. My hypothesis is that the upgrade version "steps" matter and the reason I provide details about my version history. But, that's just a wild guess.
Best regards
Niclas