[WinNTSetup v5.4.2]

It does a bit more than just setting IFEO Debuggers.

If Tweaks_NT6_Array(#Tweaks_NT6_Disbale_Defender, 1)
        
        If *Z\Build > 10100
          ORSetDword(*Z\SftHive, "Policies\Microsoft\Windows Defender", "DisableAntiSpyware", 1)
          ORSetDword(*Z\SftHive, "Policies\Microsoft\Windows Defender", "DisableAntiVirus", 1)
          
          ORSetString(*Z\SftHive, "Microsoft\Windows\CurrentVersion\Explorer", "SmartScreenEnabled", "Off")        
          ORSetDword(*Z\SftHive, "Policies\Microsoft\Windows\System", "EnableSmartScreen", 0)
          ORSetDword(*Z\SftHive, "Policies\Microsoft\Windows Defender\SmartScreen", "ConfigureAppInstallControlEnabled", 1)
          ORSetDword(*Z\SftHive, "Policies\Microsoft\Windows Defender\SmartScreen", "ConfigureAppInstallControl", 1)
          
          ORSetDword_USClasses(*Z, *Z\Usr_Classes_Hive, "Local Settings\Software\Microsoft\Windows\CurrentVersion\AppContainer\Storage\microsoft.microsoftedge_8wekyb3d8bbwe\MicrosoftEdge\PhishingFilter", "EnabledV9", 0)
          ORSetDword_US(*Z, "Software\Microsoft\Windows\CurrentVersion\AppHost", "EnableWebContentEvaluation", 0)
          
        EndIf
        
        ORSetDword(*Z\SftHive, "Microsoft\Windows Defender\Real-Time Protection", "DisableRealtimeMonitoring", 1)
        ORSetDword(*Z\SftHive, "Microsoft\Windows Defender\Real-Time Protection", "DisableAntiSpywareRealtimeProtection", 1)
        
        ORSetDword(*Z\SftHive, "Microsoft\Windows Defender", "DisableAntiSpyware", 1)
        ORSetDword(*Z\SftHive, "Microsoft\Windows Defender", "DisableAntiVirus", 1)
        
        If *Z\Build > 18300
          ORSetDword(*Z\SftHive, "Microsoft\Windows Defender\Features", "TamperProtection", 0)
        EndIf
        
        If *Z\Build >= 22000
          ORSetDword(*Z\SftHive, "Microsoft\Windows Defender\Real-Time Protection", "DpaDisabled", 1)
          ORSetString(*Z\SftHive, "Microsoft\Windows NT\CurrentVersion\Image File Execution Options\MpCmdRun.exe", "Debugger", "NUL")          
          ORSetString(*Z\SftHive, "Microsoft\Windows NT\CurrentVersion\Image File Execution Options\MsMpEng.exe", "Debugger", "NUL")
          ORSetString(*Z\SftHive, "Microsoft\Windows NT\CurrentVersion\Image File Execution Options\smartscreen.exe", "Debugger", "NUL")
          
          ORSetDword(*Z\SysHive, "ControlSet001\Services\SecurityHealthService", "Start", 0)
          ORDeleteValue(*Z\SftHive, "Microsoft\Windows\CurrentVersion\Run", "SecurityHealth")
          
        EndIf
        
      EndIf

 

[WinNTSetup v5.4.2]

Don't think there is a good way to remove defender. But WinNTSetup's tweak should completely disable it.

This can be reversed later, it needed.

[WinNTSetup v5.4.2]

Yes, there were some reports of this with Server 2022.
I can't reproduce it and checking if a file exist, is the most basic feature.

I could only assume something like an antivirus or filter driver that does interfere,
but it does not happen if I install Server 2022 with WinNTSetup. The new system does not show any problem.

The version display of wimlib and wimgapi will be removed, it just leads to wrong assumption and
some people start updating them manually, what only causes problems.

[WinNTSetup v5.4.2]

10 hours ago, freqout said:

This is great.  Wondering if this can be used to make the VHD bootable instead of actuing on my local boot partition, and if it can be scripted and completely automated from Powershell.

Yes, if you select a different boot drive, your local boot partition will not not be touched. 
For automation there are many command line options, see F1 - help.

[WinNTSetup v5.4.2]

That could happen if you update wimlib, the official version is no longer supported.

[WinNTSetup v5.4.2]

1 hour ago, wuliyen said:

Some files are located in the WINSXS folder when installed by default, but the MUI files exist in the Languages folder. What should I do in this case?

I would ignore them. If there is no lpq.exe in system32 than that applications is no installed and does not need a .mui file.

If it get's installed (by dism) later, it should copy the .mui, too.

[WinNTSetup v5.4.2]

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

[WinNTSetup v5.4.2]

Ok, could generate a crash under some WinPE environments.

WIMHost_1.2.1.0.zip

[WinNTSetup v5.4.2]

Well I can't reproduce it.
Where can I download that exact ISO?
Did you try with different source, maybe a clean MDSN version?

[WinNTSetup v5.4.2]

Yes, noticed there was a problem, should be fixed now.

 

[WinNTSetup v5.4.2]

I don't get that error. Make sure you don't miss any dependency of this proxy dll.

[WinNTSetup v5.4.2]

That should be fixed with WimHost.exe 1.1.0.3, posted yesterday.

[WinNTSetup v5.4.2]

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.

[WinNTSetup v5.4.2]

I think that I fixed all MinWin bugs reported. 

 

 

 

[WinNTSetup v5.4.2]

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.

[WinNTSetup v5.4.2]

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.

[StartAllBack for Windows 11]

Something has changed with SysTab32 controls font rendering.

Build 4888 was good, but 4892 is a bit blurry.

[WinNTSetup v5.4.2]

You can't change it, but you can add it original form.

[WinNTSetup v5.4.2]

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.

[WinNTSetup v5.4.2]

Source code is not available, but it's freeware. Do with it what you want. 

[WinNTSetup v5.4.2]

Hmm, can't reproduce that here.
Do you have a crash dump or error in eventlog?

[WinNTSetup v5.4.2]

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.

[WinNTSetup v5.4.2]

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 kept

 This version will add logging for black and whitelist as well MUI and MUN file removal.

[WinNTSetup v5.4.2]

PerformenceV2 deletes the registry keys under:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\_V2Providers

[WinNTSetup v5.4.2]

@suxichao You the first one having that problem. Try to nail down what causing it.

@wuliyen Seems the MUI progression if a bit a aggressive. This should limit it to *.mui files only.