I got back into this machine today, same issue, says there are three prerequisites, but they are already installed. I couldn't find how/where to use the Spoiler feature. Also, tried to find a way to grab the text out of the Update History but no luck, so this it just the last 8 months or so. Oddly, it shows some recent updates.
Thanks, I saw in the installed updates list at least two of the three were able to be found. I'll let you know if I find success, but it is a remote machine and I need someone on the other end to initiate a session, so may be a while.
Thanks for your response ! After many test, many installation/reinstallation of the WUesu, etc etc..Everything is now working fine ! And Bitdefender is making some problems too.. I need to exclude some folder to be sure it's working.. Thanks !
Hi snofte, I had to work this last weekend. I have finished my command file which will resolve your issue. First, I need to test my command file since I can recreate your issues of thousands of files in the PendingRenames folder, simply by running SFC /scannow. While doing so won't generate nearly the same number of files which you are seeing, I already know from recent experience that performing the SFC /scannow command will generate around 8000 files in my computer's PendingRenames folder. Tomorrow, I will perform a backup of my computer's Windows partition. Next, I will deliberately load up my computer's PendingRenames folder by performing a SFC /scannow. Then I will run my script which should force Windows to process all files in the PendingRenames folder. I am extremely confident that it will work. Note that the computer you are working on has 10x my expected number of files which I expect to process in the PendingRenames folder. I anticipate that it may take around an hour to clear out the PendingRenames folder on that computer, depending on its CPU speed.
Risk Assessment... I tried out v10 of the EsuBypass scripts and patches over the weekend on my home W7SP1 system, and I'm happy to report that everything worked perfectly! I was surprised that WU only came up with two updates--a December monthly security rollup and an optional .NET rollup, but since these are supposed to be cumulative, I guess that this is normal and Ok. Thank you VERY MUCH to the developers for creating this! Where can I deposit some thanks in your account? I did a complete disk backup before I put this bypass software on my PC, to be safe. But, reading that the bypass cannot be removed after you have used it to install any ESU's makes me a little nervous--If MS comes up with a way to break this bypass system, will the result be a dead and unbootable system, or will you just not be able to get any more updates? I could easily live with the latter, but a dead PC is pretty devastating. If this happened a year from now, I would have backup images leading up to that point, but everything from December 2020 on would have the bypass software and updates obtained with it. Would I have to do a complete reinstall of W7 and all application programs, pulling the data files from the backup images? That would be painful and take weeks to do. Does anyone have any assessment of the risks involved in using this bypass software? I'm not as much worried about legal trouble from MS as I am of ending up with a dead PC someday. Perhaps a basic explanation of how this system works would help. I'm not criticizing the software or project in any way--I think it is wonderful what has been done. I'm trying to think about the future. Thank you so much.
They can only prevent future updates like they did in September and we had to update the ESU Suppressor
But it's otherwise not a security update itself and only necessary if you're having issues installing certain ESU packages and new BypassESU versions?
Anyway, I would still like a link to the post about the NDP fix in case I run into this issue when prepping a new system for Windows 7. Perhaps the main post could be updated to include it?
Hi snofte, As mentioned, I had to work all weekend. I have a lot on my plate for the next couple of days as well. Yet hopefully I will have the time in the next two or three days to deliberately replicate your issues then test my command file which will resolve your issues. Needless to say, this first requires me to make a full backup of my Windows 7 OS partition. Only then will replicate your issue by populating the PendingRenames folder, and then test my command file which will force Windows 7 to clean up the PendingRenames folder. My target for posting a tested command file script is by Christmas eve.
# BypassESU v11 - Implemented .NET 4 ESU Bypass v5 - Note: to update from v9/v10 to v11, you would only need to run option [7]
Maybe i think PreferExternalManifest registry cause the same issues for NT 6.0 too and Vista would still need the IFEO hook
I can't update the image via Wim-Integration.cmd from v10 to v11. system: Windows 10 20H2 (19042.685) x64. It says done but the file doesn't change anything.