That's a commercial to buy that software, people should stop trying to get an ancient OS on the most current/modern hardware.
I don't really want to get off topic for this thread, but my Ryzen 3900X /X570 Gaming Plus has been working flawlessly with Windows 7 x64 for the past 3 years including a NVMe SSD at PCIe 4.0 x4 speeds. The thread above also contains useful information on booting Windows 7 with UEFI other than just the information provided by the PrimeExpert Software Company.
Interesting side note: If you look at the comments from Gen2 on his latest posting for WIndows 7 over on 1337x, he is referencing this very tool. Without any credit to the author of the Simplix Update Pack, or to Enthusiast for this tool.
People, please stay on topic. This thread is meant for discussing the Simplix update pack project. There are numerous other threads on topics like INT 10H handler emulation, driver modding, and/or slipstreaming. While each such component interrelates with all the others when it comes to installing an up-to-date version of Windows 7 on modern hardware platforms, it's better to stick with the theme of each thread for the sake of tidiness.
Has anyone else had an issue installing UpdatePack7R2-23.4.11 on an SP1 clean install or otherwise? I haven't tried it integrated with the MDL Win7 Tool yet, but the 2022 UpdatePack worked with it. Which leads me to believe some more recent update may have broken something or posed some sort of incompatibility with my system. I might go ahead and test the 2022 Update Pack on a clean install, as well as the MDL Legacy tool and the Modern Tool with the current release just to see if it works that way. As 23.4.11 results in a bootloop error on my end. And while the 2022.8.x pack did work with the MDL Modern Tool, my system seems sort of sluggish and my theme keeps getting knocked off of Aero back to Basic seemingly at random. (Perhaps something to do with... is it WinSAT or Windows Experience profiling?)
I'm having some kind of strange issue with Office 2016 after installing the April pack. My AutoKMS has long been broken and leaving crap in the event log, but this time it insisted on crashing all the time and running the MSI installer every time it restarted until I killed and disabled the OSPP service. I'm half suspecting M$ put something in to grief pirates?? Haven't had this on Feb 23 pack That's about as much problem as I've ever had with any of Simplix's updates, and AFAIK considering what I put my computer thru, it runs far smoother than any Win10 machine on similar specs I've seen. Aero included (Windows experience is a pathetic 5) MSI I take it? I heard in multiple places they're the best for NT 6.x. I'm considering their X670E for my next machine
@Alexandros C. Couloumbis What KUC self argument exactly? it's not up-to-date, so it doesn't recognize the new updates, as it says in #1 for #3, KUC usually have the latest version of updates and hotfixes, while Simplix follow WU version
KUC at the very end of the whole update cycle resorts in a loop offering to add & then remove 1 package every-time is been run (as shown on images #1 & #2)
KB2603229 is special weird update, that even MS didn't correctly install it in some cases you should remove KB2603229 (both GDR/LDR if present) install it manually via msu file then, copy/paste and run these in command prompt as administrator Code: set "_sreg=HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" set "_treg=HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows NT\CurrentVersion" for /f "skip=2 tokens=2*" %i in ('reg.exe query "%_sreg%" /v RegisteredOwner') do reg.exe add "%_treg%" /v RegisteredOwner /d "%j" /f for /f "skip=2 tokens=2*" %i in ('reg.exe query "%_sreg%" /v RegisteredOrganization') do reg.exe add "%_treg%" /v RegisteredOrganization /d "%j" /f
your directions resolved (for me) the KUC loop issue with the add/remove KB2603229 package (see attached images) thank you
Just thought I'd come back and report that I think I've pinpointed the cause of me ending up with a bootloop after installing Simplix UpdatePack7 (tested with 23.4.11 on a clean install and later using the MDL Win7 Tool with the included Simplix pack from 2022 as well as 23.4.11). My mobo has Geforce6100 onboard graphics and nForce4 chipset. I've always had issues with installing chipset drivers for these motherboards (I have 2, nearly identical...) as they were written to target WinXP and Windows Vista. Installing them in Win7, I assume uses some sort of compatibility layer. Anyways... I go into more details on all that here lol: https://forums.mydigitallife.net/th...-wim-esd-creation.79421/page-108#post-1788165 Turns out that trying to install my chipset drivers (Geforce 6 series, 15.49 installer) causes the bootloop. I'm guessing one of the 3 drivers it tries to install overwrites something already included with Simplix UpdatePack (DriverPacks maybe...) and creates a critical error. I can't imagine how it would create an error at boot time though.
can simplix be used to update an installed but offline system from another win7 system ? the installed offline system is able to get MS updates though dism /online /get-packages is broken probably due to a registry issue. offline dism /image:E: /get-packages on that same system is a Go Edit: my Code: dism Error: 5 issue was resolved after manually removing the invalid registry entries mentioned in CheckSUR.log generated by Code: dism /online /cleanup-image /scanhealth I had to run regedit as admin & get ownership of the invalid registry entries which reside in: Code: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages along with granting full access control under permissions, in order to be able to delete them. Edit II: running UpdatePack7R2-23.5.10 after my registry "fix", broke again dism with error: 5 by reintroducing a registry entry to a missing Package file here are the contents of CheckSUR.log Spoiler ================================= Checking System Update Readiness. Binary Version 6.1.7601.24499 2023-05-10 17:02 Checking Windows Servicing Packages Checking Package Manifests and Catalogs (f) CBS Catalog Missing 0x00000002 servicing\Packages\Package_for_KB2999226~31bf3856ad364e35~amd64~~6.1.1.6.cat (f) CBS Catalog Missing 0x00000002 servicing\Packages\Package_for_KB3050265_SP1~31bf3856ad364e35~amd64~~6.1.1.9.cat (f) CBS Catalog Missing 0x00000002 servicing\Packages\Package_for_KB3124275~31bf3856ad364e35~amd64~~6.1.1.0.cat (f) CBS Catalog Missing 0x00000002 servicing\Packages\Package_for_KB3150513~31bf3856ad364e35~amd64~~6.1.1.5.cat (f) CBS Catalog Missing 0x00000002 servicing\Packages\Package_for_KB4524752~31bf3856ad364e35~amd64~~6.1.1.0.cat (f) CBS Catalog Missing 0x00000002 servicing\Packages\Package_for_KB4578952~31bf3856ad364e35~amd64~~6.1.1.3.cat (f) CBS Catalog Missing 0x00000002 servicing\Packages\Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.24540.1.10.cat (f) CBS Catalog Missing 0x00000002 servicing\Packages\Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.26466.1.11.cat Checking Package Watchlist Checking Component Watchlist Checking Packages (f) CBS Registry Error 0x00000005 Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.26466.1.11 Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\ Failed to open store sub key Checking Component Store Summary: Seconds executed: 131 Found 9 errors CBS Catalog Missing Total count: 8 CBS Registry Error Total count: 1 Unavailable repair files: servicing\packages\Package_for_KB2999226~31bf3856ad364e35~amd64~~6.1.1.6.mum servicing\packages\Package_for_KB3050265_SP1~31bf3856ad364e35~amd64~~6.1.1.9.mum servicing\packages\Package_for_KB3124275~31bf3856ad364e35~amd64~~6.1.1.0.mum servicing\packages\Package_for_KB3150513~31bf3856ad364e35~amd64~~6.1.1.5.mum servicing\packages\Package_for_KB4524752~31bf3856ad364e35~amd64~~6.1.1.0.mum servicing\packages\Package_for_KB4578952~31bf3856ad364e35~amd64~~6.1.1.3.mum servicing\packages\Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.24540.1.10.mum servicing\packages\Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.26466.1.11.mum servicing\packages\Package_for_KB2999226~31bf3856ad364e35~amd64~~6.1.1.6.cat servicing\packages\Package_for_KB3050265_SP1~31bf3856ad364e35~amd64~~6.1.1.9.cat servicing\packages\Package_for_KB3124275~31bf3856ad364e35~amd64~~6.1.1.0.cat servicing\packages\Package_for_KB3150513~31bf3856ad364e35~amd64~~6.1.1.5.cat servicing\packages\Package_for_KB4524752~31bf3856ad364e35~amd64~~6.1.1.0.cat servicing\packages\Package_for_KB4578952~31bf3856ad364e35~amd64~~6.1.1.3.cat servicing\packages\Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.24540.1.10.cat servicing\packages\Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.26466.1.11.cat now, this is probably due to my not so appropriate "fix", but simplix also failed to fix this issue (I don't know if it's suppose to fix such inconsistencies or not)