Bypass ESU Longhorn

Discussion in 'Windows Vista' started by abbodi1406, Nov 17, 2019.

  1. huoqianyu

    huoqianyu MDL Novice

    Dec 20, 2015
    7
    5
    0
    May I ask what are the reasons why Windows Update reports error code C8000266? Is the only reason that Datastore.edb has a maximum file size limit?

    I'm asking this question because, before applying the ESU License Preparation patch, my freshly installed Windows Server 2008 SP2 can detect all patches before the ESU support start date, but as soon as I apply KB4474419, KB4493730 and activate the ESU license (either use TSForge or use BypassESU), Windows Update only reports error C8000266with no other results, no matter how many times I tried.

    I did apply the Vista datastore.edb fix, but nothing changed afterwards. During the execution of the script, it prompted that the system denied it access to the wuaueng file, and I needed to manually change the owner of the file to Administrator to resolve this issue.
     
  2. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    17,494
    92,798
    340
    It's not related to the files size itself
    https://forums.mydigitallife.net/threads/restore-windows-update-for-vista.82336/page-14#post-1774183

    you should install ESU servicing stack updates on stages, and do not install both ESU License Preparation Packages together
    see the tips in ReadMe

    this might only work for x64 only, even with the datastore.edb fix
    x86 handle or require memory that might not be available
     
  3. huoqianyu

    huoqianyu MDL Novice

    Dec 20, 2015
    7
    5
    0
    I have a guess, I wonder if it is correct?


    By using MAS to view Activate IDs in Server 2008, I found that even if only the first of the two ESU patches (KB4575904) is installed, the Server-ESU-PA (Year 1-6) certificate will actually be introduced to the system.

    And Server-ESU-PA (Year 1-6) is the ONLY ESU license that MAS has ability to activate, This is because MAS only “knows" PA key, but does not know key like ESU Year-1 or Year-2, and cannot construct a FakeCID.

    In this case, even if I did not install the second ESU patch, Windows Update would detect ALL six years of patches and the system would be unable to process them.

    Is the actual situation as I guessed? Thank you.
     
  4. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    17,494
    92,798
    340
    @huoqianyu

    That is probably correct

    ESU Preparation packs are used to determine the updates applicability (offer updates at the end of search)
    but they don't control the delivered updates metadata

    so i guess "installing SSUs by stages" is the only way to reduce the metadata load
    or finding unusable Year 1-3 keys and activate them with tsforge before Server-ESU-PA
     
  5. xrononautis

    xrononautis MDL Senior Member

    Mar 30, 2021
    392
    240
    10
    If you skip KB4575904 and go directly for the second ESU preparation package you won't need the datastore fix. The only downside is that the 2020-01 cumulative will pop up.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. huoqianyu

    huoqianyu MDL Novice

    Dec 20, 2015
    7
    5
    0

    I searched the Microsoft Update Catalog and found that the descriptions of the two patches KB4575904 and KB5016891 both show that they replace KB4538484.

    However, Microsoft does not seem to say whether there is a replacement relationship between the two patches KB4575904 and KB5016891.

    I'm not sure what Microsoft intended. The Microsoft Knowledge Base page for KB5016891 only says that its prerequisites are KB4474419 and KB4493730, but it doesn't mention KB4575904.
     
  7. huoqianyu

    huoqianyu MDL Novice

    Dec 20, 2015
    7
    5
    0
    I have been trying various methods for more than half a month to try to solve the 0xC8000266 problem when detecting ESU updates on Server 2008, but I have never succeeded.

    I tried to use BypassESU-LH V8 on a Server 2008 system that has an activated ESU license. The reason I did this was that I thought the datastore.edb fix script that comes with it might solve this error, but in fact I didn't get any improvement.

    I ran PatchWU.cmd separately, but it immediately exited because it didn't detect C:\Windows\System32\sle.dll. I think this may mean that when using BypassESU, it doesn't actually patch the logic related to datastore.edb.
     
  8. huoqianyu

    huoqianyu MDL Novice

    Dec 20, 2015
    7
    5
    0
    I find it strange to be honest, I don't think Microsoft is unaware of the datastore.edb issue on Server 2008. Not sure if they have a patch specifically for Server 2008 PA running on Azure.
     
  9. huoqianyu

    huoqianyu MDL Novice

    Dec 20, 2015
    7
    5
    0
    Well, I finally found the problem, and the answer is so simple:

    After using the tool to patch wuaueng.dll and installing updates, a new version of wuaueng.dll in the updates replaced the original patched version on the system, which made the patch invalid.

    It's unbelievable. If I hadn't accidentally seen in the folder that the creation date of wuaueng.dll changed from 2025 to 2022, I think I would never have found out the reason.