The above or switch to: https://forums.mydigitallife.net/th...egrate-hotfixes-into-win7-distribution.45005/
I had to copy the Windows 10/11 ADK osdiscimg.exe, the included one gave me error: Code: ReadFile failed ...\autorun.inf, off=0 len=800 status=103) Error 87: The parameter is incorrect.
Hi, The script does complete but I get the errors in Integrate7. See the errors from log: Code: Deployment Image Servicing and Management tool Version: 6.3.9600.17029 Image Version: 6.1.7601.23403 Processing 1 of 1 - Adding package E:\Windows7UEFI\Integrate7\hotfixes\windows6.1-kb4532945-x64.msu [=================== 32.9% ] E:\Windows7UEFI\Integrate7\hotfixes\windows6.1-kb4532945-x64.msu: An error occurred applying the Unattend.xml file from the .msu package. For more information, review the log file. Error: 0x80073712 Error: 14098 The component store has been corrupted. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log ================================================================ Adding package KB5013637 - .NET 3.5.1 Cumulative... ================================================================ Deployment Image Servicing and Management tool Version: 6.3.9600.17029 Image Version: 6.1.7601.23403 Processing 1 of 1 - Adding package E:\Windows7UEFI\Integrate7\hotfixes\windows6.1-kb5013637-x64.msu [=================== 33.0% ] E:\Windows7UEFI\Integrate7\hotfixes\windows6.1-kb5013637-x64.msu: An error occurred applying the Unattend.xml file from the .msu package. For more information, review the log file. Error: 0x80073712 Error: 14098 The component store has been corrupted. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log ================================================================ Adding package KB5020861 - .NET 3.5.1 December 2022 Cumulative... ================================================================ Deployment Image Servicing and Management tool Version: 6.3.9600.17029 Image Version: 6.1.7601.23403 Processing 1 of 1 - Adding package E:\Windows7UEFI\Integrate7\hotfixes\windows6.1-kb5020861-x64.msu [=================== 33.0% ] E:\Windows7UEFI\Integrate7\hotfixes\windows6.1-kb5020861-x64.msu: An error occurred applying the Unattend.xml file from the .msu package. For more information, review the log file. Error: 0x80073712 Error: 14098 The component store has been corrupted. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log ================================================================ Adding package KB5032000 - .NET 3.5.1 November 2023 Cumulative... ================================================================ Deployment Image Servicing and Management tool Version: 6.3.9600.17029 Image Version: 6.1.7601.23403 Processing 1 of 1 - Adding package E:\Windows7UEFI\Integrate7\hotfixes\windows6.1-kb5032000-x64.msu [=================== 33.0% ] E:\Windows7UEFI\Integrate7\hotfixes\windows6.1-kb5032000-x64.msu: An error occurred applying the Unattend.xml file from the .msu package. For more information, review the log file. Error: 0x80073712 Error: 14098 The component store has been corrupted. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log ================================================================ Adding package KB5022338 - January 2023 Cumulative... ================================================================ Deployment Image Servicing and Management tool Version: 6.3.9600.17029 Image Version: 6.1.7601.23403 Processing 1 of 1 - Adding package E:\Windows7UEFI\Integrate7\hotfixes\windows6.1-kb5022338-x64.msu [=================== 33.3% ] E:\Windows7UEFI\Integrate7\hotfixes\windows6.1-kb5022338-x64.msu: An error occurred applying the Unattend.xml file from the .msu package. For more information, review the log file. Error: 0x80073712 Error: 14098 The component store has been corrupted. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log ================================================================ Adding package KB5032252 - November 2023 Cumulative... ================================================================ Deployment Image Servicing and Management tool Version: 6.3.9600.17029 Image Version: 6.1.7601.23403 Processing 1 of 1 - Adding package E:\Windows7UEFI\Integrate7\hotfixes\windows6.1-kb5032252-x64.msu [=================== 33.3% ] E:\Windows7UEFI\Integrate7\hotfixes\windows6.1-kb5032252-x64.msu: An error occurred applying the Unattend.xml file from the .msu package. For more information, review the log file. Error: 0x80073712 Error: 14098 The component store has been corrupted. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log ================================================================ Adding package KB5010798 - Out-of-band update... ================================================================ Deployment Image Servicing and Management tool Version: 6.3.9600.17029 Image Version: 6.1.7601.23403 Processing 1 of 1 - Adding package E:\Windows7UEFI\Integrate7\hotfixes\windows6.1-kb5010798-x64.msu [================== 32.4% ] E:\Windows7UEFI\Integrate7\hotfixes\windows6.1-kb5010798-x64.msu: An error occurred applying the Unattend.xml file from the .msu package. For more information, review the log file. Error: 0x80073712 Error: 14098 The component store has been corrupted. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log Please help.
Check the first post (OP) when it is last updated (or if it says "deleteduser...), and the sticky posts would also be a way to see if it is still supported.
Nothing really stops you from editing 7.35 version (.txt URLs + .cmd) and adding last 2024-10 (EOL) update: KB5039339 2024-06 SSU KB5044356 2024-10 SMQR for Win7 KB5044011 2024-10 S&QR dotNET 3.5.1 KB5044027 2024-10 S&QR dotNET 4.8 (i manually edited cmd in every release anway, since there are some configuration changes that i did not agree with (+ also adding IF around them) Anyway: 1. With the 2024-10 = x86 is now finally EOL and done.. 2. For x64 - it is somewhat unclear how safe* it is to use Windows Server 2008 R2 (x64) updates going forward: Server 2008 R2 x64 => Windows Server Premium Assurance until 2026-01-13 * As last 2024-11 CU - borked win32k.sys signature - it causes sandboxing in FF and Chrome to fail <= requires signature enforcement to be disabled or driver won't load ~ which is too inconvenient, See: https://forums.mydigitallife.net/threads/windows-7-hotfix-repository.19461/page-560 And: github.com/win32ss/supermium/issues/1012 But then again various drivers released for windows 7 post EOL are no longer signed (since MS won't accept them).. ~ I guess we will see what is happening in 2024-12