SplWOW64.exe prevents RDP sessions from disconnecting.

Discussion in 'Windows 64 Bit' started by ajstadlin, Jan 27, 2007.

  1. ajstadlin

    ajstadlin Guest

    I just set up a new WS2003/64 bit Terminal Server with all updates. I have a
    legacy Delphi application run by Remote Desktop clients. I don't experience
    this problem in Windows 2000/32 bit Terminal Server. I discovered that the
    problem appears to be that splwow64.exe is not closing after the application

    I tried the registry setting for SplWOW64TimeOut. This seems to work after
    several minutes (when set to 1 minute). But this is too long to wait;
    especially if the user wants to quit. For some reason, my users don't like
    having to wait 2 minutes or more to quit an application. Especially when the
    feedback that they get on close is a locked up blank blue screen. This is
    particulary unacceptable for users on thin client terminals who cannot open a
    second RDP session before the previous session times out.

    I haven't found any references to fixing this problem; other than the
    SplWOW64TimeOut registry setting.

    This is a real show stopper for migrating to Windows Server 2003/64 bit
    Terminal Server.

    Does anyone have a solution to this problem?
    ajstadlin, Jan 27, 2007
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.