Startups after running NTLite not starting?

pmikep

Active Member
I reported a problem like this a few years ago. It hasn't happened since then. Until today.

I decided to update my two year old Win10 install with the latest (Sept 2022) MS CU. (KB5017308.)

I downloaded the latest NTLite (v2.3.8.8920) and ran it in my User Account, albeit as Admin via UAC. I downloaded the CU and let NTLite slipstream the CU.

When it finished, NTLite gave me a message, which I think said something like, "You need to reboot. After that, NTLite will automatically run and remove reinstalls." (I admit that I didn't read the message very carefully. It might have been telling me that I was the one who needed to Remove Reinstalls.)

I rebooted Windows and I purposely logged in as Admin this time so that NTLite could have the necessary permission to do whatever it needed to do without user intervention.

After Windows rebooted, Comodo kept alarming about MSEdge trying to access the Internet (No) and about MSEdge Updater trying to start. (No.) Multiple times. (For this install of Win10, I had previously used NTLite to removed IE and whatever browser was in vogue at the time.)

I waited a few minutes, but NTLite never started on its own.

So I started it and I ran "Remove Reinstalls."

After that, I received the message from NTLite that I had to reboot. So I did.

I can't remember if I rebooted into Admin this time or back to User. I think back to User.

Then I used CCleaner to check if there were any startup items left over. I ran CCleaner as Admin via UAC.

Yes, there were startup items pending.

Remaining startups 2.jpg

So I rebooted into Admin. After that, the start up items cleared and all seems well.

(Well, I did have to use NTLite again to remove the taskbar entry for Meet Now.)

Installed Updates.jpg
 
Last edited:
It sounds to me like some combination of defender/comodo/firewall caused a conflict which created this situation. NTLite has a warning tooltip built-in that advises you to disable antivirus while it is running for this reason too. I'm not sure there's a bug or other problem here, until we rule out the antivirus stuff first.

Another thing to consider is if you have Fast Startup enabled, I've noticed that this feature causes registry key manipulation problems, because your computer will hibernate instead of actually restarting when you choose to reboot.
 
Back
Top