Thanks for the NSLOOKUP info. I'm not finding much info about what to do if Pings work (which seems to require DNS) and NSLOOKUP fails (which is a query to DNS). I just wanted to confirm that what one of the tools VistaKing had you use was doing.
I don't recall ever seeing a DLL name show up in a tab like you show. I doubt it will help, but you can try the various things offered by this tool: SF IE Restorator - Troubleshooting General Issues with IE
Hello everyone, beautiful summer's day here in Vancouver.
I've had a great morning, undisturbed by the fact that SF IE Restorator did nothing. I tried several of the options, including restoring 64 bit IE to 64 bit Windows 7.
Seems this problem eludes us still...
Lets rerun FRST64.exe
Run Farbar Recovery Scan Tool
64-Bit Version OS Farbar Recovery Scan Tool x64 <===== Download Link
Drag the FRST64.exe from the Downloads folder to your Desktop
Right click on FRST64.exe and choose
When the tool opens click Yes on the disclaimer window .
Press Scan button.
FRST will let you know when the scan is complete and has written the FRST.txt to file
NoteThe first time Farbar Recovery Scan Tool is run, it makes also another log Addition.txt
Please upload both logs in your reply.(FRST.txt and Addition.txt)
FRST.txt and Addition.txt will be on the Desktop
Upload a File
Click on the Go Advanced button under the Message box . Scroll down to Additional Options then click on Manage Attachments in the Attach Files sections . Click the Browse button locate the file then click on the Open button . In the Upload File from your Computer section click on the Upload button . Wait until it finishes uploading then close the window . Then click Submit Reply .
I've done that once. I will try again in the morning. Good night! ~~
Open notepad. Inside notepad paste the highlighted text below
start
c:\78865d93cc7781d304\epplauncher.exe
c:\78865d93cc7781d304\amd64\Setup.exe
HKU\UpdatusUser\...\Run: [Power2GoExpress] - NA [x]
SearchScopes: HKCU - {6A1806CD-94D4-4689-BA73-E35EA1EA9990} URL =
BHO: No Name - {B164E929-A1B6-4A06-B104-2CD0E90A88FF} - No File
BHO-x32: No Name - {B164E929-A1B6-4A06-B104-2CD0E90A88FF} - No File
Handler: dssrequest - {5513F07E-936B-4E52-9B00-067394E91CC5} - No File
Handler: sacore - {5513F07E-936B-4E52-9B00-067394E91CC5} - No File
Handler-x32: dssrequest - {5513F07E-936B-4E52-9B00-067394E91CC5} - No File
Handler-x32: sacore - {5513F07E-936B-4E52-9B00-067394E91CC5} - No File
FF NetworkProxy: "share_proxy_settings", true
FF Extension: No Name - C:\Users\Vineet\AppData\Roaming\Mozilla\Firefox\Profiles\bypqlbbq.default\Extensions\extension21804@ extension21804.com
FF Extension: No Name - C:\Users\Vineet\AppData\Roaming\Mozilla\Firefox\Profiles\bypqlbbq.default\Extensions\{d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}.xpi
S3 DrWebEngine; "C:\Program Files\Common Files\Doctor Web\Scanning Engine\dwengine.exe" [x]
C:\Windows\Tasks\SA.DAT
C:\Windows\system32\Drivers\70336732.sys
end
Click on File select Save As
Location: Desktop
File Name: Fixlist.txt
Save as type: All files
Click on Save button
Launch FRST64.exe again click on the [FIX] button . Once its complete it will create a new log called Fixlog.txt upload the log with your reply .
Quote