From Newsgroup: alt.comp.os.windows-11

Why does Microsoft feel that it is necessary to nag the user the minute
the Update is available? If you don't update when MS thinks you should,
it nags by randomly making simple things respond differently or not
respond at all. The events will occur every few seconds until the update
is installed. Through the years I have observed the same thing on
several different computers using different mice.

These events occur randomly, maybe one time the program does not open,
and a few minutes later it opens normally. Maybe when you click on a
function it works normally, the next time it may not respond or act differently. There is not one thing specifically, but many tiny random
events to cause significant frustration.

The minute the update is made, all these random events disappear, and everything returns to normal

--- Synchronet 3.21b-Linux NewsLink 1.2

From Newsgroup: alt.comp.os.windows-11

On 14/02/2026 15:45, knuttle wrote:

Why does Microsoft feel that it is necessary to nag the user the minute
the Update is available? If you don't update when MS thinks you should,
it nags by randomly making simple things respond differently or not
respond at all. The events will occur every few seconds until the update
is installed.-a Through the years I have observed the same thing on
several different computers using different mice.

These events occur randomly, maybe one time the program does not open,
and a few minutes later it opens normally.-a Maybe when you click on a function it works normally, the next time it may not respond or act differently.-a There is not one thing specifically, but many tiny random events to cause significant frustration.

The minute the update is made, all these random events disappear, and everything returns to normal

There is doubt that MS overtly nags when something like its Edge browser
has an update but your covert nagging seems to be in your imagination. I
make a point of letting Windows updates mature before installing them
and have never experienced overt or covert nagging on any machine.
--- Synchronet 3.21b-Linux NewsLink 1.2

From Newsgroup: alt.comp.os.windows-11

On 02/14/2026 1:39 PM, Paul wrote:

On Sat, 2/14/2026 10:45 AM, knuttle wrote:

Why does Microsoft feel that it is necessary to nag the user the minute the Update is available? If you don't update when MS thinks you should, it nags by randomly making simple things respond differently or not respond at all. The events will occur every few seconds until the update is installed.-a Through the years I have observed the same thing on several different computers using different mice.

These events occur randomly, maybe one time the program does not open, and a few minutes later it opens normally.-a Maybe when you click on a function it works normally, the next time it may not respond or act differently.-a There is not one thing specifically, but many tiny random events to cause significant frustration.

The minute the update is made, all these random events disappear, and everything returns to normal

This is caused by services stopping and starting.

To update a file on a service "hot", one way to do it is
stop the service, insert the new files, then start the service again.

But this can have side effects on applications that might be
using the service! Even the StartExperience could be perturbed,
and there have been some "famously bad" incidents, such as the
"dancing icons" thing I experienced here once. This is why we
own powerful video cards, so the icons can dance faster.

A lot of the installation process can be done while the OS is
running. At shutdown/restart, the PendMoves can be completed, for
any materials that must wait for a quiet moment to be inserted.

None of it absolutely has to be done this way, but that is the
evolution story. They could maintain a constant service landscape,
by not working on services "in your face" so to speak. They
could easily shut down, and do any amount of installation
without you being able to use the screen. For example, the SearchIndexer could be shut off, Sysmain could be shut off, Windows Defender could be
shut off, the installer could just concentrate on getting the job done. Wouldn't that be neat ? Maybe I should get a job there, delivering
the mail.

Paul

Thanks. It is good to know I am not having hallucinations.

There have been times when I am on the verge of throwing the computer on
the floor because it is not work right. I remember the update problem, update, and the problems disappear.
--- Synchronet 3.21b-Linux NewsLink 1.2

From Newsgroup: alt.comp.os.windows-11

knuttle wrote on 2/14/2026 4:19 PM:

On 02/14/2026 1:39 PM, Paul wrote:

On Sat, 2/14/2026 10:45 AM, knuttle wrote:

Why does Microsoft feel that it is necessary to nag the user the
minute the Update is available? If you don't update when MS thinks you
should, it nags by randomly making simple things respond differently
or not respond at all. The events will occur every few seconds until
the update is installed.-a Through the years I have observed the same
thing on several different computers using different mice.

These events occur randomly, maybe one time the program does not open,
and a few minutes later it opens normally.-a Maybe when you click on a
function it works normally, the next time it may not respond or act
differently.-a There is not one thing specifically, but many tiny
random events to cause significant frustration.

The minute the update is made, all these random events disappear, and
everything returns to normal

This is caused by services stopping and starting.

To update a file on a service "hot", one way to do it is
stop the service, insert the new files, then start the service again.

