Main Forum > Tweaking.com Support & Help

Problem with Windows Repair (All in One) v2.8.3

<< < (5/5)

Shane:
The cleanup repair for the permissions is suppose to set everyone to deny, which is how you see it happen on the other machine you did it on.

But for some reason on this machine everyone is still given full access and that tells me that the cleanup isnt running or something else is going on.

The SID for Everyone is S-1-1-0

The command in the clean is
Setacl.exe -on "C:\Users\All Users\Application Data" -ot file -actn ace -ace n:S-1-1-0;p:list_folder;m:deny -ignoreerr -silent

The actuall code is
sProfilesLocation & "\All Users\Application Data"

where it pulls the profiles location on the system (Some people have the profiles stored on a different drive), in the log file I have it record what it pulls for that and it does point to the right path
Profiles Location: C:\Users

If you are up for it, send me an email and I will teamviewer in and see if I can find the variable that is doing this. If I can find the reason why it isnt getting changed back I can add code to handle it and that will make the program better in case someone else has this problem as well :-)

Shane

MarkW:
Shane,
I just ran v.2.8.5 on two machines, for confirmation after the first result was unexpected.  VirtualBox is working fine, but the infinite 'Application Data' directory has returned for All Users profile directory.  I had noticed the cmd window with the 'too long' message again, but thought it might get cleaned up at the end, like it had the other day.  (It was remained following the reboot.)
I ran Windows Repair with everything selected, but  :cry: with the 'Lock Repair List While Running Repairs' and 'Hide output To Cmd.exe Window' settings deselected.  I choose the automated system restart upon completion.

I replaced the exe with the test one from the other day, which I had set aside before installing v2.8.5 and re-ran the program using that beta exe.  That stopped me from being able to open the Application Data directory, as it should have.  I then ran it on the second box with the wrong results for the Application Data directory, so I am guessing that you had changed more than the .exe in the latest release.

Mark

Shane:
I got an email that you posted while I was about to relax and head to bed. So I came out to my off ice real fast and double checked the code and even ran the file permissions repair in Windows7 and it all works fine.

The code for the cleanup didnt get changed in anyway since the beta build I gave you, the same code is still in there.

I am curious, if you have time, and I will respond tomorrow, do a test for me.

take the new version and run all the repairs, then if the folder is unblocked again run the same version again but this time ONLY the file permissions repair and let me know if it fixes it. The goal of this test is to see if there is some bug I am not aware off where something isnt running right when the other repairs are ran along with it, such as the registry permissions repair before hand and the repairs after.

So if running the single repair by itself fixes it and running it with other repairs keeping it from working then that would point me in the right direction.

It is still odd that I cant replicate it on my end, I WANT to know what this variable we are missing is lol.

Night!

Shane

MarkW:
 :smiley:
v2.8.6 has resolved these issues on the older / slower machines.   
I even gave it a shot on an old emergency laptop: Pentium III 1.20Ghz, 785mb RAM, XP Pro Sp3, 40GB IDE ATA/100 5400 rpm hard drive.

Thank you Shane.

Mark

Shane:
Good to hear! :-)

Shane

Navigation

[0] Message Index

[*] Previous page