Hello Is this tools may function with windows home server 2011 (who is a light windows server 2008 for the home users...) Best regard
Correct. Read first message. Bypass try different method for install. With this approach, it’s easier to close the topic and leave users to their own devices. It would be normal to put questions after discussion into a separate topic, but I'm not sure that the forum allows you to transfer single messages in groups while preserving the message properties. Plus, we will need a moderator curator to post such messages. [QUOTE="titou43, post: 1573106, member: 1337892"]Is this tools may function with windows home server 2011 (who is a light windows server 2008 for the home users...)[/QUOTE] Read first message. Do not ask about it, you can check it yourself.
You can also "Watch" this thread, it's an option on this forum (see top right of page), and it will email you whenever someone posts a new message. Although not sure if it will email you if someone only edits an existing post. Can anyone confirm?
So, what about the members who implied that they ran Windows Update after successfully installing both the bypass & test update?
1. The test update has no influence on WU being slowed down by v3. 2. WU was slowed down to a point that it was not workable anymore in v3. 3. Just always use the latest release of that moment.
I guess I should have worded that differently; after uninstalling the test update, with the bypass still installed, should I have Windows Update check for updates?
Why these questions over and over again (not only from you)? There currently are no ESU updates on WU available. v4 doesn't cause WU to be slowed down, so you can keep the bypass installed if you want.
I think because until your post just now, none of the replies I saw were very clear. This should be added to the OP, I would never had asked if I read this yesterday.
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