Tech Support Forum banner
Status
Not open for further replies.
21 - 37 of 37 Posts
Discussion starter · #22 ·
Volume in drive C is OS
Volume Serial Number is 3CE7-8357

Directory of C:\Windows\system32

11/20/2010 09:23 PM 345,088 cmd.exe

Directory of C:\Windows\system32

11/20/2010 09:23 PM 345,088 Utilman.exe
2 File(s) 690,176 bytes

Directory of C:\Windows\system32\en-US

11/21/2010 01:06 AM 131,072 cmd.exe.mui

Directory of C:\Windows\system32\en-US

11/21/2010 01:06 AM 5,120 Utilman.exe.mui
2 File(s) 136,192 bytes

Total Files Listed:
4 File(s) 826,368 bytes
0 Dir(s) 409,945,726,976 bytes free
 
Please follow the instructions below VERY carefully.

1. Run Utilman.exe as Administrator (click start menu search for utilman.exe, right click and select "Run as Administrator")

NOTE: You MUST run Utilman.exe as Administrator or this fix WILL NOT WORK.

2. Press ENTER after each line of code entered below (you may copy and paste):

Code:
 cd c:\windows\system32
  
 takeown /F cmd.exe 
  
 takeown /F utilman.exe 
  
 icacls utilman.exe /grant Everyone:F
  
 icacls cmd.exe /grant Everyone:F
  
 ren cmd.exe cmd.exe.old
  
 ren utilman.exe utilman.exe.old
  
 ren utilman.exe.old cmd.exe
  
 ren cmd.exe.old utilman.exe
Done! Try opening Ease of Aaccess Center with the button at the login screen. :dance:
 
If the fix above doesn't work, you may have to copy a fresh copy of Utilman.exe from C:\windows\winsxs

1. Navigate to C:\windows\winsxs

2. In the search bar in the upper right hand corner of the window type: Utilman.exe

3. Simply copy and paste this copy over to C:\windows\system32 (You must be an administrator to do this).

4. Try Ease of Access Button again.
 
Hi, I wonder when you went back through the web site that tells you how to do this you recalled where you went wrong? (BTW there is a flaw in the info given, when you access the RE a virtual Ram drive is created in this drive your OS may be allocated a different drive letter, it is important to know this for any cmds, so first run a cmd at the x sources:- bcdedit | find "os device" the returned partition drive letter is what you need to use.

Ganjeii has had a good go, cmd will have permissions so I doubt icacls is needed (will do no harm) for reference this is checked by typing at a cmd as admin:-

icacls C:\windows\system32\utilman.exe ( applies to any file you are having permissions problems with, the result will be something like this (F being full control):-

C:\windows\system32\utilman.exe NT SERVICE\TrustedInstaller:(F)
BUILTIN\Administrators:(F)
NT AUTHORITY\SYSTEM:(F)
Everyone:(F)
BUILTIN\Users:(F)

Successfully processed 1 files; Failed processing 0 files
 
Thanks jenae, yes I should have mentioned that these commands should be run from within the OS / safe mode exactly due to complications with the RAM drive that you mention.
 
Hi, no ganjeii nothing wrong with your cmds, (just icacls not being needed, however as I said, could do no harm) I was referring to the OP's first post when he ran the hack to replace a password, something that we do not support here... BTW
 
Discussion starter · #29 ·
I tried pasting the fresh copy but it says I need permission. Mine is the only account on the computer and supposedly has Administrator permissions. Can anyone point me to the process to change or grant permission to do this?

Thanks so much!
 
Discussion starter · #33 ·
I got to this line of ganjeii's instructions and it denied me access to utilman after I hit "enter" :

icacls utilman.exe /grant Everyone:F
 
Hi, I wonder when you went back through the web site that tells you how to do this you recalled where you went wrong? (BTW there is a flaw in the info given, when you access the RE a virtual Ram drive is created in this drive your OS may be allocated a different drive letter, it is important to know this for any cmds, so first run a cmd at the x sources:- bcdedit | find "os device" the returned partition drive letter is what you need to use.

Ganjeii has had a good go, cmd will have permissions so I doubt icacls is needed (will do no harm) for reference this is checked by typing at a cmd as admin:-

icacls C:\windows\system32\utilman.exe ( applies to any file you are having permissions problems with, the result will be something like this (F being full control):-

C:\windows\system32\utilman.exe NT SERVICE\TrustedInstaller:(F)
BUILTIN\Administrators:(F)
NT AUTHORITY\SYSTEM:(F)
Everyone:(F)
BUILTIN\Users:(F)

Successfully processed 1 files; Failed processing 0 files
jenae may have covered this with the above
 
Hi, go back to step 15 in your password hack, the cmd there is to restore utilman to it's rightful place it may not have worked if your drive is being seen as C: drive not D: drive (which in most instances it is) so substitute the c for d. To be sure before doing anything at the cmd prompt (x sources) type this (exactly as shown)

bcdedit | find "osdevice" (press enter, the | is called a "pipe" and appears above the \ key)

Whatever this returns as partition drive use in your cmd.
 
also be SURE that you are running the command prompt as ADMINISTRATOR (right click file and select "Run as Administrator) before running ANY commands
 
Hi, in the hack you are instructed to do this in the RE (repair your computer) option. The cmd prompt here is by default, admin.
 
21 - 37 of 37 Posts
Status
Not open for further replies.
You have insufficient privileges to reply here.