Main Forum > Tweaking.com Support & Help
Problem with Windows Repair (All in One) v2.8.3
Shane:
Internet is finally working correctly :-)
I am downloading the videos now. I am also downloading virtual box, I will load it up in Windows 7 64 but in vmware and see if I can trace down what it doesnt like touched on the permissions.
Also on the other screen shots.
The system going to the login screen, this happens after the file permissions repair. I dont know why windows is doing that, but I call the command to exit the session 0 screen and I think because it is being called by the trusted installer it is making it go to the login screen instead of back to the logged in user. I will see if I can fix that.
As for the folders having infinite loops. Is the file permissions repair completely all the way? Because at the end of that repair it is suppose to call a cleanup command to go and fix all those folders that are normally suppose to be denied. I will test that as well on my end to make sure something didnt change.
Shane
MarkW:
Folder infinite loop - to me it looked as if the process failed when it hit the wall, and so did not have the chance to clean up properly.
I did note the other user on your blog running across similar issues with v2.83. I don't recall if his box was virtual or not.
The videos will allow you to see the programs I have installed on the computer and, plus I had mentioned in one of the initial emails that I also had the latest version of flash, shockwave and java jre installed.
Shane:
Ok I installed virtualbox on my win 7 64bit in vmware that I had alreayd ran the repairs on. I get the same error.
So I looked up the error and found the fix.
The error happens when the program registers the oleaut32.dll file. It changes two registry keys and removed the path and just has the file name. Other programs work fine with it but for some reason virtual box excepts the full path. So once I put the full path back in then virtual box opened right up.
HKEY_CLASSES_ROOT\CLSID\{00020420-0000-0000-C000-000000000046}\InprocServer32
and
HKEY_CLASSES_ROOT\CLSID\{00020424-0000-0000-C000-000000000046}\InprocServer32
Changed it to C:\Windows\system32\oleaut32.dll
So I will double check a few things and then add that path into the repairs after the register system files is ran. I have to have the repair look at what the proper system32 path is on the system, for those people who have windows running on a different drive letter and that should do it.
Let me know how that works for you.
I am also going to double check the other repairs.
Shane
Shane:
Tested and confirmed, run this in a cmd.exe window
regsvr32 oleaut32.dll
And those registry keys get changed by the dll file. Odd since SO many repairs MS recommends registering that dll.
Seems like it is a bug in virtualbox that they want the full path when all other programs work fine it with it. I think it is because virtualbox is one of the few programs that use that registry path directly instead of windows telling it which one to use like it normally does when you call an API.
But none the less, on a fresh install of windows, that path is in there. Odd that registering the file would change it like that. Makes me wonder how many other paths it updates.
Shane
Shane:
Found a old post from a couple of months ago on it, I never got a reply back so I never added it to the repair
http://www.tweaking.com/forums/index.php/topic,2109.msg13568.html#msg13568
I am working on adding it to the next update :-)
Shane
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version