Discussion Locked

auto launch programs at login

0 helpful
8 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

This is a duplicate of my previous question. I'm not familiar with this forum, and I accidentally closed the previous question when all I wanted to do was make a comment on your suggestions. Here's the question again.

"I would like to know where can you hide a program to launch automatically after logon? We have Windows NT Workstation and in one of the computers, after the user logs on, the "PJ Boogie Baby Screensaver" setup program starts to run. We looked in the user's profile startup folder as well as in the All User's profile, but it's not there. We also looked in the HKLM\Software\Microsoft\Windows\CurrentVersion in the keys Run; RunOnce; RunServices; RunServicesOnce, but still, not there. We looked in config.sys, autoexec.bat, sys.ini, win.ini again, not there.

Looking at the Task Manager as soon as the program runs, we see the process is owned by a setup program from "TG Byte Software."

One other thing, this doesn't happen if we log in as the Administrator. "

8 replies

by syscokid

Whoa, I thought I was seeing double! You posted the same question on Experts-Exchange. A user there pointed you to:

http://www.sysinternals.com/misc.htm#autoruns
I tried it, it searches for all startup menus, registry keys, etc where a program could be lurking. I wonder how that worked.

I see you've figured out that adding a comment here closes the thread-no option to comment and leave thread open.

You can post comments at Experts-Exchange. If there's anything you want to share with us here, put it on EE and I'll repost it here.

Cheers!

by limcuando

For some reason, this thing must have been tied to Novell Netware Services. As soon as we deleted CSNW, the pesky program went away.

by trurod70

You said you looked in his startup folder but did you look to see if it is in his log in script? If it only happens to him and not to other people on the same computer then I dont think it is on the users computer. Check that users login script.

by clpadmin

Okay, like I said before:

Before you log on as the other user, give them temporary Administrator rights. Log on a that user, open regedt32 and go to HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run and delete values relating to thesetup program. Demote the user back to Users.

And you asked:

Could you clarify what would change if I gave the user 'Admin' rights? He can run Regedit and Regidt32 just fine without having 'Admin' rights. Thanks.

Answer: The reason why you would have to give that user temp rights is because he will not be able to delete the values that needs to be deleted (the values specified above) as a normal user. He would need Admin rights to delete them. And the reason why he would have to log on is because then the HKEY_CURRENT_USER would take the values from his profile, and not Administrator.

This discussion is closed to new replies.