Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Possible virus, Diagnostic Policy Service is nonfunctional, Unable to


  • Please log in to reply

#46
SleepyDude

SleepyDude

    Trusted Helper

  • Malware Removal
  • 4,394 posts

Hi,

I searched for ncpa.cpl and this is the window that popped up; should the Marvell Yukon icon be there or do I need to click on something else?



It should but it seems the device isn't correctly installed!

Please post the image showing the properties of the Wireless Network Connection.
  • 0

Advertisements


#47
Kristin51505

Kristin51505

    Member

  • Topic Starter
  • Member
  • PipPip
  • 70 posts
Ok, here you go!

WNC.JPG
  • 0

#48
SleepyDude

SleepyDude

    Trusted Helper

  • Malware Removal
  • 4,394 posts

Ok, here you go!

WNC.JPG


Thanks. It seems normal no entry's related to something removed.

- Open the Device Manager like you did before (post #38) expand the Network Adapters, right click the Marvell Yukon 88E8040 PCI-E Fast Ethernet Controller device and select Uninstall.
- Restart the computer, give some time to windows reinstall the driver for the network device
- Restart the computer again
- Reopen the Device Manager and tell me if the yellow "!" continues on the Network devices.
  • 0

#49
Kristin51505

Kristin51505

    Member

  • Topic Starter
  • Member
  • PipPip
  • 70 posts
Hi SleepyDude,

I did what you asked and the "!" signs are still next to all the Network devices except for the Dell Wireless 1397 WLAN Mini-Card #2.
  • 0

#50
SleepyDude

SleepyDude

    Trusted Helper

  • Malware Removal
  • 4,394 posts
Hi,

I want you to run a OTL fix again...

Step 1 - Run OTL Fix

!!! WARNING !!! The following fix is only relevant for this system and no other, running the script on another computer will not work and may cause problems...

  • Right click on the icon Posted Image and choose Run as Administrator to execute the tool. Make sure all other windows are closed.
    Do not change any other settings unless otherwise told to do so.
  • Under the Posted Image box at the bottom, paste in the following:
    :Commands
    [CreateRestorePoint]
    
    :Files
    netsh winsock reset all /c
    netsh int 6to4 reset all /c
    netsh int ipv4 reset all /c
    netsh int ipv6 reset all /c
    netsh int httpstunnel reset all /c
    netsh int isatap reset all /c
    netsh int portproxy reset all /c
    netsh int tcp reset all /c
    netsh int teredo reset all /c
    sc start RpcSs /c
    sc start vss /c
    
    :Commands
    [EmptyTemp]
    [Reboot]
    
  • click the Posted Image button at the top. Let the program run uninterrupted.
  • click OK
Notes:
  • When OTL executes the Fix it can shutdown all running processes and you may lose the Desktop and icons, but they will return on reboot
  • OTL may ask to reboot the machine. Please accept right away.
  • The report should appear in Notepad after the reboot. Copy & Paste that report in your next reply and not as attachment.
  • The OTL fix log will be saved in the following location: C:\_OTL\MovedFiles\mmddyyyy_hhmmss.log - where mmddyyy _hhmmss is the date and time when the fix run.

Step 2 - Minitoolbox
  • Connect the computer with the Ehternet cable for now
  • Close all the programs and run MiniToolBox
    Posted Image
  • Check the following options:
    • List IP Configuration
    • List Winsock Entries
    • List last 10 Event Viewer log
    • List Devices: Only Problems
  • Click on Go.
  • Post the resulting log in your next reply.


Things I would like to see in your next reply:
  • The OTL Fix log
  • The MiniToolBox log Result.txt

  • 0

#51
Kristin51505

Kristin51505

    Member

  • Topic Starter
  • Member
  • PipPip
  • 70 posts
Hi,

Here are the new logs:

All processes killed
========== COMMANDS ==========
Restore point Set: OTL Restore Point
========== FILES ==========
< netsh winsock reset all /c >
C:\Users\Kristin\Desktop\cmd.bat deleted successfully.
C:\Users\Kristin\Desktop\cmd.txt deleted successfully.
< netsh int 6to4 reset all /c >
C:\Users\Kristin\Desktop\cmd.bat deleted successfully.
C:\Users\Kristin\Desktop\cmd.txt deleted successfully.
< netsh int ipv4 reset all /c >
C:\Users\Kristin\Desktop\cmd.bat deleted successfully.
C:\Users\Kristin\Desktop\cmd.txt deleted successfully.
< netsh int ipv6 reset all /c >
C:\Users\Kristin\Desktop\cmd.bat deleted successfully.
C:\Users\Kristin\Desktop\cmd.txt deleted successfully.
< netsh int httpstunnel reset all /c >
C:\Users\Kristin\Desktop\cmd.bat deleted successfully.
C:\Users\Kristin\Desktop\cmd.txt deleted successfully.
< netsh int isatap reset all /c >
C:\Users\Kristin\Desktop\cmd.bat deleted successfully.
C:\Users\Kristin\Desktop\cmd.txt deleted successfully.
< netsh int portproxy reset all /c >
C:\Users\Kristin\Desktop\cmd.bat deleted successfully.
C:\Users\Kristin\Desktop\cmd.txt deleted successfully.
< netsh int tcp reset all /c >
C:\Users\Kristin\Desktop\cmd.bat deleted successfully.
C:\Users\Kristin\Desktop\cmd.txt deleted successfully.
< netsh int teredo reset all /c >
C:\Users\Kristin\Desktop\cmd.bat deleted successfully.
C:\Users\Kristin\Desktop\cmd.txt deleted successfully.
< sc start RpcSs /c >
C:\Users\Kristin\Desktop\cmd.bat deleted successfully.
C:\Users\Kristin\Desktop\cmd.txt deleted successfully.
< sc start vss /c >
C:\Users\Kristin\Desktop\cmd.bat deleted successfully.
C:\Users\Kristin\Desktop\cmd.txt deleted successfully.
========== COMMANDS ==========

[EMPTYTEMP]

User: All Users

User: AppData

User: Default
->Temp folder emptied: 0 bytes
->Temporary Internet Files folder emptied: 0 bytes
->Flash cache emptied: 0 bytes

User: Default User
->Temp folder emptied: 0 bytes
->Temporary Internet Files folder emptied: 0 bytes
->Flash cache emptied: 0 bytes

User: Kristin
->Temp folder emptied: 81703536 bytes
->Temporary Internet Files folder emptied: 33170 bytes
->Java cache emptied: 0 bytes
->FireFox cache emptied: 0 bytes
->Flash cache emptied: 0 bytes

User: Public

%systemdrive% .tmp files removed: 0 bytes
%systemroot% .tmp files removed: 0 bytes
%systemroot%\System32 .tmp files removed: 0 bytes
%systemroot%\System32 (64bit) .tmp files removed: 0 bytes
%systemroot%\System32\drivers .tmp files removed: 0 bytes
Windows Temp folder emptied: 34549641 bytes
%systemroot%\sysnative\config\systemprofile\AppData\Local\Microsoft\Windows\Temporary Internet Files folder emptied: 0 bytes
RecycleBin emptied: 0 bytes

Total Files Cleaned = 111.00 mb


OTL by OldTimer - Version 3.2.69.0 log created on 02252014_153607

Files\Folders moved on Reboot...
File move failed. C:\Windows\temp\TmpFile1 scheduled to be moved on reboot.

PendingFileRenameOperations files...

Registry entries deleted on Reboot...


MiniToolBox by Farbar Version: 23-01-2014
Ran by Kristin (administrator) on 25-02-2014 at 15:56:03
Running from "F:\"
Microsoft® Windows Vista™ Home Premium Service Pack 2 (X64)
Boot Mode: Normal
***************************************************************************
========================= IP Configuration: ================================

Marvell Yukon 88E8040 PCI-E Fast Ethernet Controller = Local Area Connection 2 (Connected)
Dell Wireless 1397 WLAN Mini-Card = Wireless Network Connection (Media disconnected)
========================= Winsock entries =====================================

Catalog5 01 C:\Windows\SysWOW64\NLAapi.dll [48128] (Microsoft Corporation)
Catalog5 02 C:\Windows\SysWOW64\napinsp.dll [50176] (Microsoft Corporation)
Catalog5 03 C:\Windows\SysWOW64\pnrpnsp.dll [62464] (Microsoft Corporation)
Catalog5 04 C:\Windows\SysWOW64\pnrpnsp.dll [62464] (Microsoft Corporation)
Catalog5 05 C:\Windows\SysWOW64\mswsock.dll [223232] (Microsoft Corporation)
Catalog5 06 C:\Windows\SysWOW64\winrnr.dll [19968] (Microsoft Corporation)
Catalog9 01 C:\Windows\SysWOW64\mswsock.dll [223232] (Microsoft Corporation)
Catalog9 02 C:\Windows\SysWOW64\mswsock.dll [223232] (Microsoft Corporation)
Catalog9 03 C:\Windows\SysWOW64\mswsock.dll [223232] (Microsoft Corporation)
Catalog9 04 C:\Windows\SysWOW64\mswsock.dll [223232] (Microsoft Corporation)
Catalog9 05 C:\Windows\SysWOW64\mswsock.dll [223232] (Microsoft Corporation)
Catalog9 06 C:\Windows\SysWOW64\mswsock.dll [223232] (Microsoft Corporation)
Catalog9 07 C:\Windows\SysWOW64\mswsock.dll [223232] (Microsoft Corporation)
Catalog9 08 C:\Windows\SysWOW64\mswsock.dll [223232] (Microsoft Corporation)
Catalog9 09 C:\Windows\SysWOW64\mswsock.dll [223232] (Microsoft Corporation)
Catalog9 10 C:\Windows\SysWOW64\mswsock.dll [223232] (Microsoft Corporation)
x64-Catalog5 01 C:\Windows\System32\NLAapi.dll [61440] (Microsoft Corporation)
x64-Catalog5 02 C:\Windows\System32\napinsp.dll [62976] (Microsoft Corporation)
x64-Catalog5 03 C:\Windows\System32\pnrpnsp.dll [78848] (Microsoft Corporation)
x64-Catalog5 04 C:\Windows\System32\pnrpnsp.dll [78848] (Microsoft Corporation)
x64-Catalog5 05 C:\Windows\System32\mswsock.dll [304128] (Microsoft Corporation)
x64-Catalog5 06 C:\Windows\System32\winrnr.dll [27648] (Microsoft Corporation)
x64-Catalog5 07 C:\Program Files\Bonjour\mdnsNSP.dll [193024] (Apple Inc.)
x64-Catalog9 01 C:\Windows\System32\mswsock.dll [304128] (Microsoft Corporation)
x64-Catalog9 02 C:\Windows\System32\mswsock.dll [304128] (Microsoft Corporation)
x64-Catalog9 03 C:\Windows\System32\mswsock.dll [304128] (Microsoft Corporation)
x64-Catalog9 04 C:\Windows\System32\mswsock.dll [304128] (Microsoft Corporation)
x64-Catalog9 05 C:\Windows\System32\mswsock.dll [304128] (Microsoft Corporation)
x64-Catalog9 06 C:\Windows\System32\mswsock.dll [304128] (Microsoft Corporation)
x64-Catalog9 07 C:\Windows\System32\mswsock.dll [304128] (Microsoft Corporation)
x64-Catalog9 08 C:\Windows\System32\mswsock.dll [304128] (Microsoft Corporation)
x64-Catalog9 09 C:\Windows\System32\mswsock.dll [304128] (Microsoft Corporation)
x64-Catalog9 10 C:\Windows\System32\mswsock.dll [304128] (Microsoft Corporation)

========================= Event log errors: ===============================

Application errors:
==================
Error: (02/25/2014 03:55:21 PM) (Source: Microsoft-Windows-CAPI2) (User: )
Description: -583

Error: (02/25/2014 03:55:21 PM) (Source: Microsoft-Windows-CAPI2) (User: )
Description: -583

Error: (02/25/2014 03:55:06 PM) (Source: LoadPerf) (User: )
Description: 

Error: (02/25/2014 03:53:19 PM) (Source: Google Update) (User: Kristin-PC)
Description: Network Request Error.
Error: 0x80040801. Http status code: 0.
Url=https://www.facebook.com/omaha/update.php
Trying config: source=IE, direct connection.
trying CUP:WinHTTP.
Send request returned 0x80040801. Http status code 0.
trying WinHTTP.
Send request returned 0x80040801. Http status code 0.
trying CUP:iexplore.
Send request returned 0x80040801. Http status code 0.
Trying config: source=auto, wpad=1, script=.
trying CUP:WinHTTP.
Send request returned 0x80040801. Http status code 0.
trying WinHTTP.
Send request returned 0x80040801. Http status code 0.
trying CUP:iexplore.
Send request returned 0x80040801. Http status code 0.
Trying config: source=IE, direct connection.
trying CUP:WinHTTP.
Send request returned 0x80040801. Http status code 0.
trying WinHTTP.
Send request returned 0x80040801. Http status code 0.
trying CUP:iexplore.
Send request returned 0x80040801. Http status code 0.
Trying config: source=auto, wpad=1, script=.
trying CUP:WinHTTP.
Send request returned 0x80040801

Error: (02/25/2014 03:50:16 PM) (Source: WinMgmt) (User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

Error: (02/25/2014 03:50:15 PM) (Source: Microsoft-Windows-CAPI2) (User: )
Description: -583

Error: (02/25/2014 03:50:15 PM) (Source: Microsoft-Windows-CAPI2) (User: )
Description: -583

Error: (02/25/2014 03:40:26 PM) (Source: Windows Search Service) (User: )
Description: 40x8004117fFailed to add project: C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Projects

Error: (02/25/2014 03:40:26 PM) (Source: Windows Search Service) (User: )
Description:
Details:
The content index server cannot update or access information because of a database error. Stop and restart the search service. If the problem persists, reset and recrawl the content index. In some cases it may be necessary to delete and recreate the content index. (0x8004117f)

Error: (02/25/2014 03:39:54 PM) (Source: Windows Search Service) (User: )
Description: 40x8004117fFailed to add project: C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Projects


System errors:
=============
Error: (02/25/2014 03:53:13 PM) (Source: Service Control Manager) (User: )
Description: Windows Search4

Error: (02/25/2014 03:53:13 PM) (Source: Service Control Manager) (User: )
Description: Windows Search2147749155 (0x80040D23)

Error: (02/25/2014 03:52:01 PM) (Source: Service Control Manager) (User: )
Description: Windows Search3

Error: (02/25/2014 03:52:01 PM) (Source: Service Control Manager) (User: )
Description: Windows Search2147749155 (0x80040D23)

Error: (02/25/2014 03:51:28 PM) (Source: Microsoft-Windows-Kernel-General) (User: NT AUTHORITY)
Description: 0x8000002a6SYSTEM

Error: (02/25/2014 03:51:30 PM) (Source: Service Control Manager) (User: )
Description: Windows Search2300001Restart the service

Error: (02/25/2014 03:51:30 PM) (Source: Service Control Manager) (User: )
Description: Windows Search2147749155 (0x80040D23)

Error: (02/25/2014 03:50:56 PM) (Source: Service Control Manager) (User: )
Description: Windows Search1300001Restart the service

Error: (02/25/2014 03:50:56 PM) (Source: Service Control Manager) (User: )
Description: ccSet_NST

Error: (02/25/2014 03:50:56 PM) (Source: Service Control Manager) (User: )
Description: Diagnostic System Host


Microsoft Office Sessions:
=========================

========================= Devices: ================================

Name: isatap.{B85AA5E9-7BE2-4593-939E-734CA1D054AA}
Description: Microsoft ISATAP Adapter
Class Guid: {4d36e972-e325-11ce-bfc1-08002be10318}
Manufacturer: Microsoft
Service: tunnel
Problem: : This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)
Resolution: Update the driver

Name: isatap.{642F4715-C26C-4272-9F8C-7893530A3D30}
Description: Microsoft ISATAP Adapter
Class Guid: {4d36e972-e325-11ce-bfc1-08002be10318}
Manufacturer: Microsoft
Service: tunnel
Problem: : This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)
Resolution: Update the driver

