Windows XP SP4 Unofficial Final Version 3.1b is now available! IMPORTANT NOTICE: All SP4 users running SP4 v3.1a or earlier must delete this registry key to receive the latest WU updates: HKEYLOCALMACHINE SYSTEM CurrentControlSet Control WindowsEmbedded The sp4march16wufix.zip file in Google Drive contains a reg file that will automate the task. Double-click on the reg file, click Yes on the popup message and you're done!
Just make sure you have administrative privileges! No further action is needed.
SP4 v3.1b is intended only for new installations and removes just this key. SP4 v3.1b is the final build I intend to release. Thank you all for your support and assistance all these years.
Windows XP official support has ended. Many users - including me - who won't be able to upgrade their old machines to a newer OS would like to easily install all Windows updates in one convenient package. For this reason I started working on a Service Pack 4 package in September 2013. Windows XP Unofficial SP4 ENU is a cumulative update rollup for Windows XP (x86) English. It can be applied to a live Windows XP system which has SP1, at minimum, installed or it can be slipstreamed (integrated) in any Windows XP installation media.
It includes updates for most Windows XP components, including MCE and Tablet PC. Request-only hotfixes have been included. Currently, Microsoft.NET Frameworks 4.0, 3.5, 1.1 and 1.0 (Tablet PC only) are included in the Windows XP SP4 package. In addition, all post-eol updates for.NET Framework 1.1, 3.5 and 4.0 until January 2016 have been included. The.NET 1.x, 3.5 versions are automatically installed/updated in live installations.
Only Microsoft.NET Framework 3.5 is enabled by default in integrated installation. Microsoft.NET Framework 1.1 will be always installed if Media Center Edition is present. If you download the WindowsXP-USP4-v3.1b-x86-ENU.exe you can also scan Windows Update for POSReady updates, because the POSReady trick has been included.
Windows XP SP4 security enhancements: Windows XP SP4 includes registry updates to enhance security. I want to thank Stefan Kanthak, a security expert who has kindly given me the necessary information. These security enhancements address issues not fixed by Microsoft updates.
This is an example of security vulnerabilities fixed by Stefan's registry updates: Windows XP SP4 Documentation The Documentation Cloud folder contains all Windows XP SP4 documentation files. Windows XP SP4 Deployment Guide folder: A series of 6 WMV videos discussing some special SP4 installation scenarios. Windows XP SP4 Components Reference: A PDF file containing every update and component included in Windows XP SP4. You can also find HTML copies of the SP4 Release Notes, SP4 Live Installation Instructions and SP4 CD-ROM Installation Instructions. These files are also included in the SP4 installer. Code: magnet:?xt=urn:btih:8E6110BEA5612725BB4567A7EA14819C3A526DFC&dn=Windows%20XP%20Unofficial%20SP4%20Final&tr=udp%3a%2f%2ftracker.leechers-paradise.org%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.kicks-ass.net%3a80%2fannounce&tr=udp%3a%2f%2ftracker.mg64.net%3a2710%2fannounce&tr=udp%3a%2f%2ftracker.mg64.net%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.openbittorrent.com%3a80%2fannounce&tr=udp%3a%2f%2ftracker.openbittorrent.com%3a80%2fannounce&tr=udp%3a%2f%2ftracker.opentrackr.org%3a1337%2fannounce Verification information and description:. 1.
WindowsXP-USP4-v3.1b-x86-ENU.exe Description: Windows XP SP4 Installer with POSReady Update support Includes March 2016 Windows Update registry fix. Version: 3.1b MD5: 7D2DB4F4C47355BB8C006DEF7A8AB563 SHA1: 2C868FEEE1C078B1CBB7E9A8B4D035ED936B6BEA Date/Time Stamp: 8 March 2016 23:00:00 UTC Size: 993 MB ( bytes) 2.
![]()
PATCHES-V3.1a.ZIP Description: Windows XP SP4 Patches Version: 3.1a MD5: DC525005FB33A2EB0FA3130F6B83DFA4 SHA1: 8447159AACD6D45D3E9C54B30B5C46BFD9B77139 Date/Time Stamp: 27 January 2016 15:00:00 UTC Size: 79.7 MB (83624817 bytes) Tools to create 6 Bootable Floppy Disks for older systems: 3. WindowsXP-USP4-v3.1-Floppy-ic.exe Description: Windows XP Home Edition SP4 Floppy Disk Utility Version: 3.1 MD5: F11756F6E50784050D0B9E1464F4B851 SHA1: 3CD956D8242479F1FD458C34DB132A Date/Time Stamp: 25 January 2016 15:00:00 UTC Size: 4.46 MB (4679426 bytes) 4. WindowsXP-USP4-v3.1-Floppy-ip.exe Description: Windows XP Professional SP4 Floppy Disk Utility Version: 3.1 MD5: EC486E7317B6D7FA62246703AC9BD0E4 SHA1: 07FB0E353A50FFE896F02CDEEBC800 Date/Time Stamp: 25 January 2016 15:00:00 UTC Size: 4.46 MB (4678992 bytes) 5. PRODUKEYMODIFIER-V3.1.ZIP Description: Windows XP Product Key Update Tool Version: 3.1 MD5: 4BAA040957CCE7C89B180BE00B2D8CE2 SHA1: 12466D53C653B56CF7B69FE6ACB859B3D25DB4E4 Date/Time Stamp: 25 January 2016 15:00:00 UTC Size: 1.05 MB (1102383 bytes) WARNING! This RyanVM.net thread is the most trusted download location for Windows XP Unofficial SP4. Although some other sites can be trusted, users download at their own risk.
Generally avoid other untrusted download locations! DISCLAIMER: The author shall not be held responsible for any damage caused to your system.
It is strongly recommended that you test this update before deployment! Please contact me. You can also post you comments below. NOTE: Before installing SP4 on a system with many post-SP3 updates installed, follow the steps described here (do not restart your PC after applying these steps, just run the SP4 installer and then reboot): This will prevent a common error message: 'Failed to install catalog files'.
Although the SP4 installer takes steps to automatically delete these files, it may require manual intervention in some cases. ALL SP3 installer-related Knowledge Base Articles apply to SP4 as well. SIDE NOTES: 1.
Windows XP Unofficial SP4 can be used in English only. Howewer, it is possible to translate to other languages using MUI packs. SP4 MUI ISO Released: 2. At first reboot after SP4 is installed on a 'live' system, setup will run several.NET-related tasks in the background. This will make your computer temporarily slower and you may unable to install/remove software during that time.
It is thus recommended you wait until all pending processes have been completed. This willl take about 20-30 minutes and you can roughly tell by the CPU usage in the Task manager. The on-screen keyboard will not work in TABLET PC EDITION after first reboot. This is normal; it will reappear at next reboot. MS may release new updates for.NET Framework according to Windows XP SP4 v3.1 by default SHOWS.NET Framework 2.0 and 3.0 updates from the Control Panel.
To HIDE these updates run this reg file: 4. If you're using.NET Framework 4.0 make sure you run:%systemroot% Microsoft.NET Framework v4.0.30319 ngen.exe executequeueditems every time you install a new update or application for.NET Framework. This will boost system's performance and ensure reliability.
IMPORTANT: There is an issue with post-sp4.NET FW 4.0 updates I would like to report, which is not caused by the SP4 itself. (Also applies to legacy v2 of Unofficial SP4). Scenario: Install SP4 - Enable.NET Framework 4.0- Run Windows Update Manual Check. Install Updates - reboot - Installed all updates successfully - Run Windows Update Manual Check.
You will get the.NET Framework 4 GDR update (KB2468871) in the optional updates. Reason: This happens because one of the newest updates deletes the: HKLM, 'SOFTWARE Microsoft Updates Microsoft.NET Framework 4 Client Profile KB2468871' and HKLM, 'SOFTWARE Microsoft Updates Microsoft.NET Framework 4 Extended Profile KB2468871'registry keys. These keys are necessary to satisfy the WU detection algorithm for the XP product family (not the POSReady one), but they play no other significant role whatsoever; this is actually a flaw in WU detection algorithm. SOLUTION: You can let Windows Update download and install the update automatically (it should not be removed afterwards). Apply the patches in patches-v3.1a.zip selectively: The files inside the OC-PATCHES subfolders will change the default installation state of each respective component in slipstreamed install.
The files in 4GBPATCH directory will add support for 4GB+ RAM. You just need to copy-paste the files in a SP4v3-slipstremed installation disk and reinstall Windows. YOU WILL LOSE THE 4GB+ PATCH IF A FUTURE HAL/KERNEL UPDATE GETS INSTALLED ON YOUR SYSTEM. To enable.NET Framework 4.0 and other components automatically at Runonce follow KurtAust's instructions here: 6. Windows XP SP4 Source Files: These files have been used to build Windows XP SP4 Final (legacy version).
They are provided to You under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License. Download available at the Unofficial SP4 Source Files Cloud Folder. MD5: 50FF5BB78E7F93C2E219974F382D7EF2. Code: Thank you for visiting Microsoft answers.
To turn OFF the Digital signature do these steps:- 1. Open the Command Prompt window by clicking the Start button, clicking All Programs, clicking Accessories, and then Right clicking Command Prompt and select 'Run as Administrator'. On the Command Prompt type in the command “Bcdedit.exe /set nointegritychecks ON” without the quotes. This will disable the Digital Signature. I know, Go AWAY ELiTE. Elite's solution is intended for Windows 7 but not for XP.
Creating WINNT.SIF and adding these lines is not a solution for a service pack, because it has to be as generic as possible. @Kelsenellenelvian: It seems I have 3 options here: 1. Find a different patch for syssetup.dll, if possible. Don't modify syssetup.inf at all, but this may impose limitations in creating the service pack. Abandon the project, as you did.
I will start with number 1 to see if I can do something. A kernel debugger may be useful. Have you tried this before? Code: 6974F0A2 E85B310200 call jmppSetupVerifyFile 6974F0A7 8BF8 mov edi,eax 6974F0A9 3BFE cmp edi,esi 6974F0AB 7421 jz loc6974F0CE The jz command prevents error messages from appearing when last result zero. The cmp combined with jz has a special role: So edi and esi are subtracted. If they're equal, the result is zero, so it jumps to next routine. If it doesn't jump, it calls pSetupDebugPrint and it prints the error: 20:44:24.515,d: xpsp base ntsetup syssetup misc.c,88,Setup: MyLoadLibraryWithSignatureCheck failed pSetupVerifyFile, le = 800b0100 The error code is 0x800B0100.
This seems to be what we're looking for because the error message setup throws is: The signature for Windows XP Professional Setup is invalid. The error code is 800b0100. No signature was present in the subject. I've located the section in HEX editor: the cmp command is at offset 3E4A9. I need your help to create a patch here. Integration side effects (not UpdatePack bugs):. setuperr.log will point out harmless error messages about some IE files like imgutil.dll, inetcpl.cpl, inseng.dll, mshtml.dll, msrating.dll, pngfilt.dll, occache.dll, webcheck.dll (caused by the patched Syssetup.dll used for integration and then restored with the original one).
Windows Xp Sp4 Product Key
If you don't tolerate it you can integrate in addition this (Hash MD5 5C7AF8CA9F637C993F4AEEFFB63F39ED - Filesize: 1.28 Kb - updated 2008-03-27) which does nothing else than cleaning those false errors in your setuperr.log file. Please note that in some rare configurations the integration of this addon could cause issues, so we don't suggest to use it. Cheers and Regards.
Thanks for the tip, bphlpt, I'll check this later. Tomasz86, I've noticed that syssetup.inf is also present in the Lastgood and Lastgood.tmp directory. Is this normal? Currently working hard on the 'Battery unsigned' problem. I'm making progress: I have been able to reproduce the problem I faced with the original patch with the new one I applied yesterday. I'm confident I'll find the solution.
UPDATE: Having tried many different patches, I haven't yet intercepted the check for battery catalogs. Can someone help me debug it to find its region in EXE? Note: This is the region which, if changed, causes all catalogs not to be recognised correctly.
This seems to be independent of battery, however. It seems that battery is checked in a previous stage. Patching syssetup.dll is now completed The required steps to get rid of all syssetup.dll-related errors are presented below: 1. Grab the original XP SP3 syssetup.dll file. Using a hex editor, like XVI32, open the dll file.
Go to address (offset) 33B7B. Replace 74 with EB. Save changes to syssetup.dll 6.
Using modifype -c command or a similar tool fix the PE checksum. To get rid of the 'Battery unsigned' issue, you have to perform this additional step: Open the syssetup.inf with notepad.
Go to the DeviceInfsToInstall section of the INF file. Delete or comment the line with the battery.inf file. Save changes.
Use the new syssetup.dll and syssetup.inf files instead of the original ones. Known side-effects: Setuperr.log file reports that syssetup.dll is not properly signed.
In addition, SFC does not protect syssetup.dll after installing Windows. However, SFC does not report any problems after Windows installation.
Waiting for your comments after testing the new patch. UPDATE: Removed some redundant steps. Time to return to my SP4 project. Thanks harkaz, nice to read your 'adventures' every day. I'm not an expert, but I hope I can build a Dutch SP4 when you're done with all your magic. Yesterday, I saw xdot's page at and that looked like a nice way to collect all the updates, but of course the files on his site are English only. I still tested them with nLite and Dutch XP, but of course (?) that didn't work.
(Well, it kinda worked, but there were 2 errors). So I hope you'll tell us how we can build the SP4 when the time's right, from your last posts, I'm sure you will succeed! A new challenge: While installing the service pack (testing now) this error message appears: Setup cannot copy the file syssetup.dll. Let's see what's going on here.
UPDATE: I will also have to fix catalog installation failure. Let's see if Gurgelmeyer has done sth on that. The error GetCatVersion: Failed to retrieve version information from.CAT is also present in Gurgelmeyer's USP5. Probably patching it is not needed. UPDATE #2: The error message: 'A component's fil soes not match the information peresent in the verification manifest' seems to be related with update.ver. It is probably related with modified syssetup.inf verification.
Issue seems to have been fixed with a second patch I applied. Note that Gurgelmeyer's update.exe suffered from the same issue as well.
Messenger removed. The only thing I need to add for removal are the start menu messenger entries. After that, I'll test slipstreaming to SP3 installation media. Is there an automated way to keep the update.ver up-to-date? Extract the sfx from the KB942228 (for example) package for the desired language: In the update package of the desired language, using a hex editor, search for MSCF string. (the third one). From that one MSCF string where the CABINET file which is integrated in the update package begins, delete from cursor (including that last MSCF string).
Save as D: sp4.sfx. This the self-extracting 'header for EXE file. Create the self-extracting cabinet - Using CABARC (important, don't use makecab) run the command: cabarc -m LZX:21 -p -r N D: sp4.cab D: SP4 i386. Mark the update.exe in the cabinet for auto-run.
The update.exe will be run each time you extract the cabinet. Any argument parsed to the sfx executable will be parsed to the update.exe in the cabinet. Using a hex editor, open the sp4.cab file you just created.
Search for 'i386 update update.exe' text (without the quotation marks). Go to the hex editor section. In front of the hex numbers that translate to SP4 i386 update update.exe there is the number 20 00.
Change 20 to 60 and save changes. Append the sfx with sp4.cab file in a new self-extracting executable. Run the command: copy /b D: sp4.sfx+D: sp4.cab D: WindowsXP-UnofficialSP4-ENU-x86.exe (choose a suitable name for the EXE like the one above).
Optionally, add a manifest to require elevation each time the SP4 package is run. Right now, I'm trying to fix some issues related with modified syssetup.dll and syssetup.inf files: no catalog is installed during service pack installation. If you know Assembly, I need your help here: After some examination of the svcpack.log file (I tested various possible patches), I'm almost certain that the problem is related with the SetupDiCallClassInstaller function of the setupapi.dll library.
This function fails with error code: 0x800b0100 (No signature was present in the object). However, no 'unsigned driver' dialog is displayed. Probably the SPDEVINSTALLPARAMS structure, which is passed to the SetupDiSetDeviceInstallParams function is the key to the solution.
This function is normally called before the SetupDiCallClassInstaller and sets the device installation parameters. Which flag of this function would cause such a behaviour? Luckily, the SPDEVINSTALLPARAMS structure is fully documented:. As we read there, the DIQUIETINSTALL flag of the structure seems to do what we're looking for. When I manually tried to add some catalogs with signtool, it reported no problems. I'm trying to find out why update.exe can't do that.
UPDATE: An interesting observation: After installing SP4, the partmgr.sys driver is the only one which is signed. On the other hand, disk.sys is unsigned. However, BOTH FILES are signed by sp3.cat, as signtool indicated! MOST interesting. UPDATE#2: After some testing, it seems that the GetCatVersion error is strongly related wkth the patch applied to skip update.inf verification, The same error appears even when changing almost nothing in update.inf (existing catalogs remain installed however, thus avoiding further complications).
After all, I have been able to install the SP4 on top of SP3 with all the catalogs installed. (The GetCatVersion error is still present). I have to use the original layout.inf, syssetup.dll and syssetup.inf files for installation on a live system. Are ALL these files required for a sysprep installation - I know that layout.inf is required. Is there a patch to accept a modified layout.inf in GUI mode setup? Another issue I detected: When I create a new user profile, it tries to configure Messenger, but it complains about msmsgs.inf not being present (I've deleted it in SP4, along with messenger).
How do I update the registry to remove this?
There is no Windows XP Service Pack 4 This is off topic only. Earlier this year, a small group of people were asking for Microsoft to produce a service pack for four Windows XP.
To my surprise, there appears to be only a few people interested in this. Is that true? I would think that hundreds, even thousands of people would've requested Microsoft to create a service pack for and distribute it for a modest fee. Didn't Microsoft do that with Windows 2000? If they got thousands of orders, it could be worthwhile to have maybe one or two people in their organization diddle it. Bundle up a qyasi-service pack for and have it be distributed by some my small mail-order company for a modest price.
Against the argument against that such he would interfere with sales of Microsoft's new products. But that is hard to estimate. There are many people that just cannot make the transition to newer operating system. One reason is the cost of getting newer equipment or upgrading existing equipment. The old equipment works quite well with Windows XP, but the updates are needed. Mostly because of security issues. So, am I the only one that thinks this way.?
Here is one a few links I found that appears to be near serious. Yes, what would be the point? I have SP3 XP discs at hand and product keys. What I do not have is a collection of updates after SP3. In case of a bad problem, I either have to install from backup or from the SP3 disc.
I would like to get rid of my old PCs that take up room here. If I re install XP, it will be SP3 with no updates on it. Having a SP4 disk would help. I would gladly pay $12 for an XP disc to update my old hardware.
But no way will I pay $80 or more for a Windows 7 home disc with key just to bring old hardware up to date. IMHO a XP SP 4 could extend the life of my old junk for a couple of years. And maybe somebody else would enjoy my junk. My understanding is the automatic updates are only security patches now. So a fresh install of XP on an rejuvenated junker would not have the other things. Slipstreaming is a simple process, so if your giving up on trying this out, I wouldnt exactly give up but would give it a try to learn how its done.
I have created ISO's that are patched to the last patch and SP3 for XP Home and Pro, since on occasion I am still supporting people with systems that are running XP, some of them are able to run Windows 7, but they bought their copy of XP back during Vista before 7 came out and so they are running decent dual-core systems but XP instead of what would have been Vista for the time period of the hardware. I have sold some on the idea of either buying new computers or buying Windows 7 Home upgrade for their systems, but some people who are willing to take the risk are sticking with XP. With the fully patched slipstreams you pretty much install clean, and activate the key with Microsoft, and then your fully patched to the last and final patch. No more waiting for a computer to apply 130 updates then reboot and another 78 more and then reboot and then like another 18 and then 4 after that. So if you plan on having systems that run XP or supporting systems that run XP, I would highly advise learning how to make this slipstream and making one for Home and Professional if you have those to create from the i386 of each original disc.
The Microsoft Windows - Windows XP section probably works out just fine, otherwise we would have 2 locations of similar posts for people with XP questions. As far as the club goes. There is nothing stopping you from making this club website of your own on the web for XP at very little cost.
I have doubts that it would be created at CH, since otherwise it would spawn off DOS, Windows 3.x, 95, 98, Me, 2000, Vista, 7, and 8 forever sections and the more sections the more involved the moderation is to keep out the spam etc. Looking at the link you provided to this unofficial SP4, they should have gone 1 step further and made it to where it would claim to be SP4 in the About Computer section. Not sure how well protected this text info is to alter to have it specify SP4.
Microsoft CD Keys, CD Key Generator, Genuine Advantage ValidationMicrosoft CD Keys, CD Key Generator, Genuine Advantage Validation If you want to make up your own key of the form nnn-nnnnnnn, it seems that the first three digits can be any number you like while the last seven digits must add up to a multiple of seven. A really boring (but easy to type key) is: 1 This key has been used successfully with: BackOffice 4.5 (Beta 2) Flight Simulator 98 (OEM) Liquid Motion 1.0 Monster Truck Madness Office 97 Pro Plus! 98 Publisher 98 SQL Server Enterprise Edition Visual C 6.0 Standard Edition Visual Studio 6 (Enterprise and Pro) and 97 Windows NT Word 97 I have also read that if you take an upgrade CD key and add one to the first set of numbers (whether three or four digit) then the CD key will be for the full edition. If that didn't work, try this: 4 I am not sure what CD this is from, but I am compiling a list of all Microsoft applications that this CD Key works with. It seems to have been the standard with older CD's (95 thru 97). This key has been used successfully with: Flight Simulator 95 Monster Truck Madness Office 98 for MacIntosh Office 2001 for MacIntosh Publisher 97 Publisher 98 (with 0465 in first block) Sidewinder Game Pad CD Visual Basic 4.0 Enterprise Visual Basic 6.0a Professional Edition Visual C 4.0 and 5.0 Visual C 4.0 Professional Visual C 5.0 Professional Edition Visual C 6.0 Pro Visual Studio 97 Windows NT 4.0 Workstation Windows 95/98 Plus! Windows 95 Upgrade Windows 98 Beta 3 Works 4.5.
So if the CD Key above did not work, try this: 11 This key has been used successfully with: Office 97 Office 97 Pro Outlook 98 Power Point 97 Upgrade Project 98 Publisher 5.0 and 98 Microsoft Works Word 97 If that one doesn't work for you, try this: 80 This key has been used successfully with: Access 97 Front Page 98 Office 97 Pro Outlook 98 Project 98 Publisher 98, English, Spanish Version Visual Basic 5.0 Professional and Enterprise Edition Word 97 The format for the nnnn-nnnnnnn. The first four digits seem to make a difference, but even versus odd totals are rumored to indicate an OEM versus upgrade CD (this hasn't been worked out). The last seven digits still must add up to a multiple of seven, but certain combinations like all ones and anything ending with a zero are disallowed. 41 seems to work and is easier to type. Windows 98 If your computer came with Windows 98 (i.e. You did not upgrade your computer to Windows 98), you may need to use an OEM number which you find via this link. With Windows 98, MS seems to have gone crazy with the length of the CD Key or Product Key.
There see to only be about three common families of CD keys, OEM, full retail, and upgrade retail. The main thing seems to be just using a CD key from the same family. Two less common families are corporate (which can sometimes bypass the mandatory registration process) and academic. Windows 98 Second Edition keys are broken out in a separate section below. Some Windows 98 CD Keys you can try are: VYK42-6KXD9-2C333-3D898-J97HP R3TQR-PQTKG-HBVQ9-YBFH3-CGCRT worked with German full, English full (OEM), UK Edition, Compaq English, Spanish Full, Dutch, Compaq and IBM Recovery CDs, and U.S. Second Edition (SE) OEM, Dell SE laptop, Toshiba 4100XDVD.
RRXHQ-M3YTR-3BGRT-CQMC2-6K4C4 Q2YHH-GYWV2-MDXCD-H9P2X-HYVMM worked with several versions including SE (Second Edition), UK Edition, and US OEM. R34DV-VB6WM-XMHHV-WM4Q2-WBB3Y is supposed to work with all version of first edition Windows 98 (4.10.98), UK Edition. T7J8Q-MH7RP-9H9J2-2HVFG-C3X2M worked with four U.S. Retail versions (4.10.1998) as well as second edition version. JJK9P-G8JYJ-X24RC-XTFJ4-K9W4W worked with English retail version (CA), UK Edition. MMHK7-QPHQG-KMTP9-7GTJY-JQ6XM worked with English Retail Second Edition v4.10.2222A.
Also, HP 4440 recovery disk, UK Edition. XB88B-9B96V-CRJPG-64882-GQBDD Full verison, not upgrade, also Second Edition, UK Edition DJK2X-6XFJB-Q9J7J-WGC7P-WMHYG Compaq, HP, IBM, etc., UK Edition HGBRM-RBK3V-M9FXV-YCXDK-V38J4 Apr 98 Beta MD97J-QC7R7-TQJGD-3V2WM-W7PVM came with English Developer's Connection Version. Seems to work with same CD's as T7J8Q. Also Japanese version.
Welcome to Windows XP Service Pack 4 (Unofficial). Windows XP SP4 (Service Pack 4) is a cumulative update rollup for Windows XP. Windows XP SP4 Final is now available! IMPORTANT NOTICE FOR XP SP4 USERS : Microsoft has changed its WU update detection strategy. The following key must be removed to continue receiving automatic updates from WU: HKEYLOCALMACHINE SYSTEM CurrentControlSet Control WindowsEmbedded Use the sp4march16wufix.reg found inside the respective zip file at my Google Drive in order to automate the process. Version 3.1a users don't need to do anything more than that. A new v3.1b version has been released with this change, just for new installs.
No other updates have been added. Windows XP SP4 can installed on any version of Windows XP with SP1 or later installed or slipstreamed into any Windows XP installation source (except for Embedded versions). It includes all updated components and hotfixes for Windows XP in a single, convenient package. Except for the SP4 package installer main executable (update.exe) and a cosmetic resource modification sysdm.cpl no other binary file has been modified, everything is original from Microsoft Corporation. Microsoft.NET Frameworks 4.0, 3.5, 1.1, 1.0 are included in this package.NET Framework 1.0 will be installed only with Tablet PC Edition or Media Center Edition (Upgrade only).NET Framework 4.0 is disabled by default.
It's possible to split the slipstreamed installation source into two 650 MB CD-ROMs, which can be essential for older computers. You can also create 6 Bootable Floppy Disks to install Windows XP on older systems which cannot boot from CD-ROM. Furthermore, Windows XP SP4 includes security enhancements that address issues not fixed by Microsoft Updates.
It also includes performance tweaks that should make your PC run blazingly fast. NOTE: Before installing SP4 on a system with many post-SP3 updates installed, follow the steps described here (do not restart your PC after applying these steps, just run the SP4 installer and then reboot): This will prevent a common error message: 'Failed to install catalog files' Although SP4 installer takes steps to automatically delete these files, it may require manual intervention in some cases.
Download at Windows XP SP4 development thread at RyanVM.net: Visit RyanVM.net for additional information. (Current version: Version 3.1b Released on 08 March 2016 23:00:00 UTC) Enjoy Windows XP Service Pack 4. Screenshots: This is Windows XP SP4 slipstreamed in a Windows XP MCE 2002 installation source. Notice the Version year. Edited March 9, 2016 by harkaz. Sounds to me like a nice project with a good future and will benefit people making the switch to XP after April 2014 and beyond. I'm sure there will be tweaking along the way but it's a beginning that may lead to many new XP projects as Windows XP officially comes to an end.
Look at the excitement in the Windows 98/98SE forum and improvements that have happened over the years. This is just the beginning of a continued or second life for Windows XP.
Windows 98/98SE needed some tweaking with USB and software (KernelEx) and so forth. Windows XP is beyond all that already and may not need much tinkering or tweaking but every so often someone might make a nice discovery or solve an ongoing problem. We have a very good OS in Windows XP but others will possibly make it better down the road. I truthfully think this is a great idea.
Windows Update on the web feels extremely broken these days and half the time I can't even get it to work on a Windows XP machine so having an update pack like this is for sure an awesome idea. It's almost like Autopatcher used to be many years ago before MS shut them down except it's basically a Service Pack, not just an update script so much. This will save a boat load of time when it comes to bringing a Windows XP machine up to date in short order.
I say keep going! I'm fixing a couple of bugs in the SP4 Alpha version. One of them is the Kabul Time Zone Syndrome': in CD-ROM installations, you always get Kabul as the selected time zone no matter what you choose.
I have narrowed down the cause of this issue, so expect an Alpha 2 release very soon. By the way, I got my hands on Windows Embedded POSReady 2009.
It is Windows XP SP3 and it will be supported until 2019. In Windows Embedded POSReady 2009 Service Pack 3 I could find almost everything present in the Windows XP SP3 package. Even the ic folder was there (is there a 'Home/Personal' version of WEPOS that I don't know?). There are only a few binaries different in XP Home and Professional, as one sees in the service pack: dpcdll.dll and pidgen.dll. Dpcdll.dll is the only one which has been affected by updates (winlgon.exe updates I think affect this one).
As for the INF files, I can do everything I want with them and nothing at all will complain. It's highly likely, after all, that April 2014 won't be the end for Windows XP x86. Edited March 8, 2014 by harkaz.
Comments are closed.
|
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |