group C majority non techies and techies that think they are techies waiting for that 1 button on desktop to click every month and voila automatically downloads and installs updates or install once and every month automatically goes out and searches and installs updates
Newbie here trying for the 1st time to get February Updates. I have yet to try any other method. OS is Windows 7 Ultimate 64-bit. Here is what I did: -Installed BypassESU-v5-AIO -Installed KB4538483 -Ran Windows Update and it found 0 new Critical Updates. -Checked if my system had all prerequisites. -KB3138612: already installed -KB4474419: already installed -KB4490628: already installed -KB4536952: not installed -Tried installing KB4536952 but get the message that the update is not applicable to my computer. That must be why BypassESU-v5-AIO failed. My question therefore is how do I install KB4536952? Thank you.
Are you sure you tried to install the right version (x86 or x64) of KB4536952 on your system ? This update is indeed a prerequisite for KB4537820.
Try to remove the ESU Suppressor + WU ESU patcher from v5 and install the jan. SSU (KB4536952) and next install the bypass + wu patcher again and check WU, if WU still doesn't offer the 2020-02 rollup then do this: Code: Reboot and try WU again, if this doesn't work, do: net stop wuauserv delete c:\windows\softwaredistribution reboot run WU
Yes, but what does that have to do with the (failing) removal of KB4528069? I am trying to find what you originally were asking regarding the Feb. SSU, can you help me, did it fail to install on a previous attempt?
Even after removing ESU Suppressor + WU ESU patcher, KB4536952 still refuses to install. I did download KB4536952 64-bit version. Are you saying that stopping the wuaserv service and then deleting the softwaredistribution folder eliminates the need to install KB4536952?
Don't know where you got that from, KB4528069 is the actual ESU suppressing update, when that one is installed successfully, using the bypass v4, after it, v4 is not needed anymore, nor is v5, only for the WU patcher.
As told before, your problem has nothing to with the bypass but with the updates you install, the bypass doesn't cause temp profiles, you did that test already, install bypass, all reboots fine, install the rollup, errors appear. Your install clearly has permittion problems, given the info you've posted.
I don't understand why I can uninstall any existing Windows Update and then reinstall it without a problem prior to installing any Bypass. What changes with permissions post Bypass?
You couldn't open log files, get-packages couldn't create the packages.txt file on your desktop, scanhealth found 500 errors, iirc, when an ESU update is installed you get a profile problem, conclusion, your system is not ok.
I did get a packages text file which I attached to a previous post. I attached it again. Do you have any suggestions about how I can tackle the problem? Also, Here is my CURRENT ScanHealth result: ================================= Spoiler Checking System Update Readiness. Binary Version 6.1.7601.24499 2020-02-24 18:35 Checking Windows Servicing Packages Checking Package Manifests and Catalogs Checking Package Watchlist Checking Component Watchlist Checking Packages Checking Component Store Summary: Seconds executed: 676 No errors detected
You're right where you want to be even if you're doing a little overkill there. You only need either the monthly rollup KB4537820 -or- the security only KB4537813 + IE cumulative update KB4537767, not both. These last two are already package within the first, that is within the monthly rollup, so they're either being ignored or gleefully overwritten. No real harm in the end mind you, simply unnecessary. Just choose one or the other going forward. If you're now patched with the v5 bypass, you'll only receive the monthly rollup via WU so that choice issue will now be taken care of for you. At least as things stand. No you can leave it if you so choose. The v5 bypass tool is smart enough to work around it - or with it - as necessary. The biggest clue is no one else is indicating they're experiencing this same issue. That strongly suggests the problem you're facing preexists on your system, perhaps in a prior dormant state waiting to be effected by just the right trigger, and is not being caused by bypass tool manipulations. Why that particular rollup is invoking a temp profile condition is anyone's guess. I would try some of those things I mentioned before. Enthousiast also suggested a repair install of the OS earlier. This may help, or it may not since unfortunately many settings and personalized tweaks and files of varying sorts will remain intact with an OS repair overwrite, any of which may be contributing to the condition you're seeing. A full format and clean (re)installation of Windows OTOH will almost certainly cure the issue, but that comes at a heavier price -- a lot more recovery work and requirement to reinstall all of your programs. If you have a simple enough setup, this would be the way to go in the name of expedition. For many though, this would be an out of the question proposition -- or the ultimate nuclear meltdown option. If you had a recovery or drive image dating back not too far, that might save your bacon likewise. All I can tell you is temp profile issues can be a bitch to correct if a second system restart - and the profile list registry correction - don't do the trick. After that you have to try anything and everything that comes to mind, as quite a few things can end up invoking this maddening condition. Again, is Event Viewer revealing any clues?
The only errors in the Event Viewer that seem to date way back periodically is [1542 attributed to USER "SYSTEM". Cannot load classes registry file. Unspecified error.] Lots of errors when the failed updates occur (as expected). Can't find profile, etc unspecified. It isn't just that rollup. The Security Only update triggers the same issue. If there is no easy way to address profile issues the paid ESU may not work either. I have that on my video editing computer and it updates just fine.