win 200 admin acct. locked/device manager

  • Thread starter Thread starter jaxbak
  • Start date Start date
J

jaxbak

ok, here goes... i am running win2000 pro, 512 ram, p4 1.8
processor, very stable system. A week ago i installed SP2
to my system, a few of my applications requested SP2 so i
did.. Upon reeboot, i got the blue screen.. Upon repairing
my OS thru the recovery console, WIN 2000 notified me that
the file hccoin.dll is missing. This file is nowhere on
the install cd, but i found it in my WINNT\USB2 folder,
which seems to be a folder inside the uninstall folder.
WIN2000 wants this hccoin.dll file upon repairing, but i
do not know how to give it to the OS. make sense? i hope
so! MY SECOND problem is that my administrator account
cannot access any of the DEVICE MANAGER, nor can i
add/remove hardware on my computer. CASE POINT: i have a
usb optical mouse...i reboot computer, OS loads fine, LOG
IN box accepts password (logged in as administrator)
immediately a box pops up on desktop saying i do not have
sufficent priviliges to install any hardware on my system.
Log back in as administrator. I AM THE ADMINISTRATOR. So i
go in to device manager, and i get a message that i do not
have sufficient privilages to uninstall devices or to
change device properties...ALL REINSTALL buttons on ALL
PROPERTIES of ALL OBJECTS in the device manager are not
available to me. I am so confused here, help!!! ALSO, i
made another administrator account with full privilages
and the log out/in process is the same, all passwords are
accepted, but i get the same thing, cannot access device
manager, or add/ remove hardware. This happened upon
repairing my OS thru the recovery console, does the usb
file hccoin.dll have anything to do with this? ANY and
ALL help would be greatly appreciated....thanks
 
Don't know if this helps or not, but we had a very similar
situation here with the Admin acct on our Win2K server
having restricted priviledges.

Turned out that the "System" account did not have full
access to areas it needed within the OS. Seems one of our
techs thought it would be a good idea to remove the
Everyone account from having Full Control. Problem
is, "System" needs full control just to run system
processes and "System" was part of the Everyone account.
One side effect was that the Admin account was then unable
to perform a lot of functions.

Giving Everyone Full Control again, gave System Full
Control of areas it needed and the Admin account worked
unrestricted again.
 
Back
Top