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

Desktop Internet Shortcuts Stopped Working


  • Please log in to reply

#16
RKinner

RKinner

    Malware Expert

  • Expert
  • 20,012 posts
  • MVP

Let's see if Windows Repair All-in-one can fix the problem at least with the ESET files:

 

Windows Repair all in one
 
 
Download it and save it then run it.
 
You can skip to step 4 or 5 where it gives you the same picture as in the above link.
 
Make sure all of these are checked before hitting Start:
 
Reset Registry Permissions
Reset File Permissions
Register System Files
Repair WMI
Repair Windows Firewall
Repair Internet Explorer
Repair MDAC & MS Jet
Repair Hosts File
Remove Policies Set By Infections
Repair Icons
Repair Winsock & DNS Cache
Remove Temp Files
Repair Proxy Settings
Unhide Non System Files
Repair Windows Updates
Repair CD/DVD Missing/Not Working
 
Reboot when done and run VEW again as before.

  • 0

Advertisements


#17
Jackpine

Jackpine

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 347 posts

Hi RKinner, I'll try the Windows repair tomorrow morning.  By the way, I haven't yet tried the ESET removal tool.  The instructions say I need to run it while in Safe Mode.  Should I try it before the Windows repair? 

 

Also, how do I get into Safe Mode?

 

Thanks.


  • 0

#18
RKinner

RKinner

    Malware Expert

  • Expert
  • 20,012 posts
  • MVP
 
Reboot and when you see the maker's logo, hear a beep or it talks about F8, start tapping the F8 key slowly.  Keep tapping until the Safe Mode Menu appears and choose Safe Mode
 
Try your ESET removal tool.  IF it doesn't work then try All-in-one and then try the tool again.

  • 0

#19
Jackpine

Jackpine

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 347 posts

I can't get into Safe mode.  When I tap F8, eventually a small screen appears that lists boot order.  It's not quite the same as the boot order screen that shows up when I tap Del to get into BIOS setup, but similar.

 

Also, in post #16, what do you mean by "run VEW again as before?"  What is VEW?


Edited by Jackpine, 27 January 2017 - 09:58 AM.

  • 0

#20
RKinner

RKinner

    Malware Expert

  • Expert
  • 20,012 posts
  • MVP

OK.  Alternative method:

 

Go in to 

 

msconfig

 

 

See: http://www.netsquirr...sconfig_xp.html

on how to do that if you don't know.

 

Under Boot tab, click on 

 

Safe Boot.

Minimal

 

OK

 

Reboot.

 

After you get in to safe mode you will need to go back in to msconfig and uncheck Safe Boot and OK.


  • 0

#21
Jackpine

Jackpine

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 347 posts

OK, I'm in safe mode now and will run the ESET removal tool.

 

Update: ESET fully uninstalled!  Returned to normal boot configuration.

 

I have not run the Windows Repair Tool, or checked any web desktop shortcuts.  Prefer to hear from you on next steps first.


Edited by Jackpine, 27 January 2017 - 10:35 AM.

  • 0

#22
RKinner

RKinner

    Malware Expert

  • Expert
  • 20,012 posts
  • MVP

Run minitoolbox again.  We just want the List last 10 Event Viewer Errors  so you can uncheck all of the other options if you want.

 

That should show us if the errors have stopped.


  • 0

#23
Jackpine

Jackpine

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 347 posts

Here's the minitoolbox log:

 

MiniToolBox by Farbar  Version: 17-06-2016
Ran by Robert (administrator) on 27-01-2017 at 14:55:07
Running from "C:\Documents and Settings\Robert\Desktop"
Microsoft Windows XP Home Edition Service Pack 3 (X86)
Model: System Product Name Manufacturer: System manufacturer
Boot Mode: Normal
***************************************************************************

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

Application errors:
==================
Error: (01/27/2017 11:16:50 AM) (Source: Application Error) (User: )
Description: Faulting application tweakingregistrybackup.exe, version 3.5.0.3, faulting module gdi32.dll, version 5.1.2600.6460, fault address 0x0000ef4b.
Processing media-specific event for [tweakingregistrybackup.exe!ws!]

