Windows installer window is open at log on to a DC

Have you checked to see if there's anything in the Startup folder or in the "Run"  registry key on that server?

startup is empty.   Where exactly would I search the registry for the "Run" key?

HKCU/Software/Microsoft/Windows/CurrentVersion/Run
HKLM/Software/Microsoft/Windows/CurrentVersion/Run

see attached

Download a copy of Microsoft Autoruns.  This shows everything that runs automatically in the system, both at boot time and for the current user.  It also gives some useful information on the side, i.e., the description and the software publisher, so you can better decide whether that particular item should be running.

The Logon tab will be of particular interest since the installer window is showing when the admin logs on.

thanks I'll work on it tomorrow

See attached.  I don't see anything.   I'll keep checking.

OK.  All the stuff that is in yellow does not exist and can be disabled.  Either uncheck it to leave it in the list, or right-click and select "Delete" to remove it from the list.

Try disabling (uncheck it) the Google Chrome Installer, which since you're seeing an installer window seems like a red flag.  Reboot, see if the problem is gone.

If not, re-enable it, then disable each of the three items starting with "GoogleChromeAutoLaunch" one at a time, reboot, and see if the problem goes away.  If not, re-enable that item and move to the next one.

If the "Network Monitoring Tray" is not required, I'd disable that.

Does deleting it remove it from the registry?

Deleting will remove it from the registry.  Unchecking it does not.

I've been unchecking the items 1 at a time and rebooting.   Still pops up.  After the last reboot, I logged on as my assistant and it didn't pop up.   Logged on  as Administrator (my account) and it popped up.  Any thoughts?

No idea at this point other than walking through the "Everything" tab, which is a long trek across the desert.  Perhaps another expert will have some insight.

thanks I'll wait for additional input

Did you try unchecking the Google Chrome Installer item (last section of the Autoruns output)?  It's not one of the ones that is obviously a problem, but it is an installer app and it appears to be an MSI installer that's trying to run when you log in.  Plus it's odd that it would be running every time you log in.

Yes, I unchecked it.  I could always try uninstalling Chrome.   Did you see my post that it doesn't happen when my assistant logs in?

Yes, that points to something that would only run in an administrative context, which of course would include installing a program, likely some install process that was started by someone logged on with the admin credentials.  I'm thinking that an attempted installation has gotten hung up with a registry entry to run on the next restart or login, but it's not allowed to run because it requires a command line with some switches to operate properly.  I would definitely try uninstalling Google Chrome and see what happens.  You can always reinstall it if you need to.

I compared my everything list from Autorun to my assistant.   I have 18 items he doesn't have.   However, he has several I don't have.
I guess I could uncheck mine in groups of 5 and see what happens.   Your thoughts

It is a long shot, but you might try this:  Download a copy of Microsoft Process Explorer.

When the install window pops up, run Process Explorer and look at the process tree to see what process started the installer.  Perhaps this will suggest something.

Does your assistant have a Chrome icon on his/her desktop, task bar or quick launch? Do you?

he doesn't and I uninstalled Chrome yesterday.  Still getting the installer window when I log in.

Hmmm - did you check the registry to see if that ActiveSetup key and/or the autolaunch registry key were still there?

Is Autoruns disabled on this system?

If not, are there storage devices attached (including hard drives and USB flash drives) with autorun configuration files?

OMG.   All this time we been looking everywhere except the obvious.  It was in the Msconfig startup.

Thanks to all for helping

Thanks

LOL - I usually try to do those obvious ones early on, but made the mistake (as we all do occasionally) of assuming we'd already covered that!  Glad we finally got it fixed for you.

Yep, been there done that.  Thanks