The admin account on a single user machine which did not require a password to logon has been changed by an update this week to require a password which of course does not exist. The question is how can the Admin account be reset to allow access. There is a second non-admin account which boots without a password, but is of little use, because ther are none of apps etc that are contained in the admin account. The user does not have a Micrsoft account.
This was originally an OEM pre-installed Win 7 Home version and was upgraded by Windows update.
It is possible to setup a new account from the secondary account, the question is, how to replicate the admin account apps in a new admin account?
There's a thread already covering this think... Try search? (I'm on my mobile so can't find it).
Since I opened this thread, I have found various solutions to this problem by manipulating the utilman.exe file from a cmd window via the installation DVD. They refer to utilman file being in windows/system32, however I have this file in two places winsxs and wow64. I am now confused as to which of the files is being used by the 64bit OS during bootup, my guess is the one in wow64, am I right?The admin account on a single user machine which did not require a password to logon has been changed by an update this week to require a password which of course does not exist. The question is how can the Admin account be reset to allow access. There is a second non-admin account which boots without a password, but is of little use, because ther are none of apps etc that are contained in the admin account. The user does not have a Micrsoft account.
This was originally an OEM pre-installed Win 7 Home version and was upgraded by Windows update.
It is possible to setup a new account from the secondary account, the question is, how to replicate the admin account apps in a new admin account?
Prior to writing my previous post, I used "Everything search engine" which I now find does not include any results from the system32 folder. A File explorer search of the system32 folder immediately located the utilman.exe file, my confusion has been resolved.Since I opened this thread, I have found various solutions to this problem by manipulating the utilman.exe file from a cmd window via the installation DVD. They refer to utilman file being in windows/system32, however I have this file in two places winsxs and wow64. I am now confused as to which of the files is being used by the 64bit OS during bootup, my guess is the one in wow64, am I right?
Regarding my original question regarding resetting the admin password, I have gathered some information, and now await the return of my nieghbour to see if the proposed solution works on his locked computer. If the recovery works I will post back the details.
Just after my last post, my neighbour informed me that he was back to normal with his Windows 10. His son had contacted Microsoft and they issued a login code/password that allowed him to login to his admin account.
The solution I had intended to try is still untested. If anyone is interested, have look at the attachment which is a copy of an article by isumshare
