Windows checks for updates as usual. When updates found, it sends a wnf event to trigger notification. Since notification process is replaced with a dummy, there's no expected reply, so it does it again, couple times. So far so good. Shortly after, windows-as-a-service kicks in: Windows checks connection type, working hours, postpone settings, update registry, update policies - it's all purely informative. If certain flags are set on the respective update (most are flagged security critical and mandatory reboot even if not required) and time between last updated and current is past a certain range, Windows will straight out proceed to downloading and installing the update. Else, will keep appearance of giving user a choice in the matter and trigger another notification every x minutes. Again, no expected reply, so it does it again, couple times. The time until Windows gets impatient and proceeds with downloading and installing the update without user confirmation depends on many factors, it can range from 15 minutes to couple hours to days for non-critical stuff. This is what I mean by late schedule - it's not much different than normal. After update has been auto installed and a pending reboot was set, Windows starts spamming reboot notifications. No expected reply, so it does it again, like clockwork. Might also run remediation services in between, smelling something fishy, but won't find anything wrong because the scripts haven't touched update services / registry / policies. So now you can stay outdated without being nagged for as long as you can keep your PC on. I once did that for almost 4 months without noticing it as PC was set to enter sleep on idle. Hence the reminder for people that rarely reboot / shutdown their PC to check settings - updates from time to time and deal with pending reboots: accept or ignore (also noticeable on the start menu - power icon).
So it means we have to check this option manually, will the updates be installed after that or is it done automatically
Since most updates are set for mandatory reboot, if you don't reboot your device windows can't proceed with installing another one (with some exceptions). The alternative would be to fully allow automatic updates (there are registry / policies for that), but then who in the world would want their PC suddenly reboot?! It's not an issue for most people that do shutdown their PC over night. And most people will notice the power icon overlay anyway. Pick your poison?
@Rallye89 read/re-read all nfo's from link posted from neofita & this maybe can help https://forums.mydigitallife.net/posts/1586314
With all respect, I beg your pardon & ask where is the original one which talks about it clearly. I will instantly change it. Thanks. ...
I have installed windows 10 pro yesterday and I am the administrator When I am deleting anything in C drive it is asking for admin rights, how is it possible
Just stop linking to the copied from mdl crap by chef kock, i've told you over and over that he doesn't know sqaud and all "his" "work" is copied from here or anywhere on the net. He finally left mdl and now you keep posting his crap here.
Its possible for specific files even when everything is normal! > After asking for admin rights, Does it offer you Continue & finally you are able to delete them ? > What are the exact files & their names ? Are they system files ? Are they owned by TrustedInstaller ? > Make a new account with admin privilege & try the same thing. Thanks. ...
That is for safety reasons. (yes, even if you are the Administrator). To disable it: Open UserAccountControlSettings and set it to the lowest.
Wow, there are still people not knowing about UAC (User Account Control), providing userspace separation. If you want to be THE Administrator, you need to activate the Super Admin account first. In a shell with Admin rights: Code: net user Administrator /active:Yes This account won't be bothered with UAC prompts.