Getting Error failed to create process when trying to run trusted installer? Run with system works fine been using this for several week now, just started today. win 10 pro 1803
I hope I made sense. For example, CCleaner Scheduled Tasks: 1. Launch NSudo.exe as Admin, use TI permission, All Privs, select CCleaner64.exe 2. Right-click (content menu) on CCleaner64.exe, select NSudo TI permission + All Privs What you see in Scheduled Tasks with #1 is not the same as what you see with #2, but they should be identical...
Thanks! So stupid, DWS disabled it, should of clicked UAC off, to NOT be changed. Couldnt start it through services, had to cmd prompt it enabled and then start through services. I feel dumb for not checking that and thinking it was the program. Sorry =/ Thanks again though.
Does anyone know which Windows services are required to be enabled for using NSudo? I've disabled a bunch of them (150+) and getting error "Failed to create a process." when clicking on Run. It used to work before disabling services, but testing them all one by one is gonna to take a lot of time. I suspected the service Secondary Logon needed to be enabled, but this does not seem to help.
Try NSI, Network Store Interface, disabling it stops some things running as Administrator, Export System Packages by Knarz. Testing services by disabling 1 at a time is the only way you will find what services affect things. You cannot wholesale disable things then pray your system works.
If you need to get TrustedInstaller token, you should not disabled the TrustedInstaller service. NSudo uses CreateProcessAsUser to create process, and it needs Secondary Logon service.
Thanks for the quick replies, guys. All three services are already enabled (default state); nsi/Network Store Interface Service, Windows Modules Installer/TrustedInstaller, Secondary Logon. So it must be another service. No errors in the event logs as well. I like to run a very basic system, and do not seem to miss out on anything - well, except NSudo of course I'll give it a shot to try to find the missing service. EDIT: Just figured out NSudo works when I run the process locally instead of via a Samba share. It used to work from the Samba share as well, though. But this should help me in the right direction to find the service.
Today, I am proud to announce the NSudo 6.1 Preview 1. It add some new command line options, you can use them with the command line help. **NSudo 6.1.1808.16** Merge NSudoC and NSudoG projects to NSudo project. Update copyright of license. Add VC-LTL 4.0 or later support for NSudo release configuration for ARM and ARM64 and drop the earlier version of VC-LTL support. (Huge thanks to mingkuang.) Refactoring the command line parser. Add "Wait" option in the command line usage. (Suggested by testtest322, wzzw and Domagoj Smolčić) Add "Help" and "Version" option in the command line usage. In the next preview, I will still add some new command line options. Mouri_Naruto
Name is somewhat confusing, had hope it would work like linux sudo, allowing me to give admin permissions for specific commands to specific users but still, great tool
I am sorry because I was busy in the recent days. But I can continue to improve NSudo in these days. I think I will add options about window (minimize, maximize, hide and etc) and priority (real-time, high, medium and low) settings to the next preview of NSudo. Mouri
There are lots of things for NSudo to improve. For example, using the singleton design mode to manage the global variables, using the ATL, even the WTL to implement the UI, merging the source code files, and etc. Mouri