Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Windows Sockets initialization failed: 5


  • Please log in to reply
20 replies to this topic

#1 Without_A_Monitor

Without_A_Monitor

  • Members
  • 339 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:teh bleepinverse
  • Local time:07:43 AM

Posted 06 April 2014 - 07:41 PM

I don't know if this is the right section for this thread. So, please redirect me if it isn't the right place. I recently discovered that when using netstat, there is info stating that "Windows Sockets initialization failed:5" "can not obtain ownership information." Can someone please help me with this issue and guide me to resolve it?



BC AdBot (Login to Remove)

 


#2 Without_A_Monitor

Without_A_Monitor
  • Topic Starter

  • Members
  • 339 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:teh bleepinverse
  • Local time:07:43 AM

Posted 15 April 2014 - 02:11 PM

Hey, I was just wondering if someone would be so kind as to help me with this issue. I have Windows Vista Home Premium 64-bit SP2. Sorry for not originally stating that.



#3 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,714 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:04:43 AM

Posted 15 April 2014 - 02:44 PM

Please download and install Windows Repair (All in one)
 
To open the program click on the Start orb.
 
Click on All Programs.
 
Click on Windows Repair (All in one), this may be listed as Tweaking.com.
 
If you are running Windows Vista, 7, or 8 right click on Windows Repair (All in one)  and then click on Run as administrator.
 
Notice:  You will need to disable your antivirus in order to run this program, for this reason you should run this while off line.
 
Go to Step 2 and click on the Do it button to allow CheckDisk to run. 
 
windowsrepairstep2-1_zps08aed02b.png
 
Go to Step 3 and click on the Do it button to run System File Check.
 
windowsrepairstep3-1_zps935b7603.png
 
Go to Step 4 and click on the Create button under System Restore.
 
windowsrepairstept4-1_zpseb336401.png
 
Go to Start Repairs and click on the Start button.
 
Important: Do not make any changes to the check marks.
 
For those running Windows 8 please note that  Reset Registry Permissions is not checked by design.
 
When the page below opens click on the Start button.
 
windowsrepairstartrepairs-1_zpsa179850d.
 
Please copy and paste the Windows Repair Log in your next post.  This log (_windows_repair_log.txt) is located in the following folder:
 
*  64-bit systems file path - C:\Program Files (x86)\Tweaking.com\Windows Repair (All in One)\Logs
 
*  32-bit systems file path - C:\Program Files\Tweaking.com\Windows Repair (All in One)\Logs
 
Copy the file path for your version of Windows (32-bit or 64-bit), click on the Start orb and paste it in the Search all programs and files box.
 
Click on Logs.
 
Click on _Windows_Repair_Logs.
 
Copy and paste this log in your next post. 

Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#4 Without_A_Monitor

Without_A_Monitor
  • Topic Starter

  • Members
  • 339 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:teh bleepinverse
  • Local time:07:43 AM

Posted 16 April 2014 - 02:35 PM

Thank you very much for your help and reply, dc3. I will most likely perform the procedure tonight or sometime tomorrow. Is it possible that attempting to use Windows Repair will cause any further damage to my laptop/vista?

 

I apologize for not posting the following information earlier. Is it possible that my laptop shows "windows sockets initialization failed: 5" because of Scorpion Saver with Adpeak and Level Quality Watcher? I was infected with the with those three problems in November (2013) and resolved the issue from receiving help on BleepingComputer in the "Am I Infected..." section. Is it possible that Adpeak damaged, corrupted or even hid something to cause "Windows Sockets initilization failed: 5" to occur?



#5 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,714 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:04:43 AM

Posted 16 April 2014 - 02:41 PM

The all in one repair will not harm you operating system or other data or programs.

 

As for a previous infection being responsible for the problems you are experiencing, that was a long time ago.  If you were to have problems related to the infection which was cleaned it should have been noticed well over a year ago.


Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#6 Without_A_Monitor

Without_A_Monitor
  • Topic Starter

  • Members
  • 339 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:teh bleepinverse
  • Local time:07:43 AM

Posted 16 April 2014 - 09:57 PM

I appreciate the verification on running the all-in-one repair, dc3.

 

While I understand and do not necessarily disagree with your statements about the infection and windows socket initialization problem, I only discovered that there "windows sockets initialization failed: 5" problem because I just started using netstat about two weeks ago from now. That was when I first noticed and realized that there was even an issue. So, it is possible (how ever unlikely) that the infection from long ago altered my windows sockets to some degree/effect without causing any glaring problems and/or without me noticing until the info presented itself such as in netstat?



#7 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,714 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:04:43 AM

Posted 17 April 2014 - 07:40 AM

Please scan your computer with ESET OnlineScan

  • Hold down Control and click on this link to open ESET OnlineScan in a new window.
  • Click the esetonlinebtn.png button.
  • For alternate browsers only: (Microsoft Internet Explorer users can skip these steps)
    • Click on esetsmartinstaller_enu.exe to download the ESET Smart Installer. Save it to your desktop.
    • Double click on the esetsmartinstaller_enu.png icon on your desktop.
  • Check "YES, I accept the Terms of Use."
  • Click the Start button.
  • Accept any security warnings from your browser.
  • Under scan settings, check "Scan Archives" and "Remove found threats"
  • Click Advanced settings and select the following:
    • Scan potentially unwanted applications
    • Scan for potentially unsafe applications
    • Enable Anti-Stealth technology
  • ESET will then download updates for itself, install itself, and begin scanning your computer. Please be patient as this can take some time.
  • When the scan completes, click List Threats
  • Click Export, and save the file to your desktop using a unique name, such as ESETScan. Include the contents of this report in your next reply.
  • Click the Back button.
  • Click the Finish button.

Please download Malwarebytes Anti-Malware.

 

 

mbam1_zps95cc812c.png
 
Click on Update Now, after Malwarebytes is updated click on Scan.
 
If this isn't the first time you have run this version, then you will see an image like the one below.  Click on Scan
 
mbam1_zps98e7fba9.png
 
You will be prompted to update Malwarebytes, to do so click on Update Now.
 
 mbam2_zps85f38f0c.png
 
3)  The scan will automatically run now.
 
mbamreplace_zps3ead4824.png
 
 
4)  When the scan is complete the results will be displayed.  Click on Quarantine All, then click on Apply Actions
 
mbam4_zps23e52ad4.png
 
 
5)  To complete any actions taken you will be asked if you want to restart your computer, click on Yes
 
 mbam4_zps490948cc.png
 
6)  Please post the Malwarebytes log.
 
To find your Malwarebytes log,download mbam-check.exe from here and save it to your desktop.
 
To open the log double click on mbam-check.exe on your desktop.  When the log opens, copy it and paste this in your next post.

 
 


Edited by dc3, 17 April 2014 - 07:45 AM.

Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#8 Without_A_Monitor

Without_A_Monitor
  • Topic Starter

  • Members
  • 339 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:teh bleepinverse
  • Local time:07:43 AM

Posted 17 April 2014 - 04:53 PM

Thank you once again for your help, dc3. I'm sorry that I'm just posting this now. I was busy for most of today.

I have run both ESET online scanner and MBAM recently, but neither of them found any issues besides ESET finding bundled toolbars.

 

 

 

Here is the log from ESET online scanner from March 26th, 2014:

 

 

C:\Users\El Diego\Downloads\rcsetup147.exe    Win32/Bundled.Toolbar.Google.D potentially unsafe application    deleted - quarantined
C:\Users\El Diego\Downloads\spsetup125.exe    Win32/Bundled.Toolbar.Google.D potentially unsafe application    deleted - quarantined
 

 

 

 

 

 

Here is the log from MBAM from March 26th, 2014:

 

 

 

 

Malwarebytes Anti-Malware
www.malwarebytes.org

Scan Date: 3/26/2014
Scan Time: 11:06:55 PM
Logfile: mbam log (3.26.14).txt
Administrator: Yes

Version: 2.00.0.1000
Malware Database: v2014.03.26.07
Rootkit Database: v2014.03.25.01
License: Trial
Malware Protection: Enabled
Malicious Website Protection: Enabled
Chameleon: Disabled

OS: Windows Vista Service Pack 2
CPU: x64
File System: NTFS
User: El Diego

Scan Type: Threat Scan
Result: Completed
Objects Scanned: 246402
Time Elapsed: 24 min, 41 sec

Memory: Enabled
Startup: Enabled
Filesystem: Enabled
Archives: Enabled
Rootkits: Enabled
Shuriken: Enabled
PUP: Warn
PUM: Enabled

Processes: 0
(No malicious items detected)

Modules: 0
(No malicious items detected)

Registry Keys: 0
(No malicious items detected)

Registry Values: 0
(No malicious items detected)

Registry Data: 0
(No malicious items detected)

Folders: 0
(No malicious items detected)

Files: 1
PUP.Optional.SavingsBull.A, C:\Users\El Diego\AppData\Roaming\Mozilla\Firefox\Profiles\z7ozoluc.default\prefs.js, Good: (), Bad: (user_pref("30563486-6F5F-3700-86C7-0AEBF3E9C73E.home", "http://d.4jsdw9ta.com/xuiow/");), Replaced,[bf1b2add9dded363d35bf33e9e669c64]

Physical Sectors: 0
(No malicious items detected)


(end)

 

 

 

 

 

 

 

 

 

 

 

 

 

Should I still proceed with the windows all-in-one repair like you initially posted?



#9 Without_A_Monitor

Without_A_Monitor
  • Topic Starter

  • Members
  • 339 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:teh bleepinverse
  • Local time:07:43 AM

Posted 23 April 2014 - 02:15 PM

Hey, dc3. I realize that you are probably extremely busy in general and with helping other people on here. Moreover, you're also being kind enough and taking the time to help me. So, please respond when you can. I am just seeking to know if I should install and run the Windows all-in-one- repair like you first stated. Please let me know. Much obliged.



#10 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,714 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:04:43 AM

Posted 23 April 2014 - 03:05 PM

Yes, please run the all-in-one repair.


Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#11 Without_A_Monitor

Without_A_Monitor
  • Topic Starter

  • Members
  • 339 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:teh bleepinverse
  • Local time:07:43 AM

Posted 23 April 2014 - 05:34 PM

Thanks for the confirmation and reply. I followed the Windows all-in-one-repair as you listed.

 

While I cannot claim to know this, I think that the steps and instructions that you provided were of an older version of the tool. So, some things were slightly different than described, but I attempted to follow what you posted and advised. For example, the actual log was in a folder titled "4.23.2014_5.39.28-pm" inside of the "logs" folder, even though there was a "_windows_repair_log" file inside the "logs" folder. Additionally, there are other text documents inside the "4.23.2014_5.39.28-pm" folder that specifically  address each issue/fix from the repair. With that said, I think this is the log that you requested, dc3. Please let me know what else I should do. Thank you very much once again.

 

 

 

 

 

 

 

 

 

 

 

System Variables
--------------------------------------------------------------------------------
OS: Windows Vista ™ Home Premium
OS Architecture: 64-bit
OS Version: 6.0.6002
OS Service Pack: Service Pack 2
Computer Name: EL_DIEGO
Windows Drive: C:\
Windows Path: C:\Windows
Current Profile:
Current Profile SID: S-1-5-21-1786916353-3864107569-3064167919-1000
Current Profile Classes: S-1-5-21-1786916353-3864107569-3064167919-1000_Classes
Profiles Location: C:\Users
Profiles Location 2: C:\Windows\ServiceProfiles
Local Settings AppData: C:\Users\El Diego\AppData\Local
--------------------------------------------------------------------------------

System Information
--------------------------------------------------------------------------------
System Up Time: 0 Days 00:04:08

Process Count: 79
Commit Total: 1.55 GB
Commit Limit: 8.10 GB
Commit Peak: 1.75 GB
Handle Count: 17980
Kernel Total: 272.63 MB
Kernel Paged: 220.11 MB
Kernel Non Paged: 52.52 MB
System Cache: 906.40 MB
Thread Count: 886
--------------------------------------------------------------------------------

Memory Before Cleaning with CleanMem
--------------------------------------------------------------------------------
Memory Total: 3.97 GB
Memory Used: 1.32 GB(33.3698%)
Memory Avail.: 2.64 GB
--------------------------------------------------------------------------------

Cleaning Memory Before Starting Repairs...

Memory After Cleaning with CleanMem
--------------------------------------------------------------------------------
Memory Total: 3.97 GB
Memory Used: 1.16 GB(29.1822%)
Memory Avail.: 2.81 GB
--------------------------------------------------------------------------------

Starting Repairs...
   Start (4/23/2014 5:39:30 PM)

01 - Reset Registry Permissions 01/03
   HKEY_CURRENT_USER & Sub Keys
   Start (4/23/2014 5:39:32 PM)
   Running Repair Under Current User Account
   Done (4/23/2014 5:39:43 PM)

01 - Reset Registry Permissions 02/03
   HKEY_LOCAL_MACHINE & Sub Keys
   Start (4/23/2014 5:39:43 PM)
   Running Repair Under System Account
   Done (4/23/2014 5:43:14 PM)

01 - Reset Registry Permissions 03/03
   HKEY_CLASSES_ROOT & Sub Keys
   Start (4/23/2014 5:43:14 PM)
   Running Repair Under System Account
   Done (4/23/2014 5:44:32 PM)

03 - Register System Files
   Start (4/23/2014 5:44:32 PM)
   Running Repair Under Current User Account
   Running Repair Under System Account
   Done (4/23/2014 5:45:45 PM)

04 - Repair WMI
   Start (4/23/2014 5:45:45 PM)

   Starting Security Center So We Can Export The Security Info.

   Exporting Antivirus Info...
   ESET NOD32 Antivirus 7.0 Exported.

   Exporting AntiSpyware Info...
   Windows Defender Exported.
   ESET NOD32 Antivirus 7.0 Exported.

   Exporting 3rd Party Firewall Info...
   No Firewall Products Reported.

   Running Repair Under Current User Account
   Done (4/23/2014 5:49:49 PM)

05 - Repair Windows Firewall
   Start (4/23/2014 5:49:49 PM)
   Running Repair Under Current User Account
   Running Repair Under System Account
   Done (4/23/2014 5:50:37 PM)

06 - Repair Internet Explorer
   Start (4/23/2014 5:50:37 PM)
   Running Repair Under Current User Account
   Running Repair Under System Account
   Done (4/23/2014 5:51:47 PM)

07 - Repair MDAC/MS Jet
   Start (4/23/2014 5:51:47 PM)
   Running Repair Under Current User Account
   Running Repair Under System Account
   Done (4/23/2014 5:52:17 PM)

08 - Repair Hosts File
   Start (4/23/2014 5:52:17 PM)
   Running Repair Under System Account
   Done (4/23/2014 5:52:19 PM)

09 - Remove Policies Set By Infections
   Start (4/23/2014 5:52:19 PM)
   Running Repair Under Current User Account
   Running Repair Under System Account
   Done (4/23/2014 5:52:24 PM)

10 - Repair Start Menu Icons Removed By Infections
   Start (4/23/2014 5:52:24 PM)
   Running Repair Under System Account
   Done (4/23/2014 5:52:26 PM)

11 - Repair Icons
   Start (4/23/2014 5:52:26 PM)
   Running Repair Under Current User Account
   Done (4/23/2014 5:52:29 PM)

12 - Repair Winsock & DNS Cache
   Start (4/23/2014 5:52:29 PM)
   Running Repair Under Current User Account
   Running Repair Under System Account
   Done (4/23/2014 5:52:45 PM)

14 - Repair Proxy Settings
   Start (4/23/2014 5:52:45 PM)
   Running Repair Under Current User Account
   Running Repair Under System Account
   Done (4/23/2014 5:52:49 PM)

16 - Repair Windows Updates
   Start (4/23/2014 5:52:49 PM)
   Running Repair Under Current User Account
   Running Repair Under System Account
   Done (4/23/2014 5:53:22 PM)

17 - Repair CD/DVD Missing/Not Working
   Start (4/23/2014 5:53:22 PM)
   iTunes was found, adding UpperFilters for iTunes Reg Key
   UpperFilters added?: True
   Done (4/23/2014 5:53:22 PM)

18 - Repair Volume Shadow Copy Service
   Start (4/23/2014 5:53:22 PM)
   Running Repair Under Current User Account
   Running Repair Under System Account
   Done (4/23/2014 5:53:39 PM)

20 - Repair MSI (Windows Installer)
   Start (4/23/2014 5:53:39 PM)
   Running Repair Under Current User Account
   Running Repair Under System Account
   Done (4/23/2014 5:53:52 PM)

22.01 - Repair bat Association
   Start (4/23/2014 5:53:52 PM)
   Running Repair Under Current User Account
   Running Repair Under System Account
   Done (4/23/2014 5:53:57 PM)

22.02 - Repair cmd Association
   Start (4/23/2014 5:53:57 PM)
   Running Repair Under Current User Account
   Running Repair Under System Account
   Done (4/23/2014 5:54:02 PM)

22.03 - Repair com Association
   Start (4/23/2014 5:54:02 PM)
   Running Repair Under Current User Account
   Running Repair Under System Account
   Done (4/23/2014 5:54:06 PM)

22.04 - Repair Directory Association
   Start (4/23/2014 5:54:06 PM)
   Running Repair Under Current User Account
   Running Repair Under System Account
   Done (4/23/2014 5:54:11 PM)

22.05 - Repair Drive Association
   Start (4/23/2014 5:54:11 PM)
   Running Repair Under Current User Account
   Running Repair Under System Account
   Done (4/23/2014 5:54:16 PM)

22.06 - Repair exe Association
   Start (4/23/2014 5:54:16 PM)
   Running Repair Under Current User Account
   Running Repair Under System Account
   Done (4/23/2014 5:54:21 PM)

22.07 - Repair Folder Association
   Start (4/23/2014 5:54:21 PM)
   Running Repair Under Current User Account
   Running Repair Under System Account
   Done (4/23/2014 5:54:25 PM)

22.08 - Repair inf Association
   Start (4/23/2014 5:54:25 PM)
   Running Repair Under Current User Account
   Running Repair Under System Account
   Done (4/23/2014 5:54:30 PM)

22.09 - Repair lnk (Shortcuts) Association
   Start (4/23/2014 5:54:30 PM)
   Running Repair Under Current User Account
   Running Repair Under System Account
   Done (4/23/2014 5:54:35 PM)

22.10 - Repair msc Association
   Start (4/23/2014 5:54:35 PM)
   Running Repair Under Current User Account
   Running Repair Under System Account
   Done (4/23/2014 5:54:40 PM)

22.11 - Repair reg Association
   Start (4/23/2014 5:54:40 PM)
   Running Repair Under Current User Account
   Running Repair Under System Account
   Done (4/23/2014 5:54:44 PM)

22.12 - Repair scr Association
   Start (4/23/2014 5:54:44 PM)
   Running Repair Under Current User Account
   Running Repair Under System Account
   Done (4/23/2014 5:54:49 PM)

23 - Repair Windows Safe Mode
   Start (4/23/2014 5:54:49 PM)
   Running Repair Under Current User Account
   Running Repair Under System Account
   Done (4/23/2014 5:54:54 PM)

24 - Repair Print Spooler
   Start (4/23/2014 5:54:54 PM)
   Running Repair Under Current User Account
   Running Repair Under System Account
   Done (4/23/2014 5:55:11 PM)

25 - Restore Important Windows Services
   Start (4/23/2014 5:55:11 PM)
   Running Repair Under Current User Account
   Running Repair Under System Account
   Done (4/23/2014 5:55:40 PM)

26 - Set Windows Services To Default Startup
   Start (4/23/2014 5:55:40 PM)
   Running Repair Under Current User Account
   Running Repair Under System Account
   Done (4/23/2014 5:55:55 PM)

   Skipping Repair.
   Repair is for Windows v6.2 (Windows 8 & Newer) or higher.
   Current version: 6.0

   Skipping Repair.
   Repair is for Windows v6.2 (Windows 8 & Newer) or higher.
   Current version: 6.0

   Skipping Repair.
   Repair is for Windows v6.2 (Windows 8 & Newer) or higher.
   Current version: 6.0

Cleaning up empty logs...

All Selected Repairs Done.
   Done (4/23/2014 5:55:55 PM)
   Total Repair Time: 00:16:27


...YOU MUST RESTART YOUR SYSTEM...
   Running Repair Under Current User Account
 



#12 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,714 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:04:43 AM

Posted 24 April 2014 - 09:27 AM

My apologies for forgetting to include the instructions, yesterday was just one of those days where I was constantly being interrupted.

 

For future reference, here are the instructions.

 

Windows Repair (All in one)
 
Please download and install Windows Repair (All in one)
 
To open the program click on the Start orb.
 
