Are spaces in paths now working in latest version? Nevermind, just checked R3, spaces in paths are still a problem.
Unfortunately, Windows was never really good with spaces in paths, they haunt us one way or another, since at least Windows 95.
I'm sorry, because I was busy a while ago. So I didn't start to develop NSudo until yesterday. Today, I add a new argument called "-Wait" or "/Wait" for NSudo. Although it works (you can know it on my screenshot), I found the limitations of the NSudo command-line parser. So I need to improve NSudo command-line parser before I add other commands.
I'm refactoring NSudo's source code. I will use a third-party command line parser to parse the command line and it may cause that NSudo 6.1 will not compatible with the command line parameters which the earlier version used and users need to watch the NSudo's command line help again after NSudo 6.1 published. I will use several design patterns like singleton, object oriented and etc. Because I hope more and more people can contribute NSudo easily. The goal of NSudo development plan is that NSudo 6.1 can replace the runas and psexec tool. And I hope I can make it come ture because the plan is starting from NSudo 4.0. And I hope some people can help me write the help documentations for NSudo because I am not good at teaching others. Mouri
This is my idea of the command line usage for the future version of NSudo: Code: NSudo /RunAs="User Current" cmd NSudo /RunAs="User System" cmd NSudo /RunAs="User AnotherUser" cmd NSudo /RunAs="Service TrustedInstaller" cmd NSudo /RunAs="SessionID 3" cmd NSudo /RunAs="ProcessID 2333" cmd NSudo /RunAs="Process AS SSD Benchmark.exe" cmd NSudo /RunAs="AppContainer Microsoft.MicrosoftEdge_8wekyb3d8bbwe" cmd NSudo /RunAs="AppContainerSID S-1-15-2-4091397703-2130778903-3059587552-834565532-3998612792-80322464-294630515" cmd NSudo /RunAs="..." /WorkDir="C:\Workspace\NSudo Test Folder" cmd NSudo /RunAs="..." /Wait="Infinity" cmd NSudo /RunAs="..." /Wait="1000" cmd NSudo /RunAs="..." /Mode="Elevated" cmd NSudo /RunAs="..." /Mode="LUA" cmd NSudo /RunAs="..." /Mode="EnableAllPrivileges" cmd NSudo /RunAs="..." /Mode="DisableAllPrivileges" cmd NSudo /RunAs="..." /IntegrityLevel="Low" cmd NSudo /RunAs="..." /IntegrityLevel="Medium" cmd NSudo /RunAs="..." /IntegrityLevel="MediumPlus" cmd NSudo /RunAs="..." /IntegrityLevel="High" cmd NSudo /RunAs="..." /IntegrityLevel="System" cmd NSudo /RunAs="..." /IntegrityLevelID="8192" cmd NSudo /RunAs="..." /ProcessPriority="Idle" cmd NSudo /RunAs="..." /ProcessPriority="BelowNormal" cmd NSudo /RunAs="..." /ProcessPriority="Normal" cmd NSudo /RunAs="..." /ProcessPriority="AboveNormal" cmd NSudo /RunAs="..." /ProcessPriority="High" cmd NSudo /RunAs="..." /ProcessPriority="RealTime" cmd NSudo /RunAs="..." /ShowWindowMode="Show" cmd NSudo /RunAs="..." /ShowWindowMode="Hide" cmd NSudo /RunAs="..." /ShowWindowMode="Maximize" cmd NSudo /RunAs="..." /ShowWindowMode="Minimize" cmd NSudo /RunAs="..." cmd /c start /wait "" "C:\Program Files\Internet Explorer\iexplore.exe" NSudo /? NSudo /h NSudo /Help NSudo /Install NSudo /Uninstall What do you think about that? Mouri
Any updates? I noticed that right-click and launch with NSudo context-menu does not always produce the same result as launching NSudo.exe first and then starting the same program. Permissions differ sometimes, even though "Trusted Installer All Permissions" option is selected every time.