I am reporting a bug with:

Adobe DC Pro version 2017.009.20058
Running on Windows 10 Version 1709 Build 16299.492

When I print any document using the Adobe PDF Converter and the "View Adobe PDF Results" option is checked receive an Interactive Services Detection notification on my Windows Task Bar. If i click the flashing icon in my Task Bar the ISD window opens (see attached image).

If I click "Ask me later" within five minutes the icon will start flashing again.

If I click "View the message" a lot happens. Actually not much happens , But it takes a lot of words to explain it. First I am switched to be shown Windows Session 0 which displays a "How do you want to open this file?" window (see attached file). There is also another window with a button to return to my session, Session 1". The issue is that I am unable to do anything while in Session 0. Neither my mouse, nor my keyboard do anything. After about 30 seconds Session 0 will close and I will be shown the log in screen, as if I were switching users in Windows. To top this off everything I had open when this happens is moved to one monitor, so I have to move most of my open windows. Also within the next five minutes the ISD window icon will start flashing again. Just to be clear, this is very annoying.

According to what I read on Microsoft's web site users used to be logged in to Session 0, but with Vista, or Windows 8, or Windows 10 this was changed to Session 1 leaving Session 0 for critical OS activities.

I can circumvent this problem by unchecking the "View Adobe PDF Results" option in the driver settings. Though with some programs this option can be changed in the program from which the document is being printed. This means that any of my users could check that option and end up in situation I described above.

The only way I've found to break the cycle of the icon flashing at me, and the only way to make the icon leave the Task Bar is to stop the ISD service and restart it.

It appears as if at least one code snippet had been missed, or something, when updating Acrobat to work with newer versions of Windows.

I would appreciate it if Adobe could correct this bug sooner rather than later.