When extracting the cab files, it must first extract the LCU cab and integrate the SSU, but it does not do so. (in offline scenario) you can test it yourself
Code: http://download.windowsupdate.com/c/msdownload/update/software/secu/2022/12/windows10.0-kb5021234-x64_43c00ec144a0adb6b31af04aa6e39abc1ad0ddf4.cab
@atplsx It seems W10UI treats it as [setup du] Code: ============================================================ Running W10UI v10.25 ============================================================ ============================================================ Extracting files from update cabinets (.cab)... *** This will require some disk space, please be patient *** ============================================================ 1/8: defender-dism-x64_steven4554_Dec_13_2022.cab 2/8: windows10.0-kb5007575-x64_DU_Critical_Net35.cab 3/8: Windows10.0-KB5011048-x64_NDP481_BASE_9110.10.cab [NetFx] 4/8: Windows10.0-KB5012170-x64_PSFX_DBX.cab [SecureBoot] 5/8: windows10.0-kb5020379-x64_DU_Sources_1270.cab [Setup DU] 6/8: windows10.0-kb5021040-x64_DU_SafeOS_1215.1.0.cab [SafeOS DU] 7/8: windows10.0-kb5021234-x64_43c00ec144a0adb6b31af04aa6e39abc1ad0ddf4.cab [Setup DU] 8/8: Windows11.0-KB5020882-x64-NDP481_CU_9115.6.cab [NetFx]
It was more out of curiosity, never knew that a wsus LCU is in cab format only and it contained the same stuff as the WU/Catalog MSU.
VC AIO has not properly dig signed vc2005 version (either no sha256 or unsign dll imgs inside- i didnt dig but on load images msvc*80.dll not signed /see some proc exps/), same thing with vc70/71 - but they are too old to be signed and up-to-date vc2005/2008 appear officially reuploaded/reupdated by MS with proper dig sign both sha1/256 in 2021; whereas AIO packed "newer" versions are both early access ones by date 201* (not "new" MS ones 202*) with old sha1 or none sha256 or as turned unsigned(?) after AIO (vc2005 - *80.dll on load... maybe AIO *90.dll affected too... didn't dig too much however) +the "newly" signed 2021 vc2005 (6195) by MS shows dll signed on load btw
@asmfan They only re-signed the exe installer, the msi installer and the dll files are not changed or re-signed vc2005/2008 are SxS assemblies, digital signature for dll files themselves are not important or required it's all controlled by the binding manifest/security catalog, otherwise the OS will not allow them to install all of them are already properly signed, but the CA root certificates are not installed by default you can install it manually if you like Code: http://crl.microsoft.com/pkiops/certs/MicAssDesRoo_2011_03_23.crt http://crl.microsoft.com/pkiops/certs/MicAssDesPCA2011_2011-06-28.crt CertUtil -addstore -f Root MicAssDesRoo_2011_03_23.crt CertUtil -addstore -f CA MicAssDesPCA2011_2011-06-28.crt
abbodi1406, you can take a look at this, I loaded a BTRC activator today with a mondo licence. Office 365 likes mondo 2016 Unfortunately there is a stupid file.exe, I'd be interested to know what the exe does exactly. you have a chance to look in
I myself use this of course not only for testing in a vmware do not worry I stay true to you *g ^^ have a good time, wish you a happy new year 2023
Hi Abbodi1406 I want to use your KMS_VL_ALL_AIO.cmd My windows11 is genuine, but my Microsoft365 needs activation. I'm afraid if I use this KMS, it will affect windows too. I mean perhaps it will crack it also. Can you please clarify this. Can I activate only the MS365 without touching the Windows?