I ran Sfc /scannow from the cmd prompt in order to try to fix an error I am continuously getting where windows explorer shuts down. I am trying to find out if I am missing some needed files that may be missing or corrupt. My original operating system was windows xp media edition however when SP3 was loaded it now comes up saying I have windows xp professional and as a result the Sfc /scannow verifcation process is asking me to insert your Windows XP Professional Service Pack 3 CD which of course I do not have since it was a downloaded update from microsoft. I downloaded 'xpsp35512.0usax86frespcd.iso' based on one of the MS forums and burned this to a CD however when I put this CD in it says it's the wrong cd. If you find events to post, here is how to do that: Look in the Event Viewer for clues around the time of the incident Here is a method to post the specific information about individual events. To see the Event Viewer logs, click Start, Settings, Control Panel, Administrative Tools, Event Viewer. A shortcut to Event Viewer is to click Start, Run and in the box enter:%SystemRoot% system32 eventvwr.msc /s Click OK to launch the Event Viewer.

1. Windows Xp Pro Sp3 Iso
2. Windows Xp Service Pack 3 Iso

Microsoft Windows XP Professional ISO image with service pack 3 is the latest edition in Win XP series. Get Windows XP SP3 ISO Full Version Free Download through our direct link available for the users of the Softlay.net. Amazingly, even after 13 long years, this OS hasn’t let down its users.

Windows Xp Pro Sp3 Iso

The most interesting logs are usually the Application and System logs. Some logs such as Security and Internet Explorer may be completely empty or have only a few items. The default settings for XP is not to log all that activity unless you need to troubleshoot some issue in those areas. If you enable the logging for them the logs fill up quickly and could negatively effect your system performance with all the extra (usually unnecessary) activity. If you have Microsoft Office installed, it has its own logs and they may be empty or occasional boring activity or very little activity if there is no problem with your Office applications. This is normal.

Not every event is a problem, some are informational messages that things are working okay and some are warnings. However, no event should defy reasonable explanation. Each event is sorted by Date and Time. Errors will have red Xs, Warnings will have yellow!s. Information messages have white is. Not every Error or Warning event means there is a serious issue.

Some are excusable at startup time when Windows is booting. Try to find just the events at the date and time around your problem.

If you double click an event, it will open a Properties window with more information. On the right are black up and down arrow buttons to scroll through the open events. The third button that looks like two pages on top of each other is used to copy the event details to your Windows clipboard.

When you find an interesting event that occurred around the time of your issue, click the third button under the up and down arrows to copy the details and then you can paste the details (right click, Paste or CTRL-V) the detail text back here for analysis. Remove any personal information from your information after pasting if you are compelled to do so. If you paste an Event, it will look something like this boring system startup event: Event Type: Information Event Source: Service Control Manager Event Category: None Event ID: 7035 Date: 7/14/2010 Time: 5:54:18 PM User: Jose Computer: Computer Description: The Remote Access Connection Manager service was successfully sent a start control. For more information, see Help and Support Center at To get a fresh start on any Event Viewer log, you can choose to clear the log (backing up the log is offered), then reproduce your issue, then look at just the events around the time of your issue and troubleshoot the events that are happening when you have your issue. You can look up events on the following World Wide Web site and get some ideas.

• In the file system path, specify the path in the bindings directory where you want to store bindings file. Select Transport to be MQ Client if your MQ installation is on some other system than your Interchange installation. • Set properties for the QMGR you are trying to connect, hostname (listener port) of your MQ installation, and specify the Server connection channel you use for connecting. • Create a new connection factory of type “Queue connection factory”. Swtor key bindings file.

This is where folks have events they see and then post up their questions, ideas and solutions: If you find your event in the discussion, the first idea or discussion does not necessarily mean it is the 'answer' for your situation, so read through all of the ideas to find the one that sounds most like your situation. That's because it IS the wrong CD. SFC /scannow is looking for a Windows XP CD (that is at the SP3 level). I suppose you could create your own XP installation CD at the SP3 level, using a process often referred to as slipstreaming.

Then again, even if you were to go through all that extra work, I agree with JoseIbarra that SFC /scannow will almost surely not fix your particular problem. (Also, for what it's worth, XP MCE is a superset of XP Pro, and this is why you got that particular message.) Why not just tell us what the actual problem is so we can guide you to a solution? EDIT: Just saw your other post. You need to run Event Viewer.

Hi Tracy, Yes, there will be an integrated build of Windows XP with SP3 (32-bit) in the MSDN subscriber download section in the first week of May 2008. It will be available to MSDN and TechNet subscribers. In the 3rd paragraph, it says: We still plan to begin rolling out the integrated build for Windows XP SP3 during the first week of May. We value your support and enthusiasm, and will continue to listen to your feedback as we deliver the MSDN Subscription service. Hi Tracy, Yes, there will be an integrated build of Windows XP with SP3 (32-bit) in the MSDN subscriber download section in the first week of May 2008. It will be available to MSDN and TechNet subscribers. In the 3rd paragraph, it says: We still plan to begin rolling out the integrated build for Windows XP SP3 during the first week of May.

Windows Xp Service Pack 3 Iso

We value your support and enthusiasm, and will continue to listen to your feedback as we deliver the MSDN Subscription service.