@abbodi1406 Just an update. I was testing ReFS on my old and new machines with Hyper-V and everything was super quick. Today I decided to test W10UI on ReFS using Dev Drive VDHX 50GB on Win 11 23H2 with Win 11 24H2 ISO. It was done in 15 mins for Home and Pro including adding all my customization using WinToolkit. It seems NTFS has some IO bottleneck on heavy IO workloads.
DISM support ReFS, and ReFS has a clear speed advantage. I mount and unmount the same install.wim image on two partitions (NTFS and ReFS) on one NVMe SSD. This is their time consumption. NTFSReFSMount34.19s22.97sUnmount85.38s75.82s
But it's not compatible for all versions https://forums.mydigitallife.net/th...mated-batch-script.68791/page-27#post-1737006
Why do you have to use ReFS in a private environment? NTFS has proven itself, absolutely stable. and on the ml sec, i'll buy a bag of rice that falls off the car
Yes, I don't trust ReFS on PC and never use it to store important data. Only use ReFS for DISM operations to mounted image. Due to ReFS excellent 4K performance, it will save time.
uup-converter-wimlib-113 creates MountUUP folder on a system drive instead of Dev Drive (ReFS), how to disable this check? there's no mounting options like in W10UI just a guess: set line 4339 to this? Code: if /i not "%_ntf%"=="NTFS" if /i not "%_ntf%"=="ReFS" ( upd: seems like mounting / unmounting works fine, but the Edge and Apps integration doesn't Spoiler: UUP Converter v113 Code: === Running UUP Converter v113 === === Checking UUP Info . . . === Configured Options . . . AutoStart 1 ForceDism === Parsing Apps CompDB . . . === Preparing Reference ESDs . . . cabs_HyperV-OptionalFeature-VirtualMachinePlatform-Client-Disabled-FOD-Package-amd64 cabs_Microsoft-Edge-WebView-FOD-Package-amd64 cabs_Microsoft-OneCore-ApplicationModel-Sync-Desktop-FOD-Package-amd64 cabs_Microsoft-OneCore-DirectX-Database-FOD-Package-amd64 cabs_Microsoft-Windows-DirectoryServices-ADAM-Client-FOD-Package-amd64 cabs_Microsoft-Windows-DirectoryServices-ADAM-Client-FOD-Package-wow64 cabs_Microsoft-Windows-EnterpriseClientSync-Host-FOD-Package-amd64 cabs_Microsoft-Windows-EnterpriseClientSync-Host-FOD-Package-wow64 cabs_Microsoft-Windows-Ethernet-Client-Intel-E1i68x64-FOD-Package-amd64 cabs_Microsoft-Windows-Ethernet-Client-Intel-E2f68-FOD-Package-amd64 cabs_Microsoft-Windows-Ethernet-Client-Realtek-Rtcx21x64-FOD-Package-amd64 cabs_Microsoft-Windows-Ethernet-Client-Vmware-Vmxnet3-FOD-Package-amd64 cabs_Microsoft-Windows-FoDMetadata-Package cabs_Microsoft-Windows-Hello-Face-Package-amd64 cabs_Microsoft-Windows-InternetExplorer-Optional-Package-amd64 cabs_Microsoft-Windows-Kernel-LA57-FoD-Package-amd64 cabs_Microsoft-Windows-LanguageFeatures-Basic-en-us-Package-amd64 cabs_Microsoft-Windows-LanguageFeatures-Basic-ru-ru-Package-amd64 cabs_Microsoft-Windows-LanguageFeatures-Handwriting-ru-ru-Package-amd64 cabs_Microsoft-Windows-LanguageFeatures-OCR-en-us-Package-amd64 cabs_Microsoft-Windows-LanguageFeatures-OCR-ru-ru-Package-amd64 cabs_Microsoft-Windows-LanguageFeatures-TextToSpeech-ru-ru-Package-amd64 cabs_Microsoft-Windows-MediaPlayer-Package-amd64 cabs_Microsoft-Windows-MediaPlayer-Package-wow64 cabs_Microsoft-Windows-Notepad-System-FoD-Package-amd64 cabs_Microsoft-Windows-Notepad-System-FoD-Package-wow64 cabs_Microsoft-Windows-PowerShell-ISE-FOD-Package-amd64 cabs_Microsoft-Windows-PowerShell-ISE-FOD-Package-wow64 cabs_Microsoft-Windows-Printing-PMCPPC-FoD-Package-amd64 cabs_Microsoft-Windows-ProjFS-OptionalFeature-FOD-Package-amd64 cabs_Microsoft-Windows-SenseClient-FoD-Package-amd64 cabs_Microsoft-Windows-SimpleTCP-FOD-Package-amd64 cabs_Microsoft-Windows-SmbDirect-FOD-Package-amd64 cabs_Microsoft-Windows-StepsRecorder-Package-amd64 cabs_Microsoft-Windows-StepsRecorder-Package-wow64 cabs_Microsoft-Windows-TabletPCMath-Package-amd64 cabs_Microsoft-Windows-Telnet-Client-FOD-Package-amd64 cabs_Microsoft-Windows-TerminalServices-AppServer-Client-FOD-Package-amd64 cabs_Microsoft-Windows-TerminalServices-AppServer-Client-FOD-Package-wow64 cabs_Microsoft-Windows-TFTP-Client-FOD-Package-amd64 cabs_Microsoft-Windows-VBSCRIPT-FoD-Package-amd64 cabs_Microsoft-Windows-VBSCRIPT-FoD-Package-wow64 cabs_Microsoft-Windows-Wallpaper-Content-Extended-FoD-Package-amd64 cabs_Microsoft-Windows-Wifi-Client-Broadcom-Bcmpciedhd63-FOD-Package-amd64 cabs_Microsoft-Windows-Wifi-Client-Broadcom-Bcmwl63a-FOD-Package-amd64 cabs_Microsoft-Windows-Wifi-Client-Broadcom-Bcmwl63al-FOD-Package-amd64 cabs_Microsoft-Windows-Wifi-Client-Intel-Netwbw02-FOD-Package-amd64 cabs_Microsoft-Windows-Wifi-Client-Intel-Netwew00-FOD-Package-amd64 cabs_Microsoft-Windows-Wifi-Client-Intel-Netwew01-FOD-Package-amd64 cabs_Microsoft-Windows-Wifi-Client-Intel-Netwlv64-FOD-Package-amd64 cabs_Microsoft-Windows-Wifi-Client-Intel-Netwns64-FOD-Package-amd64 cabs_Microsoft-Windows-Wifi-Client-Intel-Netwsw00-FOD-Package-amd64 cabs_Microsoft-Windows-Wifi-Client-Intel-Netwtw02-FOD-Package-amd64 cabs_Microsoft-Windows-Wifi-Client-Intel-Netwtw04-FOD-Package-amd64 cabs_Microsoft-Windows-Wifi-Client-Intel-Netwtw06-FOD-Package-amd64 cabs_Microsoft-Windows-Wifi-Client-Intel-Netwtw08-FOD-Package-amd64 cabs_Microsoft-Windows-Wifi-Client-Intel-Netwtw10-FOD-Package-amd64 cabs_Microsoft-Windows-Wifi-Client-Marvel-Mrvlpcie8897-FOD-Package-amd64 cabs_Microsoft-Windows-Wifi-Client-Qualcomm-Athw8x-FOD-Package-amd64 cabs_Microsoft-Windows-Wifi-Client-Qualcomm-Athwnx-FOD-Package-amd64 cabs_Microsoft-Windows-Wifi-Client-Qualcomm-Qcamain10x64-FOD-Package-amd64 cabs_Microsoft-Windows-Wifi-Client-Ralink-Netr28x-FOD-Package-amd64 cabs_Microsoft-Windows-Wifi-Client-Realtek-Rtl8192se-FOD-Package-amd64 cabs_Microsoft-Windows-Wifi-Client-Realtek-Rtwlane-FOD-Package-amd64 cabs_Microsoft-Windows-Wifi-Client-Realtek-Rtwlane01-FOD-Package-amd64 cabs_Microsoft-Windows-Wifi-Client-Realtek-Rtwlane13-FOD-Package-amd64 cabs_Microsoft-Windows-WinOcr-FOD-Package-amd64 cabs_Microsoft-Windows-WinOcr-FOD-Package-wow64 cabs_OpenSSH-Client-Package-amd64 === Creating Setup Media Layout . . . === Creating install.wim . . . Using LZX compression with 8 threads Archiving file data: 7540 MiB of 7540 MiB (100%) done === Updating install.wim / 1 image{s} . . . === Servicing Index: 1 Deployment Image Servicing and Management tool Version: 10.0.26100.2454 Mounting image [==========================100.0%==========================] The operation completed successfully. === Adding Microsoft Edge . . . Deployment Image Servicing and Management tool Version: 10.0.26100.2454 Error: 1812 The request is not supported. The DISM log file can be found at C:\WINDOWS\Logs\DISM\DismEdgeWim.log === Adding Apps . . . Unhandled exception: Microsoft.Dism.DismException: The request is not supported. в Microsoft.Dism.DismUtilities.ThrowIfFail(Int32 hresult, DismSession session, String callerMemberName) в Microsoft.Dism.DismSession.Reload() в Appx.Program.Main(String[] args) Deployment Image Servicing and Management tool Version: 10.0.26100.2454 Saving image [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.26100.2454 Image File : F:\uup-converter-wimlib-113\ISOFOLDER\sources\install.wim Image Index : 1 Unmounting image [==========================100.0%==========================] The operation completed successfully. === Rebuilding install.wim . . . "ISOFOLDER\sources\install.wim" original size: 3156759 KiB Using LZX compression with 8 threads Archiving file data: 7540 MiB of 7540 MiB (100%) done "ISOFOLDER\sources\install.wim" optimized size: 3148829 KiB Space saved: 7929 KiB === Creating winre.wim . . . Using LZX compression with 8 threads Archiving file data: 1240 MiB of 1240 MiB (100%) done === Adding winre.wim to install.wim . . . === Creating boot.wim . . . Deployment Image Servicing and Management tool Version: 10.0.26100.2454 Mounting image [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.26100.2454 Saving image [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.26100.2454 Error: 1812 The request is not supported. The DISM log file can be found at C:\WINDOWS\Logs\DISM\DismNUL.log Deployment Image Servicing and Management tool Version: 10.0.26100.2454 Image File : F:\uup-converter-wimlib-113\ISOFOLDER\sources\boot.wim Image Index : 1 Saving image [==========================100.0%==========================] Unmounting image [==========================100.0%==========================] The operation completed successfully. === Rebuilding boot.wim . . . "ISOFOLDER\sources\boot.wim" original size: 493474 KiB Using LZX compression with 8 threads Archiving file data: 1264 MiB of 1264 MiB (100%) done "ISOFOLDER\sources\boot.wim" optimized size: 488932 KiB Space saved: 4541 KiB === Creating ISO . . . OSCDIMG 2.56 CD-ROM and DVD-ROM Premastering Utility Copyright (C) Microsoft, 1993-2012. All rights reserved. Licensed only for producing Microsoft authorized content. Scanning source tree (1000 files in 91 directories) Scanning source tree complete (1052 files in 95 directories) Computing directory information complete Image file is 4484399104 bytes (before optimization) Writing 1052 files in 95 directories to 27863.1000.250517-1909.RS_PRERELEASE_CLIENTPRO_OEMRET_X64FRE_RU-RU.ISO 100% complete Storage optimization saved 95 files, 20686848 bytes (1% of image) After optimization, image file is 4466225152 bytes Space saved because of embedding, sparseness or optimization = 20686848 Done. Finished. Press 0 or q to exit.
Here's the funny part, I created a VHDX on existing NTFS W11 23H2 from diskmgmt.msc and booted off Strelec Win 11 PE to format the VHDX with ReFS since Dev Drive kept on failing with invalid format option. There is one downside to VHDX i.e disk space usage actually increased and had to use sdelete with -z option and retrim command twice to bring back to sane usage <1GB after deleting everything once ISO was tested in Hyper-V VM. Which CPU & SSD? I didn't even see loading times. Almost felt like a huge upgrade jumping from HDD -> SSD back in the days of using WinReducer.
ReFS is quirky because the version supported by Win 10 22H2 is v3.10 while 24H2 supports 3.14 so you can upgrade without destroying existing volumes/data.
https://gitlab.com/-/project/11037551/uploads/bbdc7aae987d08f8e2bf6533942e623a/office2010_ohook.7z password: 2010
@abbodi1406 I have a vague memory that w10ui doesn't handle LCUs that consist of .psf + .cab or .psf + .wim files. Am I correct? In which case, do I use PSFX MSU Maker and then use the resulting msu with w10ui for integration?
@shhnedo W10UI include PSFX2MSU functionality since v10.48 it will create the msu file if the required files are detected (AggregatedMetadata cab + DesktopDeployment cab and/or SSU cab)
Dear @abbodi1406 , I'm using right now UUP to ISO script. Thanks for this great tool Please, can you tell me what this options does??? "UpdtBootFiles" "Update ISO boot files bootmgr/memtest/efisys.bin with new files from Cumulative Update. This option will also update new UEFI CA 2023 boot files if detected." Is it recommended to enable it??? If I want to boot Win10 USB (for example, generated by Rufus), either FAT32 (install.esd) or NTFS (install.wim), enabling this option will change anything??? Maybe this option doesn't allow to Boot from ancient PC (from 2007 with old BIOS/UEFI) because it requires the PC to have the updated 2023 UEFI (that of course PCs before 2020 doesn't have)...
@June's Hill I have no idea i never use SecureBoot probably it's more safe to avoid 2023 UEFI until it's mandatory legacy BIOS is not affected