Ok, now the thread is actually getting off-topic. We already have a thread that covers the nvidia issue.
So no need to take care of them separately? Good! Done... KB5025279 is installed. Had entries for the driver "bthpan.inf" in the setupapi.dev.log "Failed to find driver update". I then installed it from WinSxS using "pnputil -a". After this KB5025279 installed successfully. It's funny, especially since the problem according to the log file has existed for years. But whatever - thank you Ready_Slavik and abbodi1406!
Or use a malware spy certificate driver from unknown peoples from the internet without an summonable address.
Then probably do not use anything downloaded from internet. My certificate is generated following official MS documentation, it's up to you to decide which solution is best. Just stick your comments about trustworth into related topic. As we already drive to offtopic - it's much better to use resigned driver with custom certificate instead enabling TEST mode if you talking about privacy.
I've ran the ESU bypass, was up to date with 2023-01 final 7 patches, and ran the POSReady patches via the WSUS proxy. I am using a VM with snapshots (QEMU) and noticed IE11 broke with an ieframe.dll error after the 7 Embedded updates. Would crash upon starting. Not complaining about anything, but warning others something can go wrong. I ran CHECKSUR and sfc /scannow before and after the updates were installed. Good thing I don't need IE11 so not a deal breaker for me. Maybe an option to use Server 2008 R2 ESUs would have more desirable behavior even though we would get 10 months less of updates? I used the Server 2008 updates with ESU bypass on an updated Vista VM and IE9 never crashed. So maybe Server 2008 R2 patches would fare better? Not sure. EDIT: I got IE11 to run again by disabling and re-enabling under Turn Windows Features on or off, then restarting Explorer, then disabling the IE to Edge redirect in Edge. Maybe the BHO messes with the security updated IE11?
IE11 started experiencing these exact trouble symptoms during the original W7 ESU in July 2021. The same thing happened with Windows 8.1's IE11, yet MS managed to get that version working again for a while in March 2022 but not the Windows 7 version. The blame for it is on Microsoft. I never installed MS Edge on either OS machine too (their October 2021 Cumulative Update "Enterprise Mode Site List To MS Edge Redirection Fix" did nothing for W7 IE11.) Your method to get it running again was appreciated. I, instead went to Control Panel => Internet Options => In General Tab, press the Delete button in the 'Browsing history' section (all ticks in all the boxes when in the next options window, press 'Delete' button.) I gave it a try with 'Start InPrivate Browsing' and it opened on this occasion without breaking. So the current IE11 version from KB5022835 may be alive (also with an "Install new versions automatically" option when you select Help => About Internet Explorer.) Check which Add-Ons it still uses (Select Tools => Manage add-ons => DISABLE possibly unsupported or security vulnerable ones like Adobe Shockwave Object, JAVA Plug-In (2) SSV Helper.) You can use HTTPS Everywhere v0.0.0.1 by Zscaler in W7 IE11.
What a shame you must are for all for us. If you are a decent person you can let us know your summonable address that we can indict you if we have problems with your microsoft fake malware spy certificate driver.
Im a bit out of loop here after 01/2023 than M$ stoped ESU windows 7 updates how can we still update the OS? Should I revert to Embended workaround?
Alrght. First attempt with v9-AIO didn't work out well. Removed it again. So just to have it clear: 1. To try with v12 I start by installing recommended updates 2. In several posts I read that I have to manually install monthly updates before ESU can 'take over' - is this correct? 3. Do I then remove the .NET Framework for later re-install? 4. Do I then install v12 and let it do it's magic? Or maybe use WHDownloader to manually update the system?
1) RE: 4) You really need this new version of BypassESU for the recent ESU security updates that started from 2023-02 (February 2023). I would recommend BypassESU v11 for the original ESU 3-year support era (from 2020-02 to 2023-01), though in practice I used BypassESU v6 (2020-[02-04]), v7 (2020-[05-08]), v9 (2020-[09-12]) and v11 (2021-01 - 2023-01). 2) RE: 2) Yes, it would be wiser to have your PC at the rightful stage to install the final Security Monthly Quality Rollup from 2020-01 before installing any BypassESU for installing the original ESU 3-year security updates. If you need a general list of pre-ESU security updates, take a look at this article # 11007 on this other forum (Windows 7 Hotfix Repository) for answers: https://forums.mydigitallife.net/threads/windows-7-hotfix-repository.19461/page-551 3) RE: 3) It's an ambiguous question, except with respects to BypassESU there has been a .NET Framework v4.x Bypass included since BypassESU v7 (May 2020). During the course of ESU, whenever there are updates that won't install it is recommended to remove the .NET Framework v4.x Bypass temporarily. Then try installing your security updates, and when all successful, you can run the BypassESU setup again and re-install that .NET Framework v4.x Bypass component. 4) RE: 1) If you're using an x64 version of Windows 7, you may discover that you are also being offered Windows Server 2008 R2 security updates. For now, try getting your PC up to date with updating to 2023-01 before concerning yourself about these recommended updates.
Thanks a LOT for the thorough explanations - I wasn't aware that you should keep using/adding/installing the newest version of BypassESU, had just thought that it was like a fix that would keep working. Will definitely go through the hotfixes, have grabbed some already before these questions but I see it make sense to have fixes/updates as early as possible before trying to add never ones.
I did a fresh build from a captured wim which included the latest embedded updates thru April. I forgot to run the LiveOS-Setup.cmd before the capture so I did it via the Wim-Integration.cmd. The install went fine, but my Dism packages.txt doesn't look right. I'm also getting 7 embedded updates offered after running Add_wsus-and-Reset_DataStore.cmd and checking for updates. This may well be related to to what is refected in the messed up packages.txt. I'm not sure at what point this happened or why. Also, the listed updates all look like they are superseded. Anyone have an idea how this can be repaired? Spoiler Code: 2020-10 Security and Quality Rollup for .NET Framework 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 for Windows Embedded Standard 7 for x64 (KB4579977) superseded Cumulative Security Update for Internet Explorer 11 for Windows Embedded Standard 7 for x64-based Systems (KB3185319) 7 package entries Security Update for Windows Embedded Standard 7 for x64-based Systems (KB2676562) 7 package entries Security Update for Windows Embedded Standard 7 for x64-based Systems (KB2813347) 8 package entriess Security Update for Windows Embedded Standard 7 for x64-based Systems (KB3076949) 5 package entries Security Update for Windows Embedded Standard 7 for x64-based Systems (KB3124280) 5 package entries Update for Windows Embedded Standard 7 for x64-based Systems (KB2533552) 2 package entries