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.
That doesn't mean the file is absent. (If that was the case it would simply be not in the list of files at all. For example, look at the KB article and the file listing for Windows 8.1, it shows only 2 files and the other files are simply not listed because they are not used there.) The "not applicable" under the file version column means the file does not have a version number and the one under platform means that 32bit vs 64bit is not relevant. Both of these make sense since if you view the file in Notepad, it is basically a text file, and text files generally do not have those features. The eventID 1542 does look like the similar problem that was seen in the past. I'm not sure why it is "from time to time" rather than consistent. It does generally mean that some permissions thing is not set correctly at the times it does appear. Could you post the other ones too? And the recent 1502 you mention - or was that a typo and you mean the 1542 you posted is the one happening after system restore cleans up the mess? Also it is the Feb updates KB4537813 (security only) or KB4537820 (rollup), not the Jan ones nor any IE Cum that triggers the problem? Here's another thing to try - after system restore cleans up and reboot, try to manually install one of those updates without first doing the bypass stuff. It should fail to install. Reboot anyway, maybe twice. Does the profile still get hosed?
Wow man. Just reinstall. Snatch what you want and reinstall. I started a New 7 pro October with 2 more. My games are good on 7. COPY the saved files in case a reinstall has to be done! Steam is on 7 and 10. Storage has all my software. A day a broke pc can be fixed better than new. Waiting on March. I wouldnt have my system perfect without this page. I went through this with XP. Was a ride. Thanks!!
That's correct. The paid ESU may not work either under these circumstances. Profile corruption tends to either be fairly EASY to correct, or quite DIFFICULT to. There's very little in between based on what I've seen. Part of the reason is such a wide variety of things can contribute to creating this kind of condition. For now trying to work with w2k4eva on this may be your most promising avenue since it is directly related to a prior updating issue he experienced that caused a like condition. So at least this offers some kind of identifiable and related footprint. But short of this, it'll be back to the pick and shovel method of attempting various measures that have been known to correct this type of issue, or of course turning to bigger corrective guns like a repair install or a format + re-installation of the OS. Unfortunately no one shoe fits all cleanly when it comes to profile compromisation.
Quick question @abbodi1406 Is it possible to do backport the new bypass method for windows vista? The only extra step that it's probably needed is to trick windows update services to "think" that you have server 2008 installed. That bypass would make Vista a "supported and safe" operating system once again and a viable option to extremely old devices with vista COAs.
@craftech Format your machine and install clean Win7, or don't but please, stop posting in this thread or you will be reported
Server 2008 updates do not get "fully" installed on Vista, i verified this myself there is no point into tricking WU or the OS itself that your are using Server edition, the updates will not be complete and the test update KB4528081 is available for x64 only so, i will prepare Bypass-v5 variant for Server 2008 anyway