JFX
-
Posts
1,270 -
Joined
-
Last visited
-
Days Won
6 -
Donations
0.00 USD
Content Type
Profiles
Forums
Events
Posts posted by JFX
-
-
Sure, just add a APPX dispaly name to the RemoveAPPX section.
Wildcards like ? and * are allow, too.
2 -
It depends if there is a wimlib_WIMHOST_error.log than 47
is one of the wimlib error codes else it would be a System Error Codes.
2 -
SAB tires to start ImmersiveShellController before sending Local\ShellStartupEvent, this can't work in a WinPE.
It's ok with a tiny twinui.pcshell.dll, but maybe SAB could ignore this check if:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MiniNT key exists.
1 -
WinNTSetup has an option to save drive letter assignment.
If this not works for you, than manually backup the registry value of your Z: under
HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices.0 -
It is the same syntax as the ini file uses:
WinNTSetup_x64.exe NT6 -sysPart:HDD0:1 -tempDrive:Z: -sysLetter:C: -bcd:EFI -silent -setup1 -
Yes, seems there got something wrong with the rar creation.
WinNTSetup 5.4.1
- added missing LANG folder
- bootice language files prefer MUI names
- disabled multicore apply for x86 version.
- removed system menu integration1 -
See first post as usual.
Merry xmas and a happy new year to all.
4 -
WinNTSetup 5.4
- support for Windows 24H2 and Server 2025
- added arm64 and x86 versions
- language files prefer MUI names
- support for RTL languages
- use only one DISM session
- fixed Windows 7 ESP drive mounting
- updated Windows 7 USB3 drivers instructions
- new disable defender tweak includes Windows Malicious Software Removal Tool
4 -
The NTFS permissions comes from the WIM file.
MinWin apply only changes the admin rights (MinWin\Default\Options.ini --> AdminAccess = 1)
EDIT: I'll disable AdminAccess in next version, it's useful to test and modify MinWin installation, but should not be default.
0 -
On 8/9/2024 at 4:58 PM, sharicov@gmail.com said:
Cannot install Windows 11 from Win11_23H2_English_x64v2.iso
Windows 10 installation works fine (source: Win10_22H2_EnglishInternational_x64v1.iso)
Installing on USB disk (Samsung T3)
Winntsetup version 5.3.5.2
Tried all ways: normal, VHD and VHDx ways, static and dynamic.
Getting VHD BOOT INITIALIZATION FAILED Blue Screen error or BOOT INITIALIZATION FAILED Blue Screen error depends on installation type.
Please help.
Did you make any progress on this?
Sounds like the USB disk becomes inaccessible during boot.
Did you tried different hardware to boot the USB disk?
Is there any difference with official Windows To Go setup?0 -
2 hours ago, click-click said:
one last question for now
Does WinNtSetup do anything with BootDriverFlags?
No, it does not touch this value.
0x1C - is the default on Windows 10/11, so I wonder why you have a different one.
0 -
WinNTSetup_x64.exe NT6 -sysPart:Q: -tempDrive:Z: -sysLetter:-C: -bcd:ALL -silent -setup
1 -
Yes, the currently running system has the correct data in \DosDevices\Z:.
The offline system has invalid data in \DosDevices\C:1 -
Mountpoints are calculated, but if you want to do it manually
Look up the data of the new partition under HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices
and add it to the offline systems registry \DosDevices\C: value.8 hours ago, click-click said:The BCD had the correct entries in the boot menu.
I doubt that. VHDs are unique, you need to updated the BCD for every new VHD.
2 -
Fixing mountpoint of system drive is always done, there is no special command line switch needed.
1 -
Than maybe something is wrong with the WIM files you have.
0 -
@ibay770 WinNTSetup has reach EOL status.
You could use it's command line options to automate these steps.
@hhui Access denied error is very common with wimgapi or Dism, WinNTSetup already use Trusted Installer rights to overcome some of them.
You could try wimlib (top right window icon --> WIM API --> wimlib) for apply instead.
0 -
On 7/4/2024 at 5:18 PM, KittyMaster said:
I've two issues.
1st issue:
Use bootsect.exe to update the bootcode : ALL results in followingWindows 7 in UEFI mode is a bit picky about partition layout. It only support GPT.
On 7/4/2024 at 5:18 PM, KittyMaster said:2nd issue:
I've placed the correct x64 files from Win8 backported drivers as instructed, but USB3 still didn't work:The backported driver were update and are now signed with SHA-256.
So this method does not work, unless you find the older drivers.
0 -
2 hours ago, KittyMaster said:
Note: Inside the sources folder of the ISO, I noticed there are two files called "install.swm" and "install2.swm". Could these be causing the problem?
Dunno, maybe a Windows 7 related problem. Try older version like 4.25.
Maybe the SWM file is broken, try apply with image.exe.
0 -
WinNTSetup 5.3.5.2
- fixed crash with no source selection
- removed policy for HiberbootEnabled4 -
Yes, the second policy for HiberbootEnabled has no effect and will be removed.
The first one seems to be different between windows versions.1 -
On 6/23/2024 at 4:40 AM, wuliyen said:
!\Windows\SysWOW64\wbem\
!\Windows\SysWOW64\WindowsPowerShell\The above writing style, only the directory files will be retained, the directory folders will not be retained.
Yes, MinWin focus on deleting files. It's unusual to delete complete folder and than want to keep it.
In that case, use wildcard pattern:
!\Windows\SysWOW64\WindowsPowerShell\*1 -
It's just a problem with settings app. It properly tries to communicate with Defender and does not get any respond.
0 -
Yes, Windows 10 2015 version already uses a 16 MB partition.
1
WinNTSetup v5.4.1
in Install Windows from USB
Posted
Don't know, you properly the first one ever getting this error message.
Make sure you not running out of free disk space. You need at least the size of \Windows\System32\config\SOFTWARE.