Search results

  1. T

    TUTORIAL: Create perfect Windows Post-Setup using OOBE.cmd

    To anyone reading this guide, NTLite natively has the capacity to integrate ps1, scripts and registry files, but there are several things to keep in mind. First, you should only integrate Local Machine registry entries prior to the first logon; because the user hasn't been created yet...
  2. T

    SlimJim LTSC 2021 Preset (free)

    NTlite has a gaming preset, best you stick to that. But for hardware and drivers, you can look at my preset and merge it with the gaming preset of NTlite. To answer your question, probably yes, but if you want to make sure... Regards,
  3. T

    SlimJim LTSC 2021 Preset (free)

    So my particular deployment of Ntlite is anal and complicated as can be; sometimes you have to make yourself your own tools case and point SlimJim. So what is the point of SlimJim preset. It is an ideal image for virtualization, includes .net 3.5, you can install the old run times like VC++...
  4. T

    Windows 10/11 Features/Components to Disable, Best Practice, Courtesy by Microsoft

    When trying to assess the full breath of Windows 11 24H2 features, I found information extremely lacking despite what was found here: Windows 11 24H2 Even you you expand everything, I felt like not everything was being told. Because I am also referencing in the back of my mind all the news...
  5. T

    What NTLite component is tied to "Random hardware addresses"?

    Agreed, but not quite as stupid as Only Allowing One Bluetooth game controller to operate at one time.
  6. T

    What NTLite component is tied to "Random hardware addresses"?

    Not exactly what I wanted, but kind of like finding a needle in a haystack I guess so your alternative is helpful. Thank you.
  7. T

    What NTLite component is tied to "Random hardware addresses"?

    Basically, if "Use random hardware addresses" is ON you get a can't connect to the network error. Then you you Admin CMD: ipconfig /flushdns netsh winsock reset Restart your computer Open settings -> Network and Internet -> Network Reset Restart your computer and Bang, you can connect to...
  8. T

    Integrating specific REG breaks Start Menu and Search (LTSC 2021 IoT)

    So there's a few options here: If you think about it, it's silly to add currentuser entries before the first login. Therefore it follows that NTLite delete all those entries if added to the registry portion or before login portion in post-setup. This will prevent lots of problems for users. All...
  9. T

    Integrating specific REG breaks Start Menu and Search (LTSC 2021 IoT)

    Confirmed, the confirmed suspect(s) are: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Search] "CortanaConsent"=dword:00000000 [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Start] "ShowRecentList"=dword:00000000 End of...
  10. T

    Integrating specific REG breaks Start Menu and Search (LTSC 2021 IoT)

    Wrong again apparently, these entries vindicated: [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\SettingSync] "SyncPolicy"=dword:00000005 [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\SettingSync\Groups\Personalization] "Enabled"=dword:00000000...
  11. T

    Integrating specific REG breaks Start Menu and Search (LTSC 2021 IoT)

    The offender has been confirmed to be here: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\CDP] "RomeSdkChannelUserAuthzPolicy"=dword:00000000 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Search]...
  12. T

    Integrating specific REG breaks Start Menu and Search (LTSC 2021 IoT)

    LMAO this is one elusive MOFO, my stab at it failed as well. Namely, the following maintains start menu and search function: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\OneDrive] "DisableFileSyncNGSC"=dword:00000001...
  13. T

    Integrating specific REG breaks Start Menu and Search (LTSC 2021 IoT)

    Good try, but that wasn't it. I'm developing my own theory, let's see.
  14. T

    Integrating specific REG breaks Start Menu and Search (LTSC 2021 IoT)

    When applying add.reg on the post-setup page, the issue goes away, start menu and search work. Good I will try just keeping those entries you have mentioned.
  15. T

    Integrating specific REG breaks Start Menu and Search (LTSC 2021 IoT)

    I have re-affirmed that the offender is in here: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\OneDrive] "DisableFileSyncNGSC"=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OneDrive] "PreventNetworkTrafficPreUserSignIn"=dword:00000001...
  16. T

    Integrating specific REG breaks Start Menu and Search (LTSC 2021 IoT)

    Scratch that last, offending bits superseed last reply Consequently, the two tests I just did are useless and I have learned nothing.
  17. T

    Integrating specific REG breaks Start Menu and Search (LTSC 2021 IoT)

    I will test that momentarily, the offending bits appear to be in here: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\CapabilityAccessManager\ConsentStore\activity] "Value"="Deny"...
  18. T

    Integrating specific REG breaks Start Menu and Search (LTSC 2021 IoT)

    The offender is somewhere in here: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\OneDrive] "DisableFileSyncNGSC"=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OneDrive] "PreventNetworkTrafficPreUserSignIn"=dword:00000001...
  19. T

    Integrating specific REG breaks Start Menu and Search (LTSC 2021 IoT)

    When the following reg file is applied, Start Menu works; this is good news for Nuhi, Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System] "ValidateAdminCodeSignatures"=dword:00000000 Applying halving algorithm
  20. T

    Integrating specific REG breaks Start Menu and Search (LTSC 2021 IoT)

    Suspect vindicated; issue persists with add.reg even with that entry removed.
Back
Top