But this can have side effects on applications that might be
using the service! Even the StartExperience could be perturbed,
and there have been some "famously bad" incidents, such as the
"dancing icons" thing I experienced here once. This is why we
own powerful video cards, so the icons can dance faster.

A lot of the installation process can be done while the OS is
running. At shutdown/restart, the PendMoves can be completed, for
any materials that must wait for a quiet moment to be inserted.

None of it absolutely has to be done this way, but that is the
evolution story. They could maintain a constant service landscape,
by not working on services "in your face" so to speak. They
could easily shut down, and do any amount of installation
without you being able to use the screen. For example, the SearchIndexer
could be shut off, Sysmain could be shut off, Windows Defender could be
shut off, the installer could just concentrate on getting the job done.
Wouldn't that be neat ? Maybe I should get a job there, delivering
the mail.

-a-a-a Paul

Thanks.-a-a-a It is good to know I am not having hallucinations.

There have been times when I am on the verge of throwing the computer on
the floor because it is not work right.-a-a I remember the update problem, update, and the problems disappear.

For both Win10 22H2(two devices - desktop, Surface) and Win11 25H2 I've
never experienced a 'device not working right' problem when an update is available or installing or pending restart(when required).

Possibly the reason not having those symptoms is the hardware having more
than sufficent specs(RAM, SSD, CPU etc.) for its(my) usage pattern and history.

Care to elaborate more on specifics.
e.g.
- what simple things respond differently?
- what events occur every *few seconds*?
- why you chose to include that issues occur when using different mice
on different devices.
--
...w-i|#-o-#-n|#
--- Synchronet 3.21b-Linux NewsLink 1.2

From Newsgroup: alt.comp.os.windows-11

On Sat, 14 Feb 2026 10:45:02 -0500, knuttle <keith_nuttle@yahoo.com>
wrote:

Why does Microsoft feel that it is necessary to nag the user the minute
the Update is available? If you don't update when MS thinks you should,
it nags by randomly making simple things respond differently or not
respond at all. The events will occur every few seconds until the update
is installed. Through the years I have observed the same thing on
several different computers using different mice.

These events occur randomly, maybe one time the program does not open,
and a few minutes later it opens normally. Maybe when you click on a >function it works normally, the next time it may not respond or act >differently. There is not one thing specifically, but many tiny random >events to cause significant frustration.

The minute the update is made, all these random events disappear, and >everything returns to normal

AFAIK, I've never experienced what you're reporting, and I've used a lot
of Windows computers, running a lot of Windows versions, over a period
of a lot of years.

--- Synchronet 3.21b-Linux NewsLink 1.2

From Newsgroup: alt.comp.os.windows-11

knuttle wrote on 2/15/2026 5:10 AM:

On 02/14/2026 9:00 PM, ...w-i|#-o-#-n|# wrote:

knuttle wrote on 2/14/2026 4:19 PM:

On 02/14/2026 1:39 PM, Paul wrote:

On Sat, 2/14/2026 10:45 AM, knuttle wrote:

Why does Microsoft feel that it is necessary to nag the user the
minute the Update is available? If you don't update when MS thinks
you should, it nags by randomly making simple things respond
differently or not respond at all. The events will occur every few
seconds until the update is installed.-a Through the years I have
observed the same thing on several different computers using
different mice.

These events occur randomly, maybe one time the program does not
open, and a few minutes later it opens normally.-a Maybe when you
click on a function it works normally, the next time it may not
respond or act differently.-a There is not one thing specifically,
but many tiny random events to cause significant frustration.

The minute the update is made, all these random events disappear,
and everything returns to normal

This is caused by services stopping and starting.

To update a file on a service "hot", one way to do it is
stop the service, insert the new files, then start the service again.

But this can have side effects on applications that might be
using the service! Even the StartExperience could be perturbed,
and there have been some "famously bad" incidents, such as the
"dancing icons" thing I experienced here once. This is why we
own powerful video cards, so the icons can dance faster.

A lot of the installation process can be done while the OS is
running. At shutdown/restart, the PendMoves can be completed, for
any materials that must wait for a quiet moment to be inserted.

None of it absolutely has to be done this way, but that is the
evolution story. They could maintain a constant service landscape,
by not working on services "in your face" so to speak. They
could easily shut down, and do any amount of installation
without you being able to use the screen. For example, the SearchIndexer >>>> could be shut off, Sysmain could be shut off, Windows Defender could be >>>> shut off, the installer could just concentrate on getting the job done. >>>> Wouldn't that be neat ? Maybe I should get a job there, delivering
the mail.

-a-a-a Paul

Thanks.-a-a-a It is good to know I am not having hallucinations.

There have been times when I am on the verge of throwing the computer
on the floor because it is not work right.-a-a I remember the update
problem, update, and the problems disappear.

