LastOS AIO (WIP)

The NRO trick no longer works (according to some forums) but the TPM/RAM etc bypass being part of the AutoUnattend I will put in, wont hurt to anyway. Thanks

 

@Glenn, you might find this interesting -
Slimdown10 – turn Windows 10 22H2 or LTSC 2021 into classic/legacy Windows
- actively being developed.

 

And here's a note about the latest Windows 10 update:
Windows 10, version 22H2 Release Preview: 19045.3513 (KB5030300) now live:
Info: https://blogs.windows.com/windows-insider/2023/09/13/releasing-windows-10-19045-3513/

The above info and the below links were found here:

Code:

Name: 19045.3513_x64_Release_Preview.zip
Size: 811292714 bytes (773 MiB)
CRC32: E69C124B
CRC64: A6077A774ED9C99E
SHA256: 31fe12455b3544374fe46ec49752b27ba4958ab281618128a7b6c46bda3e6f05
SHA1: 69a1c064df7490cdc278ba2aa9295d11c74be20e
BLAKE2sp: 26513dca153b5429a83eea4288fc5c1b7388559ea4dca3f999b5aee35ac977f4

Content:

Code:

223fae168efdb5158daa688e929135917b06eb89 *SSU-19041.3505-x64.cab
d2721bd1ef215f013063c416233e2343b93ab8c1 *Windows10.0-KB5015684-x64.cab
f9e328320da9157244edc1b3ac1386f03bab9f56 *Windows10.0-KB5030300-x64.cab
8d1880d95f920fc8a4c2d96ca8d3b44f3e044581 *windows10.0-kb5027389-x64.cab
8750fa3c7e42f95fc70d36ee33526009a431dd24 *windows10.0-kb5028311-x64.cab

Code:

Name: 19045.3513_x86_Release_Preview.zip
Size: 452467862 bytes (431 MiB)
CRC32: 91878A7C
CRC64: E75EC31025BBC297
SHA256: 87bbe9720cc00c775e949363e47d8f53e03a5dd53979d47a8a8cc8607f39a10a
SHA1: e14f90317f9c2ccb8d2fb8a5a5a798d819e12b29
BLAKE2sp: fae7d63717f4be260c947226a713f33965e6ee057e4cc707e5d24c639e6bc5a0

Content:

Code:

d0f03ddd7276c87089cce0156f2ddc295aadb9d0 *SSU-19041.3505-x86.cab
3734a3f6f4143b645788cc77154f6288c8054dd5 *Windows10.0-KB5015684-x86.cab
f3f8daa7b357e389b1362174393c3c1bb4f44d84 *Windows10.0-KB5030300-x86.cab
24c75bece6b8f3714c5f0a6d5e3579d7baf143c7 *windows10.0-kb5027389-x86.cab
e9f7f60777203c88cdf870666e9bbeb1b2223d9f *windows10.0-kb5028311-x86.cab

I asked:

and aboddi1406 replied here:

 

@Glenn, here's a summary of a way to install the latest (19044.3324) IoT LTSC [which obviously will still need your and @Trouba's massaging to add all of the LastOS goodness that it deserves] -- [info from here]

1. download the Enterprise 2021 LTSC ISO: https://forums.mydigitallife.net/threads/discussion-windows-10-enterprise-iot-enterprise-n-ltsc-2021.84509/page-166#post-1794948

2. run this in an elevated cmd:

Code:

reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v EditionID /d EnterpriseS /f

3. Mount/Open the Enterprise 2021 LTSC ISO in explorer/Unpack the ISO to a folder and run setup.exe

Spoiler

4. When the upgrade is finished you can switch to IoT Enterprise 2021 LTSC by running this in an elevated cmd:

Code:

slmgr -ipk QPM6N-7J2WJ-P88HH-P3YRH-YY74H

5. Now you can run a KMS solution like KMS_VL_ALL and activate IoT Enterprise 2021 LTSC.

Spoiler

 

This is WAY beyond my capabilities, and I'm sure that the existing methods you already use have similar functions, but I hadn't seen this before, so I'm just passing it along.

Optimize-Offline Guide - Windows Debloating Tool, Windows 1803, 1903, 19H2, 1909, 20H1 and LTSC 2019

On github, latest release

 

I've noticed a sysprep of any windows 10 Pro takes a good 20 to 30 minutes to "Getting Things Ready" where it detects hardware on first boot. Not sure why, but if anyone has the solution to this, it'll save me a lot of trial and error making new VMs and wims to figure it out... If it's still this slow, I don't think I'll bother releasing it as nobody wants to waste that much time waiting. I'd just release a standard Windows 10 with no integrated updates. Honestly the same PC VM'S are at the desktop in 3 minutes for LTSC and Win 11 Pro. It's just weird.

-EDIT-

I've tried x86 and x64 and both are the same. I am going to try to capture a fresh install with no changes at all and see if it still installs extra slow - will reply soon.

-EDIT-

Yes, a fresh captured install works fast again, I'll narrow down the issues and share the results so we don't have to figure this out ever again.

It's not VMClean, I am guessing it's the Updates, but still searching.

Pretty sure it's much slower after I run the tweaks, service tweaks and disable defender - I'll narrow down some more. I've not even tried to do the updates yet and got it to slow down, so it's gonna be fixable at least.

I am 100% sure it's the tweaks, not the service tweaks, I'll find the actual problematic one now

It's the LastOS tweaks being applied, I'll check to see if it's the local machine ones or the default user ones.

It's in the Local machine tweaks

I've rebuild the sysprep for windows 10 pro to not have the reg tweaks, so should be fine now.

-EDIT-

Yep, tested as fixed, takes less than 2 minutes to detect hardware and continue setup - instead of 20 to 30 minutes (longer on slow machines). So keep this in mind if you ever try to apply to many tweaks to a sysprep, it may slow down the installation (for no obvious reason).

 

I've managed to make my AIO with Win 11 23H2 Release Preview (No Watermark), I am still tinkering away with things. The new Paint with Layers, background removal and generative AI is really making Paint much more usable/useful. The Copilot is very useful, just not fast. I am looking forward to the better file explorer, but that's not yet available in any stable way. The new Settings Home page is so much better - actually a pleasure to use it now.

I don't think their is a reason to continue using 22H2 as it can all be hidden/disabled or ignored without much HDD space or resource usage.

I am just really looking forward to the day someone makes a new AI face detection photo manager so I can finally update from using Picasa and WLPG, all the existing ones are slow, crash, lack features and are WAY worse than those two.

 

I've modded my Copy boot.wim to WinRE.wim as an option on the HDD, it will detect x:\sources\boot.wim and if that doesn't exist (as with AIO) it'll use the X:\SavePE_10_x64.wim, this will allow you to remove the default WinRE.wim from the sysprep saving 400 to 500mb of space and then use our LastOS PE to recover/backup/restore the installed PC without needing a USB to do so (not ideal for Schools etc, but you can just not pick it from ssWPI and use the USB to boot from like normal in this case).

I made ssWPI run post install if it detects a pre selection from the PE it will install them, else it'll just run ssWPI (so you can pick items or just quit it) - As I have remove Chrome, Java etc I figured it's best to do it this way so I remember after a install that I need to install them again