Non of the partition managers I tried are able to resize an exfat partition. I tried Minitool, AOMEI, EaseUS, gparted.Any partition management tool like Gparted should be able to adjust the partitions.
This is the first time I've heard of this issue. I'm wondering if maybe there's a certain driver in the boot.wim file of the WinPE that your PC doesn't agree with. That's the only thing that really comes to mind. Easy_DISM can remove third-party drivers from the boot.wim, so you could try that and see if it fixes it for you. (I'm also a HUGE fan of my iODD 2541 enclosure, it makes PC repair a fucking BREEZE! Paired with a 500GB SSD, it's easily the best investment of my entire career!)Hello,
Currently, I'm trying the Windows 10 mini OS from MediCat. However it doesn't boot on my main PC. It's getting stuck on the Windows logo with the rotating dots. After a while, the IO light of the USB device doesn't blink anymore, Which means WinPE stopped loading files. I have this issue with the separate ISO from 19.10 as with the new MediCat 20.05.
I've tried to boot from either BIOS (Legacy) mode and UEFI mode. I also tried USB 3.0 and 2.0 ports. I also tried to boot from an USB stick and from a virtual USB stick mounted by a IODD 2541 HDD Enclosure.
Loading with MEMDISK also gives me the same result.
My PC has a Ryzen R7 3700X as CPU with a Gigabyte Aorus X570 Master motherboard and 32GB of DDR4 RAM on 3200mHz. Also my PC has 3 monitors plugged in but i doubt the problem is related to that.
I've also tried to boot a different WinPE image from someone else and that one boots fine. Booting the Windows 10 mini OS on my laptops works fine as from the IODD hard drive as the USB stick.
If you need more information, please let me know.
I don't have any clue how to turn a bootable USB into a bootable iso, only the other way around.Hi,
This is amazing. I've been using the 19.10 before on multiple PCs.
Unfortunately I cannot try 20.05, because it is distributed as a binary.
I use it to boot on any PC, including my macs. The previous versions were iso files, which means I could extract the files and make the necessary partitions and EFI to work.
It is not feasible to extract and change the image on its current format. Do you think you could provide this in iso?
Better yet, if you include rEFInd, which supports all the OS
Thanks!
I don't have any clue how to turn a bootable USB into a bootable iso, only the other way around.
It doesn't have to be bootable. In my case, I just need to extract the contents. My knowledge on boot logic is basic, but rEFInd supports creating a bootable USB that you can then modify. Works everywhere.
I'll see if I can reupload it in split chunks of 4GB later tonight. But I'm stuck at work for another 6 hours. My PC is on at home seeding. Hopefully between me and my friends seedbox it will pick up speed.
--------------------- MERGED ---------------------------
Any partition management tool like Gparted should be able to adjust the partitions.
I have removed all the third-party drivers using Easy_DISM, committed all the changes into boot.wim and repackaged the WINPE into an ISO. But sadly it's still stuck at the rotating dots.This is the first time I've heard of this issue. I'm wondering if maybe there's a certain driver in the boot.wim file of the WinPE that your PC doesn't agree with. That's the only thing that really comes to mind. Easy_DISM can remove third-party drivers from the boot.wim, so you could try that and see if it fixes it for you. (I'm also a HUGE fan of my iODD 2541 enclosure, it makes PC repair a fucking BREEZE! Paired with a 500GB SSD, it's easily the best investment of my entire career!)
If you're having that issue, go into Windows Settings App (Windows+I), select "Update & Security", select "Windows Security" on the left, and then select "Virus & threat protection". You should turn off Real-time protection in the window that opens.Thank you very much for MediCat USB 20.05.
Any idea how to disable "Windows Defender" during creation of the MediCat USB stick?
Even so the pendrive become unbootable in legacy mode. Just tried it and after the move + resize process (which really finishes within 10 minutes) the drive refuses to boot up.@ all who feel the need to resize an exFat partition: just let Eassos DiskGenius do its job! Even though it might show a high estimated time remaining number at some point, my experience is that that goes down significantly suddenly. I never had to wait over nite for an exFat resize to finish. And even if, so what..
Amazing advice, I'll do that. I might make a 64GB version too, since folks aren't too keen on my 32GB version. I was just trying to save space, but hopefully 7Zip will compress that empty space close to zero for a similar file size.Also a small suggestion, tweak:
Put a .ventoyignore file in every folder that not containing iso files (PortableApps, Programs, and your custom folders).
That will make the init process of ventoy much faster since it does not need to scan these folders\subfolders.
Boot for me went from 13 seconds to 2 with this.
You have to put only 1 file in every root folders so they don't need to be present in every subfolders under them... but I guess you figured that one by yourself.Amazing advice, I'll do that. I might make a 64GB version too, since folks aren't too keen on my 32GB version. I was just trying to save space, but hopefully 7Zip will compress that empty space close to zero for a similar file size.
If you update Ventoy, it will undo all my changes, but will function exactly the same as mine. My changes are purely cosmetic so far, and I'm just trying to make things easier to use.Hello, is it safe to update ventoy in medicat? I downloaded Ventoy and doen't recognize the version installed on the flash drive.
Ventoy seems to have been an interesting discovery, has more advantages than other similar software and is just at the beginning of development.
1. launch BootIce. Choose your Medicat flash drive and backup both, PBR and MBR. Also note what kind they are, if BootIce displays that infoEven so the pendrive become unbootable in legacy mode. Just tried it and after the move + resize process (which really finishes within 10 minutes) the drive refuses to boot up.