This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(153.6, 62%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ET%3C/text%3E%3C/svg%3E)
I just started training in a Security+ class and was introduced to Autoruns. I have had some strange behavior on my PC for some time (random wakeups, monitors changing their number assignment, etc) but were usually explained by regular Windows error type things. But in looking through my Autoruns, I noticed some increased strangeness.
First of all, Autoruns will not stay running for long enough to make any changes. I got it to stay open for about 15 seconds by restarting my computer (long enough to get the screenshot below) but no matter what I do, it will close immediately (even as admin).
Additionally, I noticed that some of the (Verified) publishers had Chinese or other special characters in them.
So I'm just curious if anyone can vouch for these Autorun entries? And if so, is anyone aware of a known issue with Autoruns auto-closing?
Hi, I believe that these publishers are being displayed as an effect of a bug that was fixed in Friday's Autoruns release (v13.100). Can you please check with that version as well?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(236.8, 23%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EW%3C/text%3E%3C/svg%3E)
The bug with the broken Publisher display is still present in the current version (13.100), I made sure to download the sysinternals.zip again just now.
This pretty much breaks Autoruns because, since it doesn't detect the publisher properly, it can't filter out MS/Windows entries and doesn't properly compare autoruns files.