He can keep renaming the file until his fingers fall off his hand, it's not going to help. UpdatePack7R2 is not a magical tool that works wonders on all machines. Usually, for it not to work there is a problem with the current windows installation itself. In which case it's easier to make backup of important data and perform a clean install with an offline serviced windows 7 image.
currently I am experimenting with KUC W7 UpdateChecker. after all the WU installs, I am thinking on using something like this: remove_crw.cmd @ github & then trying simplix again Edit: apparently, there are some inconsistencies/conflicts among KUC UpdateChecker & Simplix. KUC feels it can remove some KBs while Simplix keeps reinstalling them: Code: KB# State Superseded Type Status Version Superseded by Remarks 2900986 Installed yes REMOVE 6.1.1.1 Security Update 4018271 Windows6.1-KB2900986-x64.msu This update is superseded. You can REMOVE it! All of the superseding updates are installed. 2834140 Installed yes REMOVE 6.1.2.0 Update 3125574 Windows6.1-KB2834140-v2-x64.msu This update is superseded. You can REMOVE it! All of the superseding updates are installed. 2853587 Installed yes ADLDS REMOVE 6.1.1.2 Security Update 3012660 Windows6.1-KB2853587-x64.msu This update is superseded. You can REMOVE it! All of the superseding updates are installed. 3138612 Installed na WUC REMOVE 6.1.1.1 Update na Windows6.1-KB3138612-x64.msu You can remove this package for WUC! 2603229 Installed na REMOVE/FORCED 6.1.1.0 Update na Windows6.1-KB2603229-x64.msu Registry keys NOT set correctly! 3161102 Superseded yes REMOVE 6.1.1.1 Update na Windows6.1-KB3161102-x64.msu The version of this package is lower than that of the reference (6.1.2.0)! The reference version is also installed! 2545698 Superseded yes REMOVE 6.1.1.3 Update 3125574, 5005633 Windows6.1-KB2545698-x64.msu The version of this package is lower than that of the reference (6.1.1.5)! The reference version is also installed! This update is superseded. You can REMOVE it! All of the superseding updates are installed. Finnaly, Simplix keeps trying to install KB3125574-v4 over & over again (in each fresh boot of the PC) until interrupted by hitting cancel, without any further hint, log or explanation Conclusion: KUC is happy, WU is happy, Simplix re-installs some KBs that KUC feels are no longer needed & keeps reinstalling KB3125574-v4
Updated with the latest ndp48 addons by @abbodi1406 : https://forums.mydigitallife.net/th...-install-wim-esd-creation.79421/#post-1516362
The app I mentioned last month here fails to connect again and I have no response from the company yet. So I made the forementioned registy change that wants me to create the key manually. But am I doing it right? I right click > create > dword value (32bit) > name it and set it to 1.
Changelog 21.11.10: Added KB5007236-x86-x64 with disabled telemetry and cpu check (replaces KB5006743-x86-x64) Updated certificates for KB931125 and KB2917500 for November 2021
Updatepack 21.11.10 log: https://forums.mydigitallife.net/th...l-wim-esd-creation.79421/page-77#post-1703725 Updated the Simplix Pack OP with UpdatePack 21.11.10 Updated the WA Addons post with the latest vcredist WA files by @abbodi1406
Because the Windows 10 update in the past three months will cause printing problems, I tested UpdatePack7r2 in October and November, and it seems that there will be printer sharing connection problems. I wonder if anyone has encountered it?
Sorry for not mentioning that I used UpdatePack7r2-21.11.10 to integrate the ISO installation. I have tried this and cannot uninstall KB5007236 Does anyone know how UpdatePack7r2 can skip a single KB5007236
Got a small bug to report. After installing a simplix updatepack I think it was the one from august or september, the Programs and features window won't open normally. It opens, starts loading programs, then Windows Explorer goes not responding and has to be closed, killing all open Explorer windows. After that the explorer restarts and I can open Programs and features again and it will load and work normally.
November is almost over, why bother with an aug/sep release? Even still, I saw no such issue in any of those releases.
Checked it was the August pack. I installed it back then and forgot to write about it until I went to install this month's pack. Sorry for bothering it's probably M$ fault anyway or some combination of programs I run, I usually have the taskbar completely full Edit (Nov 23): urq, this month's patch tuesday took that bug up to 11. Is there a way to uninstall an update installed with Simplix? They aren't showing up under Control Panel > Add/remove > installed updates Edit 2, Nov 28: the bug is happening less frequently now. I think it may have something to do with thumbnail generation, Microsoft's fault
Yes I update with "Simplix Update Pack 7R2" Will I also have the BypassESU included? or do I have to put the bypassESU?
The updatepacks are meant for never using WU again, just monthly running the new updatepack + WA files will be sufficient in the intended scenario, when you still want to be able to use WU you need the ESU bypass by @abbodi1406 to be installed.
ok, thanks now then I can make my iso windows 7 updated with the bypassESU included, thanks for clarifying my doubts
Enthousiast Thanks for your great effort SiMPLiX_AiO_ISO_Full_Tool_2_7_21.8.11 Spoiler: efisys.bin echo=============================================== echo Creating ISO... echo=============================================== for /f "tokens=2 delims==." %%# in ('wmic os get localdatetime /value') do set "_date=%%#" set "isodate=%_date:~0,4%-%_date:~4,2%-%_date:~6,2%" bin\cdimage.exe -bootdata:2#p0,e,b"TEMP\ISO\boot\etfsboot.com"#pEF,e,b"TEMP\ISO\efi\Microsoft\boot\efisys.bin" -o -m -u2 -udfver102 -l%LabelVar% "TEMP\ISO" %LabelVar2%_%StarterLang%_SiMPLiXED_%isodate%.iso file efisys.bin in the path TEMP\ISO\efi\Microsoft\boot\efisys.bin is Missing Creating ISO = Errors www*mediafire*com/file/jemmjxpwdp4ge9j/efisys.bin/file Copy to track path TEMP\ISO\efi\Microsoft\boot .After creating files TEMP