Instal the new Process Monitor 3.912/29/2023 Sysinternals - cmd.exe started with process ID 8612. SysinternalsSuite>.\PsExec64.exe -di cmd.exe All examples below are run from an elevated command prompt. Note: using psexec.exe or psexec64.exe makes no difference below, the same error shows up. October 2017 feedback link with the error message on the laptop: On my desktop, on an ethernet network connection, it shows the error message "The specified network name is no longer available." On my laptop, on a wireless network connection that's set to "private network" firewall mode for the home network, it shows the error message "The network path was not found." It's been three months now since 1709 was released and there has been no update. In October 2017, after Fall Creators Update was installed, PSEXEC stopped working and i haven't been able to make it work ever since then. PS The users on the Win10 Pro machine in question use different interface languages (just in case this is significant). So making an educated guess I navigated to the registry key in question:Īnd changed the access rights for ALL APPLICATION PACKAGES I began by using Process Monitor to capture the events caused by Autoruns64.exeĪnd sure enough the crash occurred when Autoruns tried to access a registry key from another user: Autoruns (圆4, v13.81) then began to crash again during the startup scan.Ĭonsequently I figured out the cause and a workaround so I figured that it might help others if I post this ‘workaround’ on this forum. Last week I set up a new machine for the same group and Autoruns first ran fine until I added another user. Starting around September / October Autoruns began to crash during the startup scan on a multi-user Win 10 Pro machine I share with others. Subject: Autoruns crashes after adding a user on Win 10 Pro
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |