Jump to content

Help!


RJARRRPCGP

Recommended Posts

Why when I install a stock Windows 2000 Pro, install SP4, then after I go to Windows Update, it appears to be fine, but in the \WINNT directory, I have a lot of hotfix log files.

The majority of the hotfix log files contain these lines:

KBxxxxxx installation did not complete.

Update.exe extended error code = 0xf201

I installed all of the prerequisites! :realmad:

Edited by RJARRRPCGP
Link to comment
Share on other sites


Wow, I just checked Google! Google didn't give sufficient results! :realmad:

"Only" 670 :huh: Most of the suggestions seem to be permission related. Have you checked these? A fresh install is no guarantee for a trouble-free system, as you have now discovered.

Link to comment
Share on other sites

Wow, I just checked Google! Google didn't give sufficient results! :realmad:

"Only" 670 :huh: Most of the suggestions seem to be permission related. Have you checked these? A fresh install is no guarantee for a trouble-free system, as you have now discovered.

I wiped the HDD with MHDD, thus I repartitioned and reformatted the HDD!

Also, a lot of the problems found with Google aren't even the same problem I have!

I can install the service pack. It's just the hotfixes that refuse to continue.

The hotfixes think that my Windows 2000 installation was tampered, even when it wasn't!

Link to comment
Share on other sites

Um well first off you need to slipstream Sp4 into windows 2000 disk then create a bootable disk this article will help you with that http://www.petri.co.il/windows_2000_sp_slipstreaming.htm

then from there run Mircosoft Upadate. if you need help just message me.

Always slipstream service packs because they work better that way :)

Link to comment
Share on other sites

Since the error isn't really an error (0xf201 means "STATUS_READY_TO_INSTALL", might be DCOM permissions:

1. Change DCOM default security

- Open Dcomcnfg

- Click on the Default Security tab

- Click "Edit" on "Default Access Permissions"

- Add the Administrators group, Allow Access

2. Check DCOM communication

- Open Dcomcnfg

- Click on the Default Properties tab

- In the "Default Distributed COM communication Properties" section:

Default Authentication Level should be set to "Connect".

Default Impersonation Level should be set to "Identify".

Apply the changes and reboot the machine, and update.exe should work again.

Link to comment
Share on other sites

Since the error isn't really an error (0xf201 means "STATUS_READY_TO_INSTALL", might be DCOM permissions:

1. Change DCOM default security

- Open Dcomcnfg

- Click on the Default Security tab

- Click "Edit" on "Default Access Permissions"

- Add the Administrators group, Allow Access

2. Check DCOM communication

- Open Dcomcnfg

- Click on the Default Properties tab

- In the "Default Distributed COM communication Properties" section:

Default Authentication Level should be set to "Connect".

Default Impersonation Level should be set to "Identify".

Apply the changes and reboot the machine, and update.exe should work again.

Have you recently found this out? Boy, Microsoft is ticking me off! :realmad:

Also, while I never saw the following problem under Windows 2000, under Windows XP SP2,

I get the following error message in logs for important hotfixes:

The Update.ver file is not correct.

Also, this error message can repeat up to 20 times! (up to 20 in a row)

Appears to be a Microsoft bug that Microsoft won't admit.

Edited by RJARRRPCGP
Link to comment
Share on other sites

Easy there - I know nothing of your setup other than the error you're seeing, and that it happens after SP4. The status message that the error is giving is that the update is ready to install, but fails. I know I've seen this when DCOM permissions are screwed, or the OLE key contains entries that are invalid or too restrictive for DCOM settings. No need to get angry.

One other point - you state that you're getting an error installing updates on a 2000 Pro machine after installing SP4, and now you state that you're also seeing different update errors on an XP SP2 machine. Does this happen for every install you do on 2000 w/SP4 or XP w/SP2, or just the current installations? Have you modified any of the files on the installation source for either install disc?

Link to comment
Share on other sites

Easy there - I know nothing of your setup other than the error you're seeing, and that it happens after SP4. The status message that the error is giving is that the update is ready to install, but fails. I know I've seen this when DCOM permissions are screwed, or the OLE key contains entries that are invalid or too restrictive for DCOM settings. No need to get angry.

One other point - you state that you're getting an error installing updates on a 2000 Pro machine after installing SP4, and now you state that you're also seeing different update errors on an XP SP2 machine. Does this happen for every install you do on 2000 w/SP4 or XP w/SP2, or just the current installations? Have you modified any of the files on the installation source for either install disc?

With Windows 2000 Pro, some 2005 hotfixes appeared to have been installed. The majority of the failures probably are the 2006 hotfixes. I saw a 2005 date for a system file. If it wasn't updated, it would be a June, 2003 date.

Also, under Windows XP SP2, the "The Update.ver file is not correct." error message can repeat up to 20 times or more in a hotfix log, it would look like this:

The Update.ver file is not correct.

The Update.ver file is not correct.

The Update.ver file is not correct.

The Update.ver file is not correct.

The Update.ver file is not correct.

The Update.ver file is not correct.

The Update.ver file is not correct.

The Update.ver file is not correct.

The Update.ver file is not correct.

The Update.ver file is not correct.

The Update.ver file is not correct.

The Update.ver file is not correct.

The Update.ver file is not correct.

The Update.ver file is not correct.

The Update.ver file is not correct.

The Update.ver file is not correct.

The Update.ver file is not correct.

The Update.ver file is not correct.

The Update.ver file is not correct.

The Update.ver file is not correct.

Edited by RJARRRPCGP
Link to comment
Share on other sites

  • 1 month later...
  • 5 weeks later...
Why don't you just slipstream SP4 and the hotfixes?

http://www.vorck.com/2ksp5.html

Before Microsoft stop supporting windows 2000 altogether.

Yep. Also, I saw the above s*** on someone's Dell Dimension with Windows XP 2002 SP2.

It appears that Windows Update likely isn't applying the updates in the right order! :realmad:

Link to comment
Share on other sites

More than likely, you had something broken on your computer before Windows Updates. Have you tried running Dial-a-fix and then attempting to reinstall the updates?

Nope. Still the same after I reformatted the HDD then reinstalled Windows from scratch.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...