Are you asking if it is possible to install an image of Windows on a USB so that it will be recognized as a bootable Windows disk, and run as such, if the BIOS boot priority tells it to look at that USB before looking at the internal drive?
The answer to that would be yes!
I just don’t know where you would get an image to do that.
Did you make an offline mirror (on a USB drive) of your original Windows 11 disk??? If that true mirror is on an external USB drive, maybe you could get a “recovery” disk for Windows to correctly rebuild the boot sector on that USB drive (it was pointing at your internal drive) to point to the USB for the Windows installation.
I’m not an expert, but others who are could give you specific instructions … but that might not be on this site. You might want to ask that question on LinuxCommunity.io .
I would like some clarity because this topic is confusing with its lack of specific information.
This is what I think is being asked:
I have a Lenovo with Lubuntu as the only operating system and want to know how to update BIOS/UEFI when the manufacturer only provides Windows .exe for this.
An ISO file follows an International Organization for Standardization (ISO) 9660 standard (1998); that allows data to be written to optical disc media, on devices originally intended for musical data. It’s a rather broad standard with many purposes.
An EXE is a Microsoft DOS created executable, that is still used today by Microsoft Windows; not a global (ISO) standard, but one owned by a company. As its been used for decades; there are many versions.
They are rather different things (ISO 9660 files versus an Microsoft Executable), and whilst yes it would be possible to convert data from one file to another; it would be unlikely to be a generic tool that works with all ISOs, and likely vice-versa.
I apply my firmware updates using the provided firmware-updater tool that Lubuntu provides; but my machine is a Dell, who provide the image so different OSes can auto-install it; rather than requiring me to go to their [OEM] web site, download a file (so it can be tracked by OEM) & run specific executables (that again may send detail to the OEM). Some OEMs do like their control & tracking data, in my opinion.
Of note: On my release, the firmware-updater is provided as a snap package, meaning that if this was a minimal install; that application would NOT have been installed, as the minimal install does NOT include snapd (snap infrastructure) nor any snap packages.
Happy you sorted things out. If any one of the above responses gave you the hint that got you there, please mark that post as the solution.
If not, if you issue is truly resolve, mark you own final post as the solution, but …
To give back to the community, if you shared the reference to the specific tidbit that did fix your issue, that would save others the heartache you went thru … and would be greatly appreciated.