none
AutorunsC64.exe v13.90 Stops (Crashes?) during display of rdpclip data RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I'm seeing AutoRunsC64.exe v13.90 just stop (crash? not sure; it's in a scheduled batch job) while dumping data out for:

    HKLM\System\CurrentControlSet\Control\Terminal Server\Wds\rdpwd\StartupPrograms

    The command is:

    autorunsc64 -a *

    What version 13.82 displays successfully is the following:

    (a few hundred kB of data)
    .
    .
    .
       NTDS
         %SystemRoot%\System32\winrnr.dll
         LDAP RnR Provider DLL
         Microsoft Corporation
         6.3.9600.17415
         c:\windows\system32\winrnr.dll
         10/28/2014 10:44 PM

    HKLM\System\CurrentControlSet\Control\Terminal Server\Wds\rdpwd\StartupPrograms
       rdpclip
         rdpclip
         RDP Clipboard Monitor
         Microsoft Corporation
         6.3.9600.18402
         c:\windows\system32\rdpclip.exe
         7/3/2016 11:45 PM

    HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Userinit
       C:\Windows\system32\userinit.exe
         C:\Windows\system32\userinit.exe
         Userinit Logon Application
         Microsoft Corporation
         6.3.9600.17415
         c:\windows\system32\userinit.exe
         10/28/2014 9:28 PM
    .
    .
    .
    (a few hundred kB more data)
     

    Where version 13.90 stops is in the middle of the rdpclip output, as shown here:

    (a few hundred kB of data)
    .
    .
    .
       NTDS
         %SystemRoot%\System32\winrnr.dll
         LDAP RnR Provider DLL
         Microsoft Corporation
         6.3.9600.17415
         c:\windows\system32\winrnr.dll
         10/28/2014 10:44 PM

    HKLM\System\CurrentControlSet\Control\Terminal Server\Wds\rdpwd\StartupPrograms
       rdpclip
         rdpclip


    (it just stops right there, with no further output)

    I've dropped back to 13.82 for now.  Please fix this.

    -Noel

    Detailed how-to in my eBooks:  

    Configure The Windows 7 "To Work" Options
    Configure The Windows 8 "To Work" Options
    Not feeling enough love to make one for Windows 10



    Sunday, July 29, 2018 9:59 AM
    |

Answers

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    What OS is yours? Windows 2012 R2?
    It doesn't happen on Windows 10 latest build.. even if the date of the file is for sure clearly wrong.. :-)
    2/19/1933 3:47 PM
    6/10/1908 4:03 PM
    5/13/2035 8:27 PM
    10/10/1965 4:17 AM

      NTDS
         %SystemRoot%\System32\winrnr.dll
         LDAP RnR Provider DLL
         Microsoft Corporation
         10.0.17134.1
         c:\windows\system32\winrnr.dll
         2/19/1933 3:47 PM

    HKLM\System\CurrentControlSet\Control\Terminal Server\Wds\rdpwd\StartupPrograms
       rdpclip
         rdpclip
         Monitor Appunti RDP
         Microsoft Corporation
         10.0.17134.1
         c:\windows\system32\rdpclip.exe
         6/10/1908 4:03 PM

    HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Userinit
       C:\WINDOWS\System32\Userinit.exe
         C:\WINDOWS\System32\Userinit.exe
         Applicazione accesso Userinit
         Microsoft Corporation
         10.0.17134.1
         c:\windows\system32\userinit.exe
         5/13/2035 8:27 PM

    HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\VmApplet
       SystemPropertiesPerformance.exe
         SystemPropertiesPerformance.exe
         Modifica impostazioni prestazioni computer
         Microsoft Corporation
         10.0.17134.1
         c:\windows\system32\systempropertiesperformance.exe
         10/10/1965 4:17 AM

    Tuesday, July 31, 2018 3:00 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    I'm running Win 8.1 Pro/MCE.

    Looks like a use of a bad pointer.

    -Noel

    Detailed how-to in my eBooks:  

    Configure The Windows 7 "To Work" Options
    Configure The Windows 8 "To Work" Options
    Not feeling enough love to make one for Windows 10

    Tuesday, July 31, 2018 10:43 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    I've documented crash details in another TechNet thread while helping a user troubleshoot a symptom of this. Based on another user's observation and my testing, it appears something within the login ASEP has issues.

    As a short term workaround, you can downgrade to v13.82 or exclude login startups by including all autostart entries except "l":

    • autorunsc.exe -a bcdeghikmnoprstw
    Tuesday, August 7, 2018 6:36 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Mark & Luke just pushed Autoruns v13.91 to https://live.sysinternals.com which resolves this issue :)
    • Proposed as answer by Kyle Hanslovan Wednesday, August 8, 2018 2:35 AM
    • Marked as answer by Noel Carboni Friday, August 10, 2018 12:40 PM
    Wednesday, August 8, 2018 2:35 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks for the heads-up.  It works.

    I'm left wondering, though...  Is this the right venue through which to report bugs, or did the problem get fixed by coincidence?

    -Noel

    Detailed how-to in my eBooks:  

    Configure The Windows 7 "To Work" Options
    Configure The Windows 8 "To Work" Options
    Not feeling enough love to make one for Windows 10

    Friday, August 10, 2018 12:42 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    This is Mark's preferred location for documenting Sysinternals related bug issues. As for notification, he prefers email linking back to the documented bug. I've also seen successful bug coordination on Twitter. For this issue, I used email.

    Glad to see the bug fix worked. There's a couple more I'm tracking related to path handling and duplicated file extensions. Based on conversation thus far, I'd expect that to come shortly.




    Sunday, August 19, 2018 5:34 PM
    |