Name: WAN Miniport (L2TP)
Description: WAN Miniport (L2TP)
Class Guid: {4d36e972-e325-11ce-bfc1-08002be10318}
Manufacturer: Microsoft
Service: Rasl2tp
Problem: : This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)
Resolution: Update the driver

Name: WAN Miniport (Network Monitor)
Description: WAN Miniport (Network Monitor)
Class Guid: {4d36e972-e325-11ce-bfc1-08002be10318}
Manufacturer: Microsoft
Service: NdisWan
Problem: : This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)
Resolution: Update the driver

Name: WAN Miniport (IP)
Description: WAN Miniport (IP)
Class Guid: {4d36e972-e325-11ce-bfc1-08002be10318}
Manufacturer: Microsoft
Service: NdisWan
Problem: : This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)
Resolution: Update the driver

Name: WAN Miniport (IPv6)
Description: WAN Miniport (IPv6)
Class Guid: {4d36e972-e325-11ce-bfc1-08002be10318}
Manufacturer: Microsoft
Service: NdisWan
Problem: : This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)
Resolution: Update the driver

Name: WAN Miniport (PPPOE)
Description: WAN Miniport (PPPOE)
Class Guid: {4d36e972-e325-11ce-bfc1-08002be10318}
Manufacturer: Microsoft
Service: RasPppoe
Problem: : This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)
Resolution: Update the driver