For both Win10 22H2(two devices - desktop, Surface) and Win11 25H2 I've
never experienced a 'device not working right' problem when an update
is available or installing or pending restart(when required).

Possibly the reason not having those symptoms is the hardware having
more than sufficent specs(RAM, SSD, CPU etc.) for its(my) usage pattern
and history.

Care to elaborate more on specifics.
-a-ae.g.
-a-a- what simple things respond differently?
-a-a- what events occur every *few seconds*?
-a-a- why you chose to include that issues occur when using different
mice on different devices.

OP:-a My current computer has an Intel(R) Core(TM) Ultra 7 155U;-a 16.0 GB ram, and a 1TB solid state drive.

This has been happening through several computers the oldest had an i3
CPU that I bought that one nearly 20 years age. It is the only computer
that actually stop running with a "POP"

Care to elaborate on something specific.
- if it started on a 20 yr old device and still occurring on the
current, that should be plenty of time to at least provide a specific
name of a program or event.
--
...w-i|#-o-#-n|#
--- Synchronet 3.21b-Linux NewsLink 1.2

From Newsgroup: alt.comp.os.windows-11

On 02/15/2026 10:18 AM, ...w-i|#-o-#-n|# wrote:

knuttle wrote on 2/15/2026 5:10 AM:

On 02/14/2026 9:00 PM, ...w-i|#-o-#-n|# wrote:

knuttle wrote on 2/14/2026 4:19 PM:

On 02/14/2026 1:39 PM, Paul wrote:

On Sat, 2/14/2026 10:45 AM, knuttle wrote:

Why does Microsoft feel that it is necessary to nag the user the
minute the Update is available? If you don't update when MS thinks >>>>>> you should, it nags by randomly making simple things respond
differently or not respond at all. The events will occur every few >>>>>> seconds until the update is installed.-a Through the years I have >>>>>> observed the same thing on several different computers using
different mice.

These events occur randomly, maybe one time the program does not
open, and a few minutes later it opens normally.-a Maybe when you >>>>>> click on a function it works normally, the next time it may not
respond or act differently.-a There is not one thing specifically, >>>>>> but many tiny random events to cause significant frustration.

The minute the update is made, all these random events disappear, >>>>>> and everything returns to normal

This is caused by services stopping and starting.

To update a file on a service "hot", one way to do it is
stop the service, insert the new files, then start the service again. >>>>>
But this can have side effects on applications that might be
using the service! Even the StartExperience could be perturbed,
and there have been some "famously bad" incidents, such as the
"dancing icons" thing I experienced here once. This is why we
own powerful video cards, so the icons can dance faster.

A lot of the installation process can be done while the OS is
running. At shutdown/restart, the PendMoves can be completed, for
any materials that must wait for a quiet moment to be inserted.

None of it absolutely has to be done this way, but that is the
evolution story. They could maintain a constant service landscape,
by not working on services "in your face" so to speak. They
could easily shut down, and do any amount of installation
without you being able to use the screen. For example, the
SearchIndexer
could be shut off, Sysmain could be shut off, Windows Defender
could be
shut off, the installer could just concentrate on getting the job
done.
Wouldn't that be neat ? Maybe I should get a job there, delivering
the mail.

-a-a-a Paul

Thanks.-a-a-a It is good to know I am not having hallucinations.

There have been times when I am on the verge of throwing the
computer on the floor because it is not work right.-a-a I remember the >>>> update problem, update, and the problems disappear.

For both Win10 22H2(two devices - desktop, Surface) and Win11 25H2
I've never experienced a 'device not working right' problem when an
update is available or installing or pending restart(when required).

Possibly the reason not having those symptoms is the hardware having
more than sufficent specs(RAM, SSD, CPU etc.) for its(my) usage
pattern and history.

Care to elaborate more on specifics.
-a-ae.g.
-a-a- what simple things respond differently?
-a-a- what events occur every *few seconds*?
-a-a- why you chose to include that issues occur when using different
mice on different devices.

OP:-a My current computer has an Intel(R) Core(TM) Ultra 7 155U;-a 16.0
GB ram, and a 1TB solid state drive.

This has been happening through several computers the oldest had an i3
CPU that I bought that one nearly 20 years age. It is the only
computer that actually stop running with a "POP"

Care to elaborate on something specific.
-a- if it started on a 20 yr old device and still occurring on the
current, that should be plenty of time to at least provide a specific
name of a progPram or event.

OP: It is completely random, as to action, program, etc.

I believe the explaintion of preinstalation of some components (earlier
post) seems to fit what I am seeing.

--- Synchronet 3.21b-Linux NewsLink 1.2