Rufus Error Extracting Iso

[Ceola Roefaro]

Im trying to install Ubuntu 16.04 from a USB drive. I'm using Rufus to create a bootable stick, but everytime I click start, it starts, and then gives the error ISO image extraction failure. What can I do?

for me the case was that I deleted the rufus_files folder rufus created when it's ran for the very first time. Actually, I keep a different folder for softwares, so i only copied .exe after i did my first iso extraction with rufus and deleted the folder (rufus_files).

I was trying to create the bootable USB from my office laptop and got in to this issue. I have read many solutions and it didn't work out.From one answer they said it might be due to the anti-virus effect and i tried using my personal laptop and it did work out.

In my case, the USB drive was encrypted with BitLocker. I had to remove BitLocker from the drive before it worked. In Windows, just search for BitLocker from the start menu, and see if BitLocker-To-Go is enabled for your drive. Disabling it, then trying Rufus again to write Ubuntu to the drive worked.

Edit - I tried extracting it again, and the total size like in the first picture is not 1564 MiB, but 2014 MiB. There was a new value the 3rd time I tried just now. Same error everytime, but the total size in the extraction box differs every single time.

I suppose you tried to open that file as user nomad. You have to be root to edit system files. The loader variable you set, must be added to /boot/device.hints. You can open that file as root with the ee editor as follows:

Edit 2 -

I have reached my replies limit for my first day of signing up , came up here just wanted to express some gratitude.

Thanks for all the help.

Hopefully someday I can nudge someone towards NomadBSD when they require so.

recently i want to make a bootable disk for my flashdisk. I've done this ton of times, but today while doing so my flashdisk is ejecting by it self. Rufus is stuck at extracting so i cancel the operation. ( still around 400 mb ). But now my flash disk is broken. Here's my rufus log

I'm trying to make a copy of my Windows 10 USB installation drive using ImgBurn by making a bootable ISO file which I plan on writing to a new USB drive. There are options for making images bootable but for some reason it requires that I provide the boot image, and although there are options for extracting one from my current system this fails for some reason. I get this error:

Correct me if I'm doing this wrong, but the way I do it is I open ImgBurn in Build mode and then add the drive letter of the Windows 10 USB to Source and a file location on Desktop as my Destination. Then I go to Advanced tab, Bootable Disc and click on the blue floppy disk icon with my Windows C drive selected in the list (to extract image from).

Yes, try getting an ISO with the Windows Media Creation Tool. You can then burn that ISO to a disc with ImgBurn or write it to a flash drive with something like Rufus. Unless you plan on adding files to the disc before burning/writing it. Which you're best off getting some kind of ISO injector like UltraISO or just writing the ISO to flash drive and copying over the new files to that.

I just needed to supply the "etfsboot.com" file which was already on my USB drive. So I copied all files and folders from the USB drive to a new folder on the desktop (C drive) before adding that folder to ImgBurn as source, and then specifying the boot image file from within that folder.

I wanted to make a backup copy of the Windows 10 build that's already on my USB drive (it's the May 2020 update and still supported) before I format the drive, and I also wanted to see if it's possible to make it bootable (just for learning how it's done). I have not this sort of thing in years. Most guides I found on the web explain how to use existing Windows ISO files to create bootable CD/DVD/USB.

I'm trying to install Windows (tried and failed both 10 and 11) on a Lenovo IdeaPad 3 15ITL6. Neither Windows installer recognises any storage drives. I've tried both with and without Intel VMD enabled in BIOS, to no avail.

With Intel VMD enabled, Windows suggests the "Intel RST VMD Controller 9A0B" driver but, after installing it, the installer returns an error saying "No new device drivers were found. Make sure the installation media contains the correct drivers, then click OK.".

I have checked the image that I previously flashed to the USB drive when I used gnome-disk-utility and the integrity check passed for Windows 11. This is the last image that I flashed, so I couldn't check the Windows 10 one. This also means that the Windows 11 image that I downloaded from Microsoft's servers here -us/software-download/windows11 contains all the files that's expected of it.

