Sorry to be a bit dim, but how does one actually *install* BypassESU? I have downloaded and installed the relevant MS security updates, as specified. I have also downloaded and unpacked the BypassESU zip file. This is where I get stuck. I have clicked on the superUser64.exe file in the bin folder and all I get is an administrator dialog box and a flashing cursor. I am not actually sure how to run/install the program. Can anyone help? Thanks so much.
I've managed to download and install on my Window 7 64 (after installing the patch yesterday). Some of the updates installed fairly quickly but some of them took ages, the larger one (5th one) took an hour. It looks like nothing is happening but then it gets downloaded and installed. This is longer than normal for sure. Security Intelligence Update for Windows Defender Antivirus - KB915597 (Version 1.307.2344.0) Windows Malicious Software Removal Tool x64 - January 2020 (KB890830) Security Update for Microsoft Office 2013 (KB4484227) 64-Bit Edition Security Update for Microsoft Excel 2013 (KB4484234) 64-Bit Edition 2020-01 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4534310) Windows Malicious Software Removal Tool x64 - January 2020 (KB890830) Plus this one just now, 2020-01 Servicing Stack Update for Windows 7 for x64-based Systems (KB4536952)
So, there is no need to keep cluttering this thread, about a very specific subject, with updates reports for the last regular updates yesterday. The fix needs an update and the kurwica team will be investigating it as we speak.
Not for nothing, I'm a little suspicious of that last minute Servicing Stack Update, KB4536952. It just doesn't make sense to me. Why would Microsoft release a Servicing Stack Update for an operating system that isn't supposed to receive any future updates? It's an oxymoron. In my opinion, either it's there to provide support for the users who buy into the ESU program, or it's there to lock down any future updates for normal users. Maybe a little of both. I'd like to see someone dig into that can of worms and find it's true purpose.
When I tried to install KB4490628 yesterday, 1/14/2020 I got the message that it was not applicable for this computer. Is it necessary for the installation for the patch? and which one on the list do I use I tried the last ones on the MS catalog for x86 and x64 but neither one would install. Any suggestions?
I can tell, the failing of the ESU Bypass is not failing because of the new SSU, i did a test for that.
Again, non of yesterdays updates were ESU updates, and KB4490628 is the previous ssu, the new one was probably already installed, making the old one not applicable.
I installed the last non-ESU Updates today, rebooted, then the prerequisite updates to BypassESU. Then ran BypassESU (as admin, of course) and finally the test update (4528069) which went through without any problem. I have checked for the current version of calc.exe (apparently being an indicator of a successful install of 4528069) and it has the version number said to be associated with the ESU elegibility "test" update. I have no idea why this seems to have failed on other users' machines.
Hi, I followed first post instructions, KB4528069 failed. Rebooted, still fails. Is there a log file somewhere that could help you guys if I share it ?
You've installed KB4534310, the BypassESU, and then KB4528069 installed successfully?? That'd be a first for this thread, I think. What version of Windows 7 do you have? Pro, Ultimate, etc? 32 vs 64bit?
Well then, I tried installing the bypass and then that update... got the same results @Enthousiast produced. I've then removed the bypass soon after. I'll just wait for something new.
Just tested this on Win 7 pro x 64 the Bypass tool installed fine The only update i had missing was KB4519976 Monthly Rollup Update)-Oct 2019, that wouldn't install & said it wasn't needed. All other updates installed. I'd installed all the updates from January's patch including the new Servicing stack update KB4536952 as well as the January 2020 Security Monthly Quality Rollup KB4534310. Bypass tool installed fine but the testfile KB4528069 failed. As reported by others.
So sorry, I most likely was misled by my update history. It looks as if 4490628 and 4474419 were already on my machine, whereas -4310 came after running BypassESU. So, if -4310 is the culprit for preventing the test update from installing, it was clearly installed later than KB4528069 - only the two other prerequisitive updates came earlier. BTW, update history says they both were already installed in November, but none of them was denied installation when I "installed" them today.
It should be in the "bin" folder. I'm no expert but this may have happened when you ran the bypass without unzipping its contents first.