Search results

The entire Settings App

The component is necessary in some cases for Windows installation, if I remember correctly (I didn't have any problems without it), which is why Nuhi protected it. And it's also necessary for the Settings app (well, just one file).

I confirm that this works, the directory and content is not recreated during Windows installation when the SleepStudy component is removed from the image (registry key added automatically).

With group policy, never used. Windows 10 and 11 generally use the same settings, but not for everything, so that might be part of it. You have 11 Pro ?

For me it's good Have you restarted the PC or at least explorer.exe ?

that's the key mentioned above for "This PC" And for all users normally (but never tested) HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{20D04FE0-3AEA-1069-A2D8-08002B30309D} @="Your choice"

Do you want to rename the computer name or "This PC" in Explorer ? For "This PC" it's this registry key : [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\CLSID\{20D04FE0-3AEA-1069-A2D8-08002B30309D}] @="Your choice" Computer name ...

Need preset of modifications to see

Some ideas https://www.reddit.com/r/buildapc/comments/50sgfj/pc_doesnt_turn_off_windows_shuts_down_but/

To choose a theme (a custom theme, for example), dark or light mode, etc..., it's all good in the image. But indeed, some keys need to be "merged" after installation (Windows resets them to default or recreates them during installation).

You can also integrate them directly into HKLM\SOFTWARE\Classes

That we can't reproduce Or if nuhi has retested since

In this case, it's Windows Setup (index 2) and not WinPE (index 9) that's used. This differs from the other post, which is about WinPE (or with WinRE if used)

You're welcome. To see with nuhi to prevent the checkpoint from being automatically selected when NTLite detects build 26100.1742+

Yes maybe, if you have a problem installing Windows. Is that the case ? The only case I've seen is with Intel RAID/VMD drivers that were to be integrated, but they are "separate" drivers. Never seen any other errors during the first installation phase (boot.wim) before the first reboot (other...

You don't need to integrate the KB5043080 and KB5070311 into boot.wim

Uncheck that and just integrated the November update. After ISO 26100.1742, there's no longer any need to integrate the checkpoint.

Download and try with a new (unmodified) ISO, And depending on the ISO version, there's no need to integrate KB5043080

Hi, if you have the preset (.xml) to find out which component you deleted (remove the personal information first)

More info https://investors.micron.com/news-releases/news-release-details/micron-announces-exit-crucial-consumer-business