Jump to content











Photo
- - - - -

Rufus 3.0 has been released

rufus

  • Please log in to reply
69 replies to this topic

#51 Akeo

Akeo

    Frequent Member

  • Developer
  • 352 posts
  •  
    Ireland

Posted 11 June 2020 - 04:06 PM

Rufus 3.11 BETA is now available at its usual location.

 

This pre-release brings the following changes:

  • Add Rock Ridge deep directory support
  • Add an option to write small ISOs to an ESP (GPT only)
  • Add a cheat mode (Ctrl-SELECT) to extract content from an additional zip archive on top of the ISO
  • Add a cheat mode (Alt-G) to disable Virtual Hard Disk listing
  • Add a cheat mode (Alt-P) to toggle a GPT ESP to Basic Data (Windows 10 only)
  • Fix improper x86 32-bit NTFS driver being used for UEFI:NTFS
  • Improve UEFI:NTFS compatibility with older UEFI firmwares
  • Remove Ubuntu's splash screen for persistent UEFI drives
  • Enable ASLR for the Rufus executable

 

As usual, if you think you encountered an issue with the BETA, please report it in the official issue tracker.


  • Blackcrack likes this

#52 Akeo

Akeo

    Frequent Member

  • Developer
  • 352 posts
  •  
    Ireland

Posted 18 June 2020 - 11:26 AM

Rufus 3.11 has been released.

 

Here is the final ChangeLog:

  • Add Rock Ridge deep directory support
  • Add an option to write small ISOs to an ESP (GPT only)
  • Add a cheat mode (Ctrl-SELECT) to extract content from an additional zip archive on top of the ISO
  • Add a cheat mode (Alt-G) to disable Virtual Hard Disk listing
  • Add a cheat mode (Alt-P) to toggle a GPT ESP to Basic Data (Windows 10 only)
  • Fix improper x86 32-bit NTFS driver being used for UEFI:NTFS
  • Improve UEFI:NTFS compatibility with older UEFI firmwares
  • Improve startup time by running the ISO download feature check in the background
  • Remove Ubuntu's splash screen for persistent UEFI drives
  • Enable ASLR for the Rufus executable

  • Blackcrack likes this

#53 Akeo

Akeo

    Frequent Member

  • Developer
  • 352 posts
  •  
    Ireland

Posted 14 October 2020 - 03:45 PM

Rufus 3.12 is out now.

 

The Changelog for this version is as follows:

  • Add optional SHA-512 digest algorithm (Alt-H)
  • Add a cheat mode (Alt +/-) to increase/decrease application priority
  • Enable direct provision of install.wim/install.esd for Windows To Go
  • Move Windows To Go ESP to the beginning of the drive, on systems that allow it
  • Enforce a minimum volume size of 256 MB for ext2/ext3 partitions
  • Speed up the scanning of ISOs with lots of Rock Ridge deep directory entries
  • Fix detection of GRUB version and update embedded GRUB for Ubuntu 20.10 support
  • Fix user interface labels for accessibility
  • Work around a Windows bug where the wrong drive letter may be returned

Enjoy!


  • Tokener and Blackcrack like this

#54 Akeo

Akeo

    Frequent Member

  • Developer
  • 352 posts
  •  
    Ireland

Posted 30 April 2021 - 03:50 PM

Rufus 3.14 has been released.

 

Changes for this release are:

  • Improve DD write speed (uncompressed images only)
  • Improve checksum computation speed
  • Improve network connectivity detection
  • Only prompt for additional GRUB/Syslinux downloads when not writing in DD mode
  • Fix potential "loss" of disk after writing Ubuntu 20.10 in DD mode
  • Fix GRUB compatibility issue with Ubuntu 21.04
  • Fix Rufus MBR not being selected by default for Windows ISOs
  • Fix drag and drop being enabled during drive creation
  • Add more "exceptions" for forced DD image writing

  • Blackcrack likes this

#55 Akeo

Akeo

    Frequent Member

  • Developer
  • 352 posts
  •  
    Ireland

Posted 03 August 2021 - 11:15 AM

Rufus 3.15 has been released.

 

The changes for this release are:

  • Update GRUB to version 2.06
  • Add support for .vtsi files (Ventoy Sparse Image, courtesy of longpanda/ventoy)
  • Add workaround for openSUSE Live ISOs
  • Move default app directory to %LocalAppData%\Rufus\ and always save a log there on exit
  • Fix AppStore version of Rufus not being able to store downloaded files
  • Fix failure to open Syslinux/GRUB files when Rufus is located at the root of a drive
  • Prevent the creation of System Volume Information on ESPs written in DD mode
  • Prevent drive letter assignation to the UEFI:NTFS partition
  • Prevent persistent partition creation errors due to size
  • Enhance safety checks before running the Fido ISO download script
  • Other internal fixes and improvements

