Services Corrupted

[doze_hater]

Hi

I'm trying to start terminal services and it keeps complaing with
1083 error. That's weird on its own. But the really strange thing i
when I look at the dependencies for any service, they are blank. I
there any way to get this back to a normal state without reinstalling?


thank

 

[Steven L Umbach]

None of your services show any dependencies? That is not a good sign. If it
was just a couple of services you can edit the registry key to enter the
service dependencies but in your case I would try an upgrade/repair install
after which you would need to install first your service pack and then go to
Windows Updates to download critical security updates. Do not attempt a
fresh install until you are sure there are not files encrypted with EFS on
the computer if using XP Pro. --- Steve

http://www.michaelstevenstech.com/XPrepairinstall.htm --- XP repair
installation which does NOT involve formatting the system drive.

 

[doze_hater]

So ok, I got somewhere. I think the major problem is with terminal
services. How do I force a fresh install of terminal services?

I've tried:

%SystemRoot%\System32\rundll32.exe setupapi,InstallHinfSection
TerminalServices.FreshInstall 128 %SystemRoot%\inf\tsoc.inf

But it doesn't do anything. Is there any way to force it to install? Or
see where an error might be coming from? Also, what does the 128 mean? I
think the problem is that the registry is missing the entries for TS and
that the files are not on the filesystem.

Again, I can't do a reinstall of windows because I have to do all of
this over VNC and I don't have physical access to the computer.

 

[Steven L Umbach]

The path that the service uses is C:\WINDOWS\System32\svchost -k DComLaunch
on my XP Pro computer. I don't know what the 128 means but I would check the
logs via Event Viewer to see if any entries are recorded at the time you try
to start the service that may help. Be sure to check the security log also
for any logon failure related to that service starting. Try using the sc
command to start the service as it may give you more detailed info such as
sc start termservice. Use sc without any more syntax to see what it can do.
To see what the registry settings looked like at install of the OS where it
probably worked fine use regedit to load hive for \windows\repair\system to
see what shows on your computer. Use regedit to open the registry, highlight
HKEY_LOCAL_MACHINE, go to file menu -load hive, browse to
\windows\repair\system, choose some key name, select OK, and then go to
HKLM\controlset001\services\termservice to see the registry settings. When
done highlight the registry hive name and go to file menu and unload
ive. --- Steve