Bug: RunOnce Autoruns Set By NTLite Fail to Execute and Never Disappear

tharri

Member
runonceerror.png

I could be wrong but I believe all of the above are set by NTLite (they are not on stock iso and I didn't knowingly set them). Since they result in an error, they never execute, and thus never disappear from Autoruns.

I'm not sure if this changed with recent versions of Windows, but I think, instead of just REG ADD, you may have to use the full path now:
Code:
%SYSTEMROOT%\System32\reg.exe add
 
I remember seeing something similar years ago when running NTLite. (I reported it in the forum somewhere.) I would see a stuck "RunOnce" in either AutoRuns or CCleaner.

For a while after that, I used to only run NTLite from Admin - and then reboot into Admin immediately after, in case it was a permission problem not letting some pending NTLite operation compete. (And then I would log out of Admin and log into User.)

Since then I've gotten lazy and let NTLite run from a User account. (With UAC Admin privilege, of course.) Nevertheless I've not seen the zombie RunOnce in a year or two now.

But then, I haven't run NTLite since October or so, and then only what was the current version at the time. (Meaning that perhaps something changed in a newer version of NTLite since then.)
 
i had something similar happened to me 3 times. it was a runonce command supposed to take file from usb and run it from there. but it seems just before logining in to desktop windows setup decides to remove usb? because when i open my computer i couldn't see usb there... i had to unplug and plug again
 
Just a reminder that it is necessary to reboot into Administrator after running NTLite to let it run its RunOnce's. (At least I think that one has to reboot into Admin. That's what clears these for me.)

Below is a screenshot from CCleaner Portable, running in a User Account. It is showing a few RunOnce's associated with NTL that are pending.

NTLite v2.3.2.8526

not clearing RunOnces.jpg
 
If it IS necessary that one's computer reboots into Administrator to run these RunOnce's, then perhaps a note to this effect in the window that pops up on NTLite after processing, advising the user to reboot into Admin at least one time before using the computer as normal.
 
Last edited:
After seeing this happen a few times, I tried to get into the habit of running NTLite only as Admin. That would remind me to reboot to Admin, and then from there, I would log out and use my computer as User.

But I haven't been using NTLite very much lately and the habit never formed. And I'm lazy. So I had used NTLite from User, with, of course, Admin privileges during use. But, of course, if NTLite sets some operations to run as Administrator on the next boot, they can't run if I log on as User.
 
Back
Top