I have searched in the script, I can't find how to make Windows hello PIN work . I made too many changes in the script, I can't sign anymore, I'll look in the windows 10 script when I have time, I learned at least that using a tweaked windows can cause malfunctions
Why is it needed to delete the Win32 calculator part? Isn't it Calculator app compatible with Windows 11..?
It's true, this script is especially accessible to beginners like me. But in the spirit of this script, we do the opposite, reactivate online services...
Also remember about target release, mentioned here. No need to delete the above, because the code below will reanable Microsoft Account at later stage. I have already mentioned. Microsoft Account is always disabled during setup, then reenabled later if necessary. Code: if %EnableStore% GEQ 2 ( echo reg add "HKLM\SOFTWARE\Policies\Microsoft\MicrosoftAccount" /v "DisableUserAuth" /t REG_DWORD /d 0 /f ^>nul 2^>^&^1>>"%~dp0mount\Windows\UserSetup.cmd" echo reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System" /v "NoConnectedUser" /t REG_DWORD /d 0 /f ^>nul 2^>^&^1>>"%~dp0mount\Windows\UserSetup.cmd" echo reg add "HKLM\SOFTWARE\Microsoft\PolicyManager\default\Settings\AllowYourAccount" /v "value" /t REG_DWORD /d 1 /f ^>nul 2^>^&^1>>"%~dp0mount\Windows\UserSetup.cmd" echo reg add "HKLM\SOFTWARE\Microsoft\PolicyManager\default\Settings\AllowWorkplace" /v "value" /t REG_DWORD /d 1 /f ^>nul 2^>^&^1>>"%~dp0mount\Windows\UserSetup.cmd" echo reg add "HKLM\SOFTWARE\Microsoft\PolicyManager\default\Settings\AllowSignInOptions" /v "value" /t REG_DWORD /d 1 /f ^>nul 2^>^&^1>>"%~dp0mount\Windows\UserSetup.cmd" ) Will be included in May 2023 version.
What's the point of using Slimdown10 on Win10 LTCS? Isn't LTCS almost as clean as this script does with the Windows 10 regular release? What are the differences?
this script work on all editions, just edit the script and modify target release Reg add "HKLM\TK_SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v "ProductVersion" /t REG_SZ /d "Windows 10" /f >nul Reg add "HKLM\TK_SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v "TargetReleaseVersion" /t REG_DWORD /d "1" /f >nul Reg add "HKLM\TK_SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v "TargetReleaseVersionInfo" /t REG_SZ /d "22H2" /f >nul for windows 11 modify Windows 10 by Windows 11 REM Check Windows images set checkErrors=1 if "%ImageArchitecture%"=="x86" set checkErrors=0 if "%ImageArchitecture%"=="x64" set checkErrors=0 for /L %%i in (%ImageStart%, 1, %ImageCount%) do ( "%DISM%" /English /Get-WimInfo /WimFile:"%InstallWIMfile%" /Index:%%i | findstr /l /i /c:"Architecture" | findstr /l /i /c:"%ImageArchitecture%" >nul 2>&1 || set checkErrors=1 "%DISM%" /English /Get-WimInfo /WimFile:"%InstallWIMfile%" /Index:%%i | findstr /l /i /c:"Name :" | findstr /l /i /c:"Windows 11" >nul 2>&1 || set checkErrors=1 "%DISM%" /English /Get-WimInfo /WimFile:"%InstallWIMfile%" /Index:%%i | findstr /l /i /c:"(Default)" | findstr /l /i /c:"%ImageLanguage%" >nul 2>&1 || set checkErrors=1 ) Reg add "HKLM\TK_SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v "ProductVersion" /t REG_SZ /d "Windows 11" /f >nul Reg add "HKLM\TK_SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v "TargetReleaseVersion" /t REG_DWORD /d "1" /f >nul Reg add "HKLM\TK_SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v "TargetReleaseVersionInfo" /t REG_SZ /d "22H2" /f >nul
Windows 10 LSTC haven't Windows Store and less bloatware, by the way the script work with some modifications
@wkeller : I just realize DirectX9 never get installed after finish installing windows. There's a directx_Jun2010_redist.exe in hotfixes folder, but I guess it didn't execute the DXSETUP.exe. Do you know what's went wrong?
Like I wrote earlier there are better ways than post install scripts to install SW. But id you're stick in the 90s I believe that the original dxsetup isn't happy if you haven't the .net 3.5 installed before. Either try to integrate .net 3.5 before, or use the directx repack by abbodi, which has a more modern installer.
Ah sorry I miss your post mentioning this issue earlier acer-5100. Not a big problem really, can run dx9 manually, but just curious why it doesn't install. And thank you for your pointer, I will try to change to make .net 3.5 install first then dx9 then, Thank you and cheers... btw thanks for the tip on install with deploying image file
1. directx_Jun2010_redist.exe is unpacked to DVD\Updates\DX9 folder during ISO building phase. 2. Updates\DX9\DXSETUP.exe is silently installed during SetupComplete.cmd phase 3. DirectX v9 June 2010 does not require .NET 3.5 to work, however it does support it when it is installed.
I was not aware that it requires .NET 3.5. I have used it even on Windows XP and it seemed to install and work without .NET Framework at all (any version). However it may be different on Windows 8/8.1/10.
Again it doesn't "require", just the GUI installer, blames about net .35, then you can continue w/o it (so I guess that in silent mode that could be a blocker, given there is no one that press Y / Continue). It's obviously an installer glitch, it works perfectly w/o .net 3.5. Whatever... the repacked installer by abbodi is both way faster and not plagued by any installer problem, so isn't even worth to discuss the matter anymore.
Hello wkeller. What items in your script need to be changed in order to run your Windows 11 script? I thank everyone who can help with this for the promptness.
Just checked it and you are spreading misinformation. I have created and installed Windows 10 English 32-bit and installed it on Oracle VirtualPC. .NET FX 3.5 was not integrated and completely removed from installation media. But DirectX v9 June 2010 is installed correctly. All dll files are placed where they should be. It is outright nonsense. Unpacked installer takes second or two to install. How much faster can it be ? And there are no installer issues as I have tested it above.