Now it gets interesting
The last run was executed on my Workstation
Windows 7, 16 GB RAM using Wimlib ImageX 1.9.0 final (because its faster and the Beta was crashing too)
This job was finishing sucessful
Now a little bit more to my environment.
The Server with the errors is a self made system with 32 GB and a few Harddisks.
Its hosting about 5 always running (DC, DHCP, DNS / VPN Server / File Server / Plex / Work...) and a few temporary running VMs.
One VM is a Fileserver and the Clients (in this case the VM Host) are accessing the Files over a SMB / DFS Share mapped as Drive Z:\
So the answer to your question "is WImlib running from a network drive is" -> YES
The Wim Files however are not accessed through the Share. They are on an external drive that is connected over a USB 3 HDD docking station on the VM Host.
This Setup is more stable than i thought and i have only one or zwo crashed over about 2 years of usage (and another 2 or 3 because of power failures
and i can't remember any big problems with accessing the Files in the Fileserver.
The sucessful job on my Workstation was accessing Wimlib over Drive Z: (my Netzwork drive).
Maybe the following happens on the Server:
-I was running wimlib from Network drive
-everything works fine and there are much disk IO / memory and CPU useage on the VM Host
-there is so much load on the host, that die FileServer VM gets no resources and the SMB session times out
-at the end of processing WIM Files, WimLib tries to do something that needs to access the wimlib exe or dll (loading a funktion ?!?)
-the Session is closed and the access is not possible and the process craches
OR
i have a hardware failure (memory?) on the Server and i really hope everything is OK.
Now i start a job with Wimlib exe and dll located on the lokal USB Disk with the WIM Files.
I'am so sorry that you troubleshoot my mistakes.
Can i donate a few dollars for your help and the great tool?