didn't update

Before making an image of C: I always use the standard Windows disk clean
utility to clean up junk.
The next time I boot te computer, I get a desktop screen (before logging
in), stating: "configuring updates. do not shut down". And: "cleaning up. do
not shut down".
After waiting for minutes I can then log in.
What's this all about? I didn't have any updates previously!
BTW The same happens on my other computer...



--


|\ /|
| \/ |@rk
\../
\/os

Linea Recta wrote:

Before making an image of C: I always use the standard Windows disk clean
utility to clean up junk.
The next time I boot te computer, I get a desktop screen (before logging
in), stating: "configuring updates. do not shut down". And: "cleaning up. do
not shut down".
After waiting for minutes I can then log in.
What's this all about? I didn't have any updates previously!
BTW The same happens on my other computer...

Some updates require a new boot of the OS so files to replace but are
inuse are free to replace on startup. This eliminates a mismatch of
files between the old set and new set from the update. Alas, Windows
Update does not always say when a reboot is required to complete an
update. The system may be usable until the next reboot but the update
actually completes during the next boot. So you might've applied
updates a long time ago, left your computer running all that time, and
then got the update notice on shutdown or on the next startup telling
those old updates are now actually allowed to complete.

When you update Windows, and whether or not it tells you to reboot, do a
reboot after what looks to be the update's finish.

"VanguardLH" schreef in bericht
...
Linea Recta wrote:

Before making an image of C: I always use the standard Windows disk clean
utility to clean up junk.
The next time I boot te computer, I get a desktop screen (before logging
in), stating: "configuring updates. do not shut down". And: "cleaning up.
do
not shut down".
After waiting for minutes I can then log in.
What's this all about? I didn't have any updates previously!
BTW The same happens on my other computer...

Some updates require a new boot of the OS so files to replace but are
inuse are free to replace on startup. This eliminates a mismatch of
files between the old set and new set from the update. Alas, Windows
Update does not always say when a reboot is required to complete an
update. The system may be usable until the next reboot but the update
actually completes during the next boot. So you might've applied
updates a long time ago, left your computer running all that time, and
then got the update notice on shutdown or on the next startup telling
those old updates are now actually allowed to complete.

When you update Windows, and whether or not it tells you to reboot, do a
reboot after what looks to be the update's finish.



OK but thet being said, I haven't updated for some time.
I just used Windows clean disk (also the restore points)





--


|\ /|
| \/ |@rk
\../
\/os

Linea Recta wrote:
"VanguardLH" schreef in bericht
...
Linea Recta wrote:

Before making an image of C: I always use the standard Windows disk
clean
utility to clean up junk.
The next time I boot te computer, I get a desktop screen (before logging
in), stating: "configuring updates. do not shut down". And: "cleaning
up. do
not shut down".
After waiting for minutes I can then log in.
What's this all about? I didn't have any updates previously!
BTW The same happens on my other computer...

Some updates require a new boot of the OS so files to replace but are
inuse are free to replace on startup. This eliminates a mismatch of
files between the old set and new set from the update. Alas, Windows
Update does not always say when a reboot is required to complete an
update. The system may be usable until the next reboot but the update
actually completes during the next boot. So you might've applied
updates a long time ago, left your computer running all that time, and
then got the update notice on shutdown or on the next startup telling
those old updates are now actually allowed to complete.

When you update Windows, and whether or not it tells you to reboot, do a
reboot after what looks to be the update's finish.



OK but thet being said, I haven't updated for some time.
I just used Windows clean disk (also the restore points)

Try "PendMoves" ?

It is supposed to list the files scheduled for deletion
on a reboot.

https://technet.microsoft.com/en-us/...nals/pendmoves

Paul

Paul wrote:

Linea Recta wrote:
"VanguardLH" schreef in bericht
...
Linea Recta wrote:

Before making an image of C: I always use the standard Windows disk
clean
utility to clean up junk.
The next time I boot te computer, I get a desktop screen (before logging
in), stating: "configuring updates. do not shut down". And: "cleaning
up. do
not shut down".
After waiting for minutes I can then log in.
What's this all about? I didn't have any updates previously!
BTW The same happens on my other computer...

Some updates require a new boot of the OS so files to replace but are
inuse are free to replace on startup. This eliminates a mismatch of
files between the old set and new set from the update. Alas, Windows
Update does not always say when a reboot is required to complete an
update. The system may be usable until the next reboot but the update
actually completes during the next boot. So you might've applied
updates a long time ago, left your computer running all that time, and
then got the update notice on shutdown or on the next startup telling
those old updates are now actually allowed to complete.

When you update Windows, and whether or not it tells you to reboot, do a
reboot after what looks to be the update's finish.

OK but thet being said, I haven't updated for some time.
I just used Windows clean disk (also the restore points)

Try "PendMoves" ?

It is supposed to list the files scheduled for deletion
on a reboot.

https://technet.microsoft.com/en-us/...nals/pendmoves

But that won't present a user prompt as Recta noted. Those pending
moves/renames/deletes are done invisibly and on the next new load of
Windows, not on a shutdown of Windows.

Other tools can use that registry key, too. For example, Unlocker will
use it if it cannot delete a file and cannot release the handle from the
process currently owning that file. It will ask if you want to delete
the file on the next boot of Windows. If you say yes, it adds to the
pend key to do a "move" (which is a delete, in this case because no
destination is specified).

https://technet.microsoft.com/en-us/.../cc960241.aspx

The PendingFileRenameOperations data item won't exist until an entry is
added. The multi-string syntax per entry is:

\??\source!\??\target

A rename is accomplished by using the same path for the target file but
a different filename. Move is accomplished by changing the path for the
target. Delete is accomplished by not specifying a target. plus there
must be 2 NULs at the end of the line: a NUL as a placeholder for the
target argument and the string terminating NUL (strings are often
terminated by a NUL to indicate where they end). You have to modify the
string to add NULs by selecting Modifying Binary Data since the editor
won't let you input NULs.

That registry item is read at Windows load time (every early in the load
process to ensure the source is not locked up). It happens invisibly to
the user. There are no "configuring updates" and "cleaning up" prompts.
Those occur when there have been Windows updates but they have pending
operations to perform either on shutdown, startup, or both.

Note that is has been proven in the past that having Windows Update
configured to always notify (never download, never install) does not bar
Microsoft from pushing some updates. For example, if WU is enabled and
even when set to notify only, Defender will use WU to get its sig
updates without prompting or listing WU updates. I've seen the WU
client get updated without user prompt. That is why I disable both the
BITS and WU services to ensure Microsoft cannot push anything onto my
computer until *I* am ready: do an image backup, enable BITS and WU,
check for updates, *review each one*, detemine which to allow and which
to hide, perform the updates, disable BITS and WU, and reboot even if
not told to do so to make sure any non-blocking but pending changes get
applied.