I'm aware of all that. I always use Simplix 20.9.10 (or whatever the newest version is) to update a clean install of Windows 7 Pro SP1 64-bit. I was just trying to explain what the install and update process looks like when NOT using Simplix 20.9.10. It's a much longer process, and not the way I would recommend people do it. However, many people still do it the old way, so I like to have the steps available for them.
I showed that too, it takes 25min to do it by Bypass v9 on WU (would even be much faster when people ran the updates manually) and there is no need for v5 and all the updates you showed, only the may+ ssu, the ESU licensing preparation package, the latest rollup and the latest ndp4x update are needed. Bypass 20.9.10 is latest. And the dotnetfx48 WA won't take on starter/basic/premium, it needs the .net ESU bypass to have it show up as installed.
That was a typo on my part. Simplix 20.9.10 is what I meant. I've corrected my previous reply. AFTER I do a clean install of Windows 7 Pro SP1 64-bit and get it up-to-date to January 2020, these are the ONLY updates I need to install to get it up-to-date to September 2020? If so, where in the process is BypassESU-v9 put to use? I'm guessing it's after KB4538483 and before KB4577051.
Let's see if I got it right what you said. AFTER doing a clean install of Windows 7 Professional SP1 64-bit and getting it up-to-date to January 2020 (including KB4536952 SSU), I deploy the following in the order listed:
Thanks for the 7-minute video. I watched it twice and didn't see where KB4575903 (ESU licensing package) was installed.
Is there any way of resetting your video to 0:00 and watching it from the beginning? By the time I load this page and then find the video, several seconds of it have passed, so I miss the beginning of it.
I can tell I'm becoming a pest, so I'll put this to an end. Thanks for your replies and the video. I think I have it figured out.
I came accross the following "problem": It might not be a real problem to everybody, but I thought I'd share it anyway. In all my videoplayers the timestamp which pops up above the "seeking slider" was not really visable and kept flickering. This made it very difficult and frustrating to search for a specific scene or time in a video. I found out, that this was caused by the latest update kb4577051 (september rollup) I have uninstalled this update using BypassESU-v9-AIO, and after that the irritating effect was gone. Than I tried kb4577053 (september's "security only" update and that gave me the same problem again. So, allthough this may not be of importance to everybody, it may very well be that there are similar visual effects or missing stuff in other software that may be caused by these updates. Given the fact that the oktober updates are comming up soon, I would consider uninstalling the september update (either rollup or security only), before istalling the october updates. The players I use are MPC-HC (media player classic) and VLC player. Also, I use Windows 7 in "Classic Theme" (I thought I'd mention that because maybe the effect does not occur when you use other settings) I had this problem with two different machines. One running Windows 7 Pro, the other one running Windows 7 home premium.
It may be a problem with the actual update but is not bypass related, there is a full windows 7 section on this forum. 2 weeks to go.
I'm also sure it has nothing to do with the Bypass. It must be in the actual update. I forgot to mention that. I will look for the other section on the forum as well. And you're right: I thought it was one week, but it's two weeks from today! The "second tuesday" in october will be quite late next month. On the other hand: there will be a BLUE MOON on october 31
Guys, do I need to install this update or hide it, since there are no problems with updates yet? BypassESU won't break? Well, really no one will answer?
That's a 6-yr old update... probably would have no affect on your System at all. It was not a prerequisite for successful operation of the byPASS so I would just hide it.
I would hide it too. There were several versions of that update, but that's all a long time ago. KB947821-v34 was the latest if I'm correct.