.NET Framework Rollup updates are chained i guess for some reason when you installed the latest, Windows Installer reconfigured all installed updates (hence the date changed) Office updates have similar behavior nothing to worry about only one .NET Framework 4.x can be installed, in this case it's 4.8 which is the latest and replace all 4.x versions that .NET Detector is misleading
Moin @ All! My May 2023 ESUpdate experience for Windows 7 Pro SP1 x64 systems: "Licensing method": KB4528069 & "new" BypassESU-v12 "Installing method": Manual download and installation via Microsoft®Update-Catalog KB5026366 (Cumulative Security Update for IE 11 for Windows Embedded 7 Standard / Windows Server 2008 R2 SP1) -> succesfully installed KB5026426 (Security Only Quality Update for Windows Embedded 7 Standard / Windows Server 2008 R2 SP1) -> succesfully installed The following additional updates were offered by the Microsoft servers via the Windows Update Search and were also successfully installed: Security Intelligence-Update for Microsoft Security Essentials. @ abbodi1406: Thx for your support! Great job!
Thanks a million for putting my mind at rest abbodi1406. My computer has been working fine during these last months so I didn't hit the panic button...but it bothered me that I couldn't understand why it had happened. Many thanks again.
What is the difference between Bypass 12 and 12_u? When I install 12_u over 12, it only gives the options to remove WU ESU Patcher and .NET4 ESU Bypass.
Need help please, I have enabled BypassESU-v12_r and downloaded via the Windows 7 WU (2023-05 Security Monthly Quality Rollup for Windows Embedded Standard 7 for x64-based Systems (KB5026413) that appeared when I booted Windows, it downloaded nd when I restarted Windows told me that the install had failed. How do I get this May Update to install correctly? Should I just forget the nagging Update message and just download it from the Catalog and install it that way?? Any help is appreciated
Take a look at responses #7363 and #7371 on this forum: https://forums.mydigitallife.net/th...dates-eligibility.80606/page-369#post-1785607 https://forums.mydigitallife.net/th...dates-eligibility.80606/page-369#post-1785705 For starters, if you have a hardware component reporting with a missing driver file, it can bring installation problems with the Monthly Rollups. Resolve this condition before attempting to install that monthly rollup again (on WU, if you've already downloaded the main package it just needs to be selected again to be installed.)
Fixed for offline integration https://forums.mydigitallife.net/th...dates-eligibility.80606/page-352#post-1777401
Thank you so much for replying. I solved this by downloading the Monthly Rollup for the catalog, and installed it that way, and voila, it installed successfully. Again, thanks
Does Microsfot Update catalog still works for you? I get zero search results regarding https://forums.mydigitallife.net/th...dates-eligibility.80606/page-351#post-1777316 Or any other KB search for that matter.
It works for me with Firefox. But there was a temporary issue you mentioned. Now it seems that it is fixed and everything works again.
Everything is working (IE11_Maxthon_Opera_Firefox). ... if you see a "white sheet" in the catalog, most likely a lot of pages are open in the browser (I have so often) => or close and open in a private window, either another browser.
You can try another browser or you can try to change usergent string (eg about:config , general.useragent.override in Firefox). Clearing cookies and data (Ctrl + Shift + Del) could also help. But these issues are random, and I confident that it is their (Microsoft) issue not ours.
I tried it now @ 06:00 GMT today (17-05-2023) with "2023-05" and I initially received a results listing in a Latin family language (Italian, Spanish, etc.) Pressing the "Search" button again with the same "2023-05" then gave me the results in English. I'd be speculating on the possibility that Microsoft maybe had a server problem (or several) for the past few days of some kind (DoS related....?) or it's a webpage scripting bug that's propped up with any new security mitigations. I recommend, when it's working to grab (download) the KBs and driver packages sought after quickly before another loss of access transpires.