space exploration ppt downloadva highspeed downloader pro 1 2 apkunity 3d mac downloadwindows 7 vlk iso download
2015 CBS Interactive Inc.
6.0 Build 6002: Service Pack 2
Editors Note: This downloadable version of Windows Vista can be an upgrade only. Users can upgrade to Windows Vista Ultimate from Windows XP Pro, Windows XP Home, Windows XP Media Center, or Windows XP Tablet PC.
The good : Windows Vista Ultimate does improve some features within Windows XP; fewer system crashes than Windows XP; Windows Vista offers better built-in support options.
The bad : Windows Vista Ultimate will not put Search around the desktop its buried within applications, inside Start Menu; optimized exclusively for the Microsoft Windows ecosystem as an example, RSS feeds from Internet Explorer 7 get preferential treatment; theres too much instead of all of it is implemented properly; no new software yet written just for Windows Vista; where there are too many editions of Windows Vista.
The the main thing : Windows Vista is basically warmed-over Windows XP. If youre currently pleased with Windows XP SP2, we view no compelling reason to upgrade. On the opposite hand, should you prefer a new computer at the moment, Windows Vista is stable enough for everyday use. Reviewed by: Robert Vamosi; Reviewed on: 1/23/07; Release date: 1/30/07
When you need to have it all, choose Windows Vista Ultimate. Its the most complete edition of Windows Vista-with the energy, security, and mobility features which you will want for work, and each of the entertainment features you want for fun.
Take selling point of all Windows Vista security measures to help protect your personal computer, the information you have, you from accidents and malicious software. Take selling point of comprehensive productivity features including Instant Search, Complete PC Backup and Restore, network support including domain join, and Windows SuperFetch. Windows Vista Ultimate includes Windows Media Center to help you enjoy your complete digital entertainment library on your own PC or with your television. Windows Mobility Center, BitLocker Drive Encryption, and Tablet and Touch Technology some of the features which make staying productive on the highway easier, and safer, than in the past.
Work great simple to use very fast wonderful features!! Simply put the top!!
Too me vista ultimate 64 bit is the most effective os ever, they will keep windows 7, i won't be buying it.
2015 CBS Interactive Inc.
5.1 Build 2600: Service Pack 3
Editors Note: The product is discontinued by its publisher, while offering this page for informational purposes only.
From Microsoft: Windows XP Home Edition offers you the freedom to try out more than you ever thought possible with your personal machine and the Internet. This is the computer home users are actually waiting for because doing so offers serious speed and stability, to help you have serious fun.
Create, share, and get movies
Communicate at any time, anywhere
Discover, download, store, and play music
It continues to be usable today, therefore it may be just like secure like a newer OS if it's configured properly.
It is often a fun operating-system.
Nothing which might be thought of.
Thank you Jesus Christ! This operating system may be with me some time however it is very enjoyable. Throughout my brief years about the computer being a new user it happens to be impressive. Just my own prefer. Even the preview of Microsoft Windows 8 won't compare to Microsoft Windows XP Home Edition with Service Pack 2.
So far Windows XP is undoubtedly the slowest OS Ive ever worked. Not well worth the buy in any respect.
Windows XP isn't a good OS, since it keeps crashing for pointless and its so slow, even though you have 1-2GB of memory. If you could have XP, I recommend that you simply upgrade to Vista SP1 or 7 now.
Reply by whatsyourpoint on June 18, 2012
Yikes! Whatever you do, dont use Vista period! 7 is nice though.
Reply by spacetimezi on February 6, 2012
Yes XP isn't perfect but hardly slow than the bloated and rushed VISTA. If you execute a clean install with XP and your personal machine is still slow then it's your hardware otherwise you have the wrong drivers installed. This isn't XPs fault.
The next thing is to buy a brand new computer with 7. You can get a whole new one a couple of hundred and prefer a great computer for tech you may build your own for some hundred also. Im sure you will find techs in your area that can help you. Either way the rule of thumb is XP for old computers, and 7 for brand spanking new ones. And if you absolutely do cant stand XP a celebrity then change to linux. Its free and far more secure.
Very, excellent Windows program
Easy to handle problems, simple to navigate. Holds more than enough. Tells when there can be a problem and fixes it easily. Fast 85% of that time period. Good household computer, tells each time a program may harm your laptop, and asks if you want to run it.
Lags sometimes ANNOYING, may be slow 35% of times. When multiple tabs windows are running simultaneously, every one of the programs immediately become unresponsive. When programs become unresponsive, inconvenience to shut this software down.
Overall, I have had this computer ALL MY LIFE, and it also still works like fresh. This computer is definitely an old but trusted friend, and if you would like to pick out a fresh program, opt for this. You wont regret it!:
if your Microsoft ME operating-system wont work anymore, get a upgrade package off ebay that converts your o/s to XP home. Yes, it truely does work OK and enables you to keep your current computer more years. as Microsoft will support XP thru 2013
no choice but to convert to xp from ME. XP home works just great and all my old software is effective on it. No support for ME which worked well for me for a decade. Time to progress to XP to maintain software current.
XP is likely to go down as Microsofts best computer ever. After service pack 2 and 3, they finally reached it working! Why reinvent the wheel? Im happy as well as set for at least several years as a result of a 50 upgrade pkg purchased off ebay
You are logged in as. Please submit your review for Microsoft Windows XP Home Edition
2. One-line summary: 10 characters minimum Count: 0 of 55 characters
3. Pros: 10 characters minimum Count: 0 of just one, 000 characters
4. Cons: 10 characters minimum Count: 0 of merely one, 000 characters
5. Summary: optional Count: 0 of a, 500 characters
The posting of advertisements, profanity, or personal attacks is prohibited.
Note that the submission may well not appear immediately on our site.
Since youve already submitted an appraisal for this product, this submission is going to be added for an update on your original review.
The posting of advertisements, profanity, or personal attacks is prohibited.
Note your submission may well not appear immediately on our site.
Summary: 0 of just one, 000 characters
The posting of advertisements, profanity, or personal attacks is prohibited.
Note that the submission might not exactly appear immediately on our site.
Add your own private message: 0 of a, 000 characters
If you imagine this comment is offensive or violates the CNETs Site Terms of Use, you are able to report it below this can not automatically eliminate the comment. Once reported, our staff will likely be notified along with the comment will likely be reviewed.
Illegal activities: Promote cracked software, or another illegal content
Your message has become reported and are going to be reviewed by our staff.
Whats new in version 5.1 Build 2600: Service Pack 3
Create, share, and luxuriate in movies
Communicate every time, anywhere
Discover, download, store, and play music
5.1 Build 2600: Service Pack 3
Clean up junk files and invalid Registry entries.
Speed up a sluggish PC, shorten startup time, and protect
Take full treating RAR and ZIP archives, in addition to
Move, resize, copy, explore, and recover hard drive
Take full treatments for RAR and ZIP archives, in conjunction with
Update PC drivers automatically using cloud technology.
Search and discover required files on PC.
Clean the PC and improve system performance.
Recover files deleted from the Windows computer.
Download, update, and copy all your Windows drivers and
Fix, improve, maintain, and protect your PC.
Monitor and block starting processes and loading DLLs.
Copy folder contents without difficulty.
Manage all internet activities.
Manage files and directories on your own PC with no trouble.
Install an os without by using a bootable CD-ROM.
CBS Interactive Inc. All rights reserved.
MMXII CBS Interactive Inc.
Please describe the situation you have with this particular software. This information will probably be sent to our editors for review.
Please opt for a feedback type.
Please enter an account.
Thank you for submitting a difficulty report! The Download team is focused on providing you with accurate software information.
Slipstreaming a Service Pack, is the method to integrate the Service Pack in to the installation making sure that with every new installation the Operating System and Service Pack are installed concurrently.
Slipstreaming is frequently done on network shares on corporate systems, just about all makes sense to the home user or business user to perform.
Microsoft added the opportunity to Slipstream a Service Pack to Windows 2000 and Windows XP. It besides has the advantage that whenever you reinstall your OS, you do not have to apply the Service Pack later, also if you update any Windows component later, you will be sure that you just get the right installation files if Windows needs any.
Download the total Network Install in the Service Pack English version 316.4 MB, and save it with a directory folder on your own hard drive in my case E:XP-SP3. Other languages might be downloaded from your Microsoft Download site.
Note: avoid spaces inside the folder name!
Next copy the belongings in your Windows XP CD in your hard drive. Just build a folder I used XP-CD, and copy all of the contents of your respective Windows XP CD as folder.
Next, open a Command Prompt Start Run cmd, and proceed to the folder the place you downloaded SP3 cd foldername. Type the command: servicepack filename /integrate: drive/path. In my example the command is/integrate:E:XP-CD.
Consult the Service Pack documentation for additional information about supported integration scenarios.
This is a result of the fact that your particular Windows XP CD contains updates that is going to be automatically installed advertising media are setup. These sort of CDs usually be from larger OEM suppliers like Dell, HP, or other people.
You cannot utilize this type of CD to produce a slipstreamed install.
First, the files are going to be extracted, and then they will probably be integrated within your Windows XP files:
When ready, you need to get a confirmation. Windows XP Service Pack 3 has now been included in your original Windows XP files.
After you install IsoBuster, you'll be able to choose to use just the products free functionality for which we want to complete; IsoBuster will look like the whole picture below you must have your original Windows XP CD within the CD-ROM drive.
Start to extract the boot loader in the original Windows XP CD. Using IsoBuster, choose the folder Bootable CD, and right-click Microsoft. From the menu choose Extract Microsoft, and extract it for the folder on the hard drive where you might have your Windows XP files E:XP-CD in my case.
Next, start Nero Burning ROM, and select CD-ROM Boot inside the New Compilation window. On the Boot tab, select Image file under Source of boot image data, and browse to your location on the Microsoft file. Also enable Expert Settings, choosing No Emulation, and changing the Number of loaded sectors to 4 otherwise it wont boot!
You can configure the Label tab in your liking; I would however recommend you keep the Volume Label the identical as on your own original Windows XP CD. Here are some English Labels:
Next press New, and from your File Browser window, pick the files and folders out of your slipstreamed location in my case E:XP-CD. Now drag drop the selected files inside ISO1 window.
You now take over a Bootable, Slipstreamed Windows XP Service Pack 3 CD!
From some sources I hear you might need a Windows XP Home or Professional with SP2 Setup CD. You cannot slipstream SP3 into a classic Windows XP CD or even an XP with SP1 CD. Slipstreaming SP3 will simply work with the XP SP2 CD. Others have suggested that slipstreaming by having an SP1 integrated CD works. Here is exactly what I found:
Windows XP Gold : Slipstreaming SP3 perceived to work until it came on the point I had to activate Windows XP. It would not activate XP over the Internet may possibly also not update with the phone utilizing the automated system. I didnt speak to some live person over it though. Without activating I couldnt use Windows Update.
Windows XP SP2 : Slipstreaming SP3 worked fine. I also might skip putting inside product key during installation that was not an option while using XP gold slipstreamed version. I had to activate to make use of Windows Update - which worked without a challenge using the Internet activation - I didnt get any errors on Windows Update, and updates were provided.
Slipstreaming a Service Pack, is the method to integrate the Service Pack into your installation in order that with every new installation the Operating System and Service Pack are installed simultaneously.
Slipstreaming is generally done on network shares on corporate systems. But with all the advent of CD burners, it can do actually make some sense to the home user or business user to complete the same.
Microsoft added the cabability to Slipstream a Service Pack to Windows 2000 and Windows XP. It not merely has the advantage that after you reinstall your OS, it's not necessary to apply the Service Pack later, also if you update any Windows component later, you will be sure that you just get the best installation files if Windows needs any.
Download the complete Network Install with the Service Pack English version 266 MB, and save it to some directory folder on your own hard drive in my case D:XP-SP2. Other languages could be downloaded on the Microsoft Download Web site.
Note: don't use spaces within the folder name!
Next copy your Windows XP CD in your hard drive. Just make a folder I used XP-CD, and copy each of the contents of your respective Windows XP CD as folder.
Next, open a Command Prompt Start Run cmd, and navigate to the folder that you downloaded SP2 cd foldername. Type the command: servicepack filename /integrate: drive/path. In my example the command is WindowsXP-KB835935-SP2-ENU/integrate:D:XP-CD.
This is a result of the fact that your particular Windows XP CD contains updates that will probably be automatically installed advertising media are setup. This style of CDs will most likely be from larger OEM suppliers like Dell, HP, kinds.
You cannot employ this type of CD to develop a slipstreamed SP2 install.
First, the files will probably be extracted, and then suddenly they will probably be integrated with your Windows XP files:
When ready, you ought to get a confirmation. Windows XP Service Pack 2 has now been slipstreamed into the original Windows XP files.
For this part I used IsoBuster and Nero Burning ROM 7/a.splitYou can naturally use your own favorite CD-burning program. After you install IsoBuster, you'll be able to choose to use just the products free functionality for we want to accomplish; IsoBuster will look like the look below you must have your original Windows XP CD from the CD-ROM drive.
Start to extract the boot loader on the original Windows XP CD. Using IsoBuster, simply select the folder Bootable CD, and right-click Microsoft. From the menu choose Extract Microsoft, and extract it towards the folder with your hard drive where you might have your Windows XP files D:XP-CD in my case.
Next, start Nero Burning ROM, and select CD-ROM Boot within the New Compilation window. On the Boot tab, select Image file under Source of boot image data, and browse towards the location in the Microsoft file. Also enable Expert Settings, choosing No Emulation, and changing the Number of loaded sectors to 4 otherwise it wont boot!
If you might have an older version of Nero you wont hold the option Do Not Add ;1 ISO file version extension under Relax ISO Restrictions. You wont have the capacity to boot a new CD, so update Nero!
You can configure the Label tab on your liking; I would however recommend that you simply keep the Volume Label a similar as on your own original Windows XP CD. Here are some English Labels:
Next press New, and in the File Browser window, simply select the files and folders from a slipstreamed location in my case D:XP-CD. Now drag drop the selected files from the ISO1 window.
You have a Bootable, Slipstreamed Windows XP Service Pack 2 CD!
Last Updated: August 27, 2004
You have Windows 10, but this article is for the previous version of Windows. Get Windows 10 help
Windows XP support has finished. Keep your PC protected. Learn more
Hi thereyoure in search of Windows 10 info! We put that stuff in a brand new spot.
Get answers for your questions inside Windows forum.
Get assistance from a support professional on the phone, email, or chat.
Get answers in your questions inside the Windows7 forum.
Get aid from a support professional on the phone, email, or chat.
Get answers for your questions from the WindowsVista forum.
Get the help of a support professional on the phone, email, or chat.
Get answers on your questions within the WindowsXP forum.
Your feedback helps improve this web site.
We thank you for feedback.
Get the saying out. Share this site with your friends.
Stay hold of Windows.
As promised before, Microsoft has now officially released Service Pack 1 Final KB976932 for Windows 7 and Windows Server 2008 R2. The RTM of SP1 is obtainable for Free to everyone but validation is necessary in order to download it.
Windows 7 and Windows Server 2008 R2 SP1 helps maintain your PCs and servers about the latest support level. It also provides ongoing improvements for the Windows Operating System OS, by including previous updates delivered over Windows Update also as continuing incremental updates for the Windows 7 and Windows Server 2008 R2 platforms according to customer and partner feedback. This enables organizations to deploy an individual set of updates.
In order to download and install Windows 7 and Windows Server 2008 R2 SP1 you need to currently have a Release to Manufacturing RTM version of Windows 7 or Windows Server 2008 R2 already installed.
If youve previously installed a pre-release version of Windows 7 Windows Server 2008 R2 SP1 on the machine, you need to uninstall that version before installing SP1.
Dont download this when you are updating one computer, instead update to SP1 directly by downloading the necessary updates via Windows Update.
We will post the download links for Standalone packages of x86 and x64 system soon!
What will be the Standalone debugging symbols for? Do we demand it? What s the differences between Checked free?
Windows 7 service pack 1 which I will undoubtedly comment on as I am not using Windows server 2008 both at home and at work, they may be hell bent on using Windows server 2000! lol it appears to work decent although some folk have come to me with issues nevertheless their computer blue screened after their computer rebooted. I instructed them to complete a system restore because the system boot repair doesn t often solve this kind of issue.
This generally seems to happen by incorporating systems that don t have informed video hardware since it s a movie card issue. Some file from the service pack changes or enhances video performance which often can effect older video cards which often will give you the BSOD.
Anyhow that s my exposure to Windows 7 service pack 1.
Posted: Mon Sep 09, 2013 3:04 pm Post subject: Welcome to Windows XP Service Pack 4
Windows XP SP4 Unofficial Final is currently available!
Windows XP official support is finished. Many users - including me - who wont have the capacity to upgrade their old machines with a newer OS want to easily install all Windows updates within a convenient package. For this reason I started taking care of a Service Pack 4 package in September 2013.
Windows XP Unofficial SP4 ENU is really a cumulative update rollup for Windows XP x86 English. It could be applied with a live Windows XP system that has SP1, at minimum, installed or it could be slipstreamed integrated in almost any Windows XP installation media.
It includes updates for almost all Windows XP components, including MCE and Tablet PC. Request-only hotfixes happen to be included. Currently, Frameworks 4.0, 3.5, 1.1 and 1.0 Tablet PC only are included inside the Windows XP SP4 package. In addition, all post-eol updates Framework 1.1, 3.5 and 4.0 until May 2014 have already been included. 1.x, 3.5 versions are automatically installed/updated in live installations. Only Framework 3.5 is enabled automatically in integrated installation. Framework 1.1 will probably be always installed if Media Center Edition is found.
If you download the it is possible to also scan Windows Update for POSReady updates, as the POSReady trick may be included.
The installer will also be downloaded from the form of two ISOs. These ISOs is usually found inside the ISO for SP4 installer Cloud folder.
Windows XP SP4 security enhancements: Windows XP SP4 includes registry updates to improve security. I want to thank Stefan Kanthak, a burglar alarm expert that has kindly given me the mandatory information. These security enhancements address issues not fixed by Microsoft updates.
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 kind of special SP4 installation scenarios.
Windows XP SP4 Components Reference: A PDF file containing every update and component contained in Windows XP SP4.
You may also find HTML copies with the SP4 Release Notes, SP4 Live Installation Instructions and SP4 CD-ROM Installation Instructions. These files will also be included inside the SP4 installer.
Size: 4.46 MB 4677668 bytes
Size: 4.46 MB 4678008 bytes
This is SP4 Final OS Version: 5.1.2600.6532
WARNING! This thread is among the most trusted download place for Windows XP Unofficial SP4. Although some other sites could be trusted, users download at their unique risk. Generally avoid other untrusted download locations!
DISCLAIMER: The author shall cease held responsible for virtually every damage caused for a system. It is strongly recommended which you test this update before deployment!
Please get in touch at. You may also post you comments below.
1. Windows XP Unofficial SP4 is usually used in English only. Howewer, you'll be able to translate with languages using MUI packs.
2. Patches Cloud folder has a number of patched files. These files, when utilized on SP4 media, needs to be digitally signed. Some of these might be used to enable installation on systems with 4 GB of RAM or greater while some will help you changing the default group of components to get installed during CD-ROM installations.
3. nLite and Windows XP Professional SP4: nLite will detect all Windows XP SP4 Professional media as Media Center ones. Ignore any Media Center-related messages, this behaviour is usually a result in the way nLite checks whether Media Center occurs. Media Center will probably be available only when SP4 is slipsteamed in a very media Center installation source.
4. A note about POST-SP4 Hotfixes. The post-sp4 update KB2918614 updates MSI 4.5. It is imperative that you simply install this update seperately. After setting it up RUN THIS COMMAND:/regserver
Also, when you are Framework 4.0 be sure you run:
every time you install a fresh update or application Framework. This will boost systems performance and make sure reliability.
5. There is definitely an issue with updates I would choose to report, which isn't caused through the SP4 itself.
Scenario: Install SP4 - Framework 4.0- Run Windows Update Manual Check. - Install Updates - reboot twice - Installed all updates successfully - Run Windows Update Manual Check.
You can get Framework 4 GDR update KB2468871 within the optional updates.
HKLM, Framework 4 Client ProfileKB2468871 and
HKLM, Framework 4 Extended ProfileKB2468871registry keys.
6. You can install SP4 v2 together with SP4 version 1.0. Before installing, howewer, delete the HKLM, SystemCurrentControlSetControlSession ManagerEnvironment, TZ, 0, MEZ-1MESZ-2 key.
7. Post-SP4 Update Pack: An update pack, which may be slipstreamed into any SP4-integrated installation disk, is actually available. You will get it inside Post-SP4 Update Pack Cloud folder.
This update pack must be utilized on Windows XP SP4 Version 2- integrated media to Clean install Windows XP SP4 all post-SP4 updates prior to the date specified below.
READ BEFORE DOWNLOADING: UNLIKE ALL OTHER UPDATE PACKS its integration is performed in these 3 steps. It need to be done BEFORE USING nlite or RyanVM integrator, on the clean SP4 v2 source:
1. Copy the I386 folder from your ZIP FILE to your installation directory.
2. Copy the CMPNENTS folder from your ZIP FILE to your installation directory.
3A. If youre using HOME Edition copy the file from your ZIP FILE for the I386 subfolder with the installation folder. OR:
3B. If youre using PROFESSIONAL Edition copy the file in the ZIP FILE to your I386 subfolder on the installation folder.
4. Copy the updated from your SYSOC directoroy for the I386 directory from the installation folder depending on your own CD-ROM edition:
5. The PATCHES folder provides the updated versions of modified, , and allows to OPTIONALLY alter the default configuration of components.
After integrating the post-sp4 update pack you'll be able to perform any tweaks you wish.
WARNING: The post-sp4 update pack, unlike Windows XP Service Pack 4 v2, has undergone limited testing! Its designed primarily for Clean, CD-ROM/DVD-ROM-based installations
This update pack is according to Framework addons and 5eraphs POSReady addon.
49806998 bytes, reuploaded MD5: 6C722FC5F90583D4B5BF8393D13E73FB
8. POSReady 2009 updates easily ported to Windows XP post-EOL
I have easily ported all updates to Windows XP. I upload the sfx installers for testing with a monthly basis. You can buy these inside Post-SP4 Update repository Cloud folder.
NOTE: Framework 3.0 updates aren't offered via Windows Update in case you apply the POSReady update hack. They might be found inside update repository at the same time as the newest post-sp4 update pack.
9. Windows XP SP4 Source Files: These files have already been used to create Windows XP SP4 Final. They are made available to You beneath a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License. Download at the Unofficial SP4 Source Files Cloud Folder.
Last edited by harkaz on Mon Nov 24, 2014 3:21 pm
Posted: Mon Sep 09, 2013 5:32 pm Post subject:
Two thumbs up. EXCELLENT idea. Not my thing, contribution wise, but BEST OF LUCK together with your
By downloading an ELiTE Switchless Installer Addon you, the End User, accept to abide by any Terms of Use prescribed through the Freeware App contained within.
Posted: Tue Sep 10, 2013 4:32 pm Post subject:
Thanks available for you support. I am organising the SP3 files and preparing to update them later. I have made a decision to remove MSN Messenger completely, because its you can forget functional.
I will likely replace MSN Explorer featuring its latest free release. The current version is 13.562.5 Build 560 source:Wikipedia but I have found MSN Explorer 10 being a free download. Is this the newest free MSN Explorer version available?
Posted: Tue Sep 10, 2013 5:08 pm Post subject:
Ask OnePiece or userhidden, they may contain the complete group of post sp3 updates for XP without having superseded updates
Please, donate any PC hardware
Posted: Wed Sep 11, 2013 3:46 pm Post subject:
Thanks for your tip. Ill send them a PM later. Right now, Im taking care of Windows Messenger removal. Its effort after all. I have just finished modifying the and can proceed using the other setup files.
Posted: Wed Sep 11, 2013 3:51 pm Post subject:
It is exactly what was utilized to build the usp5 for win2k.
Posted: Wed Sep 11, 2013 4:48 pm Post subject:
Posted: Thu Sep 12, 2013 6:52 am Post subject:
I have a difficulty with editing file. It seems that this file is digitally signed. How do I patch the file to bypass this check?
Update: I tried copying the from an Nlited disk, nonetheless it failed.
I cant look for a patched anywhere, usually be down at the moment and all of other links are dead.
Location: Riverview, MI USA
Posted: Thu Sep 12, 2013 12:09 pm Post subject:
Have you tried Zacams patch addon, PatchAddonSYSSETUPInfSkipv14.7z? Apply it to some Windows source, then pull the file in the source once patched.
Posted: Thu Sep 12, 2013 1:49 pm Post subject:
Thanks for your link. I tried with nLite under Windows 7 XP SP3 compatibility mode however it failed to patch the file. I will retry with a real XP SP3 machine boost this post.
UPDATE: Nothing happens. is the original
INF Unlock Only: PatchAddonSYSSETUPInfSkipv14.7z
Location: Riverview, MI USA
Posted: Thu Sep 12, 2013 3:36 pm Post subject:
Requires Integrator 1.3.0 or better Service Pack two or three.
Posted: Thu Sep 12, 2013 4:26 pm Post subject:
I used RyanVMi for your patch. But now Windows XP Setup shows messages about installing unsigned drivers. Is there something wrong Im doing? Is there a way of preventing this?
I also had this matter with a manual patch I did.
UPDATE: This will not happen using the original file.
in ProductCatalogsToInstall section.
Posted: Thu Sep 12, 2013 5:18 pm Post subject:
Thank you for visiting Microsoft answers.
1. Open the Command Prompt window by clicking the Start button, clicking All Programs, clicking Accessories, and Right clicking Command Prompt and select
2. On the Command Prompt type inside the command/set nointegritychecks ON without worrying about quotes.
This will disable the Digital Signature.
By downloading an ELiTE Switchless Installer Addon you, the End User, accept abide by any Terms of Use prescribed with the Freeware App contained within.
Location: Riverview, MI USA
Posted: Thu Sep 12, 2013 5:44 pm Post subject:
Try this code inside your file, harkaz:
Posted: Thu Sep 12, 2013 9:13 pm Post subject:
I used RyanVMi with the patch. But now Windows XP Setup shows messages about installing unsigned drivers. Is there something wrong Im doing? Is there a means of avoiding this?
I also had this issue with a manual patch I did.
UPDATE: This won't happen together with the original file.
in ProductCatalogsToInstall section.
Posted: Fri Sep 13, 2013 2:20 am Post subject:
Elites option is intended for Windows 7 yet not for XP.
Creating and adding these lines will not be a solution for the service pack, since it has being as generic as is possible.
1. Find a different patch for, if you can.
2. Dont modify in any way, but this can impose limitations in creating the service pack.
3. Abandon the project, since you did.
I will begin with primary to determine if I can want to do something. A kernel debugger could possibly be useful. Have you tried this before?
Posted: Fri Sep 13, 2013 8:01 am Post subject:
The pSetupVerifyFile in is responsible because of this check. I will begin working onto it. I search Setup API SDK, nevertheless its not documented My goal right this moment is to know how pSetupVerifyFile works and change its parameters, never to prevent calling it.
A glance with MASM: Can somebody assist me understanding the Assembly language?
6974F0AE 68608A7169 push offset off69718A60 ; Setup MyLoadLibraryWithSignatureCheck failed pSetupVerifyFile, le %x, 00Ah, 000h
6974F0B6 68F88A7169 push offset off69718AF8 ; d xpspbasentsetupsyssetupmisc.c, 000h
The jz command prevents error messages from appearing when last result zero.
So edi and esi are subtracted. If theyre equal, it feels right zero, in order that it jumps to next routine. If it doesnt jump, it calls pSetupDebugPrint and it also prints larger than fifteen:
06/07/2010 20:44:24.515, d:xpspbasentsetupsyssetupmisc.c, 88,, Setup: MyLoadLibraryWithSignatureCheck failed pSetupVerifyFile, le 800b0100
The error code is 0x800B0100. This generally seems to be what were seeking because the mistake message setup throws is:
The signature for Windows XP Professional Setup is invalid. The error code is 800b0100.
No signature was present inside subject.
Ive located the section in HEX editor: the cmp command is in offset 3E4A9.
I need your help to build a patch here.
Posted: Fri Sep 13, 2013 12:46 pm Post subject:
Its been a looooong time since Ive done assembly work, and I may very well be totally wrong, but it appears to be like it could be easiest to just alter the jz into a jmp, ie always jump, not merely if zero. Assuming that this non-zero result, if present, wont damage the code located at loc6974F0CE. Unless Im missing something?
Posted: Fri Sep 13, 2013 1:33 pm Post subject:
I will attempt your suggestion bphlpt, this generally seems to be the remedy. However, I have a practical problem: How do I obtain the hex code machine code after changing jz to jmp? This is required to know so as to patch the Ive already found the offset. Should I go learning from your errors?
UPDATE: I just patched it. Im testing it right this moment. Will report back soon.
Posted: Fri Sep 13, 2013 1:52 pm Post subject:
Of course in the event the file you patched can also be digitally signed, ? Good luck!
Posted: Fri Sep 13, 2013 2:03 pm Post subject:
Well. Lets start from
I havent used a kernel debugger so Probably Ill need to utilize SoftICE after For as soon as, Ill work for the existing patch.
Posted: Fri Sep 13, 2013 2:58 pm Post subject:
OK guys, I started working about the original patch.
I have GOOD NEWS: I have vastly improved the first patch.
Now the ONLY problem I face is UNSIGNED BATTERY.
I will attempt to fix this later.
6974470A C785ACF5FFFF01000000 mov dword ptr ebp-0A54h,1
SOS this can be a address on the original patch
6974477B 749D jz loc6974471A ;patched here with jmp - succeeded, only issue with battery catalogs!
UPDATE: Additional flaw I discovered. noticed my patch:
Error: Setup detected the system file named isn't signed properly by Microsoft. This file could 't be restored to the appropriate Microsoft version.
Use the SFC utility to make sure that the integrity from the file.
Needless to express that sfc/scannow shows no worries.
However, I discovered which the file will not be present in dllcache and propably it is not protected by SFC!
Have you faced anything similar? For example, after modifying Setup billboard DLL?
Posted: Fri Sep 13, 2013 6:01 pm Post subject:
Isnt this exactly the same kind of error that OnePiece mentions here?
will talk about harmless error messages about some IE files like, , , , , , , brought on by the patched useful for integration then restored using the original one. If you dont tolerate it you'll be able to integrate moreover this Onepiece Repair IE8 cosmetic problems addon
Hash MD5 5C7AF8CA9F637C993F4AEEFFB63F39ED - Filesize: 1.28 Kb - updated 2008-03-27 which does hardly anything else than cleaning those false errors as part of your file. Please note that in many rare configurations the integration on this addon might cause issues, and we dont suggest to utilize it.
Posted: Fri Sep 13, 2013 7:16 pm Post subject:
SFC wont protect unsigned files.
Posted: Sat Sep 14, 2013 10:53 am Post subject:
Thanks to the tip, bphlpt, Ill take a look later.
tomasz86, Ive noticed that is additionally present inside the Lastgood and directory. Is this normal?
Currently working hard about the Battery unsigned problem.
Im making progress: I are already able to reproduce the issue I faced with all the original patch with the another one I applied yesterday. Im confident Ill find the perfect solution.
UPDATE: Having tried various patches, I havent yet intercepted the pay attention to battery Can someone let me debug it to seek out its region in EXE?
Note: This would be the region which, if changed, causes all catalogs not for being recognised correctly. This may seem to be outside of battery, however. It appears as if battery is checked inside a previous stage:
HOT SPOT Forcing this function to jump even though successful,
reproduces the issue with the initial patch!
697447F9 E8ECD90200 call jmppSetupVerifyCatalogFile ;verify catalog files
69744802 7520 jnz loc69744824 ;IF NOT SUCCESSFUL jump near
This line MUST NOT be changed; it reproduces the condition!
6974481D B819F60000 mov eax, 0F619h
69744822 EB05 jmp loc69744829 ; it failed installing the catalogs, so that it checks for driver signing policy.
Posted: Sun Sep 15, 2013 5:49 am Post subject:
Making progress: With a second patch, I was able to completely remove Messenger its catalog was manually removed by me in file. So it appears that this patch is needed for some modifications to to actually work, besides a simple improvement in verification routines. Now, one more step is taking out the Battery unsigned issue.
Posted: Sun Sep 15, 2013 7:00 am Post subject:
Fixed the Battery unsigned issue, will perfrom some additional checks before providing you the essential details.
Posted: Sun Sep 15, 2013 7:46 am Post subject: How to properly patch
1. Grab an original XP SP3 file.
2. Using a hex editor, like XVI32, open the dll file.
3. Go to address offset 33B7B.
5. Save changes to
6. Using modifype - c command or even a similar tool fix the PE checksum.
7. To get rid with the Battery unsigned issue, you've got to perform this additional step: Open the with notepad. Go on the DeviceInfsToInstall section from the INF file. Delete or comment the line while using file. Save changes.
8. Use the modern and files instead on the original ones.
Known side-effects: file reports that is just not properly signed. In addition, SFC will not protect after installing Windows. However, SFC will not report any problems after Windows installation.
Waiting on your comments after testing the revolutionary patch.
UPDATE: Removed some redundant steps.
Posted: Mon Sep 16, 2013 7:01 am Post subject:
NEW: After reverse engineering the Gurgelmeyers USP5 I have patched the modern package installer version 6.3.15.0 - thought it was in Onepieces update pack. This will considerably improve service pack 4 installation/unistallation experience.
Posted: Mon Sep 16, 2013 9:21 am Post subject:
Thanks harkaz, nice to study your adventures each day. Im not a pro, but I hope I can develop a Dutch SP4 if you're done with your complete
Yesterday, I saw xdots page at knowning that looked like an excellent way to collect all of the updates, but needless to say the files on his site are English I still tested all of them with nLite and Dutch XP, but needless to say? that didnt Well, it kinda worked, but there have been 2 errors.
So I hope youll inform us how we are able to build the SP4 if your times right, from the last posts, Im sure you may succeed!
Location: Riverview, MI USA
Posted: Mon Sep 16, 2013 11:57 am Post subject:
The following file, when utilized on RVMi, will apply harkazs patch steps 1-6.
Tested in VirtualBox 4.2.18.
Integrates with RyanVM Integrator 1.3.0 or later only. nLite doesnt do custom patching via files.
Last edited by 5eraph on Tue Sep 17, 2013 2:55 am
Posted: Tue Sep 17, 2013 2:02 am Post subject:
Thanks Atari800xl. Im implementing MSN Explorer 10.5 update now. I havent tested the removed Messenger yet.
A great approach to download important updates from microsoft no request-only hotfixes in ALL languages, is WSUSOffline: /
Ill make you stay updated together with the latest modifications to my project.
5eraph: Have you tested the modern patch? Is it working because it should?
Location: Riverview, MI USA
Posted: Tue Sep 17, 2013 2:42 am Post subject:
Tested and being intended following steps 7 and 8 within your patching guide. Details put into my previous post.
Posted: Tue Sep 17, 2013 9:09 am Post subject:
UPDATE: I may also have to correct catalog installation failure.
The error GetCatVersion: Failed to retrieve version details are also contained in Gurgelmeyers USP5. Probably patching it just isn't
It may perhaps be related with modified verification.
Issue seems to have already been fixed having a second patch I applied. Note that Gurgelmeyers suffered on the same issue likewise.
Messenger removed. The only thing I need to add for removal include the start menu messenger entries.
After that, Ill test slipstreaming to SP3 installation media.
Is there a computerized way to maintain the up-to-date?
Posted: Thu Sep 19, 2013 6:16 am Post subject:
Some instructions to develop a self extracting executable. Example: The D:SP4 fodler is used like a source for service pack 4 components
A. Extract the sfx in the KB942228 as an example package with the desired language
In the update package with the desired language, by using a hex editor, try to find MSCF string. the 3rd one.
From that you MSCF string in which the CABINET file that's integrated from the update package begins, delete from cursor
including that last MSCF string.
This the self-extracting header for EXE file.
B. Create the self-extracting cabinet
Using CABARC important, dont use makecab run the command
Mark the from the cabinet for auto-run.
The are going to be run any time you extract this cabinet. Any argument parsed to your sfx executable
will probably be parsed to the within the cabinet.
Using a hex editor, open the file you recently created.
Search for text without worrying about quotation marks.
Go on the hex editor section. In front with the hex numbers that translate to there is
Change 20 to 60 and save changes.
Append the sfx with file in a brand new self-extracting executable.
choose the ideal name to the EXE such as one above.
Optionally, put in a manifest to require elevation each and every time the SP4 package operates.
Posted: Thu Sep 19, 2013 10:52 am Post subject:
Same instructions because the ones above were already posted by WildBill four years ago here, and here you may also find my automated version.
As for Gurgelmeyer and USP5 - he didnt modify any signed system files so no additional patching was necessary except for that installer.
Posted: Thu Sep 19, 2013 3:21 pm Post subject:
Thanks! This was the original source of theseinstructions, and thanks for mentioning it! I posted it within this thread in order that everything is one place.
Now, I have an additional issue with No catalog file installs after SP4 installation completes. Similar problems arise when slipstreaming the SP4 to installation media.
I will endeavour to create a brand new patch.
Posted: Fri Sep 20, 2013 6:17 pm Post subject:
Seeing if this can subscribe me for the thread. Interested in this particular project. Have nothing else to state except all the best ..
Last edited by X on Sat Sep 21, 2013 1:15 pm
Posted: Sat Sep 21, 2013 8:04 am Post subject:
Thanks! Right now, Im trying to solve some issues concerning modified and files: no catalog is installed during service pack installation.
If you recognize Assembly, I need your help here:
After some examination on the file I tested various possible patches, Im almost certain that the issue is related with all the SetupDiCallClassInstaller function with the library.
This function fails with error code: 0x800b0100 No signature was present inside the object.
However, no unsigned driver dialog is displayed.
Probably the SPDEVINSTALLPARAMS structure, which can be passed for the SetupDiSetDeviceInstallParams function would be the key towards the solution. This function is generally called prior to a SetupDiCallClassInstaller and sets the product installation parameters.
Which flag with this function would cause this sort of behaviour? Luckily, the SPDEVINSTALLPARAMS structure is fully documented: /en-us/library/windows/hardware/ff552346
As we read there, the DIQUIETINSTALL flag on the structure seems to complete what were seeking:
Set should the device installer functions have to be silent and utilize default choices whenever you can. Class installers and co-installers shouldn't display any UI if it flag is defined.
We search the disassembly to the SetupDiSetDeviceInstallParams function.
0107A566 C7858CF8FFFF04010000 mov dword ptr ebp-774h,104h
0107A57E 83BD98F8FFFF01 cmp dword ptr ebp-768h,1
0107A5B3 838DA8F8FFFFFF or dword ptr ebp-758h,0FFFFFFFFh
0107A5C3 C785C8FBFFFF28010000 mov dword ptr ebp-438h,128h
0107A5DB 818DD0FBFFFF00080004 or dword ptr ebp-430h,4000800h
0107A5EE C785CCFBFFFF00008000 mov dword ptr ebp-434h,800000h
0107A609 68D4720201 push offset off010272D4 ; SetupDiSetDeviceInstallParams failed with error 0x%lx,00Ah, 000h
A search in setupapi.h in Windows SDK with the DIQUIETINSTALL value provides us the hex value 0x00800000.
We can discover the value at offset 0107A5EE above, just ahead of the SetupDiSetDeviceInstallParams function is termed. An amazing coincidence Probably it installation flags are retrieved utilizing the SetupDiGetDeviceInstallParamsA call at 0107A5CD and the DIQUIETINSTALL value is added to the crooks to force a silent UI.
My goal is clear here: I want to take off the additional flag.
I attempt and test this immediately afterwards, but I wish to hear your suggestions.
Posted: Sat Sep 21, 2013 12:14 pm Post subject:
Changing the parameter to 0 changed next to nothing.
Probably it needs some debugging.
For the instant Im working within the other errors I havent checked.
The GetCatVersion failure is really a characteristic example. This error is also found in Windows 2000 USP5 when applied in addition to Windows 2000 RTM. I don't realize if it will solve the situation however.
Posted: Sat Sep 21, 2013 1:22 pm Post subject:
Its hard to install all catalogs which has a modified with a live system.
Im abandoning the idea of by using a patched for installation on the LIVE system.
After all, an improved is required limited to modification to set up catalogs during Windows XP Setup.
Posted: Sun Sep 22, 2013 4:22 am Post subject:
I put back the main and files but it really did not fix the challenge!
Location: Riverview, MI USA
Posted: Sun Sep 22, 2013 6:33 am Post subject:
Are you getting any catalog files to setup? Would it help to work with a command line tool to set up them, like SignTool?
Posted: Sun Sep 22, 2013 7:04 am Post subject:
No catalogs are installed in any way. I will test signtool. It seems how the issue is related to messenger removed INF files - the catalog fails.
Location: Riverview, MI USA
Posted: Sun Sep 22, 2013 7:44 am Post subject:
You can find the most recent known version of SignTool in the addon of mine.
Posted: Sun Sep 22, 2013 11:30 am Post subject:
When I manually aimed to add some catalogs with signtool, it reported no problems.
Im trying to discover out why cant do that.
UPDATE: An interesting observation: After installing SP4, the motorist is the only one that's signed. On another hand, is unsigned. However, BOTH FILES are signed by, as signtool indicated!
UPDATE2: After some testing, this indicates that the GetCatVersion error is tightly related to wkth the patch placed on skip verification,
The same error appears regardless if changing nothing in existing catalogs remain installed however, thus avoiding further complications.
Posted: Mon Sep 23, 2013 3:33 pm Post subject:
After all, I are already able to put in the SP4 along with SP3 with all of the catalogs installed. The GetCatVersion error remains present. I have to work with the original, and files for installation using a live system.
Are ALL these files required for any sysprep installation - I know that is needed. Is there a patch to accept an improved in GUI mode setup?
Another issue I detected: When I create a brand new user profile, it attempts to configure Messenger, nevertheless it complains about not being present Ive deleted it in SP4, in addition to messenger. How do I update the registry to take out this?
Posted: Mon Sep 23, 2013 4:23 pm Post subject:
Another issue I detected: When I create a different user profile, it efforts to configure Messenger, however it complains about not being present Ive deleted it in SP4, in addition to messenger. How do I update the registry to take out this?
Please, donate a cheap PC hardware
Posted: Mon Sep 23, 2013 4:46 pm Post subject:
Thanks ricktendo64 I will update the SP installer.
Guess what? Just added an improved and flawlessly It appears that is the culprit. Lets see whether we can fix this concern
Posted: Tue Sep 24, 2013 12:37 pm Post subject:
also replaced the, x, with,, in file
however it didnt fix the challenge.
I could keep this patch for CD-ROM installations and attempt to intercept the check.
Posted: Mon Sep 09, 2013 3:04 pm Post subject: Welcome to Windows XP Service Pack 4
Windows XP SP4 Unofficial Final has become available!
Windows XP official support ends. Many users - including me - who wont manage to upgrade their old machines to your newer OS wish to easily install all Windows updates in a single convenient package. For this reason I started implementing a Service Pack 4 package in September 2013.
Windows XP Unofficial SP4 ENU is often a cumulative update rollup for Windows XP x86 English. It might be applied with a live Windows XP system containing SP1, at minimum, installed or it might be slipstreamed integrated in almost any Windows XP installation media.
It includes updates for many Windows XP components, including MCE and Tablet PC. Request-only hotfixes are already included. Currently, Frameworks 4.0, 3.5, 1.1 and 1.0 Tablet PC only are included inside Windows XP SP4 package. In addition, all post-eol updates Framework 1.1, 3.5 and 4.0 until May 2014 are already included. 1.x, 3.5 versions are automatically installed/updated in live installations. Only Framework 3.5 is enabled automagically in integrated installation. Framework 1.1 will probably be always installed if Media Center Edition is there.
If you download the it is possible to also scan Windows Update for POSReady updates, considering that the POSReady trick has become included.
The installer will also be downloaded from the form of two ISOs. These ISOs may be found inside ISO for SP4 installer Cloud folder.
Windows XP SP4 security enhancements: Windows XP SP4 includes registry updates to improve security. I want to thank Stefan Kanthak, a burglar expert that has kindly given me the required information. These security enhancements address issues not fixed by Microsoft updates.
The Documentation Cloud folder contains all Windows XP SP4 documentation files.
Windows XP SP4 Deployment Guide folder: A series of 6 WMV videos discussing one impressive SP4 installation scenarios.
Windows XP SP4 Components Reference: A PDF file containing every update and component incorporated into Windows XP SP4.
You could also find HTML copies from the SP4 Release Notes, SP4 Live Installation Instructions and SP4 CD-ROM Installation Instructions. These files may also be included inside the SP4 installer.
This is SP4 Final OS Version: 5.1.2600.6532
WARNING! This thread is among the most trusted download spot for Windows XP Unofficial SP4. Although some other sites may be trusted, users download at their very own risk. Generally avoid other untrusted download locations!
DISCLAIMER: The author shall not held responsible for just about any damage caused on your system. It is strongly recommended you test this update before deployment!
Please get in touch at. You may also post you comments below.
1. Windows XP Unofficial SP4 is usually used in English only. Howewer, you are able to translate with other languages using MUI packs.
2. Patches Cloud folder incorporates a number of patched files. These files, when combined with SP4 media, needs to be digitally signed. Some of these could be used to enable installation on systems with 4 GB of RAM or greater while some will help you changing the default pair of components for being installed during CD-ROM installations.
3. nLite and Windows XP Professional SP4: nLite will detect all Windows XP SP4 Professional media as Media Center ones. Ignore any Media Center-related messages, this behaviour is often a result on the way nLite checks whether Media Center exists. Media Center will likely be available only when SP4 is slipsteamed in the media Center installation source.
4. A note about POST-SP4 Hotfixes. The post-sp4 update KB2918614 updates MSI 4.5. It is imperative that you just install this update seperately. After setting it up RUN THIS COMMAND:/regserver
Also, when you are Framework 4.0 you should definitely run:
every time you install a different update or application Framework. This will boost systems performance make certain reliability.
5. There is undoubtedly an issue with updates I want to report, which is just not caused because of the SP4 itself.
Scenario: Install SP4 - Framework 4.0- Run Windows Update Manual Check. - Install Updates - reboot twice - Installed all updates successfully - Run Windows Update Manual Check.
You can get Framework 4 GDR update KB2468871 from the optional updates.
HKLM, Framework 4 Client ProfileKB2468871 and
HKLM, Framework 4 Extended ProfileKB2468871registry keys.
6. You can install SP4 v2 over SP4 version 1.0. Before installing, howewer, delete the HKLM, SystemCurrentControlSetControlSession ManagerEnvironment, TZ, 0, MEZ-1MESZ-2 key.
7. Post-SP4 Update Pack : An update pack, which is usually slipstreamed into any SP4-integrated installation disk, is available. You can buy it from the Post-SP4 Update Pack Cloud folder.
This update pack must be combined with Windows XP SP4 Version 2- integrated media to Clean install Windows XP SP4 all post-SP4 updates till the date specified below.
READ BEFORE DOWNLOADING: UNLIKE ALL OTHER UPDATE PACKS its integration is finished in these 3 steps. It need to be done BEFORE USING nlite or RyanVM integrator, over a clean SP4 v2 source:
1. Copy the I386 folder on the ZIP FILE towards the installation directory.
2. Copy the CMPNENTS folder from your ZIP FILE for the installation directory.
3A. If youre using HOME Edition copy the file on the ZIP FILE on the I386 subfolder in the installation folder. OR:
3B. If youre using PROFESSIONAL Edition copy the file on the ZIP FILE to your I386 subfolder on the installation folder.
4. Copy the updated in the SYSOC directoroy to your I386 directory inside the installation folder depending on the CD-ROM edition:
5. The PATCHES folder is the updated versions of modified, , and allows to OPTIONALLY affect the default configuration of components.
After integrating the post-sp4 update pack it is possible to perform any tweaks you need.
WARNING: The post-sp4 update pack, unlike Windows XP Service Pack 4 v2, has undergone limited testing! Its designed primarily for Clean, CD-ROM/DVD-ROM-based installations
This update pack is dependant on Framework addons and 5eraphs POSReady addon.
49806998 bytes, reuploaded MD5: 6C722FC5F90583D4B5BF8393D13E73FB
8. POSReady 2009 updates easily ported to Windows XP post-EOL
I have easily ported all updates to Windows XP. I upload the sfx installers for testing using a monthly basis. You can buy these within the Post-SP4 Update repository Cloud folder.
NOTE: Framework 3.0 updates aren't offered via Windows Update although you may apply the POSReady update hack. They may be found inside the update repository too as the most up-to-date post-sp4 update pack.
9. Windows XP SP4 Source Files: These files happen to be used to make Windows XP SP4 Final. They are made available to You within Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License. Download offered by the Unofficial SP4 Source Files Cloud Folder.
Last edited by harkaz on Mon Nov 24, 2014 3:21 pm
Posted: Mon Sep 09, 2013 5:32 pm Post subject:
Two thumbs up. EXCELLENT idea. Not my thing, contribution wise, but BEST OF LUCK together with your
By downloading an ELiTE Switchless Installer Addon you, the End User, accept abide by any Terms of Use prescribed with the Freeware App contained within.
Thanks to suit your needs support. I am organising the SP3 files and preparing to update them later. I have made a decision to remove MSN Messenger completely, because its forget about functional.
I may also replace MSN Explorer featuring its latest free release. The current version is 13.562.5 Build 560 source:Wikipedia but I have found MSN Explorer 10 like a free download. Is this the newest free MSN Explorer version available?
Posted: Tue Sep 10, 2013 5:08 pm Post subject:
Ask OnePiece or userhidden, they may contain the complete group of post sp3 updates for XP without superseded updates
Please, donate a cheap PC hardware
Posted: Wed Sep 11, 2013 3:46 pm Post subject:
Thanks for that tip. Ill send them a PM later. Right now, Im taking care of Windows Messenger removal. Its working hard after all. I have just finished modifying the and can proceed using the other setup files.
Posted: Wed Sep 11, 2013 3:51 pm Post subject:
It is really what was utilized to build the usp5 for win2k.
Posted: Thu Sep 12, 2013 6:52 am Post subject:
I have problems with editing file. It seems which the file is digitally signed. How do I patch the file to bypass this check?
Update: I tried copying the from an Nlited disk, but it really failed.
I cant look for a patched anywhere, generally seems to be down at the moment and many types of other links are dead.
Location: Riverview, MI USA
Posted: Thu Sep 12, 2013 12:09 pm Post subject:
Have you tried Zacams patch addon, PatchAddonSYSSETUPInfSkipv14.7z? Apply it into a Windows source, then pull the file on the source once patched.
Posted: Thu Sep 12, 2013 1:49 pm Post subject:
Thanks with the link. I tried with nLite under Windows 7 XP SP3 compatibility mode however it failed to patch the file. I will retry using a real XP SP3 machine rrmprove this post.
UPDATE: Nothing happens. continues to be the original
INF Unlock Only: PatchAddonSYSSETUPInfSkipv14.7z
Location: Riverview, MI USA
Posted: Thu Sep 12, 2013 3:36 pm Post subject:
Requires Integrator 1.3.0 or older Service Pack two or three.
I used RyanVMi with the patch. But now Windows XP Setup shows messages about installing unsigned drivers. Is there something wrong Im doing? Is there a method for preventing this?
I also had this concern with a manual patch I did.
UPDATE: This won't happen with all the original file.
in ProductCatalogsToInstall section.
Posted: Thu Sep 12, 2013 5:18 pm Post subject:
Thank you for visiting Microsoft answers.
1. Open the Command Prompt window by clicking the Start button, clicking All Programs, clicking Accessories, after which Right clicking Command Prompt and select
2. On the Command Prompt type within the command/set nointegritychecks ON without worrying about quotes.
This will disable the Digital Signature.
By downloading an ELiTE Switchless Installer Addon you, the End User, say yes to abide by any Terms of Use prescribed through the Freeware App contained within.
Location: Riverview, MI USA
Posted: Thu Sep 12, 2013 5:44 pm Post subject:
Try this code within your file, harkaz:
Posted: Thu Sep 12, 2013 9:13 pm Post subject:
I used RyanVMi to the patch. But now Windows XP Setup shows messages about installing unsigned drivers. Is there something wrong Im doing? Is there a way of avoiding this?
I also had this issue with a manual patch I did.
UPDATE: This won't happen using the original file.
in ProductCatalogsToInstall section.
Posted: Fri Sep 13, 2013 2:20 am Post subject:
Elites option would be intended for Windows 7 yet not for XP.
Creating and adding these lines just isn't a solution for the service pack, as it has being as generic as it can be.
1. Find a different patch for, if you can.
2. Dont modify in any respect, but this can impose limitations in creating the service pack.
3. Abandon the project, while you did.
I begins with primary to determine if I can take action. A kernel debugger could be useful. Have you tried this before?
Posted: Fri Sep 13, 2013 8:01 am Post subject:
The pSetupVerifyFile in is responsible due to this check. I will become working upon it. I search Setup API SDK, however its not documented My goal today is to appreciate how pSetupVerifyFile works and change its parameters, never to prevent calling it.
A glimpse with MASM: Can somebody assist me to understanding the Assembly language?
6974F0AE 68608A7169 push offset off69718A60 ; Setup MyLoadLibraryWithSignatureCheck failed pSetupVerifyFile, le %x, 00Ah, 000h
6974F0B6 68F88A7169 push offset off69718AF8 ; d xpspbasentsetupsyssetupmisc.c, 000h
The jz command prevents error messages from appearing when last result zero.
So edi and esi are subtracted. If theyre equal, it makes sense zero, thus it jumps to next routine. If it doesnt jump, it calls pSetupDebugPrint plus it prints the mistake:
06/07/2010 20:44:24.515, d:xpspbasentsetupsyssetupmisc.c, 88,, Setup: MyLoadLibraryWithSignatureCheck failed pSetupVerifyFile, le 800b0100
The error code is 0x800B0100. This generally seems to be what were trying to find because whole body message setup throws is:
The signature for Windows XP Professional Setup is invalid. The error code is 800b0100.
No signature was present inside the subject.
Ive located the section in HEX editor: the cmp command is a offset 3E4A9.
I need your help to produce a patch here.
Posted: Fri Sep 13, 2013 12:46 pm Post subject:
Its been a looooong time since Ive done assembly work, and I could possibly be totally wrong, but it appears like it could be easiest to just customize the jz to your jmp, ie always jump, besides if zero. Assuming that this non-zero result, if present, wont wreck the code located at loc6974F0CE. Unless Im missing something?
Posted: Fri Sep 13, 2013 1:33 pm Post subject:
I will endeavour your suggestion bphlpt, this may seem to be the perfect solution is. However, I have a practical problem: How do I find the hex code machine code after changing jz to jmp? This is vital to know as a way to patch the Ive already found the offset. Should I go experimenting?
UPDATE: I just patched it. Im testing it at the moment. Will report back soon.
Posted: Fri Sep 13, 2013 1:52 pm Post subject:
Of course should the file you patched can also be digitally signed, ? Good luck!
Posted: Fri Sep 13, 2013 2:03 pm Post subject:
Well. Lets start from
I havent used a kernel debugger so Probably Ill need to make use of SoftICE after For the second, Ill work within the existing patch.
Posted: Fri Sep 13, 2013 2:58 pm Post subject:
OK guys, I started working about the original patch.
I have GOOD NEWS: I have vastly improved an original patch.
Now the ONLY problem I face is UNSIGNED BATTERY.
I attempt to fix this later.
6974470A C785ACF5FFFF01000000 mov dword ptr ebp-0A54h,1
SOS this is actually the address in the original patch
6974477B 749D jz loc6974471A ;patched here with jmp - succeeded, only downside to battery catalogs!
UPDATE: Additional flaw I discovered. noticed my patch:
Error: Setup detected which the system file named just isn't signed properly by Microsoft. This file could not restored to the proper Microsoft version.
Use the SFC utility to substantiate the integrity from the file.
Needless to state that sfc/scannow shows no worries.
However, I discovered the file just isn't present in dllcache and propably it is not protected by SFC!
Have you faced anything similar? For example, after modifying Setup billboard DLL?
Posted: Fri Sep 13, 2013 6:01 pm Post subject:
Isnt this the identical kind of error that OnePiece mentions here?
will indicate harmless error messages about some IE files like, , , , , , , attributable to the patched used by integration after which restored while using original one. If you dont tolerate it you'll be able to integrate additionally this Onepiece Repair IE8 cosmetic problems addon
Hash MD5 5C7AF8CA9F637C993F4AEEFFB63F39ED - Filesize: 1.28 Kb - updated 2008-03-27 which does little else than cleaning those false errors with your file. Please note that in certain rare configurations the integration with this addon might cause issues, and we all dont suggest to make use of it.
Posted: Fri Sep 13, 2013 7:16 pm Post subject:
SFC wont protect unsigned files.
Posted: Sat Sep 14, 2013 10:53 am Post subject:
Thanks with the tip, bphlpt, Ill follow through later.
tomasz86, Ive noticed that is usually present inside the Lastgood and directory. Is this normal?
Currently working hard within the Battery unsigned problem.
Im making progress: I are already able to reproduce the issue I faced with all the original patch with the a different one I applied yesterday. Im confident Ill find the perfect solution.
UPDATE: Having tried various patches, I havent yet intercepted the pay attention to battery Can someone assist me debug it to seek out its region in EXE?
Note: This will be the region which, if changed, causes all catalogs not for being recognised correctly. This may seem to be separate from battery, however. It appears that battery is checked within a previous stage:
HOT SPOT Forcing this function to jump regardless of whether successful,
reproduces the condition with the first patch!
697447F9 E8ECD90200 call jmppSetupVerifyCatalogFile ;verify catalog files
69744802 7520 jnz loc69744824 ;IF NOT SUCCESSFUL jump near
This line MUST NOT be changed; it reproduces the situation!
6974481D B819F60000 mov eax, 0F619h
69744822 EB05 jmp loc69744829 ; it failed installing the catalogs, therefore it checks for driver signing policy.
Posted: Sun Sep 15, 2013 5:49 am Post subject:
Making progress: With a second patch, I were completely remove Messenger its catalog was manually removed by me in file. So it appears to be that this patch is necessary for some modifications to to actually be effective, other than a simple alternation in verification routines. Now, a final step is treatment of Battery unsigned issue.
Posted: Sun Sep 15, 2013 7:00 am Post subject:
Fixed the Battery unsigned issue, will perfrom some additional checks before providing you with the essential details.
Posted: Sun Sep 15, 2013 7:46 am Post subject: How to properly patch
1. Grab the initial XP SP3 file.
2. Using a hex editor, like XVI32, open the dll file.
3. Go to address offset 33B7B.
5. Save changes to
6. Using modifype - c command or maybe a similar tool fix the PE checksum.
7. To get rid on the Battery unsigned issue, you might have to perform this additional step: Open the with notepad. Go on the DeviceInfsToInstall section with the INF file. Delete or comment the line using the file. Save changes.
8. Use the revolutionary and files instead on the original ones.
Known side-effects: file reports that isn't properly signed. In addition, SFC doesn't protect after installing Windows. However, SFC doesn't report any problems after Windows installation.
Waiting to your comments after testing the modern patch.
UPDATE: Removed some redundant steps.
Posted: Mon Sep 16, 2013 7:01 am Post subject:
NEW: After reverse engineering the Gurgelmeyers USP5 I have patched the modern package installer version 6.3.15.0 - thought it was in Onepieces update pack. This will considerably improve service pack 4 installation/unistallation experience.
Posted: Mon Sep 16, 2013 9:21 am Post subject:
Thanks harkaz, nice to see your adventures each day. Im not a pro, but I hope I can make a Dutch SP4 when you are done with your complete
Yesterday, I saw xdots page at knowning that looked like a good way to collect all of the updates, but needless to say the files on his site are English I still tested these with nLite and Dutch XP, but naturally? that didnt Well, it kinda worked, but there have been 2 errors.
So I hope youll signify how you can build the SP4 if your times right, through your last posts, Im sure you are going to succeed!
Location: Riverview, MI USA
Posted: Mon Sep 16, 2013 11:57 am Post subject:
The following file, when used in combination with RVMi, will apply harkazs patch steps 1-6.
Tested in VirtualBox 4.2.18.
Integrates with RyanVM Integrator 1.3.0 or later only. nLite doesnt do custom patching via files.
Last edited by 5eraph on Tue Sep 17, 2013 2:55 am
Posted: Tue Sep 17, 2013 2:02 am Post subject:
Thanks Atari800xl. Im working away at MSN Explorer 10.5 update now. I havent tested the removed Messenger yet.
A great method to download crucial updates from microsoft no request-only hotfixes in ALL languages, is WSUSOffline: /
Ill make you stay updated with all the latest modifications in my project.
5eraph: Have you tested the revolutionary patch? Is it working since it should?
Location: Riverview, MI USA
Posted: Tue Sep 17, 2013 2:42 am Post subject:
Tested and being employed as intended following steps 7 and 8 of the patching guide. Details included in my previous post.
Posted: Tue Sep 17, 2013 9:09 am Post subject:
UPDATE: I may also have to solve catalog installation failure.
The error GetCatVersion: Failed to retrieve version data is also within Gurgelmeyers USP5. Probably patching it will not be
It may perhaps be related with modified verification.
Issue seems to have already been fixed having a second patch I applied. Note that Gurgelmeyers suffered in the same issue too.
Messenger removed. The only thing I need to add for removal will be the start menu messenger entries.
After that, Ill test slipstreaming to SP3 installation media.
Is there a computerized way to maintain the up-to-date?
Posted: Thu Sep 19, 2013 6:16 am Post subject:
Some instructions to produce a self extracting executable. Example: The D:SP4 fodler is used as being a source for service pack 4 components
A. Extract the sfx through the KB942228 one example is package for that desired language
In the update package with the desired language, utilizing a hex editor, look for MSCF string. your third one.
From any particular one MSCF string the spot that the CABINET file which can be integrated within the update package begins, delete from cursor
including that last MSCF string.
This the self-extracting header for EXE file.
B. Create the self-extracting cabinet
Using CABARC important, dont use makecab run the command
Mark the within the cabinet for auto-run.
The will probably be run any time you extract your cabinet. Any argument parsed on the sfx executable
will probably be parsed to the within the cabinet.
Using a hex editor, open the file you merely created.
Search for text without worrying about quotation marks.
Go towards the hex editor section. In front in the hex numbers that translate to there is
Change 20 to 60 and save changes.
Append the sfx with file in a different self-extracting executable.
choose an appropriate name for your EXE such as the one above.
Optionally, convey a manifest to require elevation each and every time the SP4 package operates.
Posted: Thu Sep 19, 2013 10:52 am Post subject:
Same instructions because ones above were already posted by WildBill several years ago here, and here it is possible to also find my automated version.
As for Gurgelmeyer and USP5 - he didnt modify any signed system files so no additional patching was necessary except for that installer.
Posted: Thu Sep 19, 2013 3:21 pm Post subject:
Thanks! This was the original source of theseinstructions, and appreciation for mentioning it! I posted it within this thread in order that everything is one place.
Now, I have an additional issue with No catalog file installs after SP4 installation completes. Similar problems arise when slipstreaming the SP4 to installation media.
I will attempt to create a whole new patch.
Posted: Fri Sep 20, 2013 6:17 pm Post subject:
Seeing if this will likely subscribe me towards the thread. Interested within this project. Have nothing else to express except all the best ..
Last edited by X on Sat Sep 21, 2013 1:15 pm
Posted: Sat Sep 21, 2013 8:04 am Post subject:
Thanks! Right now, Im trying to correct some issues involving modified and files: no catalog is installed during service pack installation.
If you recognize Assembly, I need your help here:
After some examination from the file I tested various possible patches, Im almost certain that the challenge is related together with the SetupDiCallClassInstaller function from the library.
This function fails with error code: 0x800b0100 No signature was present within the object.
However, no unsigned driver dialog is displayed.
Probably the SPDEVINSTALLPARAMS structure, which can be passed on the SetupDiSetDeviceInstallParams function would be the key to your solution. This function is often called prior to the SetupDiCallClassInstaller and sets it installation parameters.
Which flag with this function would cause this kind of behaviour? Luckily, the SPDEVINSTALLPARAMS structure is fully documented: /en-us/library/windows/hardware/ff552346
As we read there, the DIQUIETINSTALL flag with the structure seems to accomplish what were seeking:
Set if your device installer functions should be silent and rehearse default choices whenever we can. Class installers and co-installers shouldn't display any UI if the flag is scheduled.
We search the disassembly for that SetupDiSetDeviceInstallParams function.
0107A566 C7858CF8FFFF04010000 mov dword ptr ebp-774h,104h
0107A57E 83BD98F8FFFF01 cmp dword ptr ebp-768h,1
0107A5B3 838DA8F8FFFFFF or dword ptr ebp-758h,0FFFFFFFFh
0107A5C3 C785C8FBFFFF28010000 mov dword ptr ebp-438h,128h
0107A5DB 818DD0FBFFFF00080004 or dword ptr ebp-430h,4000800h
0107A5EE C785CCFBFFFF00008000 mov dword ptr ebp-434h,800000h
0107A609 68D4720201 push offset off010272D4 ; SetupDiSetDeviceInstallParams failed with error 0x%lx,00Ah, 000h
A search in setupapi.h in Windows SDK to the DIQUIETINSTALL value provides the hex value 0x00800000.
We can chose the value at offset 0107A5EE above, just prior to SetupDiSetDeviceInstallParams function is referred to as. An amazing coincidence Probably these devices installation flags are retrieved utilizing the SetupDiGetDeviceInstallParamsA call at 0107A5CD and after that the DIQUIETINSTALL value is added to those to force a silent UI.
My goal is pretty obvious here: I want to get rid of the additional flag.
I attempt and test this quickly afterwards, but I wish to hear your suggestions.
Posted: Sat Sep 21, 2013 12:14 pm Post subject:
Changing the parameter to 0 changed next to nothing.
Probably it takes some debugging.
For as soon as Im working about the other errors I havent checked.
The GetCatVersion failure can be a characteristic example. This error is also seen in Windows 2000 USP5 when applied along with Windows 2000 RTM. I do not know if it will solve the issue however.
Posted: Sat Sep 21, 2013 1:22 pm Post subject:
Its hard to install all catalogs which has a modified over a live system.
Im abandoning the idea of utilizing a patched for installation on the LIVE system.
After all, an improved is required exclusively for modification to set up catalogs during Windows XP Setup.
I put back the first and files nevertheless it did not fix the issue!
Location: Riverview, MI USA
Posted: Sun Sep 22, 2013 6:33 am Post subject:
Are you getting any catalog files to put in? Would it help make use of a command line tool to fit them, like SignTool?
Posted: Sun Sep 22, 2013 7:04 am Post subject:
No catalogs are installed whatsoever. I will test signtool. It seems the issue is involving messenger removed INF files - the catalog fails.
Location: Riverview, MI USA
Posted: Sun Sep 22, 2013 7:44 am Post subject:
You can find the most recent known version of SignTool within an addon of mine.
Posted: Sun Sep 22, 2013 11:30 am Post subject:
When I manually attemptedto add some catalogs with signtool, it reported no problems.
Im trying to locate out why cant do that.
UPDATE: An interesting observation: After installing SP4, the motorist is the only one that's signed. On one other hand, is unsigned. However, BOTH FILES are signed by, as signtool indicated!
UPDATE2: After some testing, it seems like that the GetCatVersion error is highly relevant to wkth the patch used on skip verification,
The same error appears even if changing nothing in existing catalogs remain installed however, thus avoiding further complications.
Posted: Mon Sep 23, 2013 3:33 pm Post subject:
After all, I are actually able to fit the SP4 along with SP3 with every one of the catalogs installed. The GetCatVersion error continues to be present. I have to make use of the original, and files for installation using a live system.
Are ALL these files required to get a sysprep installation - I know that is needed. Is there a patch to accept an improved in GUI mode setup?
Another issue I detected: When I create a different user profile, it attempts to configure Messenger, nevertheless it complains about not being present Ive deleted it in SP4, together with messenger. How do I update the registry to eliminate this?
Another issue I detected: When I create a fresh user profile, it efforts to configure Messenger, but it really complains about not being present Ive deleted it in SP4, in addition to messenger. How do I update the registry to get rid of this?
Please, donate any PC hardware
Thanks ricktendo64 I will update the SP installer.
Guess what? Just added an improved and flawlessly It entirely possible that is the culprit. Lets see whether we can fix this concern
Posted: Tue Sep 24, 2013 12:37 pm Post subject:
also replaced the, x, with,, in file
however it didnt fix the problem.
I could keep this patch for CD-ROM installations and then try to intercept the check.