Willsroom

Monday, March 17, 2008

missing connect.dll in Windows Vista

Missing Connect.dll in Windows Vista

If you receive a message referring to a missing DLL C:\Windows\system32\connect.dll, this is part of the networking files required for Vista to connect to the internet. This error refers to part of the TCP/IP stack either being corrupt or missing.

This can happen when uninstalling Internet Security software or, in my case, when uninstalling the bundled Dell ISP Installers for NetZero, Earthlink, and AOL. I am not certain which one caused the problem, but the results were no connectivity with an error message stating:

Component GUID:{7071ECA3-663B-4BC1-A1FA-B97F3B917C55}
Component file: [C:\Windows\system32\connect.dll]
Error: (0x8007277B) .

Additional Info:
Failed to detect Internet connectivity

Not being overly familiar with Vista, I found this information on the “missing file.”

connect.dll is a part of Windows Vista.

Default location: %WinDir%\System32\connect.dll

Useful information about: connect.dll

Description: Get Connected Wizards

Version: 6.0.6000.16386 (vista_rtm.061101-2205)

Size: 1645568 (1607K)

MD5: 445269304D063FC940695B37C43BC0E3

Further research revealed this to be a common problem in Vista and that it can also be caused if Vista drivers are updated. Some Dell driver software can be old and may need to be updated. Unfortunately, Dell may not always have the best match for driver software and it may become necessary to experiment with drivers until a workable compromise is found.

In my case, I was able to find this information after updating the driver proved to be unsuccessful.

TCP/IP stack repair options for use with Windows Vista.

1. Start, Programs\Accessories and right click on Command Prompt, select "Run as Administrator" to open a command prompt.

2. Reset WINSOCK entries to installation defaults: netsh winsock reset catalog

3. Reset IPv4 TCP/IP stack to installation defaults. netsh int ipv4 reset reset.log

4. Reset IPv6 TCP/IP stack to installation defaults. netsh int ipv6 reset reset.log

5. Reboot the machine.

Anti Virus and Firewall Software

In my case, this resolved the problem. However, there is apparently a few other cases that will generate a generic error message that is similar. In the few cases I had found, the users had installed a new Anti Virus or Firewall product and the software prevented the network devices from getting an IP. This was somewhat related to my problem because I had remove Norton Internet Security and installed Trend Micro Internet Security.

It is important to note that when you are done uninstalling a Security Program, make sure to go back and delete the folder of the installation. These can be found in Program Files, sometimes under the Windows folder. But get rid of them just in case something remains. Also make sure to uninstall any of the additional Update Programs.

Windows Update

Some additional reports came regarding this issue coming after a Windows Update. I would think this might be an issue when changes are made to driver or security settings. I did not have much info on this, but I am pretty sure this was not the case for my problem.

Bottom Line

So it appears this issue can be cause by several different problems, with many varied fixes. God Bless Windows Vista (and those who use her)! I compiled the list of fixes from simple to complex. Give these a try:

1. Uninstall the network/modem driver from Device Manager – just select the items and hit Delete. Reboot.

2. TCP Repair Stack. Reboot.

3. Uninstall any recently installed Security Software on the possibility the firewall may be blocking. Then reinstall and be sure to properly configure each step of the Installation. If you have questions, contact the software manufacturer.

4. Try Window’s Update Uninstall tool. This is said to allow you to remove recently installed updates.

5. When all else fails, either do a System Recovery or a Repair Install of Windows.

If these don’t work for you, keep in mind that the computer manufacturer may simply tell you “this is an OS problem” meaning you will need to contact Microsoft for additional help. You can get Microsoft’s support at 1-800-Microsoft, but don’t be surprised if you get Apu on the other end to help you.

Labels: , ,

Sunday, March 02, 2008

March 2008!

This week has been pretty busy both at home and at work. This coupled with a nasty Sinus Infection has made the week interesting to say the least. Well, to say the least, I could just say "Yeah" but I wanted to say more than that, but not fill up an entire paragraph, which is exactly what I'm doing now. So, to say not quite the least (but not as much as, say an entire paragraph, which this would be fast approaching number two, thank you very much), I have been very busy recuperatin' and edumacatin' myself.

Paragraph 2:
This last week, William turned 8, though nobody has received any kind of notification from his mother, so I guess he didn't have a party and it went by quietly. Happy birthday son! My last letter to him was "returned to sender," so I don't know whether or not I would be able to get a card to him. Apparently, the Christmas Card got to him, but I don't know either way.

Nothing else really happened during that week, apart from my yearly performance review at work, which is what is used to gauge how I did within the last year to be used, somewhat in review for what kind of raise I get.

Third time's a charm
Sunday, (Feb 24), I played at my first airsoft game of the year. I was really not in any condition to be tromping around in the soggy snow, but I went out and gave it hell. I slipped and fell several times and was soaked and cold pretty much the rest of the day. I was able to break in my new Tigerstripe BDUs and I did get a forboding picture of me with a spring shotgun.

Monday, I jumped into the work week by ordering three additional books and begining the study programs used to practice for the various Professional Certifications I will need to help me along with my next job. I did discuss my plans with Tom about finishing out this year, obtaining my various certifications, and then looking at what else was out there. I'll leave most of the discussion out of this as it doesn't exactly have any place on here, but Tom has been supportive and understanding about training with the tech department and it has been good working with him.

The rest of the week was accentuated with excessing hacking and wheezing as the "mucus that binds us," attempted to escape my body in conveniently spaced packets that happened to appear in the back of my throat at the most inopportune of moments. I found the experience to be liberating in that I was now a few ounces free of the darkened yellow slime, but that the accompanied gagging and retching were found to be of most savagely ungentlemanly of me. I would hastily retreat to the somber confines of the men's room to expel certain disdainful materials in a half ass attempt to restore my proper respiratory function (that's amusingly mispronounced "ress-per-rate-or-ee" in an attempt to bring some sunshine into an otherwise bleak existance of coughing up various materials that somewhat resemble a finely processed guacamole, and feel like mounds of epoxy.)

The week was concluded with a 2 minute doctor's appointment that immediately folled an excessive wait of an hour and fifteen minutes, despite the fact there were only about 6 other people in the office. I am on antibiotics to try to heal up for Kris' Shoulder Surgery this week.

Pete Roller's Book
Pete is one of our Satellite Customers who is has been one of my favorite people to help out. He had been having particular troubles with his computer because of its age. He is always open to advice on how to improve things and this week had decided to by a new computer. SInce he has satellite internet, he cannot get a Windows Vista machine as SKysay does not have a stable or reliable driver for Vista.

Pete had mentioned before that he was an author and that he was working on a sequel to his previous book. He then explained about his book and I promised to give it a look. He's a nice guy, and the description of his book seemed quite interesting. Pete offereed to sell me a copy and autograph it, which to me, is just awesome.

The book is called The Crook'd Staff and is quite an excellent story. I was surprised at how easy a book it was to read and have found it to be a real joy, reading a few chapters at a time. I'm almost finished with the book, and I could easily see myself reading the sequel he is working on.

I would love to give you guys a review on the book, but I would like to wait until I'm finished so that I can see how the rest of the story ends.

Week in review:
Not much to say other than its been a somewhat miserable week with the weather teasing us with warmed days and then colder. I made a small batch of salsa to brung out the rest of this infection and can say it is working all too well. Here's hopin' that next week will be better.