Using this dotNetFx4_ESU_Installer_r, I got ==== ERROR ==== .NET 4.5.2 is the minimum supported version. I checked HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full and found that in my case Release was 378389, which means line 28: if %_ver% lss 379893 goto :E_Min applied and then the error. I deleted line 28 so line 29: if %_ver% lss 393297 set _tag=NDP45 could be executed. Luckily, it worked so, I am letting you know. By the way, this was on Win7 Ultimate x86 with .NET Target Version 4.0.0 and .NET Version 4.5.50709 applying KB4565616v2
Yeah it's not always evident whether it is installed correctly or not. The new "r" version of the dotNetFx4_ESU_Installer runs the .NET installer unattended so if there's an error during the installation process then you won't see the usual log displayed in the .NET installer's last summary page. Nor the script will show any of such errors unless you run it from a command prompt (and not from Explorer or other shells). If you do the latter you won't see any message since the script's window closes immediately after the process. You can though check the result in a log file named KBXXXXXX_Date_TIme.html created in AppData\Local\Temp. I added a pause command to line109 to avoid this to fool me again. Code: if %ERRORLEVEL% neq 0 if %ERRORLEVEL% neq 3010 echo Failed. Error code: %ERRORLEVEL% pause goto :eof
Sorry @abbodi1406 for the mention but so far I've been getting no replies on why I'm unable to install a security update on an Ultimate system while an Enterprise system has no issues installing it.
KB4565539 is the July security only cumulative update. Maybe you have the July security & qualtiy rollup already installed so then the security only rollup is not applicable. Check the "Microsoft Windows" and "Microsoft .NET Framework 4.x.x" groups in the list of Control Panel -> Programs and Features -> View Installed Updates to see what you have or have not installed. If unsure, post a screenshot of the latest items of each group.
I have now installed a completely new Windows 7 Professional 64bit operating system. I also installed all the normal updates, and install all the device drivers manually way. I have also activated the Windows 7 ostamallani original license code. I have not yet installed any antivirus program because we agreed that we will first install the Bybass and Npd updates. I have put you a private message, so could you be in touch with me out there when you have time? Thanks! Regards Mazufa
@eMTeee the revived dotNetFx4_ESU_Installer.cmd don't close immediately (unless there is batch or path error) it run the exe update and wait until it finish, then show the code if there are any error @JasWat1728 did you installed latest servicing stack update first?
Sure. I said that after showing the code if there are any error, the script seems to end immediately - which means if you start it from e.g. Windows Explorer (and not call from a Command prompt opened by yourself) as most users would do, then the command processor window that runs the script closes immediately after the script finished so you won't have a chance to see the printed error code, if there's any.
@eMTeee The cmd keeps opened till all ran, check the gif: https://forums.mydigitallife.net/th...dates-eligibility.80606/page-195#post-1610324
Yeah, in a successful installation, certanily. The script may take a different code path when an error happens. Anyway it's not a big problem at all. I just wanted to mention a possible reason of why Oliver did not realize that the install was unsuccessful for him. It happened to me so it may happen to others. Thanks for this solution and keep up the good work @abbodi1406 !!
