Keith Nuttle wrote:
A couple of updates now, the computer stalls with a black screen and a
box in the upper left corner that say it is updating the personal settings.

If you put the mouse cursor in the box it says it is not responding. If
you let it set for 5 or 10 minutes it eventually completes what ever it
is doing and then continues to the desktop.

I am running Windows 10 64 bit 17-9 build 16299.214.

I just upgraded to that build tonight with the installation of
KB4058258. When it completed installing that update, and after
rebooting, the screen with the personal settings widow came up and as I
said took about 7 minutes to complete.

Is this a bug in the installer or a problem with my computer. HP
laptop, Intel i7 CPU with 8GB of ram and 1TB of storage



Some people cannot even install that one.

https://social.technet.microsoft.com...in10itprosetup

My release machine is still showing 16299.192.
I'm guessing if I were to dig deep enough, I'll find mine
is failing too.

*******

You could temporarily create a second account "Keith2",
shut down, and log in as "Keith2" and see if the
system comes up faster. If you have auto-login set up,
you might have to temporarily disable it.

"Updating your settings", it might be messing with the
registry file in your home directory. There is a registry
file which is your "profile", and it's protected by a
journal. This is intended to make it robust against
power failures, and the registry can be repaired using
the journal state information.

Using a completely separate "Keith2" account, gives a
chance to compare the behavior of a fresh home directory
with fresh reg file created in it.

The other part of the registry, is the registry files
belonging to the system, and if those are messed up,
changing accounts will make no difference at all. Those
can be repaired after a fashion, by using a System Restore
point and going back in time. Since Win10 likes to turn
off System Restore, there might not be any available
Restore Points at present. And this is something you
might consider turning back on (until the next OS
upgrade turns it off again).

Paul