Note:I translated Japanese into English using Google Translate.
Thank you, Google.
Summary:
- Did you read "Daily Blog # 602: Solution Saturday 1/19/19"?, I read it and tested it on RDP connection.
- I ran the program via RDP and looked up the result of UserAssist. There was nothing new in my test. ;-)
----------
I used two Windows 10 to test RDP. The destination of RDP connection is Windows 10 ver 1809.(192.168.1.16).
In the MSTSC setting, assign F: drive.
Connect to the remote system with RDP and browse F drive. There is an Autoruns tool on the F drive. Run Autoruns64.exe and Autorunsc64.exe.
Load NTUSER.DAT into the Registry Explorer. (I'm very happy to be able to load the registry with Live!! :-)
You can check that Run Counter and Last Executed are recorded.
I read the article of "No run counts in UserAssist" and tested the execution of Task Scheduler.
As Matthew Seyer wrote in the article, Run Counter and Last Executed were not recorded.
Also, we tried executing the GUI program from CMD described on Twitter of Maxim Suhanov. Run Counter and Last Executed were not recorded.
There was nothing new in my test. ;-)
Thanks to everyone who has published validation results about UserAssist.
Verification environment: Windows 10 1809, Time zone UTC
Reference URL:
@HECFBlog Got the "Run count" field (in the UserAssist value) set to 0 when a GUI application was first launched from a command line. This field in an existing entry is not changed if a GUI application is launched from a command line. 1/2
— Maxim Suhanov (@errno_fail) January 19, 2019