Name: WAN Miniport (PPTP)
Description: WAN Miniport (PPTP)
Class Guid: {4d36e972-e325-11ce-bfc1-08002be10318}
Manufacturer: Microsoft
Service: PptpMiniport
Problem: : This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)
Resolution: Update the driver

Name: WAN Miniport (SSTP)
Description: WAN Miniport (SSTP)
Class Guid: {4d36e972-e325-11ce-bfc1-08002be10318}
Manufacturer: Microsoft
Service: RasSstp
Problem: : This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)
Resolution: Update the driver


**** End of log ****
  • 0

#52
SleepyDude

SleepyDude

    Trusted Helper

  • Malware Removal
  • 4,394 posts
Hi Kristin,

Now the network card seems to be correctly installed and with status connected but the Minitoolbox log doesn't show the IP configuration!

  • Open the Command Prompt bly clicking on the Start button Posted Image. In the search box, type cmd, and then press Enter.
  • On the black window type the following, and press Enter:
    ipconfig /all
    
  • please tell me what you get as result of the command.

  • 0

#53
Kristin51505

Kristin51505

    Member

  • Topic Starter
  • Member
  • PipPip
  • 70 posts
Hi SleepyDude,

Well, that sounds like good news at least! Here's what I got from the command prompt; I couldn't figure out how to copy the text so I just took some screenshots of it:

