Help

 

Here you can get help, access FAQ and tutorials, get support, report a bug of make feature request about WinSetupFromUSB by leaving a comment.

FAQ
Tutorials
Useful Links

973 thoughts on “Help

  1. Hi,
    Pendrive was working fine with multiboot, and booting with legancy and uefi, but suddenly no idea what happened, lagency boot not working, only uefi boot working.

  2. Такая вот проблема помогите пожалуйста…
    USB накопитель использую 32ГБ В WinSetupFromUSB Ставлю пункт Auto format it with FBinst, в формате FAT32 и добавляю образы по очереди, все как обычно. Но начиная с версии Win10 2004 19041.264 и все следующие новые сборки вплоть до 21H2 X64 не хотят запускаться на устройствах UEFI и MBR выдают ошибку Could not mount the virtual disk. Cannot continue, press OK to reboot.
    А образы X86 запускаются без проблем на любых устройствах с UEFI и MBR

  3. Hiren’s BootCD not working properly on my USB. Windows starts up good but there was missing utilities. Everything was good with Rufus but i experience issues with WinSetup. Whats the problem?

  4. so i need to boot a manjaro image in my pc, USB boots first the windows boot manager, when i press ESC it brings me to the computer’s boot device selector,how do i boot first to Grub4Dos without removing existing files, laptop is a Legion 5 2020

  5. Maintenance boot iso’s like Arconis and Minitool Partition Wizard don’t show up it UEFI Boot devices

  6. Hello,

    I created a multi boot disk and also added a Linux OS bootable ISO. When I boot I only see the Windows Bootable and not the Linux OS. I went into the BIOS and under security I checked off “Boot from Microsoft and 3rd Party.” Is there a different method to boot into Linux? Thank you for your help.

      • Im on Surface laptop 4 and there is no option to boot in CMS mode in the BIOS not are there any advanced options unless there is a certain way I have to enable? Appreciate your help

        • I don’t have such laptop and can’t advise what options to use.
          If there is no BIOS mode then you would need to use an alternative software that supports UEFI boot and multiple Linux sources, such as easy2boot, unetbootin, YUMI, Ventoy etc.

  7. It says could not mount the virtual disk Cannot cotinue press to reboot.
    In iso Windows 11 22h2, with isos Windows 11 21h2 don’t have problem.

  8. Please fix the following bug. When adding Windows installation ISO, you add “winpeshl.ini” file into boot.wim. On some systems it could yield an error “Could not update boot.wim in …” because of filename case mismatch. You create file with lowercase “w”, but then issue a command
    “` C:\Windows\system32\cmd.exe /c wimlib-imagex.exe update “C:\WINSETUP\TempWST\sources\boot.wim” 2 –command=”add ‘C:\WINSETUP\TempWST\Windows\System32\Winpeshl.ini’ ‘\Windows\System32\Winpeshl.ini'” “` which results in error “…(status=c0000034): Object Name not found ERROR: Exiting with error code 47: Failed to open a file.” which can be seen in WinSetupFromUSB.log file. That’s because in your command you have file name starting with capital “W”. I had to manually rename file “winpeshl.ini” to “Winpeshl.ini” (located in TempWST\Windows\System32\) in order to fix this error. Please make the file name case consistent between actual file name and file path in cmd command. Thanks.

    • Good catch, thanks. Will review the code if that’s indeed the case and publish updated version.

      Looking at wimlib-imagex documentation this doesn’t seem to be an issue. This code hasn’t been changed for years and this is the first report for this. Do you have anything specific set on your system in regards to case sensitivity, either on Windows or wimlib-imagex aide?

      https://www.systutorials.com/docs/linux/man/1-wimlib-imagex/

      • I recall I was reading something about NTFS does support case sensitivity and Windows API does not. So I’ve might been playing with casesensitivity settings for NTFS in Windows (It’s Windows 7 x64). But I can’t remember what exactly I was doing, probably some registry changes. I’m not sure if those changes are the culprit here. And I don’t even remember if I reverted those changes or not. Anyways, believe me, the error in the log file on my system is very real 🙂 I’ve even tried to run your “C:\Windows\system32\cmd.exe /c wimlib-imagex.exe update …” command manually and got the same error in console.

Leave a Reply to Chris Cancel reply