JFX
-
Posts
1,277 -
Joined
-
Last visited
-
Days Won
7 -
Donations
0.00 USD
Content Type
Profiles
Forums
Events
Posts posted by JFX
-
-
Just guessing will not help much. WinNTSetup already uses these 2 commands.
bcdboot.exe W:\Windows /s S: /f ALL bootsect.exe /nt60 S: /mbrWere W: is the Windows installation drive and S: is the selected boot partition.
Only difference I see is the missing /force switch on bootsect command.
But this is done on purpose, also diskpart does write bootable MBR and PBR.If you encounter the problem again try 1 of these command from a WinPE,
to find out witch one makes a bootable again.1 -
That sounds like a problem with the MBR of the boot disk.
By default WinNTSetup uses bootsect to update the boot sectors.
bootsect.exe /nt60 S: /mbrThe first 2 green lights are only using simple checks, there is no way to tell if the code is actually bootable.
To limit the problem, it depends on what repair you do with bootice.
1 -
Wimlib is only faster for capture. For apply there actually more or less equal.
Just wimgapi can use more than 1 CPU core, so it can speed up quite a bit.1 -
Thanks, it looks good
One thing, if I use "UEFI original Script" it ends up selecting the MSR partition as boot drive.
1 -
Found a solution. Next version will respect this setting.
1 -
There is no option. Disk index is a file property, thus it is saved inside the WIM file.
Maybe, I can alter the attributes during apply.But has this disk indexing setting still any effect since Vista?
1 -
No, i should be OK, wimlib is recommended library for creating a WIM file.
Just wonder why wimgapi has a trouble with that WIM. Never had any compatibly problems.
Expect the LZMS WIM/ESD created by earlier version of WinNTSetup, but they would cause a crash or freeze of the program.0 -
How was this WIM file created?
0 -
During this error display there should be a log file: %Temp%\WinNTSetup\Logs\wimgapi_error.log
Maybe better to switch to wimlib with (Ctrl + Shift + W) and see if it can apply the WIM.
0 -
On 7/23/2023 at 1:57 PM, Google2023 said:
Refs 3.10？
Is there any problem? You need at least build 25324 as host and source to install.
0 -
On 7/20/2023 at 10:48 AM, dimo70 said:
At now it is in russion language only, but i will make in english too. Can I public it here than?
Sure, please share, when ready.
1 -
No, WinNTSetup only applies to one partition. What you are looking for is mklink.
Move C:\Windows\Microsoft.NET to d:\Microsoft.NET than create symlink or junction.2 -
Yes, you can specific the drives with letter:
WinNTSetup_x64.exe NT6 -syspart:S: -tempdrive:W:or with drive and partition number
WinNTSetup_x64.exe NT6 -syspart:HDD1:1 -tempdrive:HDD1:4Eventually you will need a timeout after diskpart to have drive letter available on system.
ping 127.0.0.1 -n 2 > nul2 -
1 hour ago, dimo70 said:
JFX, do you have more options, that can be used in main .ini file?
There are all the GUI options you can save with CTRL+S and the 26 hidden option mentioned in the WinNTSetup.ini.txt.
Do you need anything in particular?1 hour ago, 547207991 said:怎么下载？
Links are on the first page, do you need another mirror?
On 1/31/2011 at 1:49 PM, JFX said:1 -
No, I mean you can use multi threaded WIM apply also with image.exe or DISM.exe on command prompt
by just setting WIM_FileData_Number_Workers environment variable.WinNTSetup will load an existing WinNTSetup.ini on start.
This .ini can be loaded or saved with Ctrl + L and CTRL + S hotkey and holds most GUI settings.WinNTSetup.ini.txt describes hidden feature than can be added to WinNTSetup.ini.
like:
[options] UseMultiCore=11 -
38 minutes ago, dimo70 said:
i saw x4 and x6 after the process of applying. What this digits mean?
That's the thread count used by wimgapi.
See WinNTSetup.ini.txt, by default if uses half of CPU physical cores.You can uses this with imagex.exe or DISM.exe, too.
set WIM_FileData_Number_Workers=8 Imagex /apply ...1 -
Yes, sample.ini is just there to give you an idea of the feature, you supposed to create your own *.ini file based on it.
1 -
37 minutes ago, Antonino said:
I also had jfx tell me to write some RemoveAppx.ini to contain all this, but I do not know if I should use it instead of sample.ini, together with sample.ini in the same subfolder, or someplace else.
Yes, create your own RemoveAppx.ini inside DISM folder. Sample.ini is just an example how the .ini it should be formatted.
0 -
42 minutes ago, Virgus said:
Is it already available ? In case affirmative, what is the correct syntax ?
Seems, I missed adding this to the F1 Help, there is a -dism: switch taking a file name relative to the DISM folder
WinNTSetup_x64.exe NT6 -dism:Sample.ini1 -
Yeah this tool is dead. there is simply no need for it anymore.
Stick with older version or use adksetup.exe with terrible 45 MB download.If you have a current OS, why would you need them anyway?
0 -
If you like, but not sure what difference it would make.
1 -
You can edit DISM\Sample.ini or better create your own lets say RemoveAppx.ini.
Remove the netfx3 under [EnableFeature], as it takes some space.
After using DISM option with WinNTSetup, a list of APPX packages the are not removed.Dism /Image:X:\ /Get-ProvisionedAppxPackagesAdd what you want to be removed under [RemoveAPPX] of your ini.
As for space warning, only compact:none has one
1 -
17 hours ago, Antonino said:
yes, there is one, provided ur disk or vhd has enough space for the initial installation proper, as it is impossible to compact while installing.
Using mode Compact:XPRESS*K or LZX do compress while extracting the WIM file. Free space check is disabled for these modes.
However to survive setup, tweaks like pagefile and hibernate removal might be necessary.
Using DISM option to remove APPX will also save a lot space.0 -
Yeah, that evil thing does not want to stay disabled.
To get back build-in Spyware, save this as .cmd file and run it as admin.reg delete "HKLM\Software\Policies\Microsoft\Windows Defender" /v DisableAntiVirus /f reg delete "HKLM\Software\Policies\Microsoft\Windows Defender" /v DisableAntiSpyware /f reg delete "HKLM\Software\Policies\Microsoft\Windows\System" /v EnableSmartScreen /f reg delete "HKLM\Software\Policies\Microsoft\Windows Defender\SmartScreen" /v ConfigureAppInstallControlEnabled /f reg delete "HKLM\Software\Policies\Microsoft\Windows Defender\SmartScreen" /v ConfigureAppInstallControl /f reg add HKLM\Software\Microsoft\Windows\CurrentVersion\Run /v SecurityHealth /t REG_EXPAND_SZ /d ^%%windir^%%\system32\SecurityHealthSystray.exe reg delete "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\MpCmdRun.exe" /v Debugger /f reg delete "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\MsMpEng.exe" /v Debugger /f reg delete "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\smartscreen.exe" /v Debugger /f start %windir%\system32\SecurityHealthSystray.exe1
WinNTSetup v5.4.2
in Install Windows from USB
Posted
Yes, simple use a filename with .vhdx extension and it will create a VHDX file.