cmd1.JPG

cmd2.JPG

cmd3.JPG
  • 0

#54
SleepyDude

SleepyDude

    Trusted Helper

  • Malware Removal
  • 4,394 posts

Hi SleepyDude,

Well, that sounds like good news at least! Here's what I got from the command prompt; I couldn't figure out how to copy the text so I just took some screenshots of it:

Hi,

Thanks for the screenshots :thumbsup: I was expecting to get some error and not the normal output...

- When you typed the command ipconfig was the computer with the Ethernet cable connected?

I suspect there is a little bug on the MiniToolBox tool, please copy the tool to the Desktop of the problematic computer and run it from there using the same options from post #50 with the cable connected

- Please post the answer to my question and the new MiniToolBox log.
  • 0

#55
Kristin51505

Kristin51505

    Member

  • Topic Starter
  • Member
  • PipPip
  • 70 posts
Hi SleepyDude,

No, I didn't have the Ethernet cable connected; would you like me to connect and run the command again? I copied the MiniToolBox tool to my desktop, here's the log:

MiniToolBox by Farbar Version: 23-01-2014
Ran by Kristin (administrator) on 26-02-2014 at 16:32:00
Running from "C:\Users\Kristin\Desktop"
Microsoft® Windows Vista™ Home Premium Service Pack 2 (X64)
Boot Mode: Normal
***************************************************************************
========================= IP Configuration: ================================

Marvell Yukon 88E8040 PCI-E Fast Ethernet Controller = Local Area Connection 2 (Connected)
Dell Wireless 1397 WLAN Mini-Card = Wireless Network Connection (Media disconnected)
========================= Winsock entries =====================================

Catalog5 01 C:\Windows\SysWOW64\NLAapi.dll [48128] (Microsoft Corporation)
Catalog5 02 C:\Windows\SysWOW64\napinsp.dll [50176] (Microsoft Corporation)
Catalog5 03 C:\Windows\SysWOW64\pnrpnsp.dll [62464] (Microsoft Corporation)
Catalog5 04 C:\Windows\SysWOW64\pnrpnsp.dll [62464] (Microsoft Corporation)
Catalog5 05 C:\Windows\SysWOW64\mswsock.dll [223232] (Microsoft Corporation)
Catalog5 06 C:\Windows\SysWOW64\winrnr.dll [19968] (Microsoft Corporation)
Catalog9 01 C:\Windows\SysWOW64\mswsock.dll [223232] (Microsoft Corporation)
Catalog9 02 C:\Windows\SysWOW64\mswsock.dll [223232] (Microsoft Corporation)
Catalog9 03 C:\Windows\SysWOW64\mswsock.dll [223232] (Microsoft Corporation)
Catalog9 04 C:\Windows\SysWOW64\mswsock.dll [223232] (Microsoft Corporation)
Catalog9 05 C:\Windows\SysWOW64\mswsock.dll [223232] (Microsoft Corporation)
Catalog9 06 C:\Windows\SysWOW64\mswsock.dll [223232] (Microsoft Corporation)
Catalog9 07 C:\Windows\SysWOW64\mswsock.dll [223232] (Microsoft Corporation)
Catalog9 08 C:\Windows\SysWOW64\mswsock.dll [223232] (Microsoft Corporation)
Catalog9 09 C:\Windows\SysWOW64\mswsock.dll [223232] (Microsoft Corporation)
Catalog9 10 C:\Windows\SysWOW64\mswsock.dll [223232] (Microsoft Corporation)
x64-Catalog5 01 C:\Windows\System32\NLAapi.dll [61440] (Microsoft Corporation)
x64-Catalog5 02 C:\Windows\System32\napinsp.dll [62976] (Microsoft Corporation)
x64-Catalog5 03 C:\Windows\System32\pnrpnsp.dll [78848] (Microsoft Corporation)
x64-Catalog5 04 C:\Windows\System32\pnrpnsp.dll [78848] (Microsoft Corporation)
x64-Catalog5 05 C:\Windows\System32\mswsock.dll [304128] (Microsoft Corporation)
x64-Catalog5 06 C:\Windows\System32\winrnr.dll [27648] (Microsoft Corporation)
x64-Catalog5 07 C:\Program Files\Bonjour\mdnsNSP.dll [193024] (Apple Inc.)
x64-Catalog9 01 C:\Windows\System32\mswsock.dll [304128] (Microsoft Corporation)
x64-Catalog9 02 C:\Windows\System32\mswsock.dll [304128] (Microsoft Corporation)
x64-Catalog9 03 C:\Windows\System32\mswsock.dll [304128] (Microsoft Corporation)
x64-Catalog9 04 C:\Windows\System32\mswsock.dll [304128] (Microsoft Corporation)
x64-Catalog9 05 C:\Windows\System32\mswsock.dll [304128] (Microsoft Corporation)
x64-Catalog9 06 C:\Windows\System32\mswsock.dll [304128] (Microsoft Corporation)
x64-Catalog9 07 C:\Windows\System32\mswsock.dll [304128] (Microsoft Corporation)
x64-Catalog9 08 C:\Windows\System32\mswsock.dll [304128] (Microsoft Corporation)
x64-Catalog9 09 C:\Windows\System32\mswsock.dll [304128] (Microsoft Corporation)
x64-Catalog9 10 C:\Windows\System32\mswsock.dll [304128] (Microsoft Corporation)

========================= Event log errors: ===============================

Application errors:
==================
Error: (02/26/2014 04:31:04 PM) (Source: Microsoft-Windows-CAPI2) (User: )
Description: -583

Error: (02/26/2014 04:31:04 PM) (Source: Microsoft-Windows-CAPI2) (User: )
Description: -583

Error: (02/26/2014 02:45:20 PM) (Source: Google Update) (User: Kristin-PC)
Description: Network Request Error.
Error: 0x80040801. Http status code: 0.
Url=https://www.facebook.com/omaha/update.php
Trying config: source=IE, direct connection.
trying CUP:WinHTTP.
Send request returned 0x80040801. Http status code 0.
trying WinHTTP.
Send request returned 0x80040801. Http status code 0.
trying CUP:iexplore.
Send request returned 0x80040801. Http status code 0.
Trying config: source=auto, wpad=1, script=.
trying CUP:WinHTTP.
Send request returned 0x80040801. Http status code 0.
trying WinHTTP.
Send request returned 0x80040801. Http status code 0.
trying CUP:iexplore.
Send request returned 0x80040801. Http status code 0.
Trying config: source=IE, direct connection.
trying CUP:WinHTTP.
Send request returned 0x80040801. Http status code 0.
trying WinHTTP.
Send request returned 0x80040801. Http status code 0.
trying CUP:iexplore.
Send request returned 0x80040801. Http status code 0.
Trying config: source=auto, wpad=1, script=.
trying CUP:WinHTTP.
Send request returned 0x80040801

Error: (02/26/2014 02:45:14 PM) (Source: Windows Search Service) (User: )
Description: 40x8004117fFailed to add project: C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Projects

Error: (02/26/2014 02:45:14 PM) (Source: Windows Search Service) (User: )
Description:
Details:
The content index server cannot update or access information because of a database error. Stop and restart the search service. If the problem persists, reset and recrawl the content index. In some cases it may be necessary to delete and recreate the content index. (0x8004117f)

Error: (02/26/2014 02:45:13 PM) (Source: LoadPerf) (User: )
Description: 

Error: (02/26/2014 02:44:40 PM) (Source: Windows Search Service) (User: )
Description: 40x8004117fFailed to add project: C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Projects

Error: (02/26/2014 02:44:40 PM) (Source: Windows Search Service) (User: )
Description:
Details:
The content index server cannot update or access information because of a database error. Stop and restart the search service. If the problem persists, reset and recrawl the content index. In some cases it may be necessary to delete and recreate the content index. (0x8004117f)

Error: (02/26/2014 02:44:04 PM) (Source: Windows Search Service) (User: )
Description: 40x8004117fFailed to add project: C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Projects

Error: (02/26/2014 02:44:04 PM) (Source: Windows Search Service) (User: )
Description:
Details:
The content index server cannot update or access information because of a database error. Stop and restart the search service. If the problem persists, reset and recrawl the content index. In some cases it may be necessary to delete and recreate the content index. (0x8004117f)


System errors:
=============
Error: (02/26/2014 02:45:14 PM) (Source: Service Control Manager) (User: )
Description: Windows Search7

Error: (02/26/2014 02:45:14 PM) (Source: Service Control Manager) (User: )
Description: Windows Search2147749155 (0x80040D23)

Error: (02/26/2014 02:44:40 PM) (Source: Service Control Manager) (User: )
Description: Windows Search6

Error: (02/26/2014 02:44:40 PM) (Source: Service Control Manager) (User: )
Description: Windows Search2147749155 (0x80040D23)

Error: (02/26/2014 02:44:04 PM) (Source: Service Control Manager) (User: )
Description: Windows Search5

Error: (02/26/2014 02:44:04 PM) (Source: Service Control Manager) (User: )
Description: Windows Search2147749155 (0x80040D23)

Error: (02/26/2014 01:47:32 PM) (Source: Microsoft-Windows-Kernel-General) (User: NT AUTHORITY)
Description: 0x8000002a42\SystemRoot\System32\Config\RegBack\SYSTEM

Error: (02/26/2014 01:42:29 PM) (Source: Service Control Manager) (User: )
Description: Windows Search4

Error: (02/26/2014 01:42:29 PM) (Source: Service Control Manager) (User: )
Description: Windows Search2147749155 (0x80040D23)

Error: (02/26/2014 01:42:26 PM) (Source: Service Control Manager) (User: )
Description: Windows Search3


Microsoft Office Sessions:
=========================

========================= Devices: ================================

Name: isatap.{B85AA5E9-7BE2-4593-939E-734CA1D054AA}
Description: Microsoft ISATAP Adapter
Class Guid: {4d36e972-e325-11ce-bfc1-08002be10318}
Manufacturer: Microsoft
Service: tunnel
Problem: : This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)
Resolution: Update the driver

Name: isatap.{642F4715-C26C-4272-9F8C-7893530A3D30}
Description: Microsoft ISATAP Adapter
Class Guid: {4d36e972-e325-11ce-bfc1-08002be10318}
Manufacturer: Microsoft
Service: tunnel
Problem: : This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)
Resolution: Update the driver

Name: WAN Miniport (L2TP)
Description: WAN Miniport (L2TP)
Class Guid: {4d36e972-e325-11ce-bfc1-08002be10318}
Manufacturer: Microsoft
Service: Rasl2tp
Problem: : This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)
Resolution: Update the driver

Name: WAN Miniport (Network Monitor)
Description: WAN Miniport (Network Monitor)
Class Guid: {4d36e972-e325-11ce-bfc1-08002be10318}
Manufacturer: Microsoft
Service: NdisWan
Problem: : This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)
Resolution: Update the driver

Name: WAN Miniport (IP)
Description: WAN Miniport (IP)
Class Guid: {4d36e972-e325-11ce-bfc1-08002be10318}
Manufacturer: Microsoft
Service: NdisWan
Problem: : This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)
Resolution: Update the driver

Name: WAN Miniport (IPv6)
Description: WAN Miniport (IPv6)
Class Guid: {4d36e972-e325-11ce-bfc1-08002be10318}
Manufacturer: Microsoft
Service: NdisWan
Problem: : This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)
Resolution: Update the driver

Name: WAN Miniport (PPPOE)
Description: WAN Miniport (PPPOE)
Class Guid: {4d36e972-e325-11ce-bfc1-08002be10318}
Manufacturer: Microsoft
Service: RasPppoe
Problem: : This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)
Resolution: Update the driver

Name: WAN Miniport (PPTP)
Description: WAN Miniport (PPTP)
Class Guid: {4d36e972-e325-11ce-bfc1-08002be10318}
Manufacturer: Microsoft
Service: PptpMiniport
Problem: : This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)
Resolution: Update the driver

Name: WAN Miniport (SSTP)
Description: WAN Miniport (SSTP)
Class Guid: {4d36e972-e325-11ce-bfc1-08002be10318}
Manufacturer: Microsoft
Service: RasSstp
Problem: : This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)
Resolution: Update the driver


**** End of log ****
  • 0

Advertisements


#56
SleepyDude

SleepyDude

    Trusted Helper

  • Malware Removal
  • 4,394 posts

Hi SleepyDude,

No, I didn't have the Ethernet cable connected; would you like me to connect and run the command again? I copied the MiniToolBox tool to my desktop, here's the log:

Hi,

Please keep the Ethernet cable connect during the steps because I need to see if we can get it working first only then we will try the Wireless connection because it add more variables to the mix.

I have revised the complete thread and there are fix's that we tried that the tools used failed to show me the result or the commands didn't run!

Let's see if FRST can show me what I need...

