Jump to content

wuliyen

Member
  • Posts

    43
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    China

Posts posted by wuliyen

  1. Virtualization

    \Windows\INF\hvservice.inf
    \Windows\System32\drivers\hvservice.sys
    \Windows\System32\DriverStore\FileRepository\hvservice.inf_*
    
    \Windows\INF\windowstrustedrtproxy.inf
    \Windows\System32\DriverStore\FileRepository\windowstrustedrtproxy.inf_*
    
    \Windows\INF\wvid.inf
    \Windows\System32\DriverStore\FileRepository\wvid.inf_*
    
    \Windows\System32\drivers\winnat.sys
    
    \Windows\System32\drivers\winhvr.sys
    \Windows\System32\lxss\wslsupport.dll
    \Windows\System32\migration\VsmKeyMigPlugin.dll
    
    \Windows\System32\cimfs.dll
    \Windows\System32\computecore.dll
    \Windows\System32\computelibeventlog.dll
    \Windows\System32\computenetwork.dll
    \Windows\System32\computestorage.dll
    \Windows\System32\hvhostsvc.dll
    \Windows\System32\hvloader.dll
    \Windows\System32\iumsdk.dll
    \Windows\System32\p9np.dll
    \Windows\System32\p9rdrservice.dll
    \Windows\System32\securekernel.exe
    \Windows\System32\tcblaunch.exe
    \Windows\System32\tprtdll.dll
    \Windows\System32\ucrtbase_enclave.dll
    \Windows\System32\vertdll.dll
    \Windows\System32\vid.dll
    \Windows\System32\vmdevicehost.dll
    \Windows\System32\wshhyperv.dll
    \Windows\System32\wsl.exe
    \Windows\System32\wslapi.dll

     

  2. On 5/10/2025 at 5:29 PM, Atari800XL said:

    Thanks, but do you also know if something changed with this settings over the last couple of months, meaning the last few update cycles?

    Like I said, for me this has only been a problem for a couple of months now, I didn't notice it before that.

    WinNTSetup,You check the box disable defender,it was off

  3. On 4/27/2025 at 10:16 PM, Atari800XL said:

    Does WinNTSetup use this setting in the "Disable Defender" section?

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CI\Policy]
    "VerifiedAndReputablePolicyState"=dword:00000000

    I have found that I have to add this in my own apply script to prevent some installers from becoming very slow and unresponsive after a clean install, I have only noticed this since a few months. I haven't tested with WinNTSetup, so I wondered if you used this setting all along?

    Not sure if something has changed with recent Windows 11 24h2 versions and/or updates, but I just wanted to drop the info here and ask if anyone else knew more about it.

    EDIT: Searching for this settings on the net I found some discussion about this would make the system unstable, so I'm wondering if any of you know something about that as well?

     

    Yes, without this setting, some installation programs may take a very long time to complete.

  4. 8 hours ago, Antonino said:

    TX wuliyen, I will, which will act on a new os install. How about having the same on an already installed os? Will I have to start over in order to enjoy the benefits? in other words, if I want to re-apply a wim file from some previous install or other and place my unattend.xml in the unattend slot, will wintsetup take it into account in the apply process or not? if not, I guess I would have to do it all over again from the iso. this is my very doubt and consequent question.

    unattend.xml is in the right path and will work

  5. 3 hours ago, JFX said:

    Just add this to your unattend.xml --> oobsystem.

        <component name="Microsoft-Windows-SecureStartup-FilterDriver" processorArchitecture="amd64" language="neutral" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS">
          <PreventDeviceEncryption>true</PreventDeviceEncryption>
        </component>

     

    If you want to keep most of the WinSxS folder than delete WinSxS.ini.
    Without it you black\white list WinSxS files like all other in the Remove folder.

    OK

  6. minwin Windows11_23H2_22631.3296_X64
    An error occurred during the installation of the system.
    Could not load DLL C:\Windows\system32\msdtcprx.dll; 
    The fact that the file msdtcprx.dll exists!
    What is the problem?


    SYSPRP ActionPlatform::LaunchModule: Successfully executed 'CryptoSysPrep_Specialize' from C:\Windows\system32\capisp.dll
    SYSPRP SysprepSession::ExecuteInternal: Skipping offline-capable module of Microsoft-Windows-Sysprep-SpBcd when running online
    SYSPRP ActionPlatform::LaunchModule: Executing method 'Sysprep_Online_Specialize_Bcd' from C:\Windows\System32\spbcd.dll
    SYSPRP GeneralizeBcdStore: Found the memory tester object.
    SYSPRP SpecializeBcdStore: Found the resume object {5fe9d0f0-e5ff-11ee-8bee-000c29fd7075} for the OS loader.
    SYSPRP SpecializeBcdStore: Successfully specialized {9dea862c-5cdd-4e70-acc1-f32b344d4795} application device. Status = [0x0]
    SYSPRP SpecializeBcdStore: Successfully specialized {b2721d73-1db4-4c62-bf78-c548a880142d} application device. Status = [0x0]
    SYSPRP SpecializeBcdStore: Successfully specialized {fa926493-6f1c-4193-a414-58f0b2456d1e} application device. Status = [0x0]
    SYSPRP SpecializeBcdStore: Successfully set the {fa926493-6f1c-4193-a414-58f0b2456d1e} OS device to the boot partition. Status = [0x0]
    SYSPRP SpecializeBcdStore: The /detecthal switch could not be removed because it was not found.
    SYSPRP SpecializeBcdStore: Successfully specialized {5fe9d0f0-e5ff-11ee-8bee-000c29fd7075} application device. Status = [0x0]
    SYSPRP SpecializeBcdStore: Successfully set the {5fe9d0f0-e5ff-11ee-8bee-000c29fd7075} hiberfile device to the boot partition. Status = [0x0]
    SYSPRP Sysprep_Specialize_Bcd: Successfully specialized the bcd store. Status=[0x0]
    SYSPRP ActionPlatform::LaunchModule: Successfully executed 'Sysprep_Online_Specialize_Bcd' from C:\Windows\System32\spbcd.dll
    SYSPRP SysprepSession::ExecuteInternal: Skipping offline-capable module of Microsoft-Windows-COM-DTC-Runtime when running online
    SYSPRP ActionPlatform::LaunchModule: Could not load DLL C:\Windows\system32\msdtcprx.dll; dwRet = 0x7e[gle=0x0000007e]
    SYSPRP SysprepSession::ExecuteAction: Failed during sysprepModule operation; dwRet = 0x7e[gle=0x0000007e]
    SYSPRP SysprepSession::ExecuteInternal: Error in executing action for Microsoft-Windows-COM-DTC-Runtime; dwRet = 0x7e[gle=0x0000007e]
    SYSPRP SysprepSession::Execute: Error in executing actions from C:\Windows\System32\Sysprep\ActionFiles\Specialize.xml; dwRet = 0x7e
    SYSPRP SysprepSession::Execute: Sysprep mode was not specified, deleting it from registry
    SYSPRP RunPlatformActions:Failed while executing Sysprep session actions; dwRet = 0x7e
    SYSPRP Callback_Specialize: Internal Providers Specialized Failed. System can't proceed to handle Internal Providers
    SYSPRP Callback_Specialize: Specialize return: [126]
    SYSPRP Callback_Specialize: An error occurred while either deciding if we need to specialize or while specializing; dwRet = 0x7e[gle=0x00000002]
    IBSLIB PublishMessage: Publishing message [Windows 安装程序无法将 Windows 配置为在此计算机的硬件上运行。]
     

     

  7. Some scenario where the following folder is deleted
    \Windows\bcastdvr
    The log file is large but opens empty with no content

     

    I'm sorry. It's just me.

    About bcastdvr

     

     

    QQ图片20240311215543.png

    NO \Windows\bcastdvr

    Deleting WinSxS.ini will result in an error

     

  8. On 3/7/2024 at 2:22 AM, JFX said:

    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. 

      

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

    Thanks for the update!

×
×
  • Create New...