- (EN) How to add multiple Windows XP / 2000 / 2003 sources and Kaspersky Rescue CD
- (EN) How to add multiple Windows NT6/10 (Vista, 7, 8, 10, Server 2008/2012) sources and Ubuntu Desktop with persistence
- (EN) How to figure out what type the source is and which option to use
- (EN) How to start Debian and its derivatives from USB hard disk
- (RU) WinSetupFromUSB инструкция по использованию
- (RU) Мультизагрузочная флешка с помощью WinSetupFromUSB
- (ES) Cómo instalar Windows XP, 7, 8/8.1 desde el mismo PenDrive
- (ES) WinSetupFromUSB Guide – Maravento
- (HU) Multiboot USB eszköz készítése
- (PL) Instalacja Windows XP z pendrive
- (VN) Hướng Tạo USB Chứa Nhiều Bộ Cài Đặt Windows
i have add successfully hiren-pe and windows10. also i try to add All in One – System Rescue Toolkit but i couldn’t. the massage error show
this doesn’t seem to be valid source either or all of sources boot.wim a>>>>>>>>>>>>
Is it not Ubuntu based, why adding it as Windows source? Try Linux/Orher ISO option if it’s indeed Ubuntu based. Look at Tutorial 3 above.
Olá boa noite,criei um multiboot com iso e ferramentas,como o hiréns boot,deu tela azul com o hiréns boot e com o wndows xp,alguma solução para o ocorrido?
I have a single Win7 Pro 64-bit iso whic i tried to add. But i get the error “doesn’t seem to be valid source either or all of sources boot.wim…”
I confirm that it is not a 32- and 64-bit iso. How to resolve this?
Can 7-zip open it and list its contents? The ISO might not be in UDF format as required.
Does the ISO have the default directories and files present? Sources, boot.wim, install.wim etc.
You should look at or post the log file, it’s quite self-explanatory and easy to spot the issue.
how to make win 7 64 & win 10 64
Add them one after another. Please read the FAQ page
“This doesn’t seem to be (a) valid source!
Either or all of \sources\boot.wim, \bootmgr
\boot\, \boot\BCD are missing, or source is not supported.
RETRY to select another source or CANCEL to return to the main menu(.)”
this happens when i try to burn windows 10 on the flash drive
Are you trying to add multi 32/64 bit ISO? It’s not supported. Use single 32 or 64 bit sources. If you need both- add 2 separate ISOs.
I have been trying for several days now to get an Ubuntu 18.0.4.1 live with persistence to work. I’ve followed the instructions to the letter but it appears the partition/file is not being mounted… even though I add the persistence string where needed.
Did you add “persistent” to the kernel boot options as in the tutorial, point 11?
How did you name the persistent file? Did you try changing to lower/upper case?
Yes, I added “persistent” at the indicated location. Is there a way to set that option on a permanent basis? I used the default name suggested by winsetupfromusb in the advanced options. Which upper/lower case should I be changing? I’ll be the first to admit Linux isn’t my strongest skill set… so I’m at a bit of a disadvantage there. I have however be in IT for 20 years and an not afraid to get my hands dirty trying to figure something out.
Just change CASPER-RW to casper-rw in advanced options and redo the USB stick. That works for me, typing this from Live Ubuntu 18.0.4.1 Desktop ISO, which was rebooted and preserved the wi-fi password and the test folder created in /home. Keep in mind to add persistent to the boot options.
That last bit you can change permanently by editing the Ubuntu ISO file/isolinux/txt.cfg.
Seems partition label expectations vary in each version, the default was put in capital letters because that’s what worked in earlier Ubuntu versions and Linux Mint.
That seems to have done the trick. Thank you for the assistance. For making persistent permanent I am understanding that I need to edit that file on the ISO prior to creating the thumb drive?
Yes, in the ISO, it’s booted as it is. Can edit it on the USB disk as well, but will need to defragment the ISO file after editing in case it ends up fragmented.
There is Wincontig included with the program.
Dear Team,
I create a bootable pendrive using winsetupfromusb software, this is boot the pendrive using grab system. When I am trying to install windows from that bootable pendrive. When select boot from USB, system saying. System taking USB as floppy disk, use ploop boot manager to boot from USB. Please guide, how to boot pendrive using plop boot manager without disturbing current grab os boot. Only some system have seeing this problem. Do needful.
I have a multi-OS system created with XP/Server 2003/Vista/7/8.1/10 Kaspersky Rescue Disc and Hiren’s PE version. How can I duplicate this without having to rebuild each time. I’ve tried creating an ISO from the USB and burning that to another USB but it doesn’t seem to work.
RmPrepUSB has drive to file and file to drive options. Can also use any other software which does sector by sector copy, ImageUSB for example. The target drive has to be 100% identical for this to work.
Creating ISO from USB disk won’t work ever, you are mixing different things.
Sorry, I missed sector by sector in there. That’s what I figured must be done but some how the sector by sector in AOMEI Backupper corrupted the original I made. I use Ghost usually for sector by sector but the version I have doesn’t recognize USB
Try Clonezilla for sector by sector. It supports USB drives and it has options to skip over bad-bad-bad sectors that usually cause a drive cloning operation to grind to a halt.
Thank you for the reply. I’d also tried sector by sector cloning with AOMEI Backerupper but that messed up my original. I’ll go to the RmPrepUSB. Should this work with true sector by sector as in with a standalone hardware duplicator?
How add https://www.memtest86.com/download.htm uefi image?
Not possible. Use BIOS image and boot in BIOS mode, or use Windows 7/10 memory tests under UEFI.
Forget Windows memory tests or any other hardware diagnostic software provided by Microsoft. Best to use memtest-86+, which does comprehensive memory tests. Put it on a bootable CD, a bootable floppy (people still use these?) or its own small bootable flash stick.
That’s interesting statement about the MS memory diagnostic tool. Have you got any links or something with evidence why and how it’s bad?
My only evidence is my experience across many years of repairing, building and upgrading computers. The MS memory diagnostic is simply not comprehensive enough. If I test some memory with MEMTEST-86+ and it passes the test, the memory works perfectly in one of the systems here or in systems elsewhere, with the memory and computers I sell on-line. If there is MEMTEST-86+ test failure, the memory goes into my recycling box. MEMTEST-86+ is a very thorough and transparent test of computer memory.
MS disk diagnostics, like CHKDSK and similar, do not examine the underlying disk hardware to determine if there are bad sectors. I have various programs that display the hard drive SMART data, and if there is even one defective sector, I replace the disk or recover the useful data from the disk. If a hard drive has no defective sectors, then maybe CHKDSK will do the job right. Drives with one or more defective sectors go into another recycling box, to take to a recycling center.
In general, if one does not have the assurance that computer hardware is 100% operational, then any attempts to change the software can only make the situation worse, possibly by corrupting good data.
Finally, Microsoft was, is and always will be a software company with limited expertise in computer hardware, chipsets, hardware testing.
I had only the memory diagnostic tool in mind, just never seen complains before that it’s not reliable and got curious.
I have found the Microsoft (MS) 64-bit memory test to be pretty good and pretty quick. If I suspect a ‘good’ system has gone bad, I use the MS test first because it is quicker than MemTest86 at finding simple memory faults. If that runs for a few cycles and I still suspect a memory fault may be present, I quit it and run MemTest86 for a thorough test which takes many hours.
P.S. I don’t use MemTest86+ (which is not the same as PassMark MemTest86) – it failed to find a memory error above 4GB once even though it clearly indicated it was testing all 8GB. The Microsoft memory test found a problem in 2 minutes.