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
I wander is it simply possible to configure windows firewall or edit hosts file to disable all updates?
Sorry when I use autoruns, I deselect checkbox in "Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services" for WaaSMedic, usosvc and Windows update Service, but when I run msconfig I see that they are all running fine, even if in autoruns check boxed are removed. Actually Windows Update Service is set to disabled, but after PC reboots it is enabled again. This is like a virus made my Microsoft. :O) Win11 22h2
Thats what I was talking about, go to system 32 remove trusted installed from waasmedic.svc then disable uso wuaus and tasks related to update then update won't enable itself. And yeah it's like virus.
I was thinking about the meanings of these messages when an SSU is integrated into the image. Code: The changes due to package Package_for_ServicingStack_#### requires the current servicing session to be reloaded. All the packages will be processed again. The operation completed successfully. I studied the process and the Image is not automatically committed in these procedures: 1. Reloading the Current Servicing Session; 2. Processing again; So, as none of the operations make the commit, saving the image that is being serviced, I was wrong in this assumption I made in my previous message...