Is enabling windows store something you have to choose when you run slimdown10 to build your ISO, or is there a way to enable it on a system that was installed from a built ISO when slimdown10.cmd was run with default EnableStore value of 0? I don't mind building another ISO that has it enabled if it comes down to it, but if I don't have to and could just run some commands or something to enable Store that would be cool too. I saw there is a Toggle Windows Update in Admin tools but not sure if that affects Store being enabled or not. New system build so I don't have much invested in this yet. I built an iso using 1.52 couple weeks ago. It looks like Store is there (trying to install lite version of it said a newer version is already installed) but appears to be disabled. Just curious if there is a way to re-enable it without building another ISO with EnableStore set to 1 and reinstalling with it. Thanks! 24junkie
In the Slimdown10.cmd in the first section, edit to preference before ISO creation: Code: :: Enable Windows Store :: 0 - disable Windows Store :: 1 - enable Windows Store, Desktop Appx Installer and Windows Update :: 2 - enable above + Store Purchase and Microsoft Account :: 3 - enable above + Calendar, Contacts, SMS, Calls and Tasks permisions :: 4 - enable above + Push Notifications, Location and all permisions set EnableStore=1 After install, I think you'd have to find one of those threads about installing Store on LTSC and go that route? Someone correct me if wrong. I'm not familiar with running Slimdown10 on live systems.
if I may say so, this thread is called "Slimdown10 – turn Windows 10 22H2..." I'm sorry this is a mistake.
if I may say so, this thread is called "Slimdown10 – turn Windows 10 22H2..." I'm sorry this is a mistake.
Thanks for the reply. I ended up just making ISO with EnableStore set to 1. That got me exactly what I was looking for. With the Store there and Windows Update disabled apps that need the store to run are happy and so far it looks like I don't need to worry about it getting updated against my will.
@wkeller Five or so hours (not sure if happened right after first boot) after installing a slimmed Windows 10 22H2 Education x64 on my desktop, I found all apps I ran were running as admin or high integrity level. Investigating the cause I found this group policy setting set as Disabled, it should be Enabled by default. Code: User Account Control: Run all administrators in Admin Approval Mode > Disabled Has this something to do with Slimdown10 script?
From Slimdown10.cmd Code: REM Disable User Account Control reg add "HKLM\TK_SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System" /v "EnableLUA" /t REG_DWORD /d 0 /f >nul Change to "1" for default Windows behavior. If after install, change registry setting from "0" to "1": Code: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System] ; default "EnableLUA"=dword:00000001 "EnableLUA"=dword:00000000
Yes, I saw that line, the thing is I want UAC prompts disabled too. What I don't understand is why changing that setting to "0" in the script also leaves the other one as 'Disabled' Code: User Account Control: Run all administrators in Admin Approval Mode > Disabled It should be left 'Enabled' (this is the default value). In other words, if one manually disables UAC prompts, the other setting in question remains Enabled by default. Why the mechanism of this script (or not) disables it. That's my question.
Weird stuff happens...this is similar to the issue i had with Action Centre, i had to toggle the policy (which was at its default of "Not Configured") To Disabled and force a policy update Its also slighlty amusing that my post was #666
Thanks for your wonderful and extremely useful tool. @wkeller, I was intrigued by Can you suggest an online option - how to get it working for me on my current Windows 10 install, because I looked for a file named Added DisableWindowsSearch in the ExtraScripts folder, but it's not there, I only find the relevant lines in your Slimdown10.cmd script, but I have no idea how to activate it because with cmd.exe and with powrshell.exe it doesn't work?! /Maybe it's time for @Dark Dinosaur to offer an online version of the current version again?/
Thank you for your latest ed. V1.55 Ran now & receiving the Critical Start Menu error, will retry with Openshell disabled.
Tested it in Oracle VirtualBox and it worked. Both 32 and 64bit, tested two different languages. Critical Start Menu error only appeared, when OpenShell was uninstalled. Which was normal, because built-in system Start Menu was unaivailable too. It looks like OpenShell autoinstallation failed for some reason for you during SetupComplete.cmd phase Here is the relevant code of Win10_ISO_image\install.wim\Windows\Setup\Scripts\SetupComplete.cmd Code: ... start /w "" "%ProgramFiles%\OpenShellSetup_4_4_190.exe" /qn ADDLOCAL=StartMenu rd /s /q "%ProgramData%\Microsoft\Windows\Start Menu\Programs\Open-Shell" >nul 2>&1 del /q /f "%ProgramFiles%\OpenShellSetup_4_4_190.exe" >nul 2>&1 ... and inside Win10_ISO_image\install.wim:\Program Files, OpenShellSetup_4_4_190.exe file should also reside.
I appreciate good comments. I did everything to make this modded version of Windows 10 as pleasant to use as Windows 2000/XP/7 once were. But unlike with older Windows versions, you can still use latest software with this OS. Because (modded or not) it is still Windows 10.