Click on All Programs.
 
Click on Windows Repair (All in one), this may be listed as Tweaking.com.
 
If you are running Windows Vista, 7, or 8 right click on Windows Repair (All in one)  and then click on Run as administrator.
 
Notice:  You will need to disable your antivirus in order to run this program, for this reason you should run this while off line.
 
Go to Step 2 and click on the Do it button to allow CheckDisk to run. 
 
windowsrepairstep2-1_zps08aed02b.png
 
Go to Step 3 and click on the Do it button to run System File Check.
 
windowsrepairstep3-1_zps935b7603.png
 
Go to Step 4 and click on the Create button under System Restore.
 
windowsrepairstept4-1_zpseb336401.png
 
Go to Start Repairs and click on the Start button.
 
Important: Do not make any changes to the check marks.
 
For those running Windows 8 please note that  Reset Registry Permissions is not checked by design.
 
When the page below opens click on the Start button.
 
windowsrepairstartrepairs-1_zpsa179850d.
 
Please copy and paste the Windows Repair Log in your next post.  This log (_windows_repair_log.txt) is located in the following folder:
 
*  64-bit systems file path - C:\Program Files (x86)\Tweaking.com\Windows Repair (All in One)\Logs
 
*  32-bit systems file path - C:\Program Files\Tweaking.com\Windows Repair (All in One)\Logs
 
Copy the file path for your version of Windows (32-bit or 64-bit), click on the Start orb and paste it in the Search all programs and files box.
 
Click on Logs.
 
Click on _Windows_Repair_Logs.
 
Copy and paste this log in your next post. 

 

 

Is the computer running better?


Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#13 Without_A_Monitor

Without_A_Monitor
  • Topic Starter

  • Members
  • 339 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:teh bleepinverse
  • Local time:07:43 AM

Posted 24 April 2014 - 02:01 PM

Oh, there is no need to apologize. You did list the instructions in your first post. I evidently failed to explicitly express my point in my last post. So, I'm sorry about that. In my last reply, I meant that the current version of the Windows all-in-one repair tool, v2.6.2, is later version than the version that is shown and displayed in your posts, v1.9.13. Moreover, there were some minor changes and differences in v2.6.2 compared to v1.9.13 such as the one that I described with the other folders and files. Haha, I hope that I am not belaboring how the current version differs from the old one. I just thought that I'd mention it to you because I attempted to follow your instructions, despite some differences in the tool (like the folder for example.)

 

My laptop indeed seems to be running better. I will say that I used netstat to check on the "Windows Sockets initialization failed: 5" issue after the Windows all-in-one repair tool found and fixed errors on my laptop. Unfortunately, netstat -anvbo still shows "Windows Sockets initialization failed: 5." I really appreciate your help and advice. Is there anything else that you recommend or negative?



#14 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,714 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:04:43 AM

Posted 24 April 2014 - 03:22 PM

This is a new version, this is the first I've seen of it.  It looks like there has been one additional step added.  Time to update my tutorial.  Thanks for bringing this to my attention.

 

Click on the Start orb, then type in cmd,  cmd will above the search box under Apps, right click and choose Run as administrator.  This will open the Elevated Command Prompt, it will look similar to the image below.

 

elevatedcommandpromptw7_zpseba8c499.png

 

In the Command Prompt type in  each command one at a time pressing Enter after each.

 

netsh winsock reset catalog

 

netsh int ip reset reset.log hit


Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#15 Without_A_Monitor

Without_A_Monitor
  • Topic Starter

  • Members
  • 339 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:teh bleepinverse
  • Local time:07:43 AM

Posted 24 April 2014 - 04:31 PM

Don't mention it. It is I, who must thank you for your continued support. I did as you stated with the two commands and restarted my computer as the command prompt mandated; however, after I typed "netsh int ip reset reset.log hit" as the second command, there was a response in the command prompt that stated the following message:

 

reseting echo request, failed.
access is denied

reseting interface, ok!
a reboot is required to complete this action

 

 

 

 

 

 

 

I am guessing that the aforesaid message is not the regular message that was supposed to appear after typing in the command, netsh int ip reset rest.log hit?

 

The "Windows Sockets initialization failed: 5" is still present when accessing the command, netstat -anvbo.

 

 






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users