However, as previously recommended, we suggest you try creating the installer with another tool to discard that the root cause is how was being created. We downloaded the OS image, and created the installer with Rufus and it doesn't cause any issues.

I understand that you're keen on me trying Rufus, however, I couldn't find any versions which work on Linux. Given that I can only install Linux (currently Ubundu 23.04), Rufus is a no-go. In order to use Rufus, I'd need to install Windows, first, which is the main issue here.

Please be aware that we provide an Intel RST generic driver and Computer Manufacturers make customizations to their systems, including driver software hence we recommend you check this issue with your Computer Manufacturer or Microsoft to know why is still asking for the drivers when they have been installed already. Because, as previously mentioned, we downloaded an OS image and installed it normally in an Intel system without problems.

You can carry out this procedure with both Linux and Windows, though I don't know how to extract .exe file contents in a folder on Linux. You can search online how to do that.

Go to the Asus Website, from there, download the Intel RST drivers for your exact device name/model and windows 11. If you can't find one explicitly mentioning both your device's name/model and Windows 11, then you can try searching both the things together on google e.g. Asus IRST Drivers Windows 11 for BlablaBook/BlablaPad 6 11tWL5JW. If there still isn't anything on the Asus website satisfying both your wants together then just download your model's general drivers and if even they aren't available then as a last resort download the ones for 11th gen+.

Now run the driver file and don't 'Install' it, instead if there is an option of 'Extract Only', you can even directly extract to the rufus created bootable usb, just make sure not to overwrite anything. For linux, instead of ventoy use woeusb cli method. Now back to windows, if there was no 'Extract Only' option, then close the installer and open the windows powershell as administrator and run these commands:

Command 1: cd path to where your driver.exe is stored, you can copy it from its Properties

Command 2: ./driver file name -extractdrivers blablabla

Once you have placed the drivers extracted folder into your bootable usb. Load into your bios, enable VMD and then boot into your windows installation usb. When you click on 'Customized Install', Click on 'Load Drivers', now find the extracted folder, go to its subfolder and click on 'Open'. You will now see 1 or 2 .inf extension driver VMD files. If there is 1, just use it. If there are 2, then for Windows 11 you need the one that has 19 in it. The other one which has 18 in it is recommended for Windows 10.

Now you can install and use Windows 11 with Asus VMD. Boom.

1. lack of an archive: no Windows version is able to work, but both Intel and the manufacturer provide Windows executable files exclusively instead of archives. To install the Windows drivers, customers must first have Windows installed, which makes the point moot. @Jocelyn_Intel you should really provide archived downloads instead of .exe files, because Windows doesn't run in the first place, only other operating systems do.

3. @Jocelyn_Intel makes the assumption that the operating system's installation media (SD card, USB drive, CD ROM) is incorrectly copied, in spite of the customer stating otherwise, and insists that you, the end user, are the problem, not Intel nor the manufacturer. My screenshots should be evidence enough that the installation media works. Even if the OS installation media was somehow corrupted, we're discussing the inability to install drivers found on a separate drive, not on the OS installation media itself. It feels like Intel's customer support isn't able to go off script in spite of end users having a separate problem. After reading some other replies in this forum, it looks like this is Intel's "have you tried turning it off and on again?" standard customer support message. Intel employees just follow the script, unable to comprehend what the end user's problem actually is, standard first line of support.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

alright so basically whenever i try to download popOs i run into a problem where i dont load straight into the os, rather i load into the Rescueshell where i type commands. I tried doing resume-boot but nothing happened. Help would be appreciated. note that i can download note that i can download psxitarch and other distros like fedora with the normal rescueshell method.

noob404 popos_21_10_im_ps4linux.img.xz

when i type resume-boot i guess the command isnt recognised or something like that because it just passes me down to type another command. Literally no response to the command resume-boot whatsoever.

3a8082e126