JFX
-
Posts
1,270 -
Joined
-
Last visited
-
Days Won
6 -
Donations
0.00 USD
Content Type
Profiles
Forums
Events
Posts posted by JFX
-
-
Ok, could generate a crash under some WinPE environments.
0 -
Well I can't reproduce it.
Where can I download that exact ISO?
Did you try with different source, maybe a clean MDSN version?0 -
Yes, noticed there was a problem, should be fixed now.
0 -
I don't get that error. Make sure you don't miss any dependency of this proxy dll.
0 -
That should be fixed with WimHost.exe 1.1.0.3, posted yesterday.
0 -
MinWin and RAM booting Windows was a - just for fun - project for me.
I don't share your passion about it. So if you want to create a database, be the first one adding something to it.For me, I only provide the tool and a basic example.
1 -
I think that I fixed all MinWin bugs reported.
0 -
Oh, wanted to improve that error message for years.
You have a WinPE selected as source, that's not supported and doesn't make sense.
Use bootice to create a boot entry for the WIM file.0 -
No, Setup=1 just means the filter is only used for sources that are still setup mode (SystemSetupInProgress=1).
With some luck you can get the missing file logged somewhere in \Windows\Panther.
0 -
Something has changed with SysTab32 controls font rendering.
Build 4888 was good, but 4892 is a bit blurry.
1 -
You can't change it, but you can add it original form.
0 -
12 hours ago, suxichao said:
WIMHost (wimlib) error 0x1C: The SHA-1 message digest of a WIM resource did not match the expected value.
That sounds like the WIM has data corrupted.
Try to apply the WIM with wimlib-image.exe maybe it reports more error data.If wimlib-image.exe failes and Dism works than it seems to be a wimlib bug.
0 -
Source code is not available, but it's freeware. Do with it what you want.
0 -
Hmm, can't reproduce that here.
Do you have a crash dump or error in eventlog?0 -
You should not use DISM to capture a installation WinNTSetup has prepared for this one partition.
Either delete HKLM\SYSTEM\MountedDevices before capture or
always use WinNTSetup for capture to WIM and apply to disk.0 -
Drive letter assignment is really simple stuff.
WinNTSetup will calculate and write \DosDevices\C: to HKLM\SYSTEM\MountedDevices
On first boot Windows will recognize a different drive letter and does all the work.On 3/4/2024 at 1:35 PM, wuliyen said:There is still a problem that needs to be fixed
Windows\Boot\PCAT\zh-CN\bootmgr.exe.mui
This file needs to be keptThis version will add logging for black and whitelist as well MUI and MUN file removal.
0 -
PerformenceV2 deletes the registry keys under:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\_V2Providers
0 -
-
6 hours ago, click-click said:
Is there a way to tell WinntSetup to use a different name for the OS Title?
No. And i don't want to add UI options for everything.
1 -
15 hours ago, Tihiy said:
Adjusted, please retest
NoDarkTooltips works now, thanks.
0 -
Seems the "NoDarkTooltips" reg option is ignored by this new version.
1 -
3 hours ago, click-click said:
The apply image is not broken because it installs fine to a partition. What could be the problem with the install to vhd and how to fix?
Start by looking at the log files: \Windows\Panther.
Maybe your BCD is a bit unusual are edit it to much with bootice.Maybe you some alternative boot manager.
0 -
6 hours ago, sakatgg said:
But the folder is deleted in both Server 2019 and Win11
If there is a way to make the filter work in NetFX.txt? Thank you.
Are you sure you don't delete it somewhere else. Lines that get skipped will be logged:
\Windows\Logs\WinNTSetup\*\MinWin_WimHost.log
0 -
On 2/19/2024 at 1:06 PM, dimo70 said:
Maybe better include ability scanning for sources in next version of WinNTSetup?
I don't plan any new version. Create your own tool for scanning or modify the scanfiles.cmd to your need.
16 hours ago, Antonino said:sorry about changing the subject - would anyone tell me how to change the default x: vhd drive into any other one when creating it in winntsetup? me, I would be better off having i: as the default vhd drive instead.
Change it with Disk management or bootice and hit F5 in WinNTSetup.
1
WinNTSetup v5.4.1
in Install Windows from USB
Posted
I guess system32 mui folder is a fallback location for it's subfolders.
Added recursive scanning for mui candidates.
WIMHost_1.2.3.0.zip