Main Forum > Tweaking.com Support & Help

Bug: Windows Repair breaks Oracle Virtual Box

<< < (3/3)

Shane:
Sorry for the late reply, my wife had our baby :-)

I have seen the page not loading problem on a few of my customer machines. For most of them it was a rootkit infection doing it that only combofix found and nothing else at the time.

A lot of rootkits are so well hidden they are very hard to clean and most of them hijack your network connection to redirect you to other pages with ads on it to try and make money. So because of that you will get random page not loading errors.

Then again on some of the machines it was just a corrupt DNS problem and on 2 of them it was the stupid antivirus firewall doing it.

Sometimes an antivirus can be just as annoying as the virus when it breaks lol

Shane

Willy2:
@Codelurker:  "Repair Internet Explorer" only registers a bunch of files (~ 120 files). And "Registering" means making/refreshing an entry in the registry. And that entry tells Windows in which folder it can find the files it needs. Your description of the problem would suggest that registering one or more of those ~120 files breaks the socalled "COM" subsystem. That also explains why restoring the registry to a previous state fixes this problem.

First of all: do you have IE installed ? and which version ? do you use it ?
(According to my info parts of IE are used by other programs as well.)

Have you Windows Live Mail installed and do you use it ? or any other Windows Live program ? Or do you use Outlook ?

1. Grab the file in the attachment, give it a *.bat extension and run it with admin rights. It produces a file called "Willy2.txt" in the root directory and when a "Repair IE" related file is present on your system, then "Willy2.txt" tells you where that file is located.
2. Download the 32 bits version of "REGDLLVIEW" from "Nirsoft.net".
3. Run it BEFORE you run "Repair IE". The program tells which files are registered in the registry. Export the info produced to a file that can be imported into a spreadsheet. REGDLLVIEW offers that possibility (somewhere).
4. Run WR's "Repair IE"
5. Run "REGDLLVIEW" once more and export the new info as well.
6. Post all three files produced in the next reply. (I am VERY curious, interested !!!!)
7. Take each file from "willy2.txt" and see whether is wasn't registered before & got registered by running "Repair IE". That/those file(s) is/are responsible for braking the "COM" subsystem and "Virtual Box".

When you know which file(s) break(s) Virtual Box then you can remove all the appropriate "REGSVR32" line(s) from the file "IE.txt" (in the subfolder "files" of WR).

Willy2:
And DO report what you're experiences are. did these instructions help you ?

Navigation

[0] Message Index

[*] Previous page