Windows 7 Hotfix repository

Well its MS. Early 2013 could mean March too for all i know lol.

 

McRip, these hotfix are superseded and I have not seen in your repo (Removed)

KB2703811-v4
KB2705624
KB2739674-v2
KB2778831
KB2786400

I have not seen these 2 hotfix (Added)

KB2771254
KB2777403

Thanks for your great work

 

And KB2492386 is only superseded for x86. The x64 version contains "windows-a..ence-mitigations-c2" not présent with KB2762895.
Why this hotfix can be found in WU Satisfy, is this normal?

And why KB2695321-v2 is removed? any hotfix replaced it (registry keys), info from komm.

Thanks

 

@burfadel
Is your Installer For Windows Updates V27e now capable of slipstreaming WindowsUpdateAgent30-x64.exe into an offline Windows 7 SP1 image?

Thanks for your answer.

 

No, I completely forgot about it . I'll add it in for next month's patch Tuesday release.

 

You need to login to view this posts content.

 

The whole Repository will be offline till tomorrow due to a change of the DNS Servers. This also applies to all subdomains of cesidian.info.

 

The repository should be available worldwide now as well as all subdomains.

 

Off Topic: can anybody spare FTP space for moi?

 

How many files do you have? How big is the size alltogether?

 

In between 2-3 GB, all installer repacks and XP integrateable addons

 

Will send you the login data tomorrow. Please send me your email. Ain't got no time right now.

 

[Removed by OP]

 

@rickendo. You got email

 

Yes I saw that sorry for not replying before but I had to head off! Someone else has the exact same issue reported by PM, I thought it was an isolated incidence. Technically it shouldn't happen, but something on the system must be messing around with how scripts are run. If you run the script from (made up example location) C:\Script\Location the commands in the script should be executed in the C:\Script\Location folder. If a program command is called for (such as Dism) that isn't in that location, the system path command should automatically load it from the C:\Windows\system32 folder, but execute it on the existing path. In the script I called for the location of dism etc directly, but just pointing out what should happen.

For some reason, on your system and on the other persons, when the script is run it is automatically setting the scripts patch location to somewhere else, which is why it can't find the lists folder. I will add in a special patch command in the script that will set the lists folder to load from the location of the script. Hopefully this will resolve the issue! but like I said, it's an issue that shouldn't be occurring.

 

Remember what I said some time ago? Put it into an executable which must be run as Admin, then all issues are gone. Take it into your consideration.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

@burfadel:
Hi, I see latest Old Update Remover uninstalls KB2719985 from W7 x86: so should it be changed (for x86 only)? Thanks.

 

Fixed locally so will be present in the next upload. Thanks for pointing that out!