FRST Fix

  • Open Notepad (Start =>All Programs => Accessories => Notepad). Please copy the entire contents of the code box below.
    (To do this highlight the contents of the box, right click on it and select copy.)
  • Right-click in the open Notepad and select Paste.
  • Save it on the Desktop as fixlist.txt
    (It's important that both files, FRST or FRST64 and fixlist.txt are in the same location or the fix will not work!)

    cmd: ipconfig /all
    cmd: nslookup google.com
    cmd: ping -n 2 google.com
    cmd: ping -n 2 8.8.8.8
    cmd: sc start RpcSs
    cmd: sc start vss

  • Run FRST/FRST64 and press the Fix button just once and Wait.
  • The tool will make a log (Fixlog.txt) on the same location as FRST/FRST64 please post it in your next reply.

  • 0

#57
Kristin51505

Kristin51505

    Member

  • Topic Starter
  • Member
  • PipPip
  • 70 posts
Hi SleepyDude,

So from now one I should have the Ethernet cable connected whenever I run a fix or a scan? I had it connected when I did the fix today, though I'm not sure if the fix worked or not. Here's the log:

Fix result of Farbar Recovery Tool (FRST written by Farbar) (x64) Version: 01-02-2014 04
Ran by Kristin at 2014-02-27 15:24:22 Run:5
Running from C:\Users\Kristin\Desktop
Boot Mode: Normal
==============================================

Content of fixlist:
*****************
cmd: ipconfig /all
cmd: nslookup google.com
cmd: ping -n 2 google.com
cmd: ping -n 2 8.8.8.8
cmd: sc start RpcSs
cmd: sc start vss
*****************


========= ipconfig /all =========

'ipconfig' is not recognized as an internal or external command,
operable program or batch file.

========= End of CMD: =========


========= nslookup google.com =========

'nslookup' is not recognized as an internal or external command,
operable program or batch file.

========= End of CMD: =========


========= ping -n 2 google.com =========

'ping' is not recognized as an internal or external command,
operable program or batch file.

========= End of CMD: =========


========= ping -n 2 8.8.8.8 =========

'ping' is not recognized as an internal or external command,
operable program or batch file.

========= End of CMD: =========


========= sc start RpcSs =========

'sc' is not recognized as an internal or external command,
operable program or batch file.

========= End of CMD: =========


========= sc start vss =========

'sc' is not recognized as an internal or external command,
operable program or batch file.

========= End of CMD: =========


==== End of Fixlog ====
  • 0

#58
SleepyDude

SleepyDude

    Trusted Helper

  • Malware Removal
  • 4,394 posts

Hi SleepyDude,

So from now one I should have the Ethernet cable connected whenever I run a fix or a scan?

Yes please.

I had it connected when I did the fix today, though I'm not sure if the fix worked or not.

I'm on it. Sorry one of the first fix's we run have a mistake and didn't fix the problem identified before related to the PATH. The PATH definition is missing and this causes the other tools to fail.


Let's apply the correct fix...


Step 1 - OTL Fix

  • Open Notepad (Start =>All Programs => Accessories => Notepad). Please copy the entire contents of the code box below.
    (To do this highlight the contents of the box, right click on it and select copy.)
  • Right-click in the open Notepad and select Paste.
  • Save it on the flash drive as fix.txt then copy the file to the Desktop of the infected computer
  • Make sure you have also OTL on the Desktop of the infected computer
    (It's important that both files, OTL and fix.txt are in the same location or the fix will not work!)

    :Commands
    [CreateRestorePoint]

    :reg
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment]
    "Path"=hex(2):"%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Java\jre7\bin"
    "Path3"=-

    :COMMANDS
    [REBOOT]

  • Right click on the icon Posted Image and choose Run as Administrator to execute the tool. Make sure all other windows are closed.
    Do not change any other settings unless otherwise told to do so.
  • click the Posted Image button at the top.
  • On the prompt "No fix has been provided!" click Ok and select to open the fix.txt file on the Desktop
  • Let the program run uninterrupted.
  • click OK
Notes:
  • The report should appear in Notepad after the reboot. Copy & Paste that report in your next reply and not as attachment.
  • The OTL fix log will be saved in the following location: C:\_OTL\MovedFiles\mmddyyyy_hhmmss.log - where mmddyyy _hhmmss is the date and time when the fix run.


Step 2 - Minitoolbox
  • Close all the programs and run MiniToolBox
    Posted Image
  • Check the following options:
    • List IP Configuration
    • List Winsock Entries
    • List last 10 Event Viewer log
    • List Devices: Only Problems
  • Click on Go.
  • Post the resulting log in your next reply.


Things I would like to see in your next reply:
  • The OTL Fix log
  • The MiniToolBox log Result.txt

  • 0

#59
Kristin51505

Kristin51505

    Member

  • Topic Starter
  • Member
  • PipPip
  • 70 posts
Hi SleepyDude,

I ran the fix and the scan, both the logs are below. But once I rebooted after the OTL fix I did notice that instead of the usual red "X" on the Network icon, there was the yellow "!". It went back to the red X when I disconnected the Ethernet cable, but I thought I'd let you know! Here are the logs:

========== COMMANDS ==========
Restore point Set: OTL Restore Point
Error: Unable to interpret < :reg> in the current context!
Error: Unable to interpret < [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment]> in the current context!
Error: Unable to interpret < "Path"=hex(2):"%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Java\jre7\bin"> in the current context!
Error: Unable to interpret < "Path3"=-> in the current context!
========== COMMANDS ==========

OTL by OldTimer - Version 3.2.69.0 log created on 02272014_210114


MiniToolBox by Farbar Version: 23-01-2014
Ran by Kristin (administrator) on 27-02-2014 at 21:06:48
Running from "C:\Users\Kristin\Desktop"
Microsoft® Windows Vista™ Home Premium Service Pack 2 (X64)
Boot Mode: Normal
***************************************************************************
========================= IP Configuration: ================================

Marvell Yukon 88E8040 PCI-E Fast Ethernet Controller = Local Area Connection 2 (Connected)
Dell Wireless 1397 WLAN Mini-Card = Wireless Network Connection (Media disconnected)
========================= Winsock entries =====================================

Catalog5 01 C:\Windows\SysWOW64\NLAapi.dll [48128] (Microsoft Corporation)
Catalog5 02 C:\Windows\SysWOW64\napinsp.dll [50176] (Microsoft Corporation)
Catalog5 03 C:\Windows\SysWOW64\pnrpnsp.dll [62464] (Microsoft Corporation)
Catalog5 04 C:\Windows\SysWOW64\pnrpnsp.dll [62464] (Microsoft Corporation)
Catalog5 05 C:\Windows\SysWOW64\mswsock.dll [223232] (Microsoft Corporation)
Catalog5 06 C:\Windows\SysWOW64\winrnr.dll [19968] (Microsoft Corporation)
Catalog9 01 C:\Windows\SysWOW64\mswsock.dll [223232] (Microsoft Corporation)
Catalog9 02 C:\Windows\SysWOW64\mswsock.dll [223232] (Microsoft Corporation)
Catalog9 03 C:\Windows\SysWOW64\mswsock.dll [223232] (Microsoft Corporation)
Catalog9 04 C:\Windows\SysWOW64\mswsock.dll [223232] (Microsoft Corporation)
Catalog9 05 C:\Windows\SysWOW64\mswsock.dll [223232] (Microsoft Corporation)
Catalog9 06 C:\Windows\SysWOW64\mswsock.dll [223232] (Microsoft Corporation)
Catalog9 07 C:\Windows\SysWOW64\mswsock.dll [223232] (Microsoft Corporation)
Catalog9 08 C:\Windows\SysWOW64\mswsock.dll [223232] (Microsoft Corporation)
Catalog9 09 C:\Windows\SysWOW64\mswsock.dll [223232] (Microsoft Corporation)
Catalog9 10 C:\Windows\SysWOW64\mswsock.dll [223232] (Microsoft Corporation)
x64-Catalog5 01 C:\Windows\System32\NLAapi.dll [61440] (Microsoft Corporation)
x64-Catalog5 02 C:\Windows\System32\napinsp.dll [62976] (Microsoft Corporation)
x64-Catalog5 03 C:\Windows\System32\pnrpnsp.dll [78848] (Microsoft Corporation)
x64-Catalog5 04 C:\Windows\System32\pnrpnsp.dll [78848] (Microsoft Corporation)
x64-Catalog5 05 C:\Windows\System32\mswsock.dll [304128] (Microsoft Corporation)
x64-Catalog5 06 C:\Windows\System32\winrnr.dll [27648] (Microsoft Corporation)
x64-Catalog5 07 C:\Program Files\Bonjour\mdnsNSP.dll [193024] (Apple Inc.)
x64-Catalog9 01 C:\Windows\System32\mswsock.dll [304128] (Microsoft Corporation)
x64-Catalog9 02 C:\Windows\System32\mswsock.dll [304128] (Microsoft Corporation)
x64-Catalog9 03 C:\Windows\System32\mswsock.dll [304128] (Microsoft Corporation)
x64-Catalog9 04 C:\Windows\System32\mswsock.dll [304128] (Microsoft Corporation)
x64-Catalog9 05 C:\Windows\System32\mswsock.dll [304128] (Microsoft Corporation)
x64-Catalog9 06 C:\Windows\System32\mswsock.dll [304128] (Microsoft Corporation)
x64-Catalog9 07 C:\Windows\System32\mswsock.dll [304128] (Microsoft Corporation)
x64-Catalog9 08 C:\Windows\System32\mswsock.dll [304128] (Microsoft Corporation)
x64-Catalog9 09 C:\Windows\System32\mswsock.dll [304128] (Microsoft Corporation)
x64-Catalog9 10 C:\Windows\System32\mswsock.dll [304128] (Microsoft Corporation)

========================= Event log errors: ===============================

Application errors:
==================
Error: (02/27/2014 09:06:42 PM) (Source: Windows Search Service) (User: )
Description: 40x8004117fFailed to add project: C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Projects

Error: (02/27/2014 09:06:42 PM) (Source: Windows Search Service) (User: )
Description:
Details:
The content index server cannot update or access information because of a database error. Stop and restart the search service. If the problem persists, reset and recrawl the content index. In some cases it may be necessary to delete and recreate the content index. (0x8004117f)

Error: (02/27/2014 09:06:36 PM) (Source: Microsoft-Windows-CAPI2) (User: )
Description: -583

Error: (02/27/2014 09:06:36 PM) (Source: Microsoft-Windows-CAPI2) (User: )
Description: -583

Error: (02/27/2014 09:06:36 PM) (Source: Windows Search Service) (User: )
Description: 40x8004117fFailed to add project: C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Projects

Error: (02/27/2014 09:06:36 PM) (Source: Windows Search Service) (User: )
Description:
Details:
The content index server cannot update or access information because of a database error. Stop and restart the search service. If the problem persists, reset and recrawl the content index. In some cases it may be necessary to delete and recreate the content index. (0x8004117f)

Error: (02/27/2014 09:04:44 PM) (Source: Windows Search Service) (User: )
Description: 40x8004117fFailed to add project: C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Projects

Error: (02/27/2014 09:04:44 PM) (Source: Windows Search Service) (User: )
Description:
Details:
The content index server cannot update or access information because of a database error. Stop and restart the search service. If the problem persists, reset and recrawl the content index. In some cases it may be necessary to delete and recreate the content index. (0x8004117f)
˙

Error: (02/27/2014 09:04:42 PM) (Source: WinMgmt) (User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003

Error: (02/27/2014 09:04:37 PM) (Source: Microsoft-Windows-CAPI2) (User: )
Description: -583


System errors:
=============
Error: (02/27/2014 09:06:42 PM) (Source: Service Control Manager) (User: )
Description: Windows Search3

Error: (02/27/2014 09:06:42 PM) (Source: Service Control Manager) (User: )
Description: Windows Search2147749155 (0x80040D23)

Error: (02/27/2014 09:06:40 PM) (Source: Microsoft-Windows-Kernel-General) (User: NT AUTHORITY)
Description: 0x8000002a6SYSTEM

Error: (02/27/2014 09:06:36 PM) (Source: Service Control Manager) (User: )
Description: Windows Search2300001Restart the service

Error: (02/27/2014 09:06:36 PM) (Source: Service Control Manager) (User: )
Description: Windows Search2147749155 (0x80040D23)

Error: (02/27/2014 09:06:28 PM) (Source: Print) (User: NT AUTHORITY)
Description: Printer Dell AIO Printer A940 failed to initialize because a suitable Dell AIO Printer A940 driver could not be found. The new printer settings that you specified have not taken effect. Install or reinstall the printer driver. You might need to contact the vendor for an updated driver.

Error: (02/27/2014 09:06:28 PM) (Source: Print) (User: NT AUTHORITY)
Description: Windows could not initialize printer Dell AIO Printer A940 because the print processor Dell AIO Printer A940 Print Processor could not be found. Please obtain and install a new version of the driver from the manufacturer (if available), or choose an alternate driver that works with this print device.

Error: (02/27/2014 09:06:10 PM) (Source: Service Control Manager) (User: )
Description: Windows Search1300001Restart the service

Error: (02/27/2014 09:06:09 PM) (Source: Service Control Manager) (User: )
Description: ccSet_NST

Error: (02/27/2014 09:06:09 PM) (Source: Service Control Manager) (User: )
Description: Diagnostic Service Host


Microsoft Office Sessions:
=========================

========================= Devices: ================================

Name: isatap.{B85AA5E9-7BE2-4593-939E-734CA1D054AA}
Description: Microsoft ISATAP Adapter
Class Guid: {4d36e972-e325-11ce-bfc1-08002be10318}
Manufacturer: Microsoft
Service: tunnel
Problem: : This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)
Resolution: Update the driver

Name: isatap.{642F4715-C26C-4272-9F8C-7893530A3D30}
Description: Microsoft ISATAP Adapter
Class Guid: {4d36e972-e325-11ce-bfc1-08002be10318}
Manufacturer: Microsoft
Service: tunnel
Problem: : This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)
Resolution: Update the driver

