Does the ESU-Bypass affect the results of SFC? The reason I ask is that the scan always shows Code: C:\>sfc /verifyonly Beginning system scan. This process will take some time. Beginning verification phase of system scan. Verification 100% complete. Windows Resource Protection found integrity violations. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log When I check the log, I don't see anything flagged as an error. The system runs fine as far as I can tell.
Yes, finally I hear from a suffering fellow. 2020-11 auto-update is resulting in very slow boot. Not so before installing ESU patcher and receiving the nov update. Uninstalling esu patcher afterwords does not help. Tried everything under the sun, cant get it back to normal boot time.
This says enough, it's not ESU related, maybe it's Update related. You can do an inplace upgrade using an updated to last month ISO (from before your long boot) and see if all is solved.
I have a backup hdd from before the esu and the 2020-11 update (with normal boot time). Not quite sure what you mean with "inplace upgrade using an updated to last month ISO". Maybe I could, most humbly, ask for some guideance ?
December 2020 Windows updates are out. WU only offered the monthly quality rollup so far. Installing it now.
Monthly Quality Rollup and Servicing Stack Update installed smoothly here. Win7 x64 Ultimate Thanks again!
Can anyone get the kb4592510 (2020-12 servicing stack update) to install? It fails. Wonder if it's related to the bypass or MS changed something. EDIT: I retried installing manually, no issues.
A new world record on one machine; a poorer result on another. I have two Lenovo S20s. One has an Intel Xeon X5675 (@3.07ghz) and 18gb RAM. It's pretty fast, but this was, as I wrote "a new world record" for me. The other is pretty much similar in terms of hardware (Xeon 5670 @ 2.93ghz / 12gb RAM) and software, but for some reason ... I'll start with the "happy" story: WU found the the two files and installed them in a flash. I was surprised to see that WU only offered me KB4592471 (the Monthly Quality Rollup - about 355mb), but that's all there was so I went for it. The download took about three minutes (my current download speed 95,932 kb/sec). More amazing was that it installed in about 2; the longest part was creating the restore point. After the reboot, I ran WU again and was offered the SSU (9mb), which installed w/o incident. When everything was finished, I uninstalled the NET component, which I hadn't needed anyway. Now for the less-happy report, though it's not really soooooo bad: On the other S20, WU told me no updates were available :-(. The solution was that I simply went to the M$ Catalogue and downloaded the two files manually. Installing the Quality Rollup took 3-4 times longer, but was otherwise uneventful. The SSU, of course, was much faster. What surprised me about this installation was that, unlike in the past, both showed up as being successful in the update history. Previous manual installations had invariably resulted a "Failed" in the update history, although "Installed Updates" always indicated that they were, in fact, installed. Go figure. Anyway, all's well that ends well. Let's see how things go on my laptops. Again, my most sincere thanks to the devs. You should get a Nobel Prize for this!
December Updates installed without any issues on my 2 machines: Win 7 x64 Ultimate Win 7 x32 Professional Just a bit offtopic question, anyone knows why the KB4592471 IS 350mb for x64, but only 250mb for x32 systems? cheers, thanks again for another great month of updates
In general, Windows x64 also has a folder of 32-bit system files for compatibility with existing 32-bit windows programs. Therefore, patches for Windows x64 also contain the patches for the 32-bit files where applicable, this makes the x64 patches larger.