June 15, 2024, 12:58:25 AM

Author Topic: Cannot scan pc's from windows 10 if using runas  (Read 12313 times)


  • Member
  • *
  • Posts: 1
Cannot scan pc's from windows 10 if using runas
« on: September 27, 2016, 07:41:11 PM »
I login to pc as standard user and run Newt elevated as another user. It launches the scan and fails with

Error 1312: A specified logon session does not exist. It may already have been terminated.

This method has always worked fine in Windows 7 and still does.
Scanning works if I login to windows 10 as an administrator.

It is not limited to Newt as another tool I use to deploy software will not work in this fashion with the same error.

Any ideas? Thanks

Komodo Support

  • Administrator
  • Member
  • *****
  • Posts: 2702
  • Dayton, Ohio, USA
Re: Cannot scan pc's from windows 10 if using runas
« Reply #1 on: September 28, 2016, 01:37:11 AM »
Hi again.  You had asked this in email as well, but I thought it might not be a bad idea to post it hear since you asked publicly as well.

I'm not sure why this would be.  It's possible Windows 10 has new security measure in place to prevent this.

Since these are standard Windows error messages and we're using standard methods to connect, you should be able to bypass NEWT and track this down from Windows.

Try doing the same thing with a Windows command prompt by running it as elevated.  Then use the "net use" command to connect to a remote PC, using the same credentials (or none) as you did with NEWT and the other app.  This is basically the same method we and others use.  Once you can replicate it from Windows, you can then possible get support directly from Microsoft, since it really is their error and their software.