Name: WAN Miniport (L2TP)
Description: WAN Miniport (L2TP)
Class Guid: {4d36e972-e325-11ce-bfc1-08002be10318}
Manufacturer: Microsoft
Service: Rasl2tp
Problem: : This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)
Resolution: Update the driver

Name: WAN Miniport (Network Monitor)
Description: WAN Miniport (Network Monitor)
Class Guid: {4d36e972-e325-11ce-bfc1-08002be10318}
Manufacturer: Microsoft
Service: NdisWan
Problem: : This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)
Resolution: Update the driver

Name: WAN Miniport (IP)
Description: WAN Miniport (IP)
Class Guid: {4d36e972-e325-11ce-bfc1-08002be10318}
Manufacturer: Microsoft
Service: NdisWan
Problem: : This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)
Resolution: Update the driver

Name: WAN Miniport (IPv6)
Description: WAN Miniport (IPv6)
Class Guid: {4d36e972-e325-11ce-bfc1-08002be10318}
Manufacturer: Microsoft
Service: NdisWan
Problem: : This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)
Resolution: Update the driver

Name: WAN Miniport (PPPOE)
Description: WAN Miniport (PPPOE)
Class Guid: {4d36e972-e325-11ce-bfc1-08002be10318}
Manufacturer: Microsoft
Service: RasPppoe
Problem: : This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)
Resolution: Update the driver

Name: WAN Miniport (PPTP)
Description: WAN Miniport (PPTP)
Class Guid: {4d36e972-e325-11ce-bfc1-08002be10318}
Manufacturer: Microsoft
Service: PptpMiniport
Problem: : This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)
Resolution: Update the driver

Name: WAN Miniport (SSTP)
Description: WAN Miniport (SSTP)
Class Guid: {4d36e972-e325-11ce-bfc1-08002be10318}
Manufacturer: Microsoft
Service: RasSstp
Problem: : This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)
Resolution: Update the driver


**** End of log ****
  • 0

#60
SleepyDude

SleepyDude

    Trusted Helper

  • Malware Removal
  • 4,394 posts
Hi,

The copy & past did add something that made the fix to fail!

  • Download the attached file fix.txt and save it on the same location as OTL
  • Right click on the icon Posted Image and choose Run as Administrator to execute the tool. Make sure all other windows are closed.
  • click the Posted Image button at the top.
  • Let the program run uninterrupted.
  • click OK
Notes:
  • The report should appear in Notepad after the reboot. Copy & Paste that report in your next reply and not as attachment.
  • The OTL fix log will be saved in the following location: C:\_OTL\MovedFiles\mmddyyyy_hhmmss.log - where mmddyyy _hhmmss is the date and time when the fix run.

Attached File  fix.txt   318bytes   46 downloads
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP