Main Forum > Tweaking.com Support & Help
Problem with Windows Repair (All in One) v2.8.3
MarkW:
I made the manual registry changes for the full path of the oleaut32.dll. Yes, suddenly that allowed the VirtualBox to launch again successfully.
If oleaut32.dll had been unregistered then I could understand the issue. I am surprised that the search path would not look for that file in the system32 directory. I wonder if the search path is being affected.
Prior to the manual change to the registry keys I tried registering of oleaut32.dll in a cmd.exe box/window, but saw no difference. I even tried a reboot. I know that in the past, at times, I have had to register dll's while being in the directory that they exist. Maybe I didn't do that this time.
Nothing has changed the directory structure under all users yet.
Would it be good or bad or no-effect if I ran the Windows Repair again? Would it now clean up the folder loop it left behind previously?
The other user/customer that complained about the slowness after running v2.8.3 - I experienced that as well.
Have the videos you downloaded from me, or the log files I sent later added any value to your troubleshooting? By this point I would expect you to be able to notice any deviations in the standard processes on the screen in your sleep. Of course, you have adjusted the screen processes as well.
Have you had insight on the mw2.jpg screenshot to this point? At a couple other points it showed up as a task on the TaskBar, which I pointed out in the first video. I had opened up the task to show you what it was reporting.
Thanks for your continued efforts,
Mark
MarkW:
G-hot, the other user posting the message with 'Critical Bug' in the title got the same 'too long' command windows that I did.
I'm guessing that the non-English script in his other screen capture just had to do with the language he is running on his computer.
Shane:
Just finished 2.8.4 and getting ready to put it out. The new version will now put that full path back in the registry. It isnt a bug of the program, that is just how the reg dll command works for that dll file. In XP that is how it is suppose to be, since vista and newer they never updated the register code in the dll to put the full path! Very odd.
As for slowness, I never seen any slowness after running the repairs. The commands are still the same and such, and now way for the program to actually slow down the computer. Only way I could think of is when it restored the default windows services. You get crap like the search index and such back on, which always has slowed down the machine since it is using the drive.
--- Quote ---G-hot, the other user posting the message with 'Critical Bug' in the title got the same 'too long' command windows that I did.
I'm guessing that the non-English script in his other screen capture just had to do with the language he is running on his computer.
--- End quote ---
That is because of the folders having those infinite loops. The bat file is doing the looping and so when it hits those it just keeps going until it gets to long.
On my file permissions repair I did have the cleanup of the permissions run only as the system account. If for some reason the program couldnt get the file to run as system then it wouldnt work. I have updated it to also run it as the current user account as well.
I wonder if on your system the program is having trouble running as the system account or not, but from the looks of it, it shouldnt be since we see the commands running under system in the screen shots.
Shane
MarkW:
The installation is standard, so it should not have any problems running the system account. I have not had any such problems to this point. I do not have it as part of any network domain, etc. The account that I have auto logon is the account that was created during the O/S installation process and is part of the admin group, locally. I did take the option of making it part of a home network during the O/s installation so that I could get to other computers on my LAN through shared-out directories.
I will revert to the clean snapshot and will attempt a clean run of v2.8.4, and let you know my results.
I will also grab your v1.2.0 Envelope Printer. :cheesy:
Shane:
Only reason why I ask is I had a fresh install of Vista 64 bit service pack 2 installed, not a single other update past that. And when I was testing the repairs I noticed the ones set to run as system where failing.
Turns out that the tweaking_ras.exe was crashing because one of the APIs it calls in Windows was causing a crash in the msvb6 dll. But on another system with vista sp2 and all the updates it runs just fine. Looks like there is an update that fixes that, but I normally have the updates installed. But it was the first time I seen that happen.
I am off for the day, let me know how things go with the new versions :-)
Shane
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version