Error: (01/26/2017 08:13:46 AM) (Source: MsiInstaller) (User: )
Description: Product: ESET NOD32 Antivirus -- Error 1404. Could not delete key \Software\ESET\ESET Security.  System error .  Verify that you have sufficient access to that key, or contact your support personnel.

Error: (01/26/2017 08:10:44 AM) (Source: MsiInstaller) (User: )
Description: Product: ESET NOD32 Antivirus -- Error 1321. The Installer has insufficient privileges to modify this file: C:\Program Files\ESET\ESET NOD32 Antivirus\callmsi.exe.

Error: (01/26/2017 08:10:03 AM) (Source: MsiInstaller) (User: )
Description: Product: ESET NOD32 Antivirus -- Error 1404. Could not delete key \Software\ESET\ESET Security.  System error .  Verify that you have sufficient access to that key, or contact your support personnel.

Error: (01/24/2017 05:43:02 PM) (Source: MsiInstaller) (User: FIRSTBUILD)
Description: Product: ESET NOD32 Antivirus -- Error 1404. Could not delete key \Software\ESET\ESET Security.  System error .  Verify that you have sufficient access to that key, or contact your support personnel.

Error: (01/24/2017 02:03:45 PM) (Source: MsiInstaller) (User: FIRSTBUILD)
Description: Product: ESET NOD32 Antivirus -- Error 1321. The Installer has insufficient privileges to modify this file: C:\Program Files\ESET\ESET NOD32 Antivirus\callmsi.exe.

Error: (01/24/2017 02:03:44 PM) (Source: MsiInstaller) (User: FIRSTBUILD)
Description: Product: ESET NOD32 Antivirus -- Error 1321. The Installer has insufficient privileges to modify this file: C:\Program Files\ESET\ESET NOD32 Antivirus\callmsi.exe.

Error: (01/24/2017 08:41:42 AM) (Source: MsiInstaller) (User: FIRSTBUILD)
Description: Product: ESET NOD32 Antivirus -- Error 1304. Error writing to file: C:\Program Files\ESET\ESET NOD32 Antivirus\eamsi.dll.  Verify that you have access to that directory.

Error: (01/24/2017 08:41:42 AM) (Source: MsiInstaller) (User: FIRSTBUILD)
Description: Product: ESET NOD32 Antivirus -- Error 1304. Error writing to file: C:\Program Files\ESET\ESET NOD32 Antivirus\eamsi.dll.  Verify that you have access to that directory.

Error: (01/24/2017 08:41:36 AM) (Source: MsiInstaller) (User: FIRSTBUILD)
Description: Product: ESET NOD32 Antivirus -- Error 1321. The Installer has insufficient privileges to modify this file: C:\Program Files\ESET\ESET NOD32 Antivirus\Drivers\eamonm\eamonm.sys.


System errors:
=============
Error: (01/27/2017 11:29:30 AM) (Source: 0) (User: )
Description:

Error: (01/27/2017 11:28:00 AM) (Source: DCOM) (User: NT AUTHORITY)
Description: DCOM got error "%%1084 = This service cannot be started in Safe Mode
" attempting to start the service EventSystem with arguments ""
in order to run the server:
{1BE1F766-5536-11D1-B726-00C04FB926AF}

Error: (01/27/2017 11:27:37 AM) (Source: DCOM) (User: FIRSTBUILD)
Description: DCOM got error "%%1084 = This service cannot be started in Safe Mode
" attempting to start the service netman with arguments ""
in order to run the server:
{BA126AE5-2166-11D1-B1D0-00805FC1270E}

Error: (01/27/2017 11:26:04 AM) (Source: PlugPlayManager) (User: )
Description: The device Root\LEGACY_EPFWTDIR\0000 disappeared from the system without first being prepared for removal.

