I have just updated the PC using the MCT as I wasn't getting offered the Threshold 2 update via Windows Update - I assume because I replaced the motherboard last week due to the old one dying.
I generallty use the local admin account to run everything, I am savvy enough to know what I am doing and I have to fix things if I screw them up anyway, so no drama - until I updated.
I started the update using MCT and sat back to wait, when I came back it wanted me to log in using a 'back up' account that I have on the system and when I luckily remembered the password I used this account. It showed me that the old account I used had been disabled by the upgrade - why?
next strange thing is that after I enabled my account and lodged back in, after a few minutes I find that Edge has been locked out from the local admin account and I needed to change the security policy to enable the local admin account to use edge and various other bits - again, why?
I now have everything back as it was and I am able to use the machine again as before, but why did the date do this - very strange.
Yes it is strange. I updated two machines (desktop and Surface Pro 4) and both were flawless. My 8gadgets were removed but I was prompted to reinstall them and the work fine too. There was a two-day separation between when each machine was offered the update via Windows Update. It's a staged rollout.I have just updated the PC using the MCT as I wasn't getting offered the Threshold 2 update via Windows Update - I assume because I replaced the motherboard last week due to the old one dying.
I generallty use the local admin account to run everything, I am savvy enough to know what I am doing and I have to fix things if I screw them up anyway, so no drama - until I updated.
I started the update using MCT and sat back to wait, when I came back it wanted me to log in using a 'back up' account that I have on the system and when I luckily remembered the password I used this account. It showed me that the old account I used had been disabled by the upgrade - why?
next strange thing is that after I enabled my account and lodged back in, after a few minutes I find that Edge has been locked out from the local admin account and I needed to change the security policy to enable the local admin account to use edge and various other bits - again, why?
I now have everything back as it was and I am able to use the machine again as before, but why did the date do this - very strange.
The only aspect that I can think may cause it is that I have the profile for the main account I use on the E: drive as C: is a SSD and isn't big enough for all the rubbish that I have
But then again p, this wasn't an issue for the other updates or the original upgrade from Win 7
Just curious as to what advantage you gain by using the built in administrator account?
Probably nothing but it is the account that I have used for many years when running the Windows 7 machines and it became this when I upgraded to 10.Just curious as to what advantage you gain by using the built in administrator account?
given that it is not part of a domain and has been renamed from the default name I reckon it is just as safe as any other admin account and user accounts just P me off when I am installing and deleting so much stuff
I would be careful....in Windows 10 (and probably earlier versions) Microsoft intended the built in Administrator account to be an emergency backup only and tends to lock it down. There have been several people who, relying upon the built in administrator account as their only administrator account, have found themselves locked out of their own computers when Windows 10 disabled the built in administrator account.Probably nothing but it is the account that I have used for many years when running the Windows 7 machines and it became this when I upgraded to 10.
given that it is not part of a domain and has been renamed from the default name I reckon it is just as safe as any other admin account and user accounts just P me off when I am installing and deleting so much stuff
So the next question is, other than "I've always done it that way", is there a reason not to create a personalized administrator account and leave the built in administrator account disabled until it is needed to be activated in an emergency - such as booting into safe mode? I know we hate giving control over to Microsoft, but sometimes the loss we might encounter just isn't worth it.
Using a regular account with admin privileges and turning UAC off is the same thing by the way. Then when things go south you can use the system admin account to fix it.
I agree, it is just too much hassle to move everything and set them up in a new profile - and the potential for screw ups is why I created the additional account to be able to get back in
i might take take a day out sometime to move everything at some point.
