So one of your friends, “not you of course”, has managed to nuke Internet Explorer and they are unsure how they did it. You’ve eliminated the possibility of viruses and adware, so this just leaves you and a broken IE. Before you begin to even consider running a repair install of the OS, let’s try to do a repair on IE instead.

THE REPAIR PROCESS

Start the Registry Editor by typing regedit from the Run box. Go to HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ Active Setup \ Installed Components \ {89820200-ECBD-11cf-8B85-00AA005B4383} and then right-click the “IsInstalled value.” Click Modify. From there, you will change the value from 1 to 0. All right, go ahead and close the editor and reinstall IE from this location. /http://www.microsoft.com/windows/ie/default.mspx

IF SOMETHING GOES WRONG

If messing with the registry and something goes horribly wrong, you can use “Last Known Good Configuration (F8 Safe Mode)” or a Restore Point to get back to where you were before, with your settings. Then you can try again, this time taking care to watch the portion of the registry you are changing. Most people who have troubles with this end up changing the wrong registry key.

Hope this tut helps some members.

Winsock 2 Repair

WinXP Tips & Trix - Winsock 2 Repair

Repairing Damaged Winsock2

The symptoms when Winsock2 is damaged show when you try to release and renew the IP address using IPCONFIG...

And you get the following error message:

An error occurred while renewing interface 'Internet': An operation was attempted on something that is not a socket.

Also Internet Explorer may give the following error message:

The page cannot be displayed Additionally, you may have no IP address or no Automatic Private IP Addressing (APIPA) address, and you may be receiving IP packets but not sending them.

There are two easy ways to determine if Winsock2 is damaged:

From the XP source files, go to the Support / Tools directory

Winsock Test Method 1

Run netdiag /test:winsock

The end should say Winsock test ..... passed

Winsock Test Method 2

Run Msinfo32

Click on the + by Components

Click on the by Network

Click on Protocol

There should be 10 sections if the Winsock2 key is ok

MSAFD Tcpip [TCP/IP]

MSAFD Tcpip [UDP/IP]

RSVP UDP Service Provider

RSVP TCP Service Provider

MSAFD NetBIOS [\Device\NetBT_Tcpip...

MSAFD NetBIOS [\Device\NetBT_Tcpip...

MSAFD NetBIOS [\Device\NetBT_Tcpip...

MSAFD NetBIOS [\Device\NetBT_Tcpip...

MSAFD NetBIOS [\Device\NetBT_Tcpip...

MSAFD NetBIOS [\Device\NetBT_Tcpip...

If the names are anything different from those in this list, then likely Winsock2 is corrupted and needs to be repaired.

If you have any 3rd party software installed, the name MSAFD may be changed.

There should be no fewer than 10 sections.

To repair Winsock2

Run Regedit

Delete the following two registry keys:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock2

Restart the computer

Go to Network Connections

Right click and select Properties

Click on the Install button

Select Protocol

Click on the Add button

Click on the Have Disk button

Browse to the \Windows\inf directory

Click on the Open button

Click on the OK button

Highlight Internet Protocol (TCP/IP)

Click on the OK button

Winxp Tips And Tricks, Winsock 2 repair

WinXP Tips & Trix - Winsock 2 Repair

--------------------------------------------------------------------------------

Repairing Damaged Winsock2

The symptoms when Winsock2 is damaged show when you try to release and renew the IP address using IPCONFIG...

And you get the following error message:

An error occurred while renewing interface 'Internet': An operation was attempted on something that is not a socket.

Also Internet Explorer may give the following error message:

The page cannot be displayed Additionally, you may have no IP address or no Automatic Private IP Addressing (APIPA) address, and you may be receiving IP packets but not sending them.

There are two easy ways to determine if Winsock2 is damaged:

From the XP source files, go to the Support / Tools directory

Winsock Test Method 1

Run netdiag /test:winsock

The end should say Winsock test ..... passed

Winsock Test Method 2

Run Msinfo32

Click on the + by Components

Click on the by Network

Click on Protocol

There should be 10 sections if the Winsock2 key is ok

MSAFD Tcpip [TCP/IP]

MSAFD Tcpip [UDP/IP]

RSVP UDP Service Provider

RSVP TCP Service Provider

MSAFD NetBIOS [\Device\NetBT_Tcpip...

MSAFD NetBIOS [\Device\NetBT_Tcpip...

MSAFD NetBIOS [\Device\NetBT_Tcpip...

MSAFD NetBIOS [\Device\NetBT_Tcpip...

MSAFD NetBIOS [\Device\NetBT_Tcpip...

MSAFD NetBIOS [\Device\NetBT_Tcpip...

If the names are anything different from those in this list, then likely Winsock2 is corrupted and needs to be repaired.

If you have any 3rd party software installed, the name MSAFD may be changed.

There should be no fewer than 10 sections.

To repair Winsock2

Run Regedit

Delete the following two registry keys:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock2

Restart the computer

Go to Network Connections

Right click and select Properties

Click on the Install button

Select Protocol

Click on the Add button

Click on the Have Disk button

Browse to the \Windows\inf directory

Click on the Open button

Click on the OK button

Highlight Internet Protocol (TCP/IP)

Click on the OK button

Security Researcher Threatened With Vulnerability Repair Bill

AppId is over the quota
mask.of.sanity writes "A security consultant who quietly tipped off an Australian superannuation fund about a web vulnerability that potentially put millions of customers at risk has been slapped with a legal threat demanding he allow the company access to his computer, and warned he may be forced to pay the cost of fixing the flaw. A legal document (PDF) sent from the company demanded that the researcher provide its technical staff with access to his computer. The company acknowledged the researcher's work was altruistic and thanked him for his efforts, but warned that the disclosure, which was not previously made public, may have breached Australian law. The researcher had run a batch file to access about 500 accounts, which was then handed to the company to demonstrate the direct object reference vulnerability."

Read more of this story at Slashdot.

View the original article here

So one of your friends, “not you of course”, has managed to nuke Internet Explorer and they are unsure how they did it. You’ve eliminated the possibility of viruses and adware, so this just leaves you and a broken IE. Before you begin to even consider running a repair install of the OS, let’s try to do a repair on IE instead.

THE REPAIR PROCESS

Start the Registry Editor by typing regedit from the Run box. Go to HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ Active Setup \ Installed Components \ {89820200-ECBD-11cf-8B85-00AA005B4383} and then right-click the “IsInstalled value.” Click Modify. From there, you will change the value from 1 to 0. All right, go ahead and close the editor and reinstall IE from this location. /http://www.microsoft.com/windows/ie/default.mspx

IF SOMETHING GOES WRONG

If messing with the registry and something goes horribly wrong, you can use “Last Known Good Configuration (F8 Safe Mode)” or a Restore Point to get back to where you were before, with your settings. Then you can try again, this time taking care to watch the portion of the registry you are changing. Most people who have troubles with this end up changing the wrong registry key.

Hope this tut helps some members.