[SOLVED] Used utilman backdoor to reset my machine, can't restore Utilman :(

jstnj

New member

Used this guide^^ to get access to my machine after I accidentally locked myself out due to bad msconfig settings.


Everything is booting correctly, but I tried running `sfc /scannow` and ran into errors restoring utilman. So after finding sysnative forums:

  1. Ran SFCfix once, it wasn't able to restore utilman.exe
  2. found an old thread that supplied an SFCFix.zip for windows 10 and gave it a go (see attached zip), didn't work either
  3. Running SFCFix normally now crashes


    Please see the attached files and CBS log. Let me know if you need anything else! Thanks for any advice.
 

Attachments

  • SFCFix.zip
    1.3 MB · Views: 1
  • CBS.log
    15.7 MB · Views: 2
Hi and welcome to Sysnative,

Such hacks are not without any risks, and you have also used a fix for Windows 8.x / Server 20212!?

Note: I only provide help when this is really your own system, and not when you have tried to get access to a machine which is not yours! This because I don't beleive that 'bad msconfig' settings could be the issue why you couldn't log in anymore....

However, here's the fix to repair 'utilman.exe' for Windows 11 (22621.3235).

Step 1. Download
6530fbb0f4101-56f31e53c97da-SFCFix.PNG
SFCFix and save it to your desktop.

Warning: This fix was written specifically for this system. Do not run this fix on another system.
  • Save any work you have open, and close all programs.
  • Download the attachment SFCFix.zip and save it to your desktop.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
650c22f99662d-6190d993a26f3-SFCFix-Zip-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.


Step 2. Run the System File Checker and DISM with the following commands.
Code:
SFC /Scannow
DISM /online /cleanup-image /RestoreHealth
 

Attachments

  • SFCFix.zip
    190.3 KB · Views: 2
I don't beleive that 'bad msconfig' settings could be the issue why you couldn't log in anymore...
My problem is well documented. I was trying to run benchmarks in safe mode by enabling "Diagnostic mode" and apparently if you do that...your PIN doesn't work and you are in and endless loop of not having access to your own machine.

Thank you for the assistance, I will attempt to use your SFC fix this evening and I will report back!
 
Thanks for that link, which explains a lot... (I'll need to admit I have never used a PIN log in)...

Let me know the result when you have run the fix and SFC / DISM...
 
@Maxstar i believe that worked! Thanks a lot.



Code:
Microsoft Windows [Version 10.0.22631.3447]
(c) Microsoft Corporation. All rights reserved.

C:\Windows\System32>SFC /Scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\Windows\System32>DISM /online /cleanup-image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.22621.2792

Image Version: 10.0.22631.3447

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
 

Attachments

  • SFCFix.txt
    5.6 KB · Views: 2
  • CBS.log
    882.4 KB · Views: 1
Hi,

You're welcome. Glad to hear the issue has been resolved, and the latest CBS log is clean. So we can mark this thread as solved.. (y)
 
Back
Top