If you value privacy and gaming, you have found no better thread.
Background/Context:
Suppose there was one ring to rule them all that is to same one version of LTSC 2021 that configured heavily on Security, Privacy and Performance and worked with most games and expected retail function; sort of a pipe dream because just reading it and understanding Windows 10, this is no easy task; like a balance scale typically every action tips the scale or every security function is another step backwards in function. Suppose this was mostly solved. That's kinda what this release is about.
Why LTSC 2021 IoT because it is being serviced until January 13, 2032. Some Windows 11 early builds are arguably better, but their servicing has already ended. Performance, Security, Privacy and Retail function have always been my targets. One new target is serviceability (Windows Update). The Component Store and Component-Based Servicing (CBS) is not evil. For you just think of it as an organization method making sure critical files are never lost. You remove a feature, the component store says ok, but some of the files for that feature are still being used by another feature so I'll keep those, but remove the feature you wanted removed. This is basically every interaction between dism and the component store. It does it's main job very well, but sometimes too well holding onto too many versions of files. This is what the resetbase command is for. Remove or greatly strip the component store and your image becomes serviceable. This extends beyond windows update, you are basically making your system UN-adaptable hoping no circumstances or particular combination, which could be rectified with a working component store, doesn't rear its ugly head particularly once your system is configured how you like it. And some people, like me, were very good at giving you such images that largely worked without flaw and it was beautiful in the sense of how many fewer files the system needed. But such images are fundamentally flawed - this should be clear now as the component store is the foundation that Windows is built upon. Let's make it even clearer. The Component Store's job is to keep Windows File. Why is it in NTlite that you have to have the service stack compatibility option to enable deep removal; because the component store's job is to keep Windows Files and the component store is the servicing stack that is WinSXS and dism are the service stack. Now you don't need NTlite to service an image, but what NTlite does is effectively deconstructs large packages into manageable smaller chunks thus offering much greater selection for removal; otherwise you have to remove the big chunk which sometimes isn't even feasible. For I think there's a package called WindowsFoundation. Basically, Microsoft's way of giving you the middle finger except for the saving grace of NTlite.
So now the question is How small of an image can you create if you keep the component store;
well my install.esd is 3.52 GB, but it is updated and has all the appx dependencies, and now the Microsoft Store and a few grand master scripts and reg files.
In the spirit of adapting some tweaks found on the NTlite gamer thread, I thought it only fair but then I'm like it would so incomplete without my firstrun script so I added it back in for all to see and use. And it makes all the difference.
Just a reminder boot.wim should never be trimmed because its whole purpose is to ensure it can install windows via the windows image (install.wim or install.esd). Trimming it is therefore moronic especially in lieu of distribution.
Please note, notepad4 AVX2 edition is installed to program files and replaces notepad as default; the evil old notepad is gone. Notepad++ is still superior, but not for every day notepad needs is all. So when you run notepad, notepad4 runs.
Instructions:
So attached one of my presets focusing on Serviceable, Performance, Security, Privacy and Retail. This one includes the Microsoft Store and thus Xbox Stuff as well Now Fixed. So you get yourself a copy of LTSC 2021, I use the IoT version for serviceability, but any version of LTSC 2021 will work. I am going to be meticulous with my instructions because the order you set up the system has an impact on the system's final functionality.
BTW, throughout these steps don't be a goomba and remove boot (PE) from the image and only keep the setup; keep both.
1. Mount your LTSC 2021 iso with NTlite; when it doubt, you can trust massgrave.dev (Advantageous and not just for your ISO needs
2. Download this. Extract root folder anywhere.
3. Apply the Master preset, on the latest ntlite; set max threads on NTlite to 6 for greater stability.
Content Delivery Manager and Spotlight are deliberately enabled; disable these if you know for sure you don't want them.
4. Among-st the things it will complain of missing updates and drivers.
The drivers I don't give you because it is system specific.
The updates you downloaded when you clicked on "this" above.
Just go to the updates tab in Ntlite, select all, delete and point the the directory of the updates I provided.
Which includes "almost" all dependencies for APPX, Microsoft Store and XBOX.
Put more specifically, Bing Wallpaper and Sudoku Classic both successfully install from Microsoft Store.
Or even more specifically:
I have not tested the Xbox stuff, but if it doesn't work out of the box, should be simple enough to fix.
You'll see I have taken extra care to make sure Xbox Stuff is not removed.
5. Hopefully NTlite doesn't crash on ya, and finishes.
6. Now remount LTSC 2021, should only have an IoT mount option now, and not standard enterprise.
7. Once it is done mounting, you run p.cmd as administrator found in the master download. It is very fast.
8. Then you apply the Finalize preset immediately thereafter. Yes, I have simplified things and amended p.cmd so it doesn't run our final setup
parade (previously cause very subtle annoying component store issues Now Fixed. Annoying because dism shouldn't cause component store
issues but alas even if you limit NTlite to dism, and use dism after somehow you can still have component store issues. Basically this is
another middle finger from Microsoft and more specifically from the engineering servicing team who did the bare minimum.
I have it set to ESD, but you can change it to wim if you like.
9. Now if you used the massgrave LTSC 2021 iso, then you can just download my unstripped boot.wim with 2023 updated boot manager here .
OR
10. Otherwise, you basically create a new edit in NTlite, use the same iso and apply the same updates BUT WITHOUT THE COMPONENT REMOVALS, and WITH UPDATED BOOT MANAGER 2023. This meant require two runs simply because NTlite cannot update the manager at the same time as integrating updates; has to do it after the updates; a good safety precaution - great programming.
11. So by now, you have the final install.wim or install.esd and boot.wim in the sources folder
12. Now you need the attached autounattend.xml in the root folder and the $OEM$ stuff in the sources folder.
Oh and there's a nice additions this time $OEM$.
13. Now that you have copied that $OEM$ into the sources folder, go ahead and produce an ISO with NTLite.
14. Now inside $OEM$ -> $1 > USERS -> Public -> Desktop -> Software -> Small Utilities, use Rufus 4.4; never any problem with it.
So keep all settings default, refuse online update, pick ISO, and burn without any of the extra popup options.
Please note Windows Explorer is unstable on the first boot; that is frequently graphically glitches or appears to freeze eventually on first boot.
You can try Ctrl-Shift-Esc or Ctrl-Shift-Win-B (sometimes these help). Once you update your GPU driver and restart, there is no problem.
You obviously have to provide your own valid key or activation; I'll just say this image is HWID compatible.
The protected files (where unspecified) are geared towards preserving diagnosis, hyper, active directory and .net 3.5.
The autounattend can include drivers both for initial setup (network, storage, touchpad) and for Stage 2 (Device Installation\Configuration).
BUT be weary, it installs these no matter what, so if you have drivers for different systems in there, it install them all.
The main draw of this particular release besides privacy and gaming, is that it is serviceable; works with Windows Update.
However, you'll find for cumulative updates that you have to use:
Safemode.reg, firstrun.cmd and "Remove Reinstalls" from NTlite.
You need a license to fully apply the preset.
The username of this release is: Awesome
This is critical information because it is not automatically populated upon boot for privacy reasons.
Post-Setup (Follow precisely in provided order):
15. Easiest way to add a password is once you are logged in, alt-control-delete.
This makes it a little harder to hack into your system with administrative rights so why not start with that huh.
16. Connect to your wireless or wired internet
17. Run HWID activator (not provided as per NTlite rules)
18. Run RootCertificateUpdater
19. Click in the search bar and pick email and accounts.
Add your outlook "MS starve" app only account.
Verify it however you want.
20. Now start Microsoft Store.
21. Install Bing Wallpaper and Sudoku Classic! (riz).
22. Check for updates, install all updates.
23. If you have AMD system or Nvidia or Intel, you install those graphic and chipset drivers after restart.
24. There's Stuff in the getting started folder to literally get you started.
25. Have a look at the other files in: C:\Files
Please OVERWRITE any previously downloaded file with the direct attached masters below.
IF you fail to do this, you will have problems.
Please note; This configuration is not for you if you have any reliance on File-Sharing.
This is because of the release goals: Serviceable, Performance, Security, Privacy and Retail (minus File-Sharing)
Much Time went into making sure all the tweaks and settings work together.
All attached files have been found to work with to work with Bing Wallpaper and Sudoku Classic! (riz).
Background/Context:
Suppose there was one ring to rule them all that is to same one version of LTSC 2021 that configured heavily on Security, Privacy and Performance and worked with most games and expected retail function; sort of a pipe dream because just reading it and understanding Windows 10, this is no easy task; like a balance scale typically every action tips the scale or every security function is another step backwards in function. Suppose this was mostly solved. That's kinda what this release is about.
Why LTSC 2021 IoT because it is being serviced until January 13, 2032. Some Windows 11 early builds are arguably better, but their servicing has already ended. Performance, Security, Privacy and Retail function have always been my targets. One new target is serviceability (Windows Update). The Component Store and Component-Based Servicing (CBS) is not evil. For you just think of it as an organization method making sure critical files are never lost. You remove a feature, the component store says ok, but some of the files for that feature are still being used by another feature so I'll keep those, but remove the feature you wanted removed. This is basically every interaction between dism and the component store. It does it's main job very well, but sometimes too well holding onto too many versions of files. This is what the resetbase command is for. Remove or greatly strip the component store and your image becomes serviceable. This extends beyond windows update, you are basically making your system UN-adaptable hoping no circumstances or particular combination, which could be rectified with a working component store, doesn't rear its ugly head particularly once your system is configured how you like it. And some people, like me, were very good at giving you such images that largely worked without flaw and it was beautiful in the sense of how many fewer files the system needed. But such images are fundamentally flawed - this should be clear now as the component store is the foundation that Windows is built upon. Let's make it even clearer. The Component Store's job is to keep Windows File. Why is it in NTlite that you have to have the service stack compatibility option to enable deep removal; because the component store's job is to keep Windows Files and the component store is the servicing stack that is WinSXS and dism are the service stack. Now you don't need NTlite to service an image, but what NTlite does is effectively deconstructs large packages into manageable smaller chunks thus offering much greater selection for removal; otherwise you have to remove the big chunk which sometimes isn't even feasible. For I think there's a package called WindowsFoundation. Basically, Microsoft's way of giving you the middle finger except for the saving grace of NTlite.
So now the question is How small of an image can you create if you keep the component store;
well my install.esd is 3.52 GB, but it is updated and has all the appx dependencies, and now the Microsoft Store and a few grand master scripts and reg files.
In the spirit of adapting some tweaks found on the NTlite gamer thread, I thought it only fair but then I'm like it would so incomplete without my firstrun script so I added it back in for all to see and use. And it makes all the difference.
Just a reminder boot.wim should never be trimmed because its whole purpose is to ensure it can install windows via the windows image (install.wim or install.esd). Trimming it is therefore moronic especially in lieu of distribution.
Please note, notepad4 AVX2 edition is installed to program files and replaces notepad as default; the evil old notepad is gone. Notepad++ is still superior, but not for every day notepad needs is all. So when you run notepad, notepad4 runs.
Instructions:
So attached one of my presets focusing on Serviceable, Performance, Security, Privacy and Retail. This one includes the Microsoft Store and thus Xbox Stuff as well Now Fixed. So you get yourself a copy of LTSC 2021, I use the IoT version for serviceability, but any version of LTSC 2021 will work. I am going to be meticulous with my instructions because the order you set up the system has an impact on the system's final functionality.
BTW, throughout these steps don't be a goomba and remove boot (PE) from the image and only keep the setup; keep both.
1. Mount your LTSC 2021 iso with NTlite; when it doubt, you can trust massgrave.dev (Advantageous and not just for your ISO needs
2. Download this. Extract root folder anywhere.
3. Apply the Master preset, on the latest ntlite; set max threads on NTlite to 6 for greater stability.
Content Delivery Manager and Spotlight are deliberately enabled; disable these if you know for sure you don't want them.
4. Among-st the things it will complain of missing updates and drivers.
The drivers I don't give you because it is system specific.
The updates you downloaded when you clicked on "this" above.
Just go to the updates tab in Ntlite, select all, delete and point the the directory of the updates I provided.
Which includes "almost" all dependencies for APPX, Microsoft Store and XBOX.
Put more specifically, Bing Wallpaper and Sudoku Classic both successfully install from Microsoft Store.
Or even more specifically:
Code:
"C:\Users\Awesome\Updates\Updates\Microsoft.MPEG2VideoExtension_1.2.13.0_neutral_~_8wekyb3d8bbwe.AppxBundle"
"C:\Users\Awesome\Updates\Updates\Microsoft.NET.Native.Framework.1.3_1.3.24211.0_x64__8wekyb3d8bbwe.Appx"
"C:\Users\Awesome\Updates\Updates\Microsoft.NET.Native.Framework.1.3_1.3.24211.0_x86__8wekyb3d8bbwe.Appx"
"C:\Users\Awesome\Updates\Updates\Microsoft.NET.Native.Framework.1.6_1.6.27413.0_x64__8wekyb3d8bbwe.Appx"
"C:\Users\Awesome\Updates\Updates\Microsoft.NET.Native.Framework.1.6_1.6.27413.0_x86__8wekyb3d8bbwe.Appx"
"C:\Users\Awesome\Updates\Updates\Microsoft.NET.Native.Framework.1.7_1.7.27413.0_x64__8wekyb3d8bbwe.Appx"
"C:\Users\Awesome\Updates\Updates\Microsoft.NET.Native.Framework.1.7_1.7.27413.0_x86__8wekyb3d8bbwe.Appx"
"C:\Users\Awesome\Updates\Updates\Microsoft.NET.Native.Framework.2.0_2.0.27427.0_x64__8wekyb3d8bbwe.Appx"
"C:\Users\Awesome\Updates\Updates\Microsoft.NET.Native.Framework.2.0_2.0.27427.0_x86__8wekyb3d8bbwe.Appx"
"C:\Users\Awesome\Updates\Updates\Microsoft.NET.Native.Framework.2.1_2.1.27427.0_x64__8wekyb3d8bbwe.Appx"
"C:\Users\Awesome\Updates\Updates\Microsoft.NET.Native.Framework.2.1_2.1.27427.0_x86__8wekyb3d8bbwe.Appx"
"C:\Users\Awesome\Updates\Updates\Microsoft.NET.Native.Framework.2.2_2.2.29512.0_x64__8wekyb3d8bbwe.Appx"
"C:\Users\Awesome\Updates\Updates\Microsoft.NET.Native.Framework.2.2_2.2.29512.0_x86__8wekyb3d8bbwe.Appx"
"C:\Users\Awesome\Updates\Updates\Microsoft.NET.Native.Runtime.1.3_1.3.23901.0_x64__8wekyb3d8bbwe.Appx"
"C:\Users\Awesome\Updates\Updates\Microsoft.NET.Native.Runtime.1.3_1.3.23901.0_x86__8wekyb3d8bbwe.Appx"
"C:\Users\Awesome\Updates\Updates\Microsoft.NET.Native.Runtime.1.6_1.6.24903.0_x64__8wekyb3d8bbwe.Appx"
"C:\Users\Awesome\Updates\Updates\Microsoft.NET.Native.Runtime.1.6_1.6.24903.0_x86__8wekyb3d8bbwe.Appx"
"C:\Users\Awesome\Updates\Updates\Microsoft.NET.Native.Runtime.1.7_1.7.27422.0_x64__8wekyb3d8bbwe.Appx"
"C:\Users\Awesome\Updates\Updates\Microsoft.NET.Native.Runtime.1.7_1.7.27422.0_x86__8wekyb3d8bbwe.Appx"
"C:\Users\Awesome\Updates\Updates\Microsoft.NET.Native.Runtime.2.0_2.0.25709.0_x64__8wekyb3d8bbwe.Appx"
"C:\Users\Awesome\Updates\Updates\Microsoft.NET.Native.Runtime.2.0_2.0.25709.0_x86__8wekyb3d8bbwe.Appx"
"C:\Users\Awesome\Updates\Updates\Microsoft.NET.Native.Runtime.2.1_2.1.26424.0_x64__8wekyb3d8bbwe.Appx"
"C:\Users\Awesome\Updates\Updates\Microsoft.NET.Native.Runtime.2.1_2.1.26424.0_x86__8wekyb3d8bbwe.Appx"
"C:\Users\Awesome\Updates\Updates\Microsoft.NET.Native.Runtime.2.2_2.2.28604.0_x64__8wekyb3d8bbwe.Appx"
"C:\Users\Awesome\Updates\Updates\Microsoft.NET.Native.Runtime.2.2_2.2.28604.0_x86__8wekyb3d8bbwe.Appx"
"C:\Users\Awesome\Updates\Updates\Microsoft.RawImageExtension_2.4.24.0_neutral_~_8wekyb3d8bbwe.AppxBundle"
"C:\Users\Awesome\Updates\Updates\Microsoft.Services.Store.Engagement_10.0.23012.0_x64__8wekyb3d8bbwe.Appx"
"C:\Users\Awesome\Updates\Updates\Microsoft.StorePurchaseApp_22607.1401.2.0_neutral_~_8wekyb3d8bbwe.Msixbundle"
"C:\Users\Awesome\Updates\Updates\Microsoft.UI.Xaml.2.3_2.32002.13001.0_x64__8wekyb3d8bbwe.Appx"
"C:\Users\Awesome\Updates\Updates\Microsoft.UI.Xaml.2.3_2.32002.13001.0_x86__8wekyb3d8bbwe.Appx"
"C:\Users\Awesome\Updates\Updates\Microsoft.UI.Xaml.2.4_2.42007.9001.0_x64__8wekyb3d8bbwe.Appx"
"C:\Users\Awesome\Updates\Updates\Microsoft.UI.Xaml.2.4_2.42007.9001.0_x86__8wekyb3d8bbwe.Appx"
"C:\Users\Awesome\Updates\Updates\Microsoft.UI.Xaml.2.5_2.52012.2002.0_x64__8wekyb3d8bbwe.Appx"
"C:\Users\Awesome\Updates\Updates\Microsoft.UI.Xaml.2.5_2.52012.2002.0_x86__8wekyb3d8bbwe.Appx"
"C:\Users\Awesome\Updates\Updates\Microsoft.UI.Xaml.2.6_2.62112.3002.0_x64__8wekyb3d8bbwe.Appx"
"C:\Users\Awesome\Updates\Updates\Microsoft.UI.Xaml.2.6_2.62112.3002.0_x86__8wekyb3d8bbwe.Appx"
"C:\Users\Awesome\Updates\Updates\Microsoft.UI.Xaml.2.7.x64.appx"
"C:\Users\Awesome\Updates\Updates\Microsoft.UI.Xaml.2.7.x86.appx"
"C:\Users\Awesome\Updates\Updates\Microsoft.UI.Xaml.2.8_8.2501.31001.0_x64__8wekyb3d8bbwe.Appx"
"C:\Users\Awesome\Updates\Updates\Microsoft.UI.Xaml.2.8_8.2501.31001.0_x86__8wekyb3d8bbwe.Appx"
"C:\Users\Awesome\Updates\Updates\Microsoft.VCLibs.140.00.UWPDesktop_14.0.33728.0_x64__8wekyb3d8bbwe.Appx"
"C:\Users\Awesome\Updates\Updates\Microsoft.VCLibs.140.00.UWPDesktop_14.0.33728.0_x86__8wekyb3d8bbwe.Appx"
"C:\Users\Awesome\Updates\Updates\Microsoft.VCLibs.140.00_14.0.33519.0_x64__8wekyb3d8bbwe.Appx"
"C:\Users\Awesome\Updates\Updates\Microsoft.VCLibs.140.00_14.0.33519.0_x86__8wekyb3d8bbwe.Appx"
"C:\Users\Awesome\Updates\Updates\Microsoft.VP9VideoExtensions_1.2.20.0_neutral_~_8wekyb3d8bbwe.AppxBundle"
"C:\Users\Awesome\Updates\Updates\Microsoft.WebpImageExtension_1.2.31.0_neutral_~_8wekyb3d8bbwe.AppxBundle"
"C:\Users\Awesome\Updates\Updates\Microsoft.WindowsAppRuntime.1.8_8000.946.1701.0_x64__8wekyb3d8bbwe.Msix"
"C:\Users\Awesome\Updates\Updates\Microsoft.WindowsAppRuntime.1.8_8000.946.1701.0_x86__8wekyb3d8bbwe.Msix"
"C:\Users\Awesome\Updates\Updates\Microsoft.WindowsAppRuntime.2_2.4.0.0_x64__8wekyb3d8bbwe.Msix"
"C:\Users\Awesome\Updates\Updates\Microsoft.WindowsAppRuntime.2_2.4.0.0_x86__8wekyb3d8bbwe.Msix"
"C:\Users\Awesome\Updates\Updates\Microsoft.WindowsStore_12107.1001.15.0_neutral_~_8wekyb3d8bbwe.AppxBundle"
"C:\Users\Awesome\Updates\Updates\Microsoft.WindowsTerminal_1.24.11911.0_8wekyb3d8bbwe_v1.24.11911.0.msixbundle"
"C:\Users\Awesome\Updates\Updates\Microsoft.Xbox.TCUI_1.24.10001.0_neutral_~_8wekyb3d8bbwe.AppxBundle"
"C:\Users\Awesome\Updates\Updates\Microsoft.XboxApp_48.104.4001.0_neutral_~_8wekyb3d8bbwe.AppxBundle"
"C:\Users\Awesome\Updates\Updates\Microsoft.XboxIdentityProvider_12.130.16001.0_neutral_~_8wekyb3d8bbwe.AppxBundle"
"C:\Users\Awesome\Updates\Updates\SSU-19041.6449-x64.cab"
"C:\Users\Awesome\Updates\Updates\updateplatform.amd64.exe"
"C:\Users\Awesome\Updates\Updates\windows10.0-kb5011048-x64.cab"
"C:\Users\Awesome\Updates\Updates\Windows10.0-KB5066791-x64.cab"
"C:\Users\Awesome\Updates\Updates\windows10.0-kb5099550-x64.cab"
"C:\Users\Awesome\Updates\Updates\Microsoft.DesktopAppInstaller_2021.1207.203.0_neutral_~_8wekyb3d8bbwe.AppxBundle"
"C:\Users\Awesome\Updates\Updates\Microsoft.HEIFImageExtension_1.2.48.0_neutral_~_8wekyb3d8bbwe.AppxBundle"
"C:\Users\Awesome\Updates\Updates\Microsoft.HEVCVideoExtension_2.4.45.0_neutral_~_8wekyb3d8bbwe.AppxBundle"You'll see I have taken extra care to make sure Xbox Stuff is not removed.
5. Hopefully NTlite doesn't crash on ya, and finishes.
6. Now remount LTSC 2021, should only have an IoT mount option now, and not standard enterprise.
7. Once it is done mounting, you run p.cmd as administrator found in the master download. It is very fast.
8. Then you apply the Finalize preset immediately thereafter. Yes, I have simplified things and amended p.cmd so it doesn't run our final setup
parade (previously cause very subtle annoying component store issues Now Fixed. Annoying because dism shouldn't cause component store
issues but alas even if you limit NTlite to dism, and use dism after somehow you can still have component store issues. Basically this is
another middle finger from Microsoft and more specifically from the engineering servicing team who did the bare minimum.
I have it set to ESD, but you can change it to wim if you like.
9. Now if you used the massgrave LTSC 2021 iso, then you can just download my unstripped boot.wim with 2023 updated boot manager here .
OR
10. Otherwise, you basically create a new edit in NTlite, use the same iso and apply the same updates BUT WITHOUT THE COMPONENT REMOVALS, and WITH UPDATED BOOT MANAGER 2023. This meant require two runs simply because NTlite cannot update the manager at the same time as integrating updates; has to do it after the updates; a good safety precaution - great programming.
11. So by now, you have the final install.wim or install.esd and boot.wim in the sources folder
12. Now you need the attached autounattend.xml in the root folder and the $OEM$ stuff in the sources folder.
Oh and there's a nice additions this time $OEM$.
13. Now that you have copied that $OEM$ into the sources folder, go ahead and produce an ISO with NTLite.
14. Now inside $OEM$ -> $1 > USERS -> Public -> Desktop -> Software -> Small Utilities, use Rufus 4.4; never any problem with it.
So keep all settings default, refuse online update, pick ISO, and burn without any of the extra popup options.
Please note Windows Explorer is unstable on the first boot; that is frequently graphically glitches or appears to freeze eventually on first boot.
You can try Ctrl-Shift-Esc or Ctrl-Shift-Win-B (sometimes these help). Once you update your GPU driver and restart, there is no problem.
You obviously have to provide your own valid key or activation; I'll just say this image is HWID compatible.
The protected files (where unspecified) are geared towards preserving diagnosis, hyper, active directory and .net 3.5.
The autounattend can include drivers both for initial setup (network, storage, touchpad) and for Stage 2 (Device Installation\Configuration).
BUT be weary, it installs these no matter what, so if you have drivers for different systems in there, it install them all.
The main draw of this particular release besides privacy and gaming, is that it is serviceable; works with Windows Update.
However, you'll find for cumulative updates that you have to use:
Safemode.reg, firstrun.cmd and "Remove Reinstalls" from NTlite.
You need a license to fully apply the preset.
The username of this release is: Awesome
This is critical information because it is not automatically populated upon boot for privacy reasons.
Post-Setup (Follow precisely in provided order):
15. Easiest way to add a password is once you are logged in, alt-control-delete.
This makes it a little harder to hack into your system with administrative rights so why not start with that huh.
16. Connect to your wireless or wired internet
17. Run HWID activator (not provided as per NTlite rules)
18. Run RootCertificateUpdater
19. Click in the search bar and pick email and accounts.
Add your outlook "MS starve" app only account.
Verify it however you want.
20. Now start Microsoft Store.
21. Install Bing Wallpaper and Sudoku Classic! (riz).
22. Check for updates, install all updates.
23. If you have AMD system or Nvidia or Intel, you install those graphic and chipset drivers after restart.
24. There's Stuff in the getting started folder to literally get you started.
25. Have a look at the other files in: C:\Files
Please OVERWRITE any previously downloaded file with the direct attached masters below.
IF you fail to do this, you will have problems.
Please note; This configuration is not for you if you have any reliance on File-Sharing.
This is because of the release goals: Serviceable, Performance, Security, Privacy and Retail (minus File-Sharing)
Much Time went into making sure all the tweaks and settings work together.
All attached files have been found to work with to work with Bing Wallpaper and Sudoku Classic! (riz).
Last edited: