is it possible to create a patch to get updates from embedded poready and standard win 7 ? and to integrate it to .wim
I hope that someone can help for Win 7 Embedded updates. On Patchday July KB5028939 (NET Framework) became not installed with error-code 645 on Windows-Update. Also dotNetFx4ESU_Installer_u.zip don't work - error-code 1605. Other updates (KB5028240 Monthly Rollup and 5028264 Servicing Stack) installed fine without errors. Hve someone an idea how can I solve the problem?
It is cumulative rollup for all version of Net including 4.7. Unless you didn't have Net 4.8 installed, you don't really need 4.7 updates.
Code: Error 1719.The Windows Installer Service could not be accessed. This can occur if you are running Windows in safe mode, or if the Windows Installer is not correctly installed. it just fail to start or access msiserver service for some actions nothing i can suggest to fix other than sfc /scannow
I recently ran sfc /scannow, and I also cleaned the system heavily, because I was getting error 1719 for virtually everything. And nothing helped. Then I realized that it was because of ".NET 4 ESU Bypass". And so I removed it and no longer received 1719 errors for anything else. Now I only receive it for .NET updates and nothing else. I suppose this script temporarily installs ".NET 4 ESU Bypass" prior to running the updates, and that's why it keeps receiving that error. I always get this error when I have that registry key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\msiexec.exe" in place. But, as I understand, these updates cannot be installed without this hack? But when it's installed, it causes the 1719 error. So it's kind of a dead end loop. The updates need that registry key to be installed, but having that key causes 1719 in any MSI installer including the .NET updates themselves.
This means msiesu.dll is not compatible with your OS for some reason (or AV still block it) you can use .NET 4.8 Repack instead https://forums.mydigitallife.net/goto/post?id=1796465#post-1796465
YES, I already had this with the penultimate patch. I often put duplicates of hidden updates: whether from windows defender or others. After a while, it doesn’t appear anymore. At the moment it’s not windows defender that comes back, but some updates. Better to have more than none.
Had you actually read the article that you linked, you would see "NOTE: The vendor considers this a low severity issue". Had you looked up why that might be, you would find explanations in line with what acer-5100 just shared. You could have and should have done both before posted a minimalist, cherry-picked message here with 90% of the critical context censored by lying through omission. Go fear monger somewhere else.
Really threatening issues will be patched by them, regardless if it's out of support. They have done so in the past, for XP.
What the hell is the problem with you guys? I just provided information about the vulnerability and hypothesized, not suggested to do anything. Everyone has the right to decide for themselves what they want to do, I'm not encouraging or forcing anyone to do anything. Your accusing me of anything simply has no basis in fact.
Not to be pedantic but you didn't start with "take a note about this vulnerability", you started with "time to move to windows 10" which is an exaggeration, to say the best. So don't blame other people (who responded with polite and informative replies)
Btw, got tired of not being able to get Win7 WU ESU Patcher to work so I removed the ByPass from v12, copied the contents of WU ESU Patcher's BIN folder to the BypassESU-v12/BIN folder. Running ByPassESU it did seem to run successfully... Long story short... don't do that. It broke wuauserv (Windows Update) service. Managed to fix it, but again, don't try this at home.