Anniversary U/D has corrupted startup configuration, no auto repair.

Dell Dimension E520 been running Win 10 for 9 months no problems. Two anniversary failed update attempts and I am stumped. The problem is after boot there is spinning dots with cursor. Ctrl+alt +del gives logon screen but its is empty save for the blue window frame and three icons at bottom right. Have tried: entering password blind but that failed, tried Shift + click restart, it just restarts normally, same again.
I can boot from installation usb drive and get command prompt with Ctrl+F10. to try Fixmbr commands, no affect
Have done 3x power interupt boot to get to repair screen, Auto repair ran check disk, and auto start up repair, all failed to help, but reported start up corrupted. Then tried safe mode. this boots to completely correct logon screen, showing three users: Administrator, Mum, & Dad.
Tried to log on as administrator, accepts logon but after spinning dots, just a black screen, no desk top, tried: win key+p and down arrow, no affect.
Log on as Mum just the same.
Log on as Dad it works starts desk top in safe mode can run Msconfig, Command prompt, etc. looks OK.
The only programs installed other than windows are Office 2013 and Chrome. Nothing else.
Revert to normal boot and its is still hanging.
The only things plugged in are: KB, Mouse, and Dynamode USB WiFi but have removed that and made no difference.
Any help gratefully accepted.

You could install Macrium Reflect Free, create a bootable rescue disk - then boot from that disk and try to repair your PC. See http://knowledgebase.macrium.com/dis...+boot+problems

dalchina & Steve C.
Thanks for your input.
Yes I have not put system Spec in as I look after quite a few systems for my family.
As to the fix I do not like to be beaten by Microsoft but after trying the fixes suggested and a few more, I did as you suggested, a clean install of 1607.
Downloaded the latest available version to USB and all went well, passed electronic validation, ran perfectly, Installed Office and that ran fine. Office 2013 service pack 1 and win 10 1607 updates started to load.

After final re-boot disaster in the form of Microsoft Updates had struck again.
Unable to run any commands, or install programs, and the quick launch icons had gone invisible!

Lots of messing about and I eventually figured it out: during the update checkdisk had run and to prevent any access to the C:drive all permission's had been removed save for System, to stop any interference I guess. but whilst that was running some other process had forced a restart, resulting in the permission for users not being restored to C:
"Good old Microsoft updates had struck again"
Once I was able to get a command prompt to turn on Administrator logon I could fix this, but as as a user I could not access any apps on C: Fortunately Cortana is a system tool and typing into Cortana produced a System prompt. So it was possible to access Safe mode with Administrator to set users with c: properties -security- advanced.

After reboot all back and so were the quick launch icons as the user App was able to run to set them.

Once again thanks for help and I hope my experience may be of use to others as I notice there are quite a few posts with invisible quick-launch icons.

dalchina said:

Hi, good that your system is running again. Presumably when you did the clean install you either reformatted to deleted existing partitions.

Given that, I would have hoped chkdsk wouldn't have run, so I'm curious as to how you discovered chkdsk had run.. and why you relate that to a change in permissions- would be interesting to know. chkdsk on C: runs at boot.

Have you run any checks on your disk as I suggested?

I did recommend you used Macrium Reflect to create a system/disk image- that should have been the first thing. So hope you've started doing that now, ready for the next failed update.. or not (we hope).

Yes I did disk checks as you suggested. No problems found.
The checkdisk seemed to run on the first reboot of the installation of updates.
I wanted to have my Macrium backup containing all current updates so did not use it initially, I should have done so.
We live and learn.