JFX

Hmm, this error is properly caused by the multi core decompression used in beta 4. You can disable it in the ini with. [Options] UseMultiCore=0 Can you send me the links for these *swm?

Thanks, reuploaded Beta4 with Italian Translation and a crash fix.

Hi, Sergei. same place, Tools\Win10Builds.ini. You can edit the ini file to your liking.

Version 4 uses half of your CPUs physical cores, which seems the be the best trade off. Using all cores would make the system unusable and it's unlikely that the destination drive is fast enough to actually write all the data in time. @wimb I can't really spot the cause, it never happens with debugger on, so I hope Beta 4 now fixes this bug.

Thanks, It should now be fixed in Beta 3.

Smiley is for the secure boot state. Disabled, enabled or if no smiley the EFI does not support this "feature".

Beta 2 is ready, should fix all mentioned problems.

I've written my own code, but creating a small vss.exe in purebasic will result in huge amount a false positives. I'm still planing to make a tiny vsshelper application in C++, that will be required to get WinNTSetup_x86.exe fully working inside Windows 10 ARM64.

Wimlib's shapshot option does not include any writer components. These are required to correctly read an open data base, like the windows registry. There is a VSHADOW.exe in windows SDK, i guess redistributable , but there is also a simular vscsc on sourceforge.net. Both create "good" shadow copies and have an option called "-exec=" to run a batch file after creation of the shadow and before it's removale.

Hmm, don't really understand. You are the one who checks for the wimboot flag. wimlib-imagex does not care about it. If $linesplit[1] = "WIMBoot compatible" Then $WIMBoot_compatible = StringStripWS($linesplit[2], 3) If $WIMBoot_compatible = "yes" Then $valid = 1 EndIf If you want to use dism/imagex just add this line to your program. EnvSet("WIM_SKIP_WIMBOOT_CHECK", "1") EDIT: be careful with wimlib's --snapshot option it is incomplete and useless for system backup.

All the caption options are not wimboot compatible, WinNTSetup just ignores this when applying a WIM file. I could add wimboot compression option, but i doubt anyone will use it, caused it's as very week compression. I'll fixed the other mention points later.

WinNTSetup 4.0 Beta 1 - Dark Theme support - Added Disable Reserved Storage tweak added - Added Wim Capture option - Added Hotfix uninstall option - Added Driver Export/Import option

Hi cnhtdyui, see fujianabc's osletter7.cmd: http://reboot.pro/topic/10126-nt-6x-fast-installer-install-win7-directly-to-usb-external-drive/?p=88282 But i don't think using A: is a good idea.

it's NoBootMount=1

Hi alacran, 1) Yes, that's all. Just select the drivers folder and use right click on checkbox to change the unsigned option. 2) Should look like this https://imgur.com/X8Zgd8V for 3 seconds 3) Yes, it just passed the ForceUnsigned parameter to Dism 4) Windows 7 and newer 5) It set testsigning in BCD

@click-click These are just the GUI options on the Ready? GUI. The last 3 should be 0 or 1. You just add all options in the WinNTSetup.ini there is no wimlib.ini. @SteveSi On XP Tab you need to right click on the source button to select an ISO.

Well first make sure the installation has the wof driver installed. Best if you have installed that system with any of WinNTSetups compact option. Than start the compression: WofCompress -c:LZX -path:C:\ It will automatically use the exclusion list in WimBootReCompress.ini that WinNTSetup has placed in Windows\System32 folder. You can also use it to just compress any folder, if you want: WofCompress -c:LZX -a -path:D:\Programs

Yes The WofCompress tool for Win7 - win10 http://jfx.cwcodes.net/WofCompress/WofCompress.7z

What you mean with "won't let you"? It should display a warning, but let you continue.

Added a link on first post.

Yes, a ini is always loaded if found. Either Winntsetup.ini or the one specified by -cfg parameter.

No order does not matter, expect NT6 must be first one.

WinNTSetup_x64.exe NT6 -source:%MYISO% -wimindex:1 -cfg:WinNTSetupHome.ini should do exactly that.

No, if you set source in command line you must set wimindex there too.

NONE option does not compress any file, but adds the wofadk.sys driver and copies the WimBootCompress.ini to System32 folder. So this new install can read WOF compressed files and is ready to be compressed later.