So is the message simply coded to look at the specific version number? was from the latest update. Since then it's now 1904x.3324 -> 1904x.3633 Does that mean the latest build would trigger the message but the older 3324 would not?
Is the latest Toolkit_v13.6.7z archive broken for anyone else? It ends up with 27 errors when unpacking, error "Unsupported compression method", latest 7-Zip v23.01.
Guys what iso i need to download to be supported in latest toolkit i want windows 10 22h2 but it says it isn't supported(i downloaded by microsoft creation tool)? file name is: Win10_22H2_Polish_x64v1.iso
Even if it works fine, byte size of collective files inside archive and after decompression is different.
Which download site are you getting the file from? I never had a single error when extracting the archive with 7-Zip v23.01.
if you still need windows update, use WUB as third party tools, but if you want to completely disable windows windows update, just disable it from customization
1) Defender is completely removed on my system 2) I installed 7-Zip the moment this errors appeared in WinRAR firstly and I never had 7-Zip installed prior this errors. /Edit I found the issue. It's my Windows 10 v1709 16299.15, on version 21H2 archive unpacks without errors. Very strange and I don't know why it affects this specific archive only, because other archives are decompressing fine. Especially when 7-Zip/WinRAR provides the required libraries for decompression and should not rely on OS components. Don't ask me why I still use such old OS on live system... Modding, learning, experimenting, testing with my new custom ISO took way more time than I anticipated.
This code is proprietary to MSMG, I can't say anything about it. I'm just trying to convey the information he's already shared with everyone over the years here. Yes, just use the supported version and insert the updates through the Toolkit and the removal will work properly, as the image will remain mounted as if it were the supported version. After committing the image it loses support, this will only happen after saving and unmounting. But lately DISM makes a detail when applying updates that is a remount. I'm going to make an assumption here: I don't know what the procedure is like, but it seems like a commit happens, If this is what happens, insert updates through the toolkit during ISO customization will no longer have this effect and the Toolkit will only support the version specified at its launch.
How to permanently stop updates in Windows 10, Windows 11, I don't care about store and errors. Anyone please?
My 2 cents worth; I'm running 19044.3570 (21H2). I have disabled the WaaSMedic service, Update Orchestrator (usosvc), and Windows update Service. Also disabled Windows update medic task (PerformRemediation) in scheduler. Windows update services do not get re-enabled on my system, - Windows update is effectively dead. If I remember correctly I had to disable WaasMedic via registry as SC gets an access denied error Code: REG ADD "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WaaSMedicSvc" /v Start /d 4 /t REG_DWORD /f You might like to also disabled these tasks in Update Orchestrator. Report Policies Schedule Scan Policy Install Reboot