@abbodi1406 After I installed all updates for Windows 8.1 (Update 3) from WHD, it's appeared 2 RunOnce cmd files. The one is executed and ran well, but not for the other one. I ran it after I restart-ed my OS but the progress is not even progressed. I left my PC outside for about an hour os so but still no progress. Cmd file name is this : I also attached a screenshot. Code: RunOnce_AfterRestart_DismCleanup.cmd [CODE]
@Gloeyisk Check C:\Windows\Logs\DISM\dism.log did you disable UAC? or you are using Admininstrator account?
Hello abbodi When using the latest 2012 R2 Monthly Rollups, the Hotfix KB3015354 is not needed anymore. I just noticed that newer versions of audmigplugin.dll and mmci.dll have been added to the Monthly Rollup since 2023-10
it's still not completely superseded "C:\Windows\System32\migwiz\replacementmanifests\microsoft-windows-audio-mmecore-other\audmigplugin.dll" and audio replacementmanifests are still not added to Monthly Rollup
Oh, I was looking at Server 2012 R2. These files are not present there, so these are Client-specific files ? On Server after Rollup 2023-10 (or later) is installed, the Hotfix KB3015354 gives an "not applicable" error. Would it be technically considered superseeded on Server version only ?
It's pointless hotfix currently anyway, as long as you don't intend to upgrade as for applicability, check if this package exist Code: C:\Windows\servicing\Packages\Microsoft-Windows-ServerManager-Migration-Package-avcore~31bf3856ad364e35~amd64~~6.3.9600.16384.mum
Edit : No the file wasn't there. There is an almost similar file Code: C:\Windows\servicing\Packages\Microsoft-Windows-ServerManager-Migration-Package-avcore~31bf3856ad364e35~amd64~6.3.9600.16384.mum Anyway it seems that it's the Windows Server Migration Tools Feature that is required. After installing that, the sys32\migwiz folder has almost the same content as in the Client version The Hotfix can then be installed afterwards, so yeah still not fully superseeded I guess. After the Windows Server Migration Tools are installed there are these two files : Code: C:\Windows\servicing\Packages\Microsoft-Windows-ServerManager-Migration-Package-avcore~31bf3856ad364e35~amd64~6.3.9600.16384.mum C:\Windows\servicing\Packages\Microsoft-Windows-ServerManager-Migration-Package-avcore~31bf3856ad364e35~amd64~~6.3.9600.16384.mum
Heyho guys, I tied now several stuff but kinda came to my end of knowledge. My Goal is to get maximum updated and full-featured dual-languaged win7 AIO Base (Starter till Enterprise x64 and x86, with all bonus stuff and drivers) - Without WU complains. (But I would like want I avoid simplix update pack for some personal reasons) - Also: As I understood the ESU.-Bypass is not need any more? No matter what I all integrate, in which order and what Edition I change to with the Live Patcher, WU still shows always some missing updates. I tried to install "WithoutSP2" folder, before apply the SP2, but that simply caused several stuff wasnt updated, simply skipped some. I even downloaded stuff from the Legacy List and tried out there.. also checked with KOMM (what sadly also gives a lot superseeded) Sometimes, depending on mix, WU wasn't working any more, or at finalizing part I got the error some stuff could not figurated) So yea.. idk... I give up and need help. What to do, which updates/folder in what order is correct to reach the goal? Alternatively (since I would like to use DISM-Cleanup as well) what absolute last-only updates needs (with all prerequisites etc) -? Like, is the WH7UI thingy is enough? Still need bypass or patcher or not? Maybe need the ESU-Lic updates? What about "not-recommended /notforIntegration, also WMF, does it work as normal run-once (at final state, silent install) which mode? (before or after loggin) What about MUI and MDL Tool thing (that integrates drivers etc) is that all compatible? Can imagine something does not work there... (did the Legacy Scripts tho, altho I would love using modern) (absolut optional goal would be have xp+7+10+11 all on same install.wim in one iso) Also something weird... about .NET4.x I only see .exe all over the place, is there really no chance to simply integrate as msu/cab? Would love to do that. A lot of thanks in advance.
WU will complain without ESU Patcher WHD + WHD-W7UI will give the most current Windows 7 binaries WU is not important or worth the trouble to satisfy no, .NET 4.x is not integratable
The live patcher you mean? Because that also I tried recently still showed me some updates. for server for example i got a lot of older superseded monthly.Which channel is best there? I guess embedded? I'm not sure what that all (the issues here) are about.. long ago everything worked perfect, I guess its because I'm mixing stuff like MDL tool as well etc. The normal modern list? (I tried also legacy and combination of lists etc) Ahh damn unfortunate.. anyway thanks for confirmation.
I have a question, am sorry if it sounds silly... Why would someone have to use this vs windows update? Considering on building a win 11 iot machine here, not sure if this might be handy or not
@abbodi1406 Sorry for ping. Is there a special order you would recommend? Main goal is the get multi2 (English + Another Language), all features included, maximum updated, WU satisfies.x64 and x86 (Starter to Enterprise), with MDL Tool stuff (drivers, dart, smartfix etc) -> additionl would nice to have NET 4.x and VCJ preinstalled.without any issues there. So have and did before 1. Taking normal Win7 Ultimate SP1 Refesh. 2. W7MUI 3. MDL SiMPLiX Tool (Without Simplix-Pack) 4. WHD7UI (downloaded modern List), I'm wondering for what is the legacy list? (It says to satisfy WU I need to integrate those in folder "Extras\WithoutSP2 (what is not included in modern List) 5. Done, when I install apply Patch to Server and restart. WU still shows me a lot of updates includes optionals. What now?