Main Forum > Tweaking.com Support & Help

Improvements for WindowsRepair

<< < (5/8) > >>

Willy2:
Sorry. Yes, I missed that. Yes, at least ""Subinacl.exe"" caused - at least - one error in CMD.exe. (Not recognized).

Both ""Subinacl.exe"" and ""Psexec.exe"" are found in a subfolder of ""....\Windowsrepair v1.52\"". And I found ""Subinacl.exe"" also in the ""C:\"" folder (with the hidden (???) attribute set). Or should ""Psexec.exe"" be copied to the ""C:\"" folder as well ?

Shane:
Psexec.exe is working or you would never see the command window. The problem is with Subinacl.exe. This is what sets the permissions. And it shouldn't be hidden.

Here is the bat file that the program makes and runs, you shouldn't be getting an error. I am also not sure how your  Subinacl.exe on the c drive got marked hidden. Try getting rid of it and try the repair again :wink:

 "@echo on"
"copy /y " &  App.path & "\files\subinacl.exe" & " C:\subinacl.exe"
"takeown /F " & "C:\subinacl.exe" & " >nul"
"icacls " & "C:\subinacl.exe" & " /GRANT *S-1-1-0:F >nul"
"C:\subinacl.exe" & " /subdirectories " & "\*.*"  & " /grant=administrators=f /grant=system=f /grant=everyone=f /grant=users=f"

Shane

Willy2:
Weird. ""Subinacl.exe"" works. In that script you gave the commands ""takeown"" and ""icacls"" both generate an error in CMD.exe. Or is my system faulty ? Are these commands only found in the "".NET"" software ? (Which I didn't install).

When I run ""Reset registry permissions"" then CMD.exe reports that it has rejected a command because it came across a wildcard ""*"". It seems it wants to access a part of the registry and then gets ""rejected"". Weird. Why did it work with a previous version of WR ?

I fear the removal of a piece of software or an (web-)update from Microsoft could have caused this weird behaviour.

Shane:
Those errors are excepted.

Does the reg permissions repair work? It uses the same files. And when you do it you should see the cmd window working away.

Shane

Willy2:
I have been fiddling around with Windows Repair (WR), Simple Performance Boost (SPB) and the MSDOS (CMD.exe) command CHKDSK lately. This gives me a clue what could have gone wrong in WR on my system (Windows XP). I tried to repair the filesystem of a 4 GB MicroSD memory card (FAT32) with the CHKDSK command but the response was ""Command not recognized"". Then I typed the command PATH and the response was ""PATH=<NULL>"". No wonder I couldn't use the CHKDSK command because CHKDSK is placed in the ""C\Windows\system32"" directory.

It seems WR (or SPB) issues some sort of ""PATH=<NULL>"" command. Because SPB (i.e. ""netsh.exe"") also wanted to acess a file (""framedyn.dll"") in the ""C:\windows\system32\wbem"" folder and fails to find it and generated a non fatal error. And this COULD explain why WR fails to e.g. both ""Reset file Permissions"" and ""Reset Registry Permissions"". WR extensively uses CMD.exe to execute a number of commands. WR wants to access e.g. the ""C\Windows\system32\wbem"" folder as well. So, could you check what PATH commands both WR and SPB are issueing while running. Or is my filing system broken ? Did you change something in the latest version ?

Navigation

[0] Message Index

[#] Next page

[*] Previous page