I had tested the 32bit and it was working properly, I was using en-US language, are you using en-GB or other language? Still need to extract mui language files for 14393 Win32Calc and repack the pack.
Yes you can use it but why you want to stick to v11.7 when you have updated one. Will check with the Screen Snip Quick Action bug.
@MSMG Reg add "HKLM\TK_SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v "TargetReleaseVersion" /t REG_DWORD /d "1" >nul 2>&1 to Reg add "HKLM\TK_SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v "TargetReleaseVersion" /t REG_DWORD /d "1" /f >nul 2>&1 and for TargetReleaseVersionInfo to work properly There is a need to add at the beginning of the session :ApplyTweaks the code below to do the Build Update. Code: :: Get updated Image Information if "%ImageBuild%" geq "18362" if "%ImageBuild%" leq "19044" ( call :GetUpdatedImageInformation ) :: Getting Install Image Index Architecture call :GetImageArchitecture "%InstallWim%", %DefaultIndexNo% >nul
@MSMG , In 11.8 startup function： Code: if "%HostArchitecture%" equ "x86" ( if "%HostVersion%" equ "6.1" echo. - Microsoft Windows 7 ^(%HostArchitecture%^) [%HostLanguage%] if "%HostVersion%" equ "6.3" echo. - Microsoft Windows 8.1 ^(%HostArchitecture%^) [%HostLanguage%] if "%HostVersion%" equ "10.0" echo. - Microsoft Windows 10 ^(%HostArchitecture%^) [%HostLanguage%] ) if "%HostArchitecture%" equ "x64" ( if "%HostVersion%" equ "6.1" echo. - Microsoft Windows 7 / Server 2008 R2 ^(%HostArchitecture%^) [%HostLanguage%] if "%HostVersion%" equ "6.3" echo. - Microsoft Windows 8.1 / Server 2012 R2 ^(%HostArchitecture%^) [%HostLanguage%] if "%HostVersion%" equ "10.0" echo. - Microsoft Windows 10 / Server 2016/2019 ^(%HostArchitecture%^) [%HostLanguage%] It may change all Windows 10 to Windows 10/11; change all Server 2016/2019 to Server 2016/2019/2022
Thank you. Since 11.8 is compatible only with 19043.1237 I wanted to use 11.7 which is compatible with 19043.1151. I was under the impression that the screesnip will work with 19043.1151 but it doesnt work with 19043.1151 and even with 17763.2061 either. The screen snip is the snipping tool right ?. The snipping tool just works fine from startmenu but not from the screen snip in quick actions. If i click screen snip in quick actions the screen just blinks and nothing happens. I have removed screensketch component. Is this the reason why screensnip not working in quick actions ?. And please let me know why the explorer search box in 19043.1151 serviced with v11.7 break after sometime (in a week in my case). Is this a bug in windows 1151 or due to the handling of the toolkit ?. Thank you
Thanks, I have simplified the code to display the OS Info in detail. Code: echo.Reading Host OS Information... echo. echo.%HostOSName% ^(%HostBuildBranch%^) %HostDisplayVersion% ^(v%HostVersion%.%HostBuild%.%HostServicePackBuild%^) %HostArchitecture% %HostLanguage% Code: =============================================================================== MSMG ToolKit - StartUp =============================================================================== Reading Host OS Information... Windows 10 Pro (co_release) 21H2 (v10.0.22000.194) x64 en-US Setting Toolkit and WADK tools environment path variables... DISM.exe = D:\Toolkit\Bin\x64\DISM10\Dism.exe Imagex.exe = D:\Toolkit\Bin\x64\imagex.exe Oscdimg.exe = D:\Toolkit\Bin\x64\oscdimg.exe Dvdburn.exe = D:\Toolkit\Bin\dvdburn.exe 7zip.exe = D:\Toolkit\Bin\x64\7z.exe Dism++CUI.exe = D:\Toolkit\Bin\Dism++CUI.exe /ESDFile EsdDecrypt.exe = D:\Toolkit\Bin\esddecrypt.exe ToolKitHelper.exe = D:\Toolkit\Bin\ToolKitHelper.exe ResourceHacker.exe = D:\Toolkit\Bin\ResourceHacker.exe WimlibImagex.exe = D:\Toolkit\Bin\x64\wimlib-imagex.exe =============================================================================== Press any key to continue . . .
It's the Toolkit's component removal program ToolKitHelper.exe which is tied to 19043.1237 and not the Toolkit.cmd itself. If you want to use 19043.1151 with Toolkit.cmd v11.8 then replace the ToolKitHelper.exe from v11.7 Don't know whether the search bug is with 19043.1151 CU or ToolKitHelper.exe need to check, you can check the 19043.1151 support info know the known bugs. The Windows 10 contains both the Snipping Tool - Classic and Modern, the Screen Snip is the modern version.
Though toolkit's component removal program is toolkithelper.exe, the VCRuntime packs reference are contained in the batch file toolkit.cmd isnt it ?. I am using the latest packs and toolkit.cmd in v11.7 is the earlier one which has the references to the old VCRuntime packs and I am not able to use the toolkit.cmd in v11.7 with the latest packs. It gives error when integrating the newer VCRuntime. Thats why i took the toolkit.cmd from v11.8 and used in v11.7 for 19043.1151. Correct me if I am wrong and there are no sfc errors. Now the problem I am facing is screen snip doesnt work through quick actions with 17763.2061 (serviced with 11.7) ,19043.1151 (serviced with 11.7) as well as in 19043.1237 (serviced with 11.8). My bad i didnt check the screen snip tool from the time since i started generating ISOs through UUPDUMP. Even under 19043.1153 and 19043.1237 the command DISM /Online /Cleanup-Image /Restorehealth progresses upto 55% and exits saying that something is missing. Is this usual ?
Use the latest Toolkit v11.8 + latest VCRuntime Packs + old ToolKitHelper.exe to have complete functionality for all OS. You need to re-check the packs folder structure to match with the latest Toolkit v11.8. Will check with the Screen snip and DISM /Online /Cleanup-Image /RestoreHealth thing.
Sorry, but you mean the packs folder structure or the files inside Packs\VcRuntime\w10 ?. toolkit.cmd of v11.7 needs VC_2019 files in packs. toolkit.cmd of v11.8 needs VC_2022 files in packs. Thats why I used the toolkit.cmd of 11.8 under 11.7 with VC_2022 in the packs folder.
I have changed the Toolkit's Bin and Packs folder structure to adapt to Windows 11 version, some language pack base patch files have been moved from Bin to Packs\LanguagePacks folder. If you are just adding VC Runtime Pack then it's OK to use just Toolkit.cmd, if you want to use the rest of the functions then use the full latest version always.
For Builds 22000 and above, It may speak Windows 11, not Windows 10, although they have the same NT Kernel Version Therefore, you can consider judging the operating system name based on Build. Based on the existing information, you can use 21650 as a boundary for judgment
The HOST info is read from the registry [SOFTWARE\Microsoft\Windows NT\CurrentVersion] and the ProductName subkey value is still Windows 10 Pro for Windows 11. Don't know whether the MS will change it on Oct 5, if they don't make the changes then will adapt the code to display it correctly.
@MSMG - Please let me know if the screensketch component in removepkgslist.txt is related to the screen snip shortcut in quick Actions. If i remove screensketch package will it make the screen snip shortcut in quick action non-functional ? So in order for screen snip to work should I retain Microsoft.screensketch Apps package and screensketch component package ?. I think this is the reason why screen snip is not working for me. Correct me if I am wrong. And moreover "Applying Disable Windows smartscreen tweak" title is missing while customizing in the toolkit. Dont know if it is fixed in the latest toolkit. This is for your kind information. UPDATE: Used 19043.985 with toolkit 11.5 and found out that retaining screensketch component brings back the screen snip in the quick actions. And Microsoft screensketch application is listed as snip and sketch and removing that doesnt harm the screen snip. But the dism restorehealth persists even in this version. It says "the system cannot find the file specified at 55.5%". Hope this helps.
Yes ScreenSketch is the Snip and Sketch App, removing it will also render it's functionality in Quick Actions. Will check with the Applying Disable Windows SmartScreen tweak. You need to use the correct image with CU specified in the changelog, if you use unsupported CU's then you will get SFC or DISM errors.
Just now checked 19043.985 serviced with 11.5 with screensketch app and component removed and I am surprised to note that screen snip is working without screensketch and I think removal of the same will not have an impact on screen snip shortcut in quick actions. I used 19043.985 downloaded from uupdump which is compatible with toolkit 11.5.
Ok here's is the thing which get confused with many users due to similar naming. Screen Sketch - Screen Sketch App - Windows 10 Modern screenshot tool. Snip and Sketch - Windows Ink Workspace which is part of the ShellExperienceHost.exe Snipping Tool - Windows 10 Classic screenshot tool. Screen Sketch (Snipping Tool) - Windows 11 Classic and Modern screenshot tool. Okay you can remove the Screen Sketch it won't affect the Snip and Sketch