[Discontinued] WU Zero Update Pack
i posted earlier which hotfixes were reported as incorrectly installed by qfecheck; i also posted which hacked files i'm using...
[edit]
Here, I'll repost which ones are broke for me:
Hacked Files used:
Tcpip.sys (100 Connections): RVMAddonsTCPIP_1.0.cab
UXTheme.dll: RVMAddonsUXTheme_1.0.cab
[edit]
Here, I'll repost which ones are broke for me:
KB909520: Software update for Base Smart Card Cryptographic Service Provider
KB887797: Outlook Express for Windows update
KB893066: Vulnerabilities in TCP/IP could allow remote code execution and denial of service
KB900725: Vulnerabilities in the Windows shell could allow for remote code execution
KB905915: Cumulative security update for Internet Explorer - December 2005
Hacked Files used:
Tcpip.sys (100 Connections): RVMAddonsTCPIP_1.0.cab
UXTheme.dll: RVMAddonsUXTheme_1.0.cab
Hey,boooggy wrote:fixed qfecheck issue for both and updated WGA to version 1.4.410.0
also wuzero contains updated wm addon: viewtopic.php?p=16488#16488
please report if any probs.....
So I just did a real-world test of your latest pack, and qfecheck is beter, but not perfect:
KB887797: Outlook Express for Windows updateKB887797: This hotfix should be reinstalled.
KB900725: This hotfix should be reinstalled.
KB905915: This hotfix should be reinstalled.
KB900725: Vulnerabilities in the Windows shell could allow for remote code execution
KB905915: Cumulative security update for Internet Explorer - December 2005
The other 2 now work fine. But what's wrong with these 3?
[edit]
I should note that Windows Updates shows ZERO updates to be installed - this is just qfecheck problems...
updated both packs with this month updates. also rebuild wu0 pack and it contains only wu updates (including wmp10 which final version is 10.0.0.3990). i had no problems with WU and also with qfecheck:

so a06 dont know what u doing to brake it.......

so a06 dont know what u doing to brake it.......
Last edited by boooggy on Wed Feb 15, 2006 6:02 pm, edited 1 time in total.
is KB890830 in this pack (Malicious Software Removal Tool)?
http://support.microsoft.com/kb/890830
If yes, why isn't it listed on the first post?
http://support.microsoft.com/kb/890830
If yes, why isn't it listed on the first post?
Re: [Release] Update Pack 1.2 (WU only)
MRT stands for Microsoft Removal Tool which is KB890830.......doh.....boooggy wrote:also contains MRT, highmat, original WGA and Microsoft Update
Re: [Release] Update Pack 1.2 (WU only)
LOL, ouch. Fair enough.boooggy wrote:MRT stands for Microsoft Removal Tool which is KB890830.......doh.....boooggy wrote:also contains MRT, highmat, original WGA and Microsoft Update

Sorry!
Finally got around to testing with no problems at all. I combined with dgelwin's dotnet framework beta for a big ZERO when I visited microsoft update. Thanks Booogy for your great efforts once again. Hope to test win2003 pack within the next couple of days. Any clues or hints on methods or programs (scripts) you are using to make these "update" packs. I know there is a thread on how to create an addon but i'm really intrested on how you and ryan create the update packs.
@john2003, There`s no quick answer to that i`m afraid. Think of it as each hotfix being an addon and then their all combined together in one pack, obviously with a lot of other stuff to take into consideration. That`s the best way i can describe it.
As far as scripts go everything is done manualy although i do use batches to extract and install hotfixes.
As far as scripts go everything is done manualy although i do use batches to extract and install hotfixes.
i'll be testing this, hopefully tonight.
quick request- would you be able to make the first post a little more informative, (as to what each hotfix is), and as to what else is in tha pack?
similar to: http://www.ryanvm.net/forum/viewtopic.php?t=1625
This is not to take away anything from this pack, i love it and use it!
Thanks in advance
[edit] - the test worked perfectly! no updates on WU!
thanks a ton!!
quick request- would you be able to make the first post a little more informative, (as to what each hotfix is), and as to what else is in tha pack?
similar to: http://www.ryanvm.net/forum/viewtopic.php?t=1625
This is not to take away anything from this pack, i love it and use it!
Thanks in advance
[edit] - the test worked perfectly! no updates on WU!
thanks a ton!!
Is there any addon for the xp transformation pack ?
Is there any addon for the xp transformation pack ? if there are where can i find it ?

Life is a Bliss, You just Have To Tast IT, :--____Mehedy Mizan____
Hi boooggy !
I am still having a problem with the hotfix KB887797: This hotfix should be reinstalled (qfecheck.exe), using your latest (43.9MB) pack.
I've built 2 bootable disks using the same XP Pro SP2 CD-ROM (both with the same nLite 1.0rc6) :
- one using Ryan's 2.0.3 update pack,
- one using your 43.9 MB WU0 pack,
There is only one problem with KB887797 found on a fresh install using WU0 pack, with 2 files :
wab32.dll (Ryan's version's 6.0.2900.2530, WU0 version's 6.0.2900.2527)
wabimp.dll (Ryan's version's 6.0.2900.2530, WU0 version's 6.0.2900.2527)
Would you please check if WU0 pack does contain correct versions of these two dlls ?
Other than that - a perfect pack I've been enjoying for some time now !
Cheers
I am still having a problem with the hotfix KB887797: This hotfix should be reinstalled (qfecheck.exe), using your latest (43.9MB) pack.
I've built 2 bootable disks using the same XP Pro SP2 CD-ROM (both with the same nLite 1.0rc6) :
- one using Ryan's 2.0.3 update pack,
- one using your 43.9 MB WU0 pack,
There is only one problem with KB887797 found on a fresh install using WU0 pack, with 2 files :
wab32.dll (Ryan's version's 6.0.2900.2530, WU0 version's 6.0.2900.2527)
wabimp.dll (Ryan's version's 6.0.2900.2530, WU0 version's 6.0.2900.2527)
Would you please check if WU0 pack does contain correct versions of these two dlls ?
Other than that - a perfect pack I've been enjoying for some time now !
Cheers
Hmm...
1. Extract WAB32.DL_ from the latest WUZero_UpdatePack.cab (43.9 MB downloaded on 27 Feb 2006) - I used WinRAR 3.51
2. Expand this extracted WAB32.DL_ into WAB32.DLL using Windows command "expand wab32.dl_ wab32.dll"
3. View this wab32.dll properties - it is version 6.0.2900.2527, but should be 6.0.2900.2530
4. The same applies to WABIMP.DL_
I think this is the reason why QFECHECK.EXE is complaining about KB887797...
Cheers
1. Extract WAB32.DL_ from the latest WUZero_UpdatePack.cab (43.9 MB downloaded on 27 Feb 2006) - I used WinRAR 3.51
2. Expand this extracted WAB32.DL_ into WAB32.DLL using Windows command "expand wab32.dl_ wab32.dll"
3. View this wab32.dll properties - it is version 6.0.2900.2527, but should be 6.0.2900.2530
4. The same applies to WABIMP.DL_
I think this is the reason why QFECHECK.EXE is complaining about KB887797...
Cheers
Get up to $200 off on hosting from the same people who host this website!
http://www.ryanvm.net/forum/viewtopic.php?t=2357
http://www.ryanvm.net/forum/viewtopic.php?t=2357
Hi !
I'm a little confused
In Ryan's update pack 2.05 I noticed several of your kb's to be in the
"Obsolete" section ?
Among them are:
KB904706
KB902400
KB900725
KB891781 (haven't cross referenced all of them)
Are these, (as it says) obsolete or what ?
I'm a little confused

In Ryan's update pack 2.05 I noticed several of your kb's to be in the
"Obsolete" section ?
Among them are:
KB904706
KB902400
KB900725
KB891781 (haven't cross referenced all of them)
Are these, (as it says) obsolete or what ?
;This section contains a list of obsolete hotfixes which shouldn't be installed
[obsolete]
d3dx9_24_x86
d3dx9_25_x86
d3dx9_26_x86
d3dx9_27_x86
d3dx9_28_x86
d3dx9_29_x86
KB319740
KB842520
KB884868
KB887797
KB888795
KB889527
KB891593
KB891781
KB892090
KB892233
KB892559
KB896062
KB896688
KB896984
KB897574
KB898108
KB899337
KB900387
KB900725
KB900730
KB900808
KB900930
KB902400
KB904706
KB905915
KB907405
KB909095
KB909547
KB910720
MSXML3SP7
xact_x86
xinput9_1_0_x86
Thank You, Boooggy
Thanks, boooggy, for this update pack. RyanVM's pack is great, but for certain uses I also need something that will only install all updates available in Windows Update -- no less, and no more -- so this is exactly what I was looking for! Also thank you for keeping it up to date.
hey boooggy, thanx for ur hard and good work.
i have ur latest pack (hashes match
), and it contains KB905915.CAT, which is superseeded by KB912812.
u dont have entry for it, in svcpack catalogs, but still stands there.
hope u correct next month.
and also a question, kb911565 is superseeded by KB918886. Will u include it in next pack?
Thanx
i have ur latest pack (hashes match

u dont have entry for it, in svcpack catalogs, but still stands there.
hope u correct next month.
and also a question, kb911565 is superseeded by KB918886. Will u include it in next pack?
Thanx

Hey boooggy, please read this post, and have a look at that topic.
Also thanx for update. keep it goin
Description of the contents of Windows XP Service Pack 2 and Windows Server 2003 software update packages5eraph wrote:Here is what I read: (thanks for the link, Ryan)
This seems to suggest that QFE packages are more up-to-date, but possibly less stable.The GDR package contains only the security update.
...
The QFE package contains the security update and the hotfixes.As buggy as Microsoft products can be, I still prefer a quick fix instead of no fix at all.Hotfixes are produced quickly to provide immediate assistance to specific Microsoft customers. Therefore, hotfixes may not be tested as thoroughly...
Also thanx for update. keep it goin

The KB article presents a good reason to use QFE files IMO. As it points out, the QFE files are copied to $hf_mig$ when the GDR version is installed. That's for a very specific reason. Say you need a specific hotfix down the road from MS which includes a version of the file which is postdated by the security update. With what you're doing, boooggy, the user will have to choose between installing the fix to solve their problem and then having to reinstall the security update since you don't have an $hf_mig$ directory.
To make it more clear, consider this scenario (this is basically a paraphrase of the KB article, BTW).
Say blah.dll is updated by a security update to build 2800. On a normal system, the GDR build of the DLL will be copied and the QFE build will be copied to $hf_mig$. Then say you need to request a specific fix from Microsoft which includes only the QFE build of blah.dll build 2750. In such a scenario, the hotfix installer will copy the QFE build 2800 version of blah.dll from $hf_mig$ instead of installing build 2750 so as to keep the security update intact.
So what do you suppose will happen if there is no $hf_mig$ copy of the QFE version? To be honest, I'm not sure, but I'm inclined to think that one of two things will happen. Either the hotfix will refuse to install because the currently-installed version of blah.dll has a higher version number (which leaves the user unable to install the fix for the problem they're experiencing) or the hotfix will replace the GDR build 2800 version of blah.dll with the QFE build 2750 version of the DLL, meaning that the security update would then have to be reinstalled afterwards.
If the QFE version is installed from the beginning, such situations are avoided.
It's up to you to decide what you want to include in your pack, boooggy, but I hope I've at least given a compelling argument for you to consider.
To make it more clear, consider this scenario (this is basically a paraphrase of the KB article, BTW).
Say blah.dll is updated by a security update to build 2800. On a normal system, the GDR build of the DLL will be copied and the QFE build will be copied to $hf_mig$. Then say you need to request a specific fix from Microsoft which includes only the QFE build of blah.dll build 2750. In such a scenario, the hotfix installer will copy the QFE build 2800 version of blah.dll from $hf_mig$ instead of installing build 2750 so as to keep the security update intact.
So what do you suppose will happen if there is no $hf_mig$ copy of the QFE version? To be honest, I'm not sure, but I'm inclined to think that one of two things will happen. Either the hotfix will refuse to install because the currently-installed version of blah.dll has a higher version number (which leaves the user unable to install the fix for the problem they're experiencing) or the hotfix will replace the GDR build 2800 version of blah.dll with the QFE build 2750 version of the DLL, meaning that the security update would then have to be reinstalled afterwards.
If the QFE version is installed from the beginning, such situations are avoided.
It's up to you to decide what you want to include in your pack, boooggy, but I hope I've at least given a compelling argument for you to consider.
Get up to $200 off on hosting from the same people who host this website!
http://www.ryanvm.net/forum/viewtopic.php?t=2357
http://www.ryanvm.net/forum/viewtopic.php?t=2357
Thank you...
I am gradually learning a lot about creating (more appropriately, modifying) addon packs due to the packs shared here.
Something I noticed, and am currious about, it appears you are doing a shot of your registery, installing updates and comparing to create the [KBXXXXXX.ADD.REG]'s
Can I just use the [KBXXXXXX.ADD.REG] info from the individual KBXXXXXX.INF files instead? Since this will be included in original Windows XP install, do we really need the FILES in Do we really need the FILELIST info in for that matter
I took liberty of going through your UpPck.inf file, creating more [STRINGS] entries and doing a search and replace, and utilizing the ones you already have more thoroughly...the results are about 17KB savings (while small, its some)... (If I could figure out how to attach a file, I would have attached my modified .inf.)
Something I noticed, and am currious about, it appears you are doing a shot of your registery, installing updates and comparing to create the [KBXXXXXX.ADD.REG]'s
Can I just use the [KBXXXXXX.ADD.REG] info from the individual KBXXXXXX.INF files instead? Since this will be included in original Windows XP install, do we really need the FILES in
Code: Select all
HKLM, SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KBXXXXXX
Code: Select all
HKLM, SOFTWARE\Microsoft\Updates\Windows XP\SP3\Filelist\#
I took liberty of going through your UpPck.inf file, creating more [STRINGS] entries and doing a search and replace, and utilizing the ones you already have more thoroughly...the results are about 17KB savings (while small, its some)... (If I could figure out how to attach a file, I would have attached my modified .inf.)
You Can't Get, If You Won't Give
YCGIYWG
YCGIYWG