Hello, Thanks to the authors. Successful installation V4 (confirmed par KB4528069). But a few moment later Avast Internet Sec. has found IDP.ALEXA.51 in BypassESU.dll (System32)... Such a detection was not appeared when installing V3. Sincerely
The instructions are very clear to those who care to read them. We basically have ~37 pages of drivel.
Spoiler Code: ------------------- | -------------- | ------------------ | ------------------------- Compare / Tool | Custom slc.dll | IFEO BypassESU.dll | Avfr gesu.dll (deprecated) ------------------- | -------------- | ------------------ | ------------------------- Supported Editions | ESU-supported | ALL | ALL AV Interoperability | Safe | Unfriendly | Friendly Performance Impact | None | Slight to None | Slowdown TrustedInstaller ------------------- | -------------- | ------------------ | ------------------------- https://forums.mydigitallife.net/posts/1572552/ exclude it
I just ran the V4 download from gitlab through Virustotal which includes Avast and no viruses showed up. Where did you download the BypassESU from?
Same with me. I've got Avast Free Antivirus on my Windows 7 Home Premium and, when I ran v4 of the bypass, Avast gave me no problems whatsoever.
https://forums.mydigitallife.net/threads/windows-vista-bypass-eol-with-windows-update.81026/ maybe for windows 7 with a registry modification in addition to the posready license file it would work combine with the rebuild of tokens.dat
getting error when run install.bat file on custom slc file. It fails to copy that but the other files install successfully. What does this mean? and do we have to install updates by going to windows catalogue website?
Check the AV logs. There still aren't any ESU updates, and on the second post of this thread are the prerequisite updates listed.