Error: (01/27/2017 11:22:57 AM) (Source: Service Control Manager) (User: )
Description: The following boot-start or system-start driver(s) failed to load:
AFD
AsIO
eamonm
ehdrv
ElbyCDIO
epfwtdir
Fips
HWiNFO32
intelppm
IPSec
MRxSmb
NetBIOS
NetBT
RasAcd
Rdbss
Tcpip
WS2IFSL

Error: (01/27/2017 11:22:57 AM) (Source: Service Control Manager) (User: )
Description: The IPSEC Services service depends on the IPSEC driver service which failed to start because of the following error:
%%31 = A device attached to the system is not functioning.


Error: (01/27/2017 11:22:57 AM) (Source: Service Control Manager) (User: )
Description: The TCP/IP NetBIOS Helper service depends on the AFD service which failed to start because of the following error:
%%31 = A device attached to the system is not functioning.


Error: (01/27/2017 11:22:57 AM) (Source: Service Control Manager) (User: )
Description: The DNS Client service depends on the TCP/IP Protocol Driver service which failed to start because of the following error:
%%31 = A device attached to the system is not functioning.


Error: (01/27/2017 11:22:57 AM) (Source: Service Control Manager) (User: )
Description: The DHCP Client service depends on the NetBios over Tcpip service which failed to start because of the following error:
%%31 = A device attached to the system is not functioning.


Error: (01/27/2017 11:22:40 AM) (Source: DCOM) (User: FIRSTBUILD)
Description: DCOM got error "%%1084 = This service cannot be started in Safe Mode
" attempting to start the service netman with arguments ""
in order to run the server:
{BA126AE5-2166-11D1-B1D0-00805FC1270E}


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

**** End of log ****
 


  • 0

#24
RKinner

RKinner

    Malware Expert

  • Expert
  • 20,012 posts
  • MVP

I think you got rid of ESET.  No new events from them.  Run Windows Repair All in One when you get a chance.  I'll be away from the PC the rest of the night.


  • 0

#25
Jackpine

Jackpine

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 347 posts

OK, thanks. I'm going grocery shopping now and will run it later tonight. Have a good evening.


  • 0

Advertisements


#26
RKinner

RKinner

    Malware Expert

  • Expert
  • 20,012 posts
  • MVP

OK


  • 0

#27
Jackpine

Jackpine

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 347 posts

I'm running the Windows Repair tool in Safe Mode.

 

It's taking a while, but it is progressing. 

 

To clarify: I only checked the items to be repaired that you identified in post #16.  I unchecked everything else that was already checked when the tool started up.  This is correct, right?

 

After the repair is done, I will reboot and run it a second time. Then what?


  • 0

#28
RKinner

RKinner

    Malware Expert

  • Expert
  • 20,012 posts
  • MVP

That's correct.

 

Once it's done, clear the alarms and reboot:

 

Start, Run, eventvwr.msc, OK to bring up the Event Viewer.  Right click on System and Clear All Events, No (we don't want to save the old log), OK. Repeat for Application. 
 
Reboot. 
 
Then run VEW again and post both system and application logs.

  • 0

#29
Jackpine

Jackpine

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 347 posts

I'm running the Windows repair tool now for the second time.

 

Note: the tool doesn't have the following item from your post #16:  Repair Winsock & DNS Cache.

 

What is VEW?  I'm not clear what I'm supposed to run.


  • 0

#30
RKinner

RKinner

    Malware Expert

  • Expert
  • 20,012 posts
  • MVP
Must be a newer version of the tool.
 
VEW=
1. Please download the Event Viewer Tool by Vino Rosso
and save it to your Desktop:
2. Double-click VEW.exe
3. Under 'Select log to query', select:
 
* System
4. Under 'Select type to list', select:
* Error
* Warning
 
 
Then use the 'Number of events' as follows:
 
 
1. Click the radio button for 'Number of events'
Type 20 in the 1 to 20 box
Then click the Run button.
Notepad will open with the output log.
 
 
Please post the Output log in your next reply then repeat but select Application. (Each time you run VEW it overwrites the log so copy the first one to a Reply or rename it before running it a second time.)
 
Sorry, thought I had already told you about it.

  • 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