I also think this is the case. I think it's either motherboard or SSD related.
Either the chipset drivers or some other essential memory
There's not a lot of WinPE's that are getting updated at the moment so i would like to have alternatives if Strelec quits updating the english version again.
I am not all that well aware with when strelec stopped updating the English version or when he started it again. Although constant monthly updates for the whole media sounds a bit ominous to me. If it were me, I'd at best only update the programs and distribute them instead (it's one of my goals with the winpe, have a separate programs module entirely separate from the winpe, which is more like plug n Play and can be used in any other WinPE or even normal windows, strelec uses that kind of a method too, if not then similar. Unless I am wrong about it, but anyways that's what I might be working on or making it as such)
With this, all you ever need is a winpe. And as far as I can see, you don't need to update it regularly as far as monthly updates. In fact, there might not even be a need to update the winpe portion of it and one could just update the programs on a half yearly or yearly basis. Considering all that, I don't think why one would want to constantly update them (goes for both the creator and the user). I can get with the curiosity of having the updated media but is it really that worth. In the end there might even be a point where you (speaking generally) might not end up liking the resultant winpe or whatever sort of technicians gizmo they create. You can already see an example here. I don't see anyone ever give any contradictory comments to my refutes over how ridiculous this current medicat is. All there is just baseless personal opinions instead of anything constructive against what I say. Just goes to show who is correct and who isn't. Not the first time I came across such content creator or the subsequent audience. Anyways, enough about my banter. Point is, why do you need to update it that much? If you're just curious into testing things out then cool, if you only want a functioning winpe that works for you, then find it and just stick to it. There's really no need to have it's updates regardless whether the dev circulates them or not.
1) It only detects .iso files , it does not detect .img files .
2) Ventoy formats the .iso files in EX FAT by default.
3) UEFI- GPT does not start from a removable drive, formatted in NTFS, in 99% of the cases.
Not sure what you're on about there mate.
1) Try and check the product page first (ventoy). It states that it only supports iso and wim files only (wim files are supported via wimboot)
2) Ventoy does create the second partition as exfat. I think one could just reformat it to NTFS. I think this is what Jayro did, or something similar to it. I'll test it out when I have some free time later perhaps.
3) Eh, weird cause uefi gpt has never failed me. In fact, if your own hdd is formatted as gpt I think Rufus automatically picks the gpt method instead of mbr. Or maybe that's just default, can't say because both my laptop and desktop are gpt partitioned. In fact I've even got it to work on older systems as far as 2010 and above. And yes, all my bootable usb are formatted in NTFS always and no other format, except for the primary partition (like ventoy's efi partiton which is always formatted with fat32 to give the uefi boot (this is the case for multi OS boot options only))
Also, the IMG file that Medicat distro gives currently, already has ventoy. You don't need to create another ventoy partition and copy the IMG file to it, because that won't be working. What you can do is extract the IMG file and the resultant NTFS file within it using 7zio (it'll work on both, or you can use Peazip) and extract what you need and copy that to the ventoy partition (the partition formatted as exfat) after you used the ventoy2disk.exe (ventoy software) and created a bootable media using it. Once you do that, just copy the WIM/ISO files to the ventoy partition and you can boot through it. (Make sure to keep wimboot.img which would be somewhere in the NTFS file you opened via 7zip above, that's the main gizmo used to boot wim files directly)
That's all you gotta do. Can't use the IMG file directly without burning it onto a usb disk.
Edit: if you read our previous replies correctly you'd notice that spiren is talking about the medicat mini winpe or Medicat windows portable edition.