Enjoy!


  • Blackcrack likes this

#56 Akeo

Akeo

    Frequent Member

  • Developer
  • 352 posts
  •  
    Ireland

Posted 09 October 2021 - 04:28 PM

Rufus 3.16 BETA #2 has just been made available.
 
This pre-release brings the following updates:

  • Fix ISO mode support for Red Hat 8.2+ and derivatives
  • Fix BIOS boot support for Arch derivatives
  • Fix removal of some boot entries for Ubuntu derivatives
  • Fix log not being saved on exit
  • Add Windows 11 "Extended" installation support (Disables TPM/Secure Boot/RAM requirements)
  • Add UEFI Shell ISO downloads
  • Add support for Intel NUC card readers
  • Improve Windows 11 support
  • Improve Windows version reporting
  • Speed up clearing of MBR/GPT

I guess the change that might be of interest for most people is that Rufus 3.16 provides the ability to install Windows 11 on computers that don't meet the TPM 2.0 + Secure Boot + 8 GB RAM or more official requirements (can't do much about unsupported CPUs though).
 
You will see this new feature if you select a Windows 11 ISO (which Rufus can also conveniently download through its split SELECT/DOWNLOAD button), as the Image option dropdown will list the following options:

  • Standard Windows 11 Installation (TPM 2.0, Secure Boot, 8GB+ RAM)
  • Extended Windows 11 Installation (no TPM/no Secure Boot/8GB- RAM)

If you choose the second option, Rufus will edit the relevant registry hive from sources\boot.wim and create the relevant BypassTPMCheck, BypassSecureBootCheck and BypassRAMCheck keys in HKEY_LOCAL_MACHINE\SYSTEM\Setup\LabConfig, that allow to bypass the installation restrictions.


  • Blackcrack likes this

#57 Blackcrack

Blackcrack

    Frequent Member

  • Advanced user
  • 446 posts
  •  
    Germany

Posted 10 October 2021 - 04:42 AM

thank you :))))) imho, you both, you Pete and Longpanda be in feel the Big two at the USB-Tool Technician market :)

and imho, you both Proggys be the best ! I be at moment at Berufs Foerderungs Werk Schoemberg at Renningen and make my IT-Systemelectronik certificate (yes, in my age..*g*),

there give a small PC-Hospital here in this Facility (at this point, Leia and the Team of her, there greetings to his.. ehh her, great Character and a big Charm ! a Real Elite Character )

They are happy to have such great programs as tools and send big fat thanks to you are for these great tools !
 

best regards

Blacky

 

blackysgate.de



#58 erwan.l

erwan.l

    Platinum Member

  • Developer
  • 2977 posts
  • Location:Nantes - France
  •  
    France

Posted 10 October 2021 - 12:02 PM

 

I guess the change that might be of interest for most people is that Rufus 3.16 provides the ability to install Windows 11 on computers that don't meet the TPM 2.0 + Secure Boot + 8 GB RAM or more official requirements (can't do much about unsupported CPUs though). 

 

Hi Akeo,

 

Great release as always.

About the cpu limit, have you considered/tested the key AllowUpgradesWithUnsupportedTPMOrCPU in HKEY_LOCAL_MACHINE\SYSTEM\Setup\MoSetup ?

 

While upgrading, this key supposedly removes the cpu limitation. Cant tell thus while installing from scratch.

 

Regards,

Erwan

 

allowupgradeswithunsupportedtpmorcpu-win



#59 Blackcrack

Blackcrack

    Frequent Member

  • Advanced user
  • 446 posts
  •  
    Germany

Posted 10 October 2021 - 04:52 PM

Windows Registry Editor Version 5.00

#shift + F10 at Versions selecting to open cmd, notepad, open/import

[HKEY_LOCAL_MACHINE\SYSTEM\Setup\LabConfig]
"BypassTPMCheck"=dword:00000001
"BypassSecureBootCheck"=dword:00000001
[HKEY_LOCAL_MACHINE\SYSTEM\Setup\MoSetup]
"AllowUpgradesWithUnsupportedTPMOrCPU"=dword:00000001

Microsoft make only a show for take anyone the Win11 on any computers..

i use still Win7

 

best



#60 erwan.l

erwan.l

    Platinum Member

  • Developer
  • 2977 posts
  • Location:Nantes - France
  •  
    France

Posted 10 October 2021 - 05:08 PM

Microsoft make only a show for take anyone the Win11 on any computers..

i use still Win7

 

best

 

 

I know some guys who still use XP SP2 :)


  • Blackcrack likes this

#61 Akeo

Akeo

    Frequent Member

  • Developer
  • 352 posts
  •  
    Ireland

Posted 13 October 2021 - 12:22 PM

have you considered/tested the key AllowUpgradesWithUnsupportedTPMOrCPU


We have, but this only applies to in-situ upgrades (i.e. from an already installed Windows 11) and it's therefore not useful for us since all we care about are restrictions that prevent the installation of Windows on a clean system.
 
In other words, we only care about patching the pre-installation OS' boot.wim and not the target's install.wim because once folks get their Windows 11 running, they can apply whatever registry keys they need.
 
Sure, we could also mount install.wim to apply this key, so that folks don't have to run regedit themselves, but this would be very costly to do from a USB drive, whereas Windows 11 users can just fetch a .reg somewhere once their system is up, that'll do that for them. Plus, as always, we are very reluctant to alter anything we don't need to alter from the source image.
 
 
In other news, Rufus 3.16 has now been released.
 
The final Changelog is as follows:
  • Fix ISO mode support for Red Hat 8.2+ and derivatives
  • Fix BIOS boot support for Arch derivatives
  • Fix removal of some boot entries for Ubuntu derivatives
  • Fix log not being saved on exit
  • Add Windows 11 "Extended" installation support (Disables TPM/Secure Boot/RAM requirements)
  • Add UEFI Shell ISO downloads (NB: this also retroactively applies to previous Rufus versions through FIDO)
  • Add support for Intel NUC card readers
  • Improve Windows 11 support
  • Improve Windows version reporting
  • Speed up clearing of MBR/GPT


#62 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 15923 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 13 October 2021 - 12:37 PM

@Akeo

Only to understand, when should the .reg settings be applied?

 

I mean, if I get this right, the boot.wim is "fixed on the fly" by Rufus (if the option is chosen), then the Windows Setup starts, then what?

Should one use Shift+F10 (or *whatever*) while on the setup, like Blackcrack posted?

But isn't that still the boot.wim?

Or is it already the install.wim?

:unsure:

 

 

:duff:

Wonko



#63 Akeo

Akeo

    Frequent Member

  • Developer
  • 352 posts
  •  
    Ireland

Posted 13 October 2021 - 04:45 PM

I mean, if I get this right, the boot.wim is "fixed on the fly" by Rufus (if the option is chosen), then the Windows Setup starts, then what?


Then instead of getting a screen telling you that your PC doesn't meet the requirements before the license agreement, and forcing you to abort the installation, if, say, you don't have TPM, the installation can now proceed as expected.

 

This basically accomplishes the same as hitting Shift F10 when you get to the installer and then adding the keys through regedit in the preinstallation environment.

 

The point is, if these registry keys aren't added to the boot.wim image, then not having a TPM or booting on UEFI without Secure Boot enabled will prevent you from installing Windows altogether.

 

After that, setup applies install.wim and reboots into Windows 11, where you'll be able to fiddle with the registry to add other keys... but you won't be able to boot into Windows 11 on a machine that doesn't meet the requirements unless you make sure that the registry from the boot.wim image has been patched with the LabConfig keys, either manually by the user through commandline (inconvenient for people who are unfamiliar with it and have to reference the keys to add) or automatically by a utility like Rufus.



#64 wimb

wimb

    Platinum Member

  • Developer
  • 3473 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 13 October 2021 - 05:06 PM

Another way to Install Windows 11 on an invalid PC is to Capture a fresh Windows 11 WIM file for Local Account of a valid PC and then Apply this WIM file to the invalid PC.

 

This works wthout problems since Windows 11 is Universal and will auto adjust the drivers for the hardware of the new pc (being old and considered as invalid ....)

 

Also Windows 11 on invalid PC is getting Updates and is auto Activated on the invalid PC if it has a valid Windows 10 licence 



#65 devdevadev

devdevadev

    Silver Member

  • Advanced user
  • 520 posts
  •  
    India

Posted 13 October 2021 - 05:30 PM

Another way to Install Windows 11 on an invalid PC is to Capture a fresh Windows 11 WIM file for Local Account of a valid PC and then Apply this WIM file to the invalid PC.
 
This works wthout problems since Windows 11 is Universal and will auto adjust the drivers for the hardware of the new pc (being old and considered as invalid ....)


Will this approach allow Windows 11 Updates in invalid PC ?

#66 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 15923 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 13 October 2021 - 05:31 PM

@Akeo

Sorry, I still don't get it.

 

The added key that blackcrack proposed:

 

[HKEY_LOCAL_MACHINE\SYSTEM\Setup\MoSetup]
"AllowUpgradesWithUnsupportedTPMOrCPU"=dword:00000001

 

seems to me like going while setup/boot.wim is booted into the "volatile" PE/setup Registry[1].

 

Now, either it does something or it does nothing, from what you write it does nothing, correct?

 

:duff:

Wonko

 

 

[1] while Rufus pre-patches the registry "base" inside the boot.wim that will form at boot time the PE/setup Registry, to the same effect, i.e. the PE/setup registry containing the relevant keys that are ONLY the \Setup\LabConfig ones



#67 devdevadev

devdevadev

    Silver Member

  • Advanced user
  • 520 posts
  •  
    India

Posted 13 October 2021 - 05:36 PM

@Akeo

Does Rufus mount boot.wim using DISM and inject .ini and .cmd within it which auto apply registry hacks during booting ?

What exact registry are applied by Rufus within pre installation phase ?
Does Rufus inject any .cmd within boot.wim ?

#68 Akeo

Akeo

    Frequent Member

  • Developer
  • 352 posts
  •  
    Ireland

Posted 13 October 2021 - 06:44 PM

AllowUpgradesWithUnsupportedTPMOrCPU is for upgrades, not clean install. Rufus doesn't care about upgrades. It only cares about clean install, where this key is useless, since we are not performing any kind of "upgrade" from Windows to Windows.

Rufus mounts boot.wim to patch the registry. It does not inject any .ini or .cmd. We just mount boot.wim then the SYSTEM registry hive from that mountpoint and patch the registry.

There's no need to injecting stuff when you can access and patch the registry directly once the .wim is mounted.

If you want the exact details, you can always look at the Rufus source: https://github.com/p...ec5b5a3cede0e2d


  • devdevadev likes this

#69 wimb

wimb

    Platinum Member

  • Developer
  • 3473 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 13 October 2021 - 07:36 PM

Will this approach allow Windows 11 Updates in invalid PC ?

 

Yes  :)


  • devdevadev likes this

#70 Akeo

Akeo

    Frequent Member

  • Developer
  • 352 posts
  •  
    Ireland

Posted 23 October 2021 - 04:59 PM

Rufus 3.17 has now been released.

 

This is mostly a bugfix release that brings the following improvement:

  • Fix MBR not being properly cleared
  • Fix commandline hogger not being deleted on exit
  • Improve ReFS handling for platforms that support it
  • Update UEFI:NTFS to latest and remove Secure Boot notice since this version is Secure Boot signed
  • Update Grub4DOS to latest

 

The first item, which is really what prompted this anticipated release, is needed to fix a regression introduced in 3.16 that could create issues when trying to repartition a drive.

 

However, what might be of interest to most people is that this new release brings full Secure Boot compatibility to our UEFI:NTFS solution for booting ISOs that contain files that are larger than 4 GB, which is the case of any recent retail (i.e. non MCT) Windows 10 or Windows 11 images.

 

This means that you should now be able to install Windows 10 or Windows 11 using such an image, without having to disable Secure Boot, since our UEFI:NTFS bootloader as well as its accompanying read-only NTFS driver, have now been signed by Microsoft.

 

<rant_mode>

I'm just going to point out that this is actually the culmination of about 1 year of hard work, the vast majority of which occurred behind the scenes, that started with our spending two months rewriting a GPLv2 compatible version of a UEFI NTFS driver based on ntfs-3g (thanks to Microsoft having arbitrarily decided that they would not sign anything GPLv3 -- I sure like having to waste time re-inventing the wheel, on account of complete bullshit reasons) and that was peppered with an incredible amount of setbacks and excruciatingly unwarranted delays. So, yeah, when developers tell you they are busy working on other stuff ("You wouldn't know that stuff. It's going to a different signing school in Canada"), it's usually because they are...

 

Oh and my apologies for the 4 users still using Windows RT (Man what a stupid name... Then again, that's what you expect from a company that also gave you this abomination that is the Secure Boot signing process), but Microsoft's current Secure Boot signing policies leave 32-bit ARM out. So there's no Secure Boot for you. Note that this only affects 32-bit ARM and not 64-bit ARM, so Windows ARM64 is fully supported by Rufus when Secure Boot is enabled.

</rant_mode>


  • alacran and devdevadev like this





Also tagged with one or more of these keywords: rufus

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users