What version of NSudoG hides command prompts? I tried v6.0 R3 and I get up to 8 command prompt popups in my script in my sig. With Powerrun I don't have that problem. Do you need more info?
All versions of NSudoG should not pop up console windows if you run an app that don't pop up console windows.
DISABLE WINDOWS UPDATE WITHOUT ANY NOTICE You should provide the way to restore. I am using the System Restore now. I never try your script any more if your script don't ask "yes or no" for user. I hate someone changes system files in my Windows environment. (I never disable Windows Update.) @pf100
But I am reverting the restoration because I want to try your removing script. I should launch a VM first before we talk.
There is no purpose in asking yes or no to disable update hijacker files. That's the whole point of the script. And I had no idea you'd run it, I just wanted to show you line 154 of the script that causes the popups with icacls.exe. My apologies for the misunderstanding. And lines 67, 68, and 69 in the uninstall script is what specifically reverses what line 154 does. Line 154 removes all permissions from system files that force updates. That can only be done (in 1809) by running icacls.exe as TrustedInstaller.
I read your restore script again and I restore my OS again. One of reasons that I created NSudo is that I hope everyone can change files and registry entries without changing the ACL. So I think that use icacls is not a good way to use NSudo. But I should ask your question. If I have something can be fixed, I will fix it and thanks to you. I am sorry because I am angry before. I hope you can forgive me. Mouri.
I've been awake for almost 24 hours and wasn't thinking clearly or I would have provided the uninstall script when I provided the wrapper script. I thought you already knew about my wrapper script project but I was wrong. If you know of a way to permanently disable the update hijacker files without changing the ACL's that would be nice, but the uninstaller resets the ACL's to default anyway, so it doesn't matter. The way I'm running icacls.exe as TrustedInstaller, those files cannot be read, overwritten, edited, or deleted by the system unless you run the uninstall script because all permissions are removed from those files. A CU, SFC, or even system restore can't restore them and that's the way I want it and it's the way it has to be. I don't want someone to update from 1803 to 1809 and the hijacker system files get restored and suddenly the script stops working. Those files have to be locked permanently unless the uninstaller is used. There is no other way to do it using my system file disable method approach. I disable update hijacker files, and every other project changes the registry and registry key permissions. My method is different from any other. And of course I forgive you. I would have gotten angry too if I were you. I felt quite embarrassed when I saw you ran the script without having the uninstaller script. So I must ask you to forgive me.
@pf100 I know why caused it. I can't see any flashing console windows because my laptop is very fast, lol. (My laptop have a i7-8750H with undervolt which can get 1180 cb in Cinebench R15, Toshiba 512GB XG3 NVME SSD and 32GB Dual Channel DDR4 2666 RAM.) Because icacls.exe is a console application, it will popup console windows. Today's NSudoG can popup no console windows if you run an app which is not a console application because NSudo uses "cmd /c start" to run an app and NSudo can't manage them. So I should change the way of process creation and THIS has already been on the schedule of the next preview NSudo 6.1, and this is why I don't publish the next preview recently. I hope it can help you. Mouri
Yes, I experimented with "cmd /c start" on my own and and as you see that doesn't work for my application of NSudo. I've known that this is on your to-do list and am waiting patiently for an update. No hurry, as Powerrun works and I will switch to NSudo whenever you can update it. I prefer open source software whenever possible and NSudo is great software. Thank you. I have learned from our discussion to never forget to provide the uninstaller with the script when giving examples on the forum from now on. I'm going to sleep now. Have a good day, my friend.