Frequently Asked Questions

I get a lot of emails, private messages, and posts on forums asking these and similar questions. This page will attempt to answer the most common questions. If you have a question that doesn't appear on this page, check my forums to see if the answer to your question is there.



  • When's the next version coming out?
    If I got a donation for every time I've been asked that, I'd be a very wealthy man. The answer is simple: when it's done. One thing I can guarantee is that questions like that are seen as rude and quite unwelcome with me. For the record, however, I do try to follow the MS hotfix release schedule, releasing a new version whenever new security patches come out.
  • What versions of Windows are supported by this pack?
    The only versions of Windows that this pack officially supports are English versions of Windows XP Home and Windows XP Professional. While the Update Pack may work OK on other releases of Windows XP such as XP Tablet PC Edition and Media Center Edition 2005, it is not supported by me. Integrate onto those OSes at your own risk.
  • How can I confirm that the pack is installed properly?
    From version 1.3.0 and on, a registry key is now written with the version of the update pack integrated. Open regedit and browse to HKLM\Software\Microsoft\Updates. In that key is an "Updated By" value which will show the version of the update pack integrated into that XP install. Also, the Update Pack includes a program named QFECheck with it which will verify that all hotfixed files are properly in place. To run it, open a command prompt and run the program "qfecheck".
  • Why don't I see any updates listed in Add/Remove Programs?
    The purpose of the Update Pack is to directly update files on the XP CD. Therefore, no hotfixes are actually being "installed" on the computer, because everything's already up to date! As a result, there's nothing to uninstall and no Add/Remove entries for them.
  • Can I install this on a running Windows XP installation?
    Unfortunately, no. This pack was designed to be integrated into a Windows XP install CD so that it's up to date when Windows is installed. Other parties have made similar updates for updating an already-installed copy of Windows XP, such as Autopatcher XP and harkaz' Unofficial Windows XP SP4 pack.
  • Can you send me the KBxxxxxx hotfix?
    No. If you want a specific hotfix, you'll have to request it directly from Microsoft, following the directions given in the KB article. Don't waste your time asking me to send it to you. I delete all requests without reply.
  • QFECheck reports that KBxxxxxx must be reinstalled.
    This problem is most often caused by hacking a DLL which was updated by that hotfix, such as changing the max number of connections in tcpip.sys or editing uxtheme.dll to allow unsigned themes. There's really nothing that can be done other than to just ignore the message and be aware of why it occurs. It should be noted that such an error will have no impact on the functionality of your system.
  • Why aren't all Windows Media Player 9 updates included?
    As of version 2.2.1 of the Update Pack, I am including critical security updates for Windows Media Player 9. However, due to maintainability issues, I have no plans of including any other fixes for WMP9. If you are looking for a fully up-to-date Media Player from the start, I would recommend using one of the Windows Media Player 11 addons or slipstreamers available from my forums.
  • Why does setuperr.log compain about plugin.ocx being missing?
    As of the KB912945 update from Microsoft, plugin.ocx is now obsolete and deleted during the normal installation of any Cumulative Internet Explorer Update. Therefore, I also remove the file during Update Pack integration. However, I can't remove it in such a way as to not get that error without hacking other files which goes against my "no unsigned files" policy. Therefore, setuperr.log complains. However, the message is 100% safe to ignore because the file is obsolete.
  • I get errors involving "framedyn.dll" after integrating your SP2 update pack.
    This problem is caused by a failed integration of the Update Pack. Try re-downloading the Update Pack archive and starting over with a fresh XP SP2 source without any addons and see if the problem goes away.

All material on this page is written by Ryan VanderMeulen.

Valid HTML 4.01 Transitional Get Firefox! Made with EditPad Lite