Slimdown10 – turn Windows 10 22H2 or LTSC 2021 into classic/legacy Windows

You need to login to view this posts content.

 

Great.

I reworked some options in the script, so as not to uninstall Edge, just for testing...

Look at the "Additional Configuration (line 147)" section and choose your options.

Unzip it to the script folder and run SD11v202_4.1_Start.cmd as administrator.

Edit. IT DIDN'T WORK... I'M REVIEWING THE SCRIPT...

 

You need to login to view this posts content.

 

The script above didn't work...

I'll go over the steps again...

 

Please check the following
1. New incognito tab
2. Startup page and its custom url
3. Home button and its custom url
4. New tab with search bar and favourite sites

 

Try this new version.
It seems to be working fine.
I haven't installed it in VirtualBox yet...

Test it and see if it works for you!

SD11v202_4.4.rar
password: mdl2024

Updated with new hfixes_all.txt

 

I am running the script and it seems like you have integrated latest updates in it too. That's great brother, will test and reply shortly

 

@SunLion bro plz check the attached log file after running the script, I am testing the same in Virtual machine now

 

The only problem which I found until now that windows search is not working. Also the integrated updates are for windows 10 I think as system searching and downloading latest updates

 

The script modifies the Windows search. I did not change that.

If you use OpenShell you will not need the Windows search.

The updates are for Windows 11.

I installed it in VirtualBox and everything is fine.

 

Even the search?
Have you checked my logs attached above?

 

Sorry, I forgot to attach the new hfixes_all.txt.

This one has the correct Windows 11 updates.

Put this new one in the hotfixies folder and replace the old one.

 

Sorry, I'm not following I did it once on Windows 10, does it work on Windows 11, which specific build of 11 to integrate, does it have the Windows 7 menu?

 

The original version has three versions:

About Windows 7 menu.

In the settings there are two options:
set ReplaceStartMenuWithOpenShell=0
set OpenShellLooksLikeWin7=0

Change it to 1 and see if it works!

 

Do these options change in this SD11v202_4.4 script?

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

@SunLion, any idea why installing a slimmed-down Windows 10 IoT LTSC 2021 on a VM might hang forever at the "Just a moment..." screen? I'm installing on a QEMU/KVM virtual machine through virt-manager on a Linux host (default virtualized hardware, passing through 8192 MiB of RAM; passing through 3 CPU cores or all 4 doesn't make a difference).

Installing the unmodified ISO (en-us_windows_10_iot_enterprise_ltsc_2021_x64_dvd_257ad90f.iso, SHA256 of a0334f31ea7a3e6932b9ad7206608248f0bd40698bfb8fc65f14fc5e4976c160) on the same VM setup works fine, and I actually ran the Slimdown10 script from inside of that VM.

I'm using your most recent SD10v202_10.2 version from a few days ago, and the SD10v202_10.2_Start.cmd script runs fine until the wimlib info line (it breaks there, but that should be okay as you mentioned earlier).

My config modifications from default are as follows:

Code:

set ReplaceStartMenuWithOpenShell=1
set DisableInternetConnectionChecking=1
set DisableDefender=0
set EnableStore=1
set IncludeWindowsRegulatedPackagesInLTSC=1
set CreateISO=1
set DisableF1ToGetHelp=0
set DisableAnimations=0
set DisableSoundsAndBeeps=0

I've asked it to install .NET 3.5, clean up the ISO, and integrate DaRT. I've tried your version from July 16th without cleanup or DaRT, and the results were the same.

I'm going to try running the script with default options to see if that makes a difference, but I figured I'd post this and see what happens. On the off-chance that the issue is specific to QEMU/KVM or my host setup, would you mind testing these options on your typical Virtualbox test setup?

 

You need to login to view this posts content.

 

Yes, I'm running the script(s) in a VM on QEMU/KVM running the unmodified Windows 10 IoT LTSC 2021.

I now see some DISM failures in the log that I didn't catch before, so if a VM would cause those, that's good to know. Is it also possible that I didn't disable Windows Defender well enough (turned off realtime protection only)?

My most recent attempt used that version (SD10v202_10.2), but I accidentally clobbered my log file when I started my current test (testing a default config).

I lost my log from SD10v202_10.2, but I do still have a log file from an earlier attempt on a slightly earlier version (SD10_v2_02_6 from July 16th or so). This attempt did not integrate DaRT or do cleanup, and it used a slightly different config, due to fewer options in SD10_v2_02_6:

Code:

set ReplaceStartMenuWithOpenShell=1
set DisableInternetConnectionChecking=1
set DisableDefender=0
set EnableStore=1
set IncludeWindowsRegulatedPackagesInLTSC=1
set CreateISO=1

I don't think I can attach the log as a file as a low-post-count member, but I'll post some interesting sections in spoilers below. It turns out there WERE some non-interrupting errors in it that I didn't expect, and they might indeed be responsible for the failure:

Spoiler: DISM Error: 0x800f0806

============================================================
Cleaning up the WinSxS Folder
============================================================


Deployment Image Servicing and Management tool
Version: 10.0.19041.3636

Image Version: 10.0.19044.4651


Error: 0x800f0806

The operation could not be completed due to pending operations.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Spoiler: DISM Error: 2

============================================================
Adding default app associations settings...
============================================================


Deployment Image Servicing and Management tool
Version: 10.0.19041.3636

Image Version: 10.0.19044.4651


Error: 2

Could not save C:\Users\SoForgetful\Desktop\Slimdown10\hotfixes\AppAssociations.xml as the OEM default assocations file in the image.
For more information, refer to the help.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Spoiler: Get-WInfo Error: 47

###############################################
Get-WInfo
###############################################



[ERROR] Can't open "C:\Users\SoForgetful\Desktop\Slimdown10\DVD\sources\install.wim" read-only: No such file or directory
ERROR: Exiting with error code 47:
Failed to open a file.

Spoiler: Final Lines

Stale mount entry pointing to C:\Users\SoForgetful\Desktop\Slimdown10\mount removed
Scanning drive C for stale files
The operation completed successfully.
The syntax of the command is incorrect.
The system cannot find the path specified.
The system cannot find the path specified.

I no longer have that particular dism.log to dig any deeper, but I can check it if my current attempt fails the same way.