Sign in with
Sign up | Sign in
Your question

Win2K Pro Setup stops at "Registers Components"

Last response: in Windows 2000/NT
Share
Anonymous
June 3, 2004 1:54:03 AM

Archived from groups: microsoft.public.win2000.setup (More info?)

I've spent the entire afternoon looking for an answer to this, but no
luck. I'm trying to do a Repair install on Windows 2000 Professional to
replace a few missing system DLL's. However, the Setup program
grinds to a halt on "Registers Components".

I've learned that this may be a conflict with unsupported hardware. I
use a Radeon 9600 Pro, which is not on MS's hardware compatibility
list. However, that card was already installed when I did a clean
installation of the system a while back, and I don't recall it being a
problem.

Luckily, I'm not dead in the water. I was able to create a clean
installation on another drive so I can still access my files. It had
absolutely no trouble getting through the setup procedures.

Someone out there must know why this happens and how to fix it. I
appreciate any help.

Thanks!

-- Brian Stone
Anonymous
June 3, 2004 3:35:54 AM

Archived from groups: microsoft.public.win2000.setup (More info?)

I've found a possible work-around to the problem. When setup stops
on "Registers Components", do the following:

1) Press Shift-F10 to bring up the console.
2) Type taskmgr and hit enter to bring up the task manager.
3) Click the Processes tab.
4) Click on fixmapi.exe or rundll32.exe. The problem may also be with
one of the other programs that are started up during this stage of the
setup procedure.
5) Click the End Process button.
6) When the warning pops up, click Yes to kill the process.

If you don't see either of those two names in the process list, try killing
other processes. You can open up the task manager before the setup
program gets to the "Registers Components" stage and watch the
processes start and stop. This may give you a better idea of which
process is holding up the setup procedure.

I noticed that the stall occurs on my machine soon after rundll32.exe
starts up. When I closed the task manager and reopened it, I noticed a
program called fixmapi.exe had basically taken the place of
rundll32.exe. I killed fixmapi.exe, which promptly averted the stall.

This works around the stall, but doesn't fix the cause of the problem.
The installation completed successfully, but I got a couple of errors
along the way. There were two Java install errors, and two "copy error"
messages which stated that msvidctl.dll could not be copied. I chose
to ignore these.

I believe that msvidctl.dll is an activeX streaming video component.
Not exactly a critical system component that you can't live without, so
no big deal. But, what would cause this problem to happen in the first
place?

DLL's were wiped from my system due to a furious battle with a
nagging virus. I won, but at the price of a few system files. That was
the reason I was trying to do a repair install. Perhaps something else
happened along the way that I'm not aware of.

Hope this information helps others.
Anonymous
June 3, 2004 9:14:26 AM

Archived from groups: microsoft.public.win2000.setup (More info?)

IT WORKS!!! THANKS SOOOOOOOO MUCH!!!!!

The setup did mentioned an error later, but nevertheless,
I managed to "return" back to Win2K.
THANKS again!!!


>-----Original Message-----
>I've found a possible work-around to the problem. When
setup stops
>on "Registers Components", do the following:
>
>1) Press Shift-F10 to bring up the console.
>2) Type taskmgr and hit enter to bring up the task
manager.
>3) Click the Processes tab.
>4) Click on fixmapi.exe or rundll32.exe. The problem
may also be with
>one of the other programs that are started up during
this stage of the
>setup procedure.
>5) Click the End Process button.
>6) When the warning pops up, click Yes to kill the
process.
>
>If you don't see either of those two names in the
process list, try killing
>other processes. You can open up the task manager
before the setup
>program gets to the "Registers Components" stage and
watch the
>processes start and stop. This may give you a better
idea of which
>process is holding up the setup procedure.
>
>I noticed that the stall occurs on my machine soon after
rundll32.exe
>starts up. When I closed the task manager and reopened
it, I noticed a
>program called fixmapi.exe had basically taken the place
of
>rundll32.exe. I killed fixmapi.exe, which promptly
averted the stall.
>
>This works around the stall, but doesn't fix the cause
of the problem.
>The installation completed successfully, but I got a
couple of errors
>along the way. There were two Java install errors, and
two "copy error"
>messages which stated that msvidctl.dll could not be
copied. I chose
>to ignore these.
>
>I believe that msvidctl.dll is an activeX streaming
video component.
>Not exactly a critical system component that you can't
live without, so
>no big deal. But, what would cause this problem to
happen in the first
>place?
>
>DLL's were wiped from my system due to a furious battle
with a
>nagging virus. I won, but at the price of a few system
files. That was
>the reason I was trying to do a repair install. Perhaps
something else
>happened along the way that I'm not aware of.
>
>Hope this information helps others.
>
>.
>
!