{"id":3400,"date":"2017-10-16T10:53:25","date_gmt":"2017-10-16T17:53:25","guid":{"rendered":"https:\/\/www.coretechnologies.com\/blog\/?p=3400"},"modified":"2017-10-16T10:53:25","modified_gmt":"2017-10-16T17:53:25","slug":"prevent-interactive-services-detection","status":"publish","type":"post","link":"https:\/\/www.coretechnologies.com\/blog\/alwaysup\/prevent-interactive-services-detection\/","title":{"rendered":"How do I Prevent the Interactive Services Detection Window from Constantly Coming Up?"},"content":{"rendered":"
\"Interactive<\/div>\n

Why do I see the “Interactive Services Detection” window?<\/b><\/h2>\n

\nThe Interactive Services Detection (ISD) window appears whenever a Windows Service<\/a> running on your computer is showing a window or prompt in Session 0<\/a> — a “background desktop” created when your computer boots. The ISD window allows you to switch to Session 0 where you can see the window and take action.\n<\/p>\n

\nThe next section explains the situation in greater detail; read on to find out more. You can also skip directly to the 3 solutions<\/a> if you are short on time and just want to get rid of the dreaded ISD window. \ud83d\ude42\n<\/p>\n

History\/Background<\/b><\/h2>\n

\nWindow services run in Session 0. On legacy versions of Windows (NT, XP and 2003), the first person to log into the PC was placed in Session 0 — where all the windows, alerts, tray icons and other user interface elements created by services were visible. Thus a service could easily interact with that first user.\n<\/p>\n

\nBut Microsoft changed the playing field in Windows Vista (circa 2007). Citing security concerns<\/a>, Session 0 was isolated and logging in to Session 0 was strictly forbidden. Suddenly it was impossible for a Windows Service running in Session 0 to interact with users, who were strictly working in Session 1, 2, etc. This behavior holds true for Windows 7, 8, 10 and Server 2008, 2012 and 2016.\n<\/p>\n

\nHowever isolating Session 0 introduced a problem. Services that show a window — requiring someone to click a button or enter a password to proceed — were suddenly rendered “invisible”. How do you know that a windows service application needs your input when you can’t see it?<\/b>\n<\/p>\n

\nThe Interactive Services Detection windows service<\/b> was introduced to address the invisibility problem. Whenever a window is showing in Session 0, the service will summon the ISD window to warn you and allow you to switch to Session 0.\n<\/p>\n

Working with the Interactive Services Detection window<\/b><\/h2>\n

The ISD starts out by flashing on the taskbar:<\/p>\n

\"Interactive<\/div>\n<\/p>\n

\nIt you activate the window and click Show program details<\/b>, the bottom of the window expands to reveal information on the program trying to get your attention. Here we see that it is the standard Notepad application running in Session 0 (launched as a windows service by AlwaysUp):<\/p>\n


\n\"Interactive<\/a><\/div>\n<\/p>\n

\nClicking View the message<\/b> will transport you to the austere Session 0 desktop where you will see the window that may be trying to get your attention:<\/p>\n


\n\"Session<\/a><\/div>\n<\/p>\n

\nClicking Ask me later<\/b> will dismiss the ISD window but only for 5-10 minutes. Read on and learn three ways to dispatch the window permanently!\n<\/p>\n

<\/a><\/p>\n

Solution #1: Tell AlwaysUp to hide your application’s windows<\/b><\/h2>\n

\nIf you never need to see your program’s windows, then you should have AlwaysUp suppress the windows and avoid triggering the ISD system. Simply edit your application in AlwaysUp and check the When a user logs on, don’t show the application’s windows and tray icon (if any)<\/b> box on the Logon<\/b> tab:\n<\/p>\n


\n\"Hide<\/a><\/div>\n

\nTip:<\/b> This is the best option for legacy applications, scripts and batch files which occasionally throw up command\/status windows. You can always capture console output to a log file if necessary (via controls on the Extras<\/b> tab).\n<\/p>\n

Solution #2: Disable the Interactive Services Detection Service<\/b><\/h2>\n

If you never want to see Session 0, then your best option is to do away with interactive services detection altogether. To prevent the service from starting:<\/p>\n

    \n
  1. \n

    Open the Services Control Panel Application<\/a> (services.msc)<\/p>\n<\/li>\n

  2. \n

    Find the Interactive Services Detection service; double-click it to open its properties<\/p>\n<\/li>\n

  3. \n

    Set the Startup type<\/b> value to Disabled<\/b><\/p>\n<\/li>\n

  4. \n

    Click OK<\/b> to save your changes.<\/p>\n


    \n\"Disable<\/a><\/div>\n<\/li>\n<\/ol>\n

    \nTip:<\/b> AlwaysUp will NOT be able to switch to session 0 when the ISD is disabled. Our free Switch to Session 0<\/a> utility will not work either.\n<\/p>\n

    Solution #3: Set the Interactive Services Detection Service to start manually<\/b><\/h2>\n

    If you occasionally inspect Session 0, disabling it will be inconvenient. Instead, set the ISD service to start manually and launch it whenever you want to see Session 0:\n<\/p>\n

      \n
    1. \n

      Open the Services Control Panel Application<\/a> (services.msc)<\/p>\n<\/li>\n

    2. \n

      Find the Interactive Services Detection service; double-click it to open its properties<\/p>\n<\/li>\n

    3. \n

      Set the Startup type<\/b> value to Manual<\/b><\/p>\n<\/li>\n

    4. \n

      Click OK<\/b> to save your changes.<\/p>\n


      \n\"Set<\/a><\/div>\n<\/li>\n<\/ol>\n

      \nTip:<\/b> You will be able to switch to Session 0 from AlwaysUp as normal. AlwaysUp will start the ISD service whenever you switch and will stop the service when you return to your normal desktop.\n<\/p>\n

      <\/p>\n

      \nHopefully one of these three methods works well for your situation. If not, please get in touch<\/a> and we’ll do our best to help!<\/p>\n