Official MediCat USB - A Multiboot Linux USB for PC Repair

  • Thread starter Thread starter Jayro
  • Start date Start date
  • Views Views 8,972,405
  • Replies Replies 4,084
  • Likes Likes 284
Hello,

I am testing your dev for first time, on three laptops. Very good stuff, really. I just have a problem with Mini Windows 10 on one of the laptops (Lenovo X1 Carbon 2017). It throws immediately an error "Windows failed to start" (0xc0000017, not enough memory). Of course, there is plenty of RAM in that computer (32Gb). No emergency here, since it is just a test drive, but I would like to understand the problem. Do you have any way to resolve that problem, please ?

Thank you !

hhllss
 
Hello,

I am testing your dev for first time, on three laptops. Very good stuff, really. I just have a problem with Mini Windows 10 on one of the laptops (Lenovo X1 Carbon 2017). It throws immediately an error "Windows failed to start" (0xc0000017, not enough memory). Of course, there is plenty of RAM in that computer (32Gb). No emergency here, since it is just a test drive, but I would like to understand the problem. Do you have any way to resolve that problem, please ?
Thank you !

hhllss
I've noticed some computers are really picky and throw up that error, and I don't know why. I think booting Mini Windows 10 from it's own ISO in EFI fixes that, but I'm not 100% sure.
 
Last edited by Jayro,
What is the difference between the Medicat et Mini Windows 10 ? The one include tools on boot menu, the second is just W10 live ?
 
I tested the full ISO in VirtualBox today, and instantly got an error about winload.exe being missing when attempting to try out the Live Windows 10 option. I compared the hash of the ISO I downloaded from Google Drive with the one in the hashes.txt you provided, and the hashes matched(I used Fsum Frontend v1.5.5.1). Can you tell me why this is happening and how I can solve it?

Either way, this is still an incredibly useful tool that should be much more popular.

EDIT: I tried booting using the Mini Windows 10 ISO, and it worked without any issues(except for an error that came up about Rainmeter).
 
Last edited by TheMCNerd2017,
I tested the full ISO in VirtualBox today, and instantly got an error about winload.exe being missing when attempting to try out the Live Windows 10 option. I compared the hash of the ISO I downloaded from Google Drive with the one in the hashes.txt you provided, and the hashes matched(I used Fsum Frontend v1.5.5.1). Can you tell me why this is happening and how I can solve it?

Either way, this is still an incredibly useful tool that should be much more popular.

EDIT: I tried booting using the Mini Windows 10 ISO, and it worked without any issues(except for an error that came up about Rainmeter).
What's the rain meter error, if you don't mind me asking? It works fine for me on all my hardware.
 
What's the rain meter error, if you don't mind me asking? It works fine for me on all my hardware.
Hang on, I'm installing a VirtualBox update. I'll reply back with the error.
EDIT: Here is a picture of the error.
o3lg35j.png
 
Last edited by TheMCNerd2017, , Reason: Added error message
Ah, that looks like an easy fix. I'll try to implement that fix next release.

Good find, and thank you @TheMCNerd2017 . If it makes the cut, you'll be credited in the changelog.
Your welcome.

Not sure if the other issue(winload.exe not found) I encountered with the main MediCat image is also another glitch, but it could be worth looking into. Not sure if VirtualBox could cause it through.
 
Your welcome.

Not sure if the other issue(winload.exe not found) I encountered with the main MediCat image is also another glitch, but it could be worth looking into. Not sure if VirtualBox could cause it through.
I honestly switched from using VirtualBox to VMware because weird errors like that cropped up, and I couldn't reproduce them on real hardware OR in VMware... VirtualBox was causing them for me.
 
I honestly switched from using VirtualBox to VMware because weird errors like that cropped up, and I couldn't reproduce them on real hardware OR in VMware... VirtualBox was causing them for me.
Yeah I would switch if I didn't need to pay a lot of money things that Virtualbox already includes for free.
But you do not get the missing winload.exe error on your end when booting Mini Windows 10 from the MediCat iso image?
 
Hi, I have a problem:
When I start on my USB stick, I arrive directly on the mini Windows, when I should arrive on the other selection screens before
 
Hi, I have the same problem: it directly boots on Mini Windows 10 instead of the screen before. I just checked, my bios boot in legacy mode. Can you help me?
 
I have a problem, to boot from Legacy in windows 10 I get error 0xc0000225, when trying to boot from UEFI I can only start with the installers I already had (I use WINFROMSETUPUSB), then I suppose that would be solved by booting WINPE from UEFI, but how do I extract the ISO to mount it with WINSETUPFROMUSB?
 
hi, i just created a full medicat usb stick. booted up to mini windows 10 just fine, ran a few apps and when I go shutdown or restart, nothing happens. ive tried right clicking on the windows icon and also going directly to the start menu option of shut down. i select both options and nothing happens after.
 
Hello! great tool, I installed version 18.04 and when starting mini windows 10 I get an error loading winload.exe, with version 17.10.02 I do not have that error,
I've tried it on other PCs and in all of them get the same, how can I fix it? many thanks!!
 

Attachments

  • IMG_20181003_184940[1].jpg
    IMG_20181003_184940[1].jpg
    1.5 MB · Views: 224

Site & Scene News

Popular threads in this forum