Guys i have a little problem i guess i removed too much from iso, and i need Windows Subsystem for Linux working. What are exact things needed for WSL working?
Hi MSMG, I've been using your amazing Toolkit for making an updated Windows 7 ISO (All indexes). I also used it for making W10 and W11 ISOs and it works great. However, even if Windows 7 is not supported anymore, I am making a custom image to have it ready at hand. I wanted to request (if possible) to add the following tweaks inside the toolkit (for W7), so they can be implemented in the OS image: WuaCpuFix; BypassESU; Disable Telemetry stuff; and Hide Unwanted Updates. (I can provide files for those). Another one (but difficult) is to update the OS installer to the Windows 10 One with UEFI support (in this case the user provides the updated w10 ISO file and puts it inside a folder). LMK; Thank you!
Bug report: seems that recently Microsoft has changed format for their Inbox Apps to from .appx to .AppxBundle for most codecs like HEIF and HEVC. But this is not reflected in the Toolkit, so some Inbox Apps won't install.
@MSMG is aware of this Microsoft didn't change them all at once, so the toolkit was maintained to cater for those that had changed. Microsoft has since changed them. This will probably be addressed in the next version of the toolkit, assuming MSMG has time.
Microsoft says it’s investigating reports of a Blue Screen of Death with an “UNSUPPORTED_PROCESSOR” error message that’s been cropping up on some Windows 11 PCs after installing an update released earlier this week. The latest KB5029351 update includes the usual monthly fixes, but it appears to be causing issues when used with some MSI motherboards.
Have someone ever succeeded in integrating AV1VideoExtension, MPEG2VideoExtension or HEVCVideoExtension using the Toolkit? By success I mean actually seeing these packages with the Get-AppxPackage command on the installed system. Toolkit always says that "Operation completed successfully", but these packages never really install. I suppose this is due to lack of correct AppLicense files for them. Wasted too much time figuring this out. Sadly there is no clear information about this.
Works fine for me using the integrate inbox apps option in the toolkit; dism /online /get-provisionedappxpackages shows the following on my live system; Spoiler: inbox apps C:\Users\Tanya>dism /online /get-provisionedappxpackages Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.19044.3208 Getting the list of app packages (.appx or .appxbundle) in this image... DisplayName : Microsoft.HEIFImageExtension Version : 1.0.61171.0 Architecture : neutral ResourceId : ~ PackageName : Microsoft.HEIFImageExtension_1.0.61171.0_neutral_~_8wekyb3d8bbwe Regions : DisplayName : Microsoft.MPEG2VideoExtension Version : 1.0.50901.0 Architecture : x64 ResourceId : PackageName : Microsoft.MPEG2VideoExtension_1.0.50901.0_x64__8wekyb3d8bbwe Regions : DisplayName : Microsoft.VP9VideoExtensions Version : 1.0.61591.0 Architecture : neutral ResourceId : ~ PackageName : Microsoft.VP9VideoExtensions_1.0.61591.0_neutral_~_8wekyb3d8bbwe Regions : DisplayName : Microsoft.WebMediaExtensions Version : 1.0.61591.0 Architecture : neutral ResourceId : ~ PackageName : Microsoft.WebMediaExtensions_1.0.61591.0_neutral_~_8wekyb3d8bbwe Regions : DisplayName : Microsoft.WebpImageExtension Version : 1.0.62011.0 Architecture : neutral ResourceId : ~ PackageName : Microsoft.WebpImageExtension_1.0.62011.0_neutral_~_8wekyb3d8bbwe Regions : I also tried it manually using the following command; Spoiler: dism DISM.exe /Online /Add-ProvisionedAppxPackage /PackagePath:Microsoft.MPEG2VideoExtension_1.0.50901.0_x64__8wekyb3d8bbwe.Appx /DependencyPackagePath:Microsoft.VCLibs.140.00_14.0.32530.0_x64__8wekyb3d8bbwe.Appx /DependencyPackagePath:Microsoft.VCLibs.140.00_14.0.32530.0_x86__8wekyb3d8bbwe.Appx /Licensepath:Microsoft.MPEG2VideoExtension_8wekyb3d8bbwe.x64.xml grabbed the license file from the toolkits bin\applicense folder. A note though, the files available on adguard are now bit neutral and are now appxbundle. These are "provisioned Appx packages"
Would it be possible for us end-users to have some reference to dependencies when removing/preserving packages from lists? I'd like to keep Store, Update and a working start menu (For that initial cmd > sfc /scannow + dism and finding OpenShell to replace it). I know it lists some dependencies in the gui, but reconciling them to the Toolkit names is not ideal. Also maybe some breakage warning, in reference to: Just something to consider, i know it's work and nobody likes that Ty
from 12.0 to 13.4 they are all in the current repositories, inside the "archive" folder. I believe you won't need any pre-13.3. But which build do you want to work on? I had specifically requested some very old ones to develop something into a script.
Thanks for your answer! But I can only see MPEG2VideoExtension in your system from my list in question. Have you chosen not to integrate AV1VideoExtension and HEVCVideoExtension, or it just failed to install?
The idea was just to show you that integration via the toolkit works. I do have HEVC installed, I had just cut off part of the list as I have other apps installed. With the exception of AV1 which I have not installed. Code: DisplayName : Microsoft.HEVCVideoExtension Version : 2.0.61931.0 Architecture : neutral ResourceId : ~ PackageName : Microsoft.HEVCVideoExtension_2.0.61931.0_neutral_~_8wekyb3d8bbwe Regions :
Well, as far as I can remember, I could never successfully integrate HEVCVideoExtension into WIndows 10 LTSC using the various Toolkit versions. Not so sure about MPEG2 and AV1, because HEVCVideoExtension is much more important for me, as iPhone *.heic images simply won't display without it. If someone is able to integrate it, I wonder, what is the right way to succeed. Does it depend on WIndows image version, some Toolkit settings, or it is just random luck?