XP Pro boot-up to desktop too slow.

By flyingfortress ·
I was having problems that I could not figure out with my computer, so I did a clean install of XP Pro. I also installed SP2 and SP3, and all subsequent updates. Now, it takes an unusually long time to boot to the desktop, especially the "loading personal settings" part. There is not much on the computer yet since I just reinstalled Windows, and I have ran several malware scans. Does anyone know what may be causing this?

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -

Possible Hardware Problem

by brian In reply to XP Pro boot-up to desktop ...

Have you checked/tested your RAM in the system? If not, I would recommend downloading MEMTEST86+ and booting it from floppy (you can also download the Ultimate Boot CD and run it from there). Make sure that you have a minimum of 512mb ram. Also, there is a known bug (atleast to compaq and HP) about SP3 and AMD processors not running correctly. Microsoft has not released an update to fix that bug to my knowledge, but HP made their own. The bug for AMD and SP3 affected me, but when I installed SP3, my system would not even go past loading personal settings (I had an old AMD 2600 Athlon XP). Let me know if this helps you out or points you in the right direction.

Collapse -

The HDD and maybe the Registry are Fragmented

by OH Smeg Moderator In reply to XP Pro boot-up to desktop ...

Run the Defrag utility several times.

Collapse -

Problem solved.

by flyingfortress In reply to The HDD and maybe the Reg ...

I just performed a reformat/reinstall. This install is much faster. Thanks.

Collapse -

Spoke too soon.

by flyingfortress In reply to Problem solved.

After installing SP2, SP3, and all updates, it is back to booting up slow again. I am guessing that my system is too old. At least it is quick once booted up.

Collapse -

It very well could be that adding the Service packs

by OH Smeg Moderator In reply to Spoke too soon.

Have messed up something along the way as well. If you look at the contents of the HDD you'll find at least 2 files with a long Alpha Numeric String that can not be removed. There will also be numerous changes made from the initial install after applying SP2 & 3 that could be slowing things down or even introducing errors into the Boot Process that take time to work through.

Instead of installing your copy of XP then adding SP2 & 3 try using nLite

To incorporate SP2 & 3 into your Custom Made Slipstreamed Install Disc. You can add both SP's and any specialized drivers and Patches so that it is a 1 Step Process installing Windows. Just be sure to read the directions on their Web Site here


Collapse -

Service Packs, etc.

by flyingfortress In reply to It very well could be tha ...

Funny thing, I have one of those long-named files on my slave drive (D drive) instead of where Windows is installed (C drive). I'm not sure what it is either, but it is a little over 6 MB. It has an amd64 and an i386 folder within.

I installed XP Pro, then SP2, and then SP3. Then, I installed any remaining updates. I did not install any updates in-between SP's.

Collapse -

Those files come from the Service Pack

by OH Smeg Moderator In reply to Service Packs, etc.

And depending on the hardware it is installed on can go on any HDD or maybe every HDD/Partition. The AMD64 is to address an Issue with some AMD CPU's which wouldn't allow the SP3 to install correctly and the system would roll back to SP2 and give a message that it may no longer be stable. I've also seen the same result with one model of Acer NB that had Intel CPU's and they where about as helpful as Breasts on a Bull. The most useful thing that they could say was that SP3 was still bets 3 weeks after it was released to the Windows Update Servers. I think that they where hoping that if they kept their heads in the sand long enough the problem would just go away which of course it wouldn't.

On the system that I assembled this week I only have 68e4f4793f2eacb4dd on the C Drive but then again I only had the C Drive connected when I applied the Slipstreamed Install Disc which included SP3 I think. This is because the C Drive is a Mirrored RAID Array so I didn't want to run the risk of getting the wrong drives included in the RAID. But it is a i7 CPU and 4 Gig's or RAM which is all that a 32 Bit version will support and it still takes several minutes to Boot to a usable Desktop but after that it flys along. It replaced a 2.5 P4 and there is very little difference between the Boot Times though the old unit took over 24 hours to run a complete Virus Scan where as this system now only takes 9 hours 53 minutes to do the same thing so it is considerably faster.


Collapse -

I figured as much.

by flyingfortress In reply to Those files come from the ...

I have my main C drive and a slave D drive that is empty. The file,938ef12bd08fea29fdfdc157, on my D drive is the only thing on it. Before I reformatted/reinstalled, these files used to be on my main drive only. Why is it on a slave drive. Can I move it to my C drive? Is it from SP3? Should I just leave it alone?

Collapse -

Just leave it alone

by OH Smeg Moderator In reply to XP Pro boot-up to desktop ...

Though if you have nothing at all on the Slave Drive it may pay you to move your Page File there to speed up the Drive Access Times.

That file is installed by the Service Pack or more correctly when you start to install the SP it decompresses is written to a Unmovable File on one or more HDD's/Partitions and is actually run from there as it installs. The i386 File may be used when you install any additional Hardware like USB Thumb Drives and holds a lot of Generic Drivers which may not be present in it's namesake that was installed when Windows was initially loaded.


Collapse -


by flyingfortress In reply to Just leave it alone

Not quite sure what you are exactly talking about. Could you explain or provide a link for more info? Thanks.

Related